Create a Configuration Compliance criticality map

  • Release version: Australia
  • Updated March 12, 2026
  • 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 All > Configuration Compliance > Administration > Criticality Mapping.
    2. Click New.
    3. Fill in the fields on the form, as appropriate.
      Table 1. Field mapping
      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.
    4. Click Submit.