Severity mapping for Vulnerability Response

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 2 minutes de lecture

    • Vulnerability Response ships with National Vulnerability Database (NVD) to normalized ServiceNow severity mapping. ServiceNow third-party integrations provide severity mappings upon installation. These maps can be adjusted by changing the fields in existing maps.

    Rapid7 Vulnerability Integration Severity Mapping

    Normalised_Severity

    Calculate normalised_severity on third-part entry using the severity coming from sn_vul_nvd_entry table. This is set using Business Rules for Lookup normalized severity on sn_vul_entry table.

    Source_severity

    Data from the severity_score table is mapped to source_severity table while the Rapid7 Vulnerability Integration- API is running.

    Priority

    This field is empty.

    Qualys Vulnerability Integration Severity Mapping

    Normalised_Severity

    Calculate normalised_severity on third-part entry using the severity coming from sn_vul_nvd_entry table. This is set using Business Rules for Lookup normalized severity on sn_vul_entry table.

    Source_severity

    Data from the SEVERITY_LEVEL is mapped to the source_severity table while the Qualys Knowledge Base Integration is running.

    Priority

    Data for the Priority field is obtained from SEVERITY table and mapped to priority table while Qualys Host Detection Integration is running using the Business Rule mapped to Qualys Data.

    Remarque :
    Business Rules run in the background and checks the priority for Qualys and accordingly maps the Priority. So, to map Qualys data, BR is responsible.

    Tenable.io Vulnerability Integration Severity Mapping

    Normalised_Severity

    Calculate normalised_severity on third-part entry using the severity coming from sn_vul_nvd_entry table. This is set using Business Rules for Lookup normalized severity on sn_vul_entry table.

    Source_severity

    Data from risk_factor table is mapped to source_severity table while the Tenable.io Plugin Integration is running.

    Priority

    Data from severity_id is mapped to source_severity while the Tenable.io Open Vulnerabilities Integration is running.

    VPR

    Data from score is mapped to Source_risk_score while Tenable.io Plugin Integration is running.

    Data from Calculated from score is mapped to Source_risk_rating while Tenable.io Plugin Integration is running.

    Tenable.sc Vulnerability Integration Severity Mapping

    Normalised_Severity

    Calculate normalised_severity on third-part entry using the severity coming from sn_vul_nvd_entry table. This is set using Business Rules for Lookup normalized severity on sn_vul_entry table.

    Source_severity

    Data for riskFactor table is mapped to source_severity while the Tenable.io Plugin Integration is running.

    Priority

    Data from severity received as "severity": { "id": "0", "name": "Info", "description": "Informative" } is mapped to source_severity while the Tenable.io Open Vulnerabilities Integration is running.

    VPR

    Data from vprScore is mapped to Source_risk_score while Tenable.io Plugin Integration is running.

    Data from Calculated from vprScore is mapped to Source_risk_rating while Tenable.io Plugin Integration is running.

    TVM Severity Mapping

    Normalised_Severity

    Calculate normalised_severity on third-part entry using the severuty coming from sn_vul_nvd_entry table. This is set using Business Rules for Lookup normalized severity on sn_vul_entry table.

    Source_severity

    Data from severity table is mapped to source_severity while Microsoft TVM Vulnerability(CVE) Integration is running.

    Priority

    This field is empty.