---
title: Configure a Common Vulnerability Reporting Framework vendor other than Cisco
description: Configure a Common Vulnerability Reporting Framework \(CVRF\) vendor other than Cisco with API support.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/configure-cvrf-vendor.html
release: australia
product: Vulnerability Response
classification: vulnerability-response
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 1
breadcrumb: [Common Vulnerability Reporting Framework \(CVRF\), Configure vulnerability solution providers, Setting up vulnerability solution providers, Configuring Vulnerability Response using the Setup Assistant, Vulnerability Response implementation, Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# Configure a Common Vulnerability Reporting Framework vendor other than Cisco

Configure a Common Vulnerability Reporting Framework \(CVRF\) vendor other than Cisco with API support.

## Before you begin

Role required: sn\_vul.vulnerability\_admin or sn\_vul.admin \(deprecated\), or admin

## Procedure

1.  Navigate to **All** > **Vulnerability Response** > **Connection & Credential** > **Connection & Credential Aliases**.

2.  Create a record with the vendor-supported authentication type.

    For more information on how to authenticate a vendor, see [Configure Connection and Credential aliases](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/configure-connection-credential-aliases.md).

3.  Navigate to **All** > **Vulnerability Response** > **Flow Designer**.

4.  Duplicate the flow called "Advisory Parsing".

    **Note:**

    -   If any of the actions needs to be changed, copy the action and use it in the new flow.
    -   Update the pagination-related logic as per the vendor
5.  If the date range parameter logic is not the same as Cisco, copy the action **Update Pagination Parameters** and make changes as required for the vendor.

6.  Navigate to **All** > **Vulnerability Response** > **Enrichment Data Mappings**.

7.  Create a record as per Cisco by changing the **Property key** value as per the vendor.

    This logic is for mapping required fields from an advisory payload to a ServiceNow table.

8.  Map the following API tags from API Payload.

    These tags need to be mapped with details to be filled in the Enrichment Data Mapping table. By default, the Cisco-specific mapping is shipped.

    **Note:** You need to create a record if you need to configure multiple vendors that publish advisories.

<table id="table_cmf_zmp_psb"><thead><tr><th>

Advisory payload tag

</th><th>

Column from table sn\_vul\_cvrf\_solution\_integration\_update

</th><th>

Description

</th></tr></thead><tbody><tr><td>

CVRF URL

</td><td>

cvrf\_url

</td><td>

Tag name that contains the CVRF URL.

</td></tr><tr><td>

Advisory ID \(Unique key for response\)

</td><td>

Id

</td><td>

Tag name that contains a unique identifier.

</td></tr><tr><td>

Last modified date

</td><td>

last\_modified\_date

</td><td>

Tag name that contains the date when the record was last updated.

</td></tr><tr><td>

securityAdvisoryIntegrationSysId

</td><td>

integration

</td><td>

Refers to the integration scheduled job sysId, which creates the vulnerability solution records.

</td></tr></tbody>
</table>9.  Based on the response format, change the logic of parsing by copying the action **Retrieve List** from the Advisory Parsing flow.