Define a new vulnerability integration

---
title: Define a new vulnerability integration
description: A vulnerability integration pulls report data from a third-party system, generally to retrieve vulnerability data, and process that reporting data using data sources or a custom processor.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/security-management/vulnerability-response/t\_DefineNewIntegration.html
release: brazil
product: Vulnerability Response
classification: vulnerability-response
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 3
breadcrumb: [Manually create a vulnerability integration, Vulnerability Response integrations, Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# Define a new vulnerability integration

A vulnerability integration pulls report data from a third-party system, generally to retrieve vulnerability data, and process that reporting data using data sources or a custom processor.

## Before you begin

Persona and granular roles are available to help you manage what users and groups can see and do in the Vulnerability Response application. For an initial assignment of the persona roles in Setup Assistant, see [Assign the Vulnerability Response persona roles using Setup Assistant](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/vr-assign-personas_SA.md). For more information about managing granular roles, see [Manage persona and granular roles for Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/vr_manage_granular-roles.md).

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

## Procedure

1.  Navigate to **All** > **Vulnerability** > **Administration** > **Integrations**.

2.  Click **New**.

3.  Fill in the fields, as needed.

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

Field

</th><th>

Description

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

Name

</td><td>

A descriptive name for the integration.

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

Active

</td><td>

Whether the integration is active. If you do not want it to run for a specific time period, you can set up the parameters you want to use and deactivate the job.

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

Run

</td><td>

The frequency you want the integration to run, Daily, Weekly, Periodically, and so on. As noted, subsequent fields are displayed or not based on your setting in this field.

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

Day

</td><td>

The day you want the integration to run.-   If you selected **Weekly** in the **Run** field, this field displays the days of the week.
-   If you selected **Monthly** in the **Run** field, this field displays the days of the month.


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

Time

</td><td>

The time you want the integration to start. This field appears only if you selected **Daily**, **Weekly**, or **Monthly** in the **Run** field.

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

Application

</td><td>

\[Read only\] The name of the application for which this integration was created.

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

Repeat Interval

</td><td>

If you selected **Periodically** in the **Run** field, this field displays the number of days and hours before the integration runs again.

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

Starting

</td><td>

If you selected **Periodically** in the **Run** field, this field displays the dates and time to be used as the starting point for periodic updates.

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

Conditional

</td><td>

Select this field if you want to add conditional parameters.

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

Condition

</td><td>

If you selected the **Conditional** check box, enter the conditions here.

</td></tr><tr><td colspan="2">

**Integration Details**

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

Integration script

</td><td>

Select the script include that extends the VulnerabilityIntegrationBase to be executed when the integration runs. This script defines how to retrieve data from a third-party system.

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

Integration factory script

</td><td>

Enter a script that defines how to construct the script include selected for the **Integration script**. For more information, see [Integration factory script fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/c_AboutFactoryScript.md).**Note:** Scripts require both ServiceNow and Vulnerability Response expertise.

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

Report processor strategy

</td><td>

Select the strategy you want to use to handle the data returned by the integration script when the integration runs.-   Select **Data Source Attachment** if you want to process data using a data source.
-   Select **Custom Report Processor** to select a custom processor.


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

Report processor

</td><td>

If you selected **Custom Report Processor** in the **Report processor strategy** field, select the script include that extends the VulnerabilityReportProcessorBase script include to be executed when the integration runs.This script defines how to process the data returned by the integration script.

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

Processor factory script

</td><td>

Enter a script that defines how to construct the script include selected for the **Report processor**.

</td></tr></tbody>
</table>4.  Click **Submit**.


**Related topics**  


[Vulnerability integration script](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/c_AboutVulnIntegScript.md)

[Report processor strategies](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/c_AboutRptProcStrategies.md)

[Integration factory script fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/c_AboutFactoryScript.md)

[Manually run a vulnerability integration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/t_ManualRunVulnInteg.md)