tenable.io additional integration instance credentials won't save

mgroversigital
Tera Expert

I am working to implement Tenable.io with Vulnerability Response.  We are normally filtering out vulnerabilities that are medium-severity or below.  However, a new requirement popped up for us to also import medium-severity vulnerabilities, only if they have a particular tenable asset tag.  It looks like it's possible to do this according to this docs page: https://docs.servicenow.com/bundle/washingtondc-security-management/page/product/secops-integration-...

 

In that article it specifically references the use case where multiple integration instances exist in parallel.  I have tried creating a new integration instance both through the UI page by clicking 'add integration', and also creating a new integration instance record in the back end.  In both cases, when the Access Key and Secret are entered, they don't get saved.  

 

Is there some limitation with using the same credentials for multiple integration instances, or some other issue with creating multiple integration instances?  

0 REPLIES 0