Create a Configuration Compliance criticality map

  • Freigeben Version: Australia
  • Aktualisiert 12. März 2026
  • 1 Minute Lesedauer

    • Configuration Compliance criticality mapping provides a transform map for third-party source criticality fields to recognizable fields in Configuration Compliance severity.

    Vorbereitungen

    Role required: sn_vulc.admin

    Prozedur

    1. Navigate to All > Configuration Compliance > Administration > Criticality Mapping.
    2. Click New.
    3. Fill in the fields on the form, as appropriate.
      Tabelle : 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.