Assign the Vulnerability Response persona roles using Setup Assistant › Configuring Vulnerability Response using the Setup Assistant › Vulnerability Response implementation › Vulnerability Response › Unified Security Exposure Management › Security Operations

Release: Australia · Updated: 2026-03-28 · Official documentation · View source

Configure filter values for ENISA European Union Vulnerability Database (EUVD) and Japanese Vulnerability Notes (JVN) integrations

Before activating the EUVD or JVN integrations, configure filter values and scheduled job parameters to control how vulnerability data is retrieved and processed.

Before you begin

Role required: sn_sec_int.admin

Note: Before running the Central Vulnerability Database integrations, make any necessary configuration changes based on your requirements. There is a configured run-as user for each integration record. The default value for this user is VIF.System. Do not change this value.

About this task

A successful integration requires planning and careful execution of pre-integration tasks. The scheduled job updates vulnerability data stored in the sn_vul_nvd_entry table. This data is used to enrich and maintain vulnerability records referenced by the EUVD and JVN integrations. The job should be executed as part of the initial setup, before running any external scheduled jobs, to ensure that base vulnerability records are available and up to date.

Procedure

In the Navigation Search bar, type sn_sec_int_impl.LIST and press Enter.
Select the required integration:
- ENISA EUVD Integration, or
- JVN Integration
- Open the Integration Instance Parameter tab.

Update the required configuration parameters.

Note: The maximum number of records returned per API call is:

100 for ENISA EUVD Integration
50 for JVN Integration This limit is controlled using the size parameter.

Range filter parameters for JVN Integration:

Parameter name	Default value	Possible value	Description
`rangeDateFirstPublished`	n	n, w, m	Defines the date range filter based on the first published date of the vulnerability. `n` = no range specified, `w` = last week, `m` = last month.
`rangeDatePublished`	n	n, w, m	Defines the date range filter based on the published date of the vulnerability. `n` = no range specified, `w` = last week, `m` = last month.
`rangeDatePublic`	n	n, w, m	Defines the date range filter based on the public disclosure date of the vulnerability. `n` = no range specified, `w` = last week, `m` = last month.

Save the changes by updating the record.

What to do next

After configuring filter values, proceed to configure the scheduled job settings. The following fields are available on the Vulnerability Integration form:

Field	Description
Name	Name of the scheduled job.
Active	Whether the scheduled job is active. If you do not want the job to run for a specific time period, you can set up the parameters you want to use and deactivate the job.
Run	Frequency you want the job to run. Choices include: Daily: Choose a Time Weekly: Choose a Day and Time Monthly: Choose Day and Time Periodically: Choose a Repeat interval, Starting date, and time Once: Choose a Starting date and time On Demand Business Calendar Entry Start Business Calendar Entry End
Day	The day you want the scheduled job to run. Displays days of the week for Weekly, or days of the month for Monthly.
Time	The time you want the scheduled job to start.
Integration script	The script for pulling data from the data sources specified in the Data Sources related list.
Source integration	\[Read only\]
Source Instance	\[Read only\]
Application	\[Read only\] The name of the application for which you are running the scheduled job.
Repeat Interval	The number of days and hours before the scheduled job runs again. Appears when Periodically is selected in the Run list.
Starting	The date and time to start the periodic updates. Appears when Periodically is selected in the Run list.
Conditional	The check box to add conditional parameters.
Condition	The conditions to run the scheduled job. Appears when the Conditional check box is selected.
Report processor strategy	The strategy for pulling data and processing the scheduled job: Data Source Attachment: Pulls data from the data sources in the Data Sources related list using the script in the Integration script field. Custom Report Processor: Selects a custom processor in the Report Processor script field.
Report processor	The script to be executed when the scheduled job runs. Appears when Custom Report Processor is selected in the Report processor strategy list.
Processor factory script	The script to build the report processor. Appears when Custom Report Processor is selected in the Report processor strategy list.