Configure the RBVM Data Import Connector to Import RBVM Events

You can synchronize data to Neurons for ITSM from RBVM, based on filter criteria configured in the RBVM Connector settings. With use of Open Data Protocol (OData) calls, data is imported directly from RBVM, ensuring updated information is always available. This integration also removes the requirement to edit scripts, and the limitation on importing records into Neurons for ITSM.

The connector configuration UI feature enables you to easily set up a connection, set filter criteria for the data, and set schedules to run the connector and import from RBVM. Once the data is pulled from RBVM, based on the filter criteria, Security Events and CIs are created. If the Event Severity and Risk Score of the Security Event is greater than or equal to 9 (the default value), Security Incidents are created.

Prerequisites

To enable connection between Neurons for ITSM and the RBVM client, your tenant Configuration Database (DB) needs to be configured to permit the connection, which must be setup by Ivanti. Please provide Getting help with the following information when requesting setup:

•RBVM Platform ID

•RBVM Client ID

•RBVM API Key

Configure the RBVM Connector

An RBVM Connector is provided in the Data Import Connections list. If you cannot locate this connector in the list, contact Getting help.

1.Log in as Administrator, and open the Configuration console.

2.Select Tools > Integration Tools > Data Import Connections.

3.Click on the RBVM Connector entry.
The Connection Settings configuration UI opens. You do not need to alter the default settings.

4.Click Test Connection.
The result is displayed in a popup window.

5.Click Next to open the Filter Setting window.

•The window displays pre-populated filter settings based on existing configurations. You can review and update the default criteria directly.

•You can add new filters from an extended list of filter-specific operators, and apply AND/OR logic to customize how filters are applied.

Available filters

Define or modify filter criteria

To define or modify filter criteria, follow these steps:

•Use the drop-down lists to select a field (e.g., Severity), an operator (e.g., Greater, Lesser), and enter a value (e.g., 9).

•To define multiple criteria, click Add to include additional filters.

•Use Logical operators (AND/OR) to combine filters and refine the data import logic.

The filters configured here help narrow down the data imported from the RBVM client based on specific conditions.

Example: In the example above, a filter is applied to import only those records where the Severity is greater than or equal to 9.

You can edit, add, or delete filter criteria at any time within the same window.

6.Click Next, and then select a schedule (or schedules) from the list in the Schedule Manager:

•Select one or more schedules, and then click Next to move to the next screen. To select multiple schedules, hold down the Ctrl key, and then select each schedule. You can create a new schedule in the Schedule Entry workspace if required, and then select it from this list. To create a new schedule, refer to About the Schedule Entry and Scheduled Jobs Workspaces.

•If no schedule is required, click Next to move to the next screen.
If you select to proceed without a schedule, a Confirmation dialog is shown, select Yes to proceed, or No to cancel.

7.Publish the connection configuration:

•Publish: Select this option to publish without running the connection configuration. If you selected a schedule, the connection runs at the scheduled time and imports any data from RBVM that meets the filter criteria. The imported data is automatically turned into Security Events and Security Incidents in ITSM.

•Publish and Run Now: Select this option to publish and run the connection configuration now. Selecting this option immediately imports any data from RBVM that meets the filter criteria. The imported data is automatically turned into Security Events and Security Incidents in ITSM.

•Publish and Test Run: Select this option to publish and test the connection and import only, no Security Events or incidents are created.

When you run the connector, you can check the Integration Queue to see if the request is queued, running, or has run and completed. To do this select Integration Tools > Integration Queue.

Verify the RBVM Data Import

When the RBVM Connector run has completed, check the Event, CI, and Security Incident workspaces to verify that any imported data is published into new Events, CI records, and Security Incidents.

Verify Security Events are created and linked to CI business objects

To verify Security Events are created and are linked to CI business objects:

1.Log on as Administrator.

2.Open the Event workspace and search the Event workspace for Security Events.

Enter Security Event in the Search field.

Click Show All Results.

3.Select a Security Event in the list and double-click to open it.

4.Select the Details tab and note the Host ID.

5.Select the CI tab and verify that the same ID is shown under Asset ID.

Verify CIs created from RBVM have a Security Event linked

To verify if the CIs created from RBVM have a Security Event linked:

1.Log on as Administrator.

2.Open the CI workspace.

3.Filter the CI list to display CIs created from RBVM using the RBVM Discovered CIs saved search.

At the top left of the workspace, click the Saved Search (All) drop-down.

Click All Saved Searches at the bottom right of the list.

Select RBVM Discovered CIs.

4.Select a CI entry and double-click to open it.

5.Select the Events tab and confirm the corresponding Security Event(s) are listed.

Multiple events may be linked to the same CI record. This occurs if multiple events have the same Host ID.

Verify Security Incidents are created

Security Incident creation is triggered in accordance with the RiskSense - Create Security Incident business rule triggered action conditional expression parameter, as configured for the Frs_EVT_Event.Security_Event business object. The default trigger conditional expression parameter is $(Event_Severity >= 9 && Risk_Score >= 9), therefore Security Events with Event Severity and Risk Score values greater than or equal to '9' create a Security Incident. To change the parameter setting, open the RiskSense - Create Security Incident business rule triggered action and alter the conditional expression parameter as required. For more information, refer to Creating a Triggered Action.

To verify Security Incidents are created:

1.Log on as Administrator.

2.Open the Security Incident workspace and check that corresponding new Security Incidents are created.