The Zurich release has arrived! Interested in new features and functionalities? Click here for more

Matched Discovered Items have empty 'Matching type for the DI' field

HelloCAD
Tera Contributor

We have Rapid7 integration setup for Vulnerability response. Many of the Discovered Items that have 'Matched' state has empty 'Matching type for the DI' field. How is this possible?

Is this a known error or is this happening due to some gaps?

2 REPLIES 2

Nilesh Pol
Tera Guru

@HelloCAD 

The issue you're encountering with Rapid7 integration for Vulnerability Response, where Discovered Items (DIs) in the 'Matched' state have an empty 'Matching type for the DI' field, can be attributed to several factors. Here's a breakdown of potential causes and solutions:

  1. Integration Configuration:

    • Ensure that the integration between Rapid7 and ServiceNow is correctly configured. The mapping of fields from Rapid7 to ServiceNow should be reviewed to ensure that the 'Matching type for the DI' field is correctly populated during the data transfer.
  2. Data Mapping and Transformation:

    • Check the data transformation logic used in the integration. There might be a gap in how the 'Matching type for the DI' field is mapped or transformed from Rapid7 data to ServiceNow. Ensure that the field mapping includes logic to populate this field.
  3. Scripted Transform Maps:

    • If you are using scripted transform maps, verify that the script correctly handles the population of the 'Matching type for the DI' field. There might be a condition or error in the script that prevents the field from being populated.
  4. Integration Logs:

    • Review integration logs for any errors or warnings that might indicate why the 'Matching type for the DI' field is not being populated. Logs can provide insights into any issues during the data import process.
  5. Field-Level ACLs:

    • Ensure that there are no field-level ACLs or permissions that might be preventing the population of the 'Matching type for the DI' field. Sometimes, ACLs can inadvertently restrict data updates.

By systematically checking these areas, you should be able to identify the root cause of the issue and resolve it. If the problem persists, consider reaching out to your ServiceNow administrator or Rapid7 support team for further assistance.

Hi @Nilesh Pol , thank you for your response.

Shouldn't the field 'Matching type for the DI' on Discovered item be populated after the Lookups & IREs. It should not be from the source or transform maps/scripts?

 

Thank you.