Tenable.io integration error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2023 10:32 PM
Hello,
Have you ever noticed this error with Tenable.io integration in Vulnerability Response module?
com.glide.db.impex.json.JSONLoader: com.glide.db.impex.datasource.stream.StreamDataSourceException: No fields provided for mapping to headers:
It is appearing during Assets and Vulnerability Items integration jobs and no data is loaded. Although the vulnerabilities database (Plugin integration) is updated without issues so the integration is properly configured I think.
I try to use new ServiceNow Tenable integration application with PDI instance on Utah Patch 1.
Regards, Darek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2023 12:05 AM
HI @dmarkowski2 ,
I trust you are doing great.
To resolve the error you mentioned with the Tenable.io integration in the Vulnerability Response module of ServiceNow, you can follow these steps:
Verify Field Mapping:
- Go to the Vulnerability Integration Configuration in ServiceNow.
- Ensure that the field mapping for the Assets and Vulnerability Items integration jobs is correctly defined. Make sure all the required fields are mapped properly.
Check Integration Job Configuration:
- Review the configuration settings of the integration jobs.
- Confirm that the integration job for loading data into Assets and Vulnerability Items is properly configured.
- Validate that the necessary credentials and connection details for the Tenable.io integration are correctly entered.
Validate Data Source:
- Ensure that the data source used for the integration job is properly configured.
- Verify that the data source has the necessary permissions and access to fetch the required data from Tenable.io.
Test the Integration:
- Run a test integration job to check if it retrieves data successfully from Tenable.io and loads it into the Vulnerability Response module.
- Review the job logs and any error messages to identify any specific issues that may be causing the problem.