--- title: Create a Configuration Compliance criticality map description: Configuration Compliance criticality mapping provides a transform map for third-party source criticality fields to recognizable fields in Configuration Compliance severity. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/security-management/configuration-compliance/create-criticality-map.html release: australia product: Configuration Compliance classification: configuration-compliance topic_type: task last_updated: "2026-03-12" reading_time_minutes: 1 breadcrumb: [Configure, Configuration Compliance, Unified Security Exposure Management, Security Operations] --- # 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 1. Navigate to **All** > **Configuration Compliance** > **Administration** > **Criticality Mapping**. 2. Click **New**. 3. 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. - **High** The configuration issue associated with the control is a threat, but is not causing a shutdown of critical network resources. - **Moderate** The configuration issue associated with the control is a risk, but is not an immediate threat. - **Low** 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. - **Minor** The configuration issue associated with the control is a minor risk and can be ignored if necessary. |