Create a Configuration Compliance criticality map
Configuration Compliance criticality mapping provides a transform map for third-party source criticality fields to recognizable fields in Configuration Compliance severity.
Before you begin
Role required: sn_vulc.admin
Procedure
Navigate to All > Configuration Compliance > Administration > Criticality Mapping.
Click New.
Fill in the fields on the form, as appropriate.
| Field | Description |
|---|---|
| Source | The name of the source for the criticality mapping. |
| Source value | The source criticality value. |
| Target value | The target value. Choices are: - Critical The configuration issue associated with the control is causing a disruption to one or more business-critical CIs.
The configuration issue associated with the control is a threat, but is not causing a shutdown of critical network resources.
The configuration issue associated with the control is a risk, but is not an immediate threat.
The configuration issue associated with the control is a low-level threat and can be ignored in favor of CIs that are at greater risk.
The configuration issue associated with the control is a minor risk and can be ignored if necessary. |
- Click Submit.