{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":45904,"path":"security-management/vulnerability-response/configure-csaf-vendor.md","title":"Configure a Common Security Advisory Framework vendor other than Red Hat","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure a Common Security Advisory Framework vendor other than Red Hat\n\nConfigure a Common Security Advisory Framework \\(CSAF\\) vendor other than Red Hat with API support.\n\n## Before you begin\n\nRole required: sn\\_vul.vulnerability\\_admin or sn\\_vul.admin \\(deprecated\\), or admin\n\n## Procedure\n\n1.  Navigate to **All** &gt; **Vulnerability Response** &gt; **Connection &amp; Credential** &gt; **Connection &amp; Credential Aliases**.\n\n2.  Create a record with the vendor-supported authentication type.\n\n    For more information on how to authenticate a vendor, see [Configure Connection and Credential aliases for the Common Security Advisory Framework \\(CSAF\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/configure-connection-credential-aliases-csaf.md).\n\n3.  Navigate to **All** &gt; **Vulnerability Response** &gt; **Flow Designer**.\n\n4.  Duplicate the flow called \"Advisory Parsing\".\n\n    **Note:**\n\n    -   If any of the actions needs to be changed, copy the action and use it in the new flow.\n    -   Review the page\\_index\\_key and page\\_size\\_key parameters as per the vendor API.\n    -   Update the pagination-related logic as per the vendor\n5.  If the date range parameter logic is not the same as Red Hat, copy the action **Update Pagination Parameters** and make changes as required for the vendor.\n\n6.  Navigate to **All** &gt; **Vulnerability Response** &gt; **Enrichment Data Mappings**.\n\n7.  Create a record as per Red Hat by changing the **Property key** value as per the vendor.\n\n    This logic is for mapping required fields from an advisory payload to a ServiceNow table.\n\n8.  Map the following API tags from API Payload.\n\n    These tags need to be mapped with details to be filled in the Enrichment Data Mapping table. By default, the Red Hat specific mapping is shipped.\n\n    **Note:** You need to create a record if you need to configure multiple vendors that publish advisories.\n\n<table id=\"table_cmf_zmp_psb\"><thead><tr><th>\n\nAdvisory payload tag\n\n</th><th>\n\nColumn from table sn\\_vul\\_cvrf\\_solution\\_integration\\_update\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nCSAF URL \\(Resource URL pointing to CSAF Payload\\)\n\n</td><td>\n\ncvrf\\_url\n\n</td><td>\n\nTag name that contains the CSAF URL.\n\n</td></tr><tr><td>\n\nAdvisory ID \\(Unique key for response\\)\n\n</td><td>\n\nId\n\n</td><td>\n\nTag name that contains a unique identifier.\n\n</td></tr><tr><td>\n\nLast modified date\n\n</td><td>\n\nlast\\_modified\\_date\n\n</td><td>\n\nTag name that contains the date when the record was last updated.\n\n</td></tr><tr><td>\n\ncsaf \\(Static Value\\)\n\n</td><td>\n\nadvisory\\_format\n\n</td><td>\n\nAdvisory format value for CSAF payloads. Note that this is a static value applicable for all of the CSAF Integrations.\n\n</td></tr><tr><td>\n\nsecurityAdvisoryIntegrationSysId\n\n</td><td>\n\nintegration\n\n</td><td>\n\nRefers to the integration scheduled job sysId, which creates the vulnerability solution records.\n\n</td></tr></tbody>\n</table>9.  Based on the response format, change the logic of parsing by copying the action **Retrieve List** from the Advisory Parsing flow.\n\n\n"}}