Severity mapping for Unified Security Exposure Management

concept brazil Updated Sep 10, 2026 1 min read sem-severity-mapping.md
Raw file servicenow.com

Severity mapping standardizes and normalizes the severity levels of findings detected across different sources. This process involves mapping the severity levels from various scanners and sources to a common severity scale used within Unified Security Exposure Management.

Severity mapping

Note: Business rules run in the background to evaluate the priority for Qualys data and perform the corresponding mapping to the Priority field. Therefore, the business rule is responsible for handling the mapping of Qualys data.

Field

Description

Normalised_Severity

Calculates the severity values received from the scanner.

Source_severity

  • Data from the severity_score table is mapped to the source_severity table during the execution of the Rapid7 Vulnerability Integration- API.
  • Data from the SEVERITY_LEVEL is mapped to the source_severity table during the execution of the Qualys Knowledge Base Integration.
  • Data for risk_factor table is mapped to source_severity during the execution of the Tenable.io Plugin Integration.
  • Data for riskFactor table is mapped to source_severity during the execution of the Tenable.io Plugin Integration.
  • Data from severity table is mapped to source_severity during the execution of the Microsoft TVM Vulnerability(CVE) Integration.
**Parent Topic:**[Automating prioritization and triaging](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/sem-automating-prioritization-triaging.md)

Related topics

Configure a severity map in the Security Exposure Management Workspace

Keywords Severity mapping
Search documentation
Search document titles and file paths on the brazil branch