Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Configuration Compliance criticality maps

Configuration Compliance criticality maps

Configuration Compliance criticality mapping transforms criticality fields from the source to fields in Configuration Compliance.

The Configuration Compliance base system ships with a standard Qualys Cloud Platform to standard ServiceNow mapping. Creating or editing a criticality map is intended only for customized or non-standard third-party mappings in your environment.

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 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.