Issue with setting default Vulnerability Scanner in VR

[SecOpsNor]

Hi all, 

I am implementing ServiceNow VR and SIR, and in order to submit a vulnerability scan request from SIR I need to have one of my vulnerability scanners set as default. I go to Vulnerability Response > scanners, and I try to set the default value for Tenable.sc to True, but I get the following error message: 

Tenable.sc cannot be the default scanner. 

Does anyone have any ideas as to what could be the problem? Has anyone experienced this themselves?

[Amit Gujarathi]

HI @SecOpsNor ,
I trust you are doing great.

This issue might be due to a few possible reasons. Here are some steps you can take to troubleshoot and potentially resolve the problem:

1. Check Configuration and Permissions: Ensure that Tenable.sc is properly configured in ServiceNow. This includes making sure the connection parameters are correctly set up, and that the account used has the necessary permissions to perform scans and be set as default.

2. Review ServiceNow Documentation: ServiceNow's documentation might have specific guidelines or restrictions regarding setting a scanner as the default. It's possible that there are certain conditions or configurations needed for Tenable.sc to be set as default.

3. Compatibility and Version Check: Verify that the version of Tenable.sc you are using is compatible with your current version of ServiceNow. Sometimes, compatibility issues can prevent certain functionalities from working as expected.

4. Custom Business Rules or Scripts: Check if there are any custom business rules or scripts in your ServiceNow instance that might be preventing Tenable.sc from being set as the default scanner. Sometimes, custom configurations can conflict with standard functionalities.

5. Error Logs: Examine the error logs in ServiceNow for any additional details about the error. These logs can provide more specific information about what is preventing Tenable.sc from being set as default.

6. Update ServiceNow and Tenable.sc: Ensure both ServiceNow and Tenable.sc are updated to their latest versions. Sometimes, bugs that cause such issues are fixed in updates.

[SecOpsNor]

Thanks for responding, Amit. I got a very similar answer from ChatGPT. Unfortunately, I still experience the issue. Have you experienced a similar issue yourself? 

[A-Sprague]

 HI @SecOpsNor 

I would check the business rule "Default scanner must not be Tenable.sc", it will need to be deactivated. Then you will be able to make your changes to the default setting.