---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Create a Configuration Compliance criticality map

# Create a Configuration Compliance criticality map {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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 AllConfiguration ComplianceAdministrationCriticality Mapping.
2. Click New.
3. Fill in the fields on the form, as appropriate.  
   {#create-criticality-map__table_vks_thr_ns__entry__2}

   | 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. |
   [Table 1. Field mapping]

   {#create-criticality-map__table_vks_thr_ns}
4. Click Submit.
{#create-criticality-map__steps_sm4_ssg_lw}

*[\>]: and then