{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":46152,"path":"security-management/vulnerability-response/vr-avr-sbom-csdm-guidelines.md","title":"Vulnerability Response applications and CSDM tables","bundle":null,"doc_type":null,"release":"australia","body":"\n# Vulnerability Response applications and CSDM tables\n\nThe Vulnerability Response, Application Vulnerability Response, third-party vulnerability integrations and Software Bill of Materials applications manage \\(contribute data to\\) CSDM tables. These applications also use data from CSDM tables that other applications generate. Several ServiceNow products, therefore, benefit from and add value to these Security Operations applications.\n\n\\[Omitted image \"CSDM-VR.png\"\\] Alt text: Tables highlighted that are referenced and used by the Vulnerability Response applications\n\n## CSDM tables referenced by Vulnerability Response, Application Vulnerability Response, third-party vulnerability integrations and Software Bill of Materials applications\n\nAs assets are imported from third-party vulnerability scanners \\(integrations\\), they are brought into Vulnerability Response and represented in specific tables:\n\n-   Host Vulnerability Response Discovered Items.\n-   Cloud and Container Vulnerability Response discovered images\n-   Application Vulnerability Response Discovered Applications \\(product model\\)\n\nAs part of the Security Operations CMDB configuration item \\(CI\\) look up, a search is performed to match a \\(CI\\) record from imported data with existing records in the CMDB.\n\nEach specific CI Record may contain non-discoverable attributes, for example, Support Group, or Classification, that are populated on the CI that can be used as input for vulnerable item assignment Rules. These attributes might be populated from Common Service Data Model \\(CSDM\\) synchronizations based on upstream Technical Service Offerings.\n\nIf you want to leverage related CSDM objects for Vulnerability Response, Application Vulnerability Response, third-party vulnerability integrations and Software Bill of Materials applications, you need to use scripted rules.\n\nFor example, to automatically assign vulnerable items for remediation using vulnerable item assignment rules, you might create a rule that leverages configuration item Classification values as they are updated on imported vulnerability entries. For this case, you need a scripted rule to query the target value you want from the related CSDM object.\n\nBelow is an example of a scripted query that you might use to see if a CI has Java and is tied to a vulnerability entry.\n\n\\[Omitted image \"CSDM-VR-script-example.png\"\\] Alt text: Scripting example that shows\n\nVulnerability Response, Application Vulnerability Response, third-party vulnerability integrations and Software Bill of Materials applications reference the following tables. Refer to the CSDM data framework and Vulnerability Response applications image for more information.\n\n-   The Product Model \\[cmdb\\_model\\] table \\(referenced by Application Vulnerability Response and Software Bill of Materials\\).\n-   The Application Model \\[cmdb\\_application\\_product\\_model\\] table \\(referenced by Application Vulnerability Response and Software Bill of Materials\\).\n-   The Configuration Item \\[cmdb\\_ci\\] table.\n-   The Business Service \\[cmdb\\_ci\\_service\\_business\\] table.\n-   The Service \\[cmdb\\_ci\\_service\\] table.\n-   CMDB Group \\[cmdb\\_group\\] table.\n-   Dynamic CI Group \\[cmdb\\_ci\\_query\\_based\\_service\\] table.\n\n## CSDM tables used by Vulnerability Response, Application Vulnerability Response, third-party vulnerability integrations and Software Bill of Materials applications\n\n1.  Product Model \\[cmdb\\_model\\] table \\(used by Application Vulnerability Response and Software Bill of Materials\\).\n2.  Application Model \\[cmdb\\_application\\_product\\_model\\] table \\(used by Application Vulnerability Response and Software Bill of Materials\\).\n3.  The Configuration Item \\[cmdb\\_ci\\] table.\n4.  Business Application \\[cmdb\\_ci\\_business\\_app\\] \\(used by Application Vulnerability Response and Software Bill of Materials\\).\n5.  Business Service \\[cmdb\\_ci\\_service\\_business\\].\n6.  Technology Management Service \\[cmdb\\_ci\\_service\\_technical\\] table \\(formerly Technical Service\\).\n\n**Note:**\n\nWhen you upload Software Bill of Materials files, the SBOM applications try to match any Product Model and Business Applications you upload to those that already exist in your CMDB. You can link service instances \\(formerly called application services\\) or business applications to a product model.\n\n## Products that add value to Vulnerability Response, Application Vulnerability Response, third-party vulnerability integrations and Software Bill of Materials applications\n\nUsing the Vulnerability Response applications with the following ServiceNow products can benefit your organization.\n\n-   **Third-party vulnerability scanners and integrations**\n\n    Imported vulnerabilities from the National Vulnerability Database \\(NVD\\) and detection data from third-party scanners are reconciled with the assets in your CMDB. When an imported vulnerability matches an existing asset, a vulnerable item is created. Vulnerable items are grouped automatically into tasks for remediation, risk-scored with business context, prioritized and assigned to appropriate teams for remediation. For more information and a list of integrations see [Vulnerability Response integrations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln_integrations.md).\n\n-   **The CWE Comprehensive 2000 and NVD Integrations**\n\n    Imported data from the NIST National Vulnerability Database \\(NVD\\) and Common Weakness Enumeration \\(CWE\\) integrations is used to enrich the vulnerability data in your instance and help you decide whether to escalate remediation for a vulnerability, vulnerable item, or remediation task. See [National Vulnerability Database \\(NVD\\) integration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/nvd-vuln-integration.md) and [Configure and run the scheduled job for updating CWE records](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/t_ConfigureScheduledJobsCWE.md) for more information.\n\n\n## Products that benefit from integration with Software Bill of Materials\n\n-   **Security Posture Control**\n\n    Security Posture Control enables cybersecurity teams to get visibility into their complete enterprise asset inventory and determine their overall security posture. Policies in SPC can help you detect assets with vulnerability that you import with the Vulnerability Response applications to help you locate security tool coverage gaps.\n\n-   **Governance, Risk, and Compliance**\n\n    Connect security and IT with an integrated risk program offering continuous monitoring, prioritization, and automation.\n\n-   **DevOps**\n\n    Protect your environments from potentially harmful components during software development cycles with GitHub Actions that you initiate from your GitHub environment. Upload SBOM files to the ServiceNow AI Platform from your GitHub repositories.\n\n\n"}}