TenableSCAssetsIntegration Error 403

Chris_Gitonga · ‎02-16-2024

Hello,

My VR integration to Tenable has been running fine in dev for the past few weeks. We just cloned our prod environment and after doing the same setup steps. My third party vulnerability entries are loading fine and i was even able to pull open assets. My issue is the vulnerabilities will not load I'm getting this: Error: Invalid response code received from TenableSCAssetsIntegration: 403. There is nothing in the server side logs showing any denials. I tried to test with a different query filter and I'm getting the same error. Any ideas on how else to troubleshoot this?

Jonay Luis Alon · ‎02-21-2024

Hi Chris,

I was able to fix it, I had the same error on your side, but apparently Teanble returns error 403 when it shouldn't. In my case I understand that it should return error 500 since the credentials were not the problem.

I was able to solve the error by changing the dates of "Asset import", "Plugins Import" and "Plugins Import". , "Plugins Import" and "Vulnerabilities Import" in the Setup Assistant section of Vulnerability Response. By changing the dates because I don't know why the dates had a future value, I could not select the current or previous date. The date fields seem to be wrong in this module, but after several attempts I was able to set an earlier date and the integration worked and Tenable no longer returns error 403.

try changing the import dates inside the setup assistant in case this solves your problem.

Regards

View solution in original post

Jonay Luis Alon · ‎02-19-2024

Hello,

Were you able to find out what was wrong, in my case we reset the api key and the secret key and it stopped working.

Regards

Chris_Gitonga · ‎02-20-2024

Ive not found a solution yet. I opened a ticket with Support, ill post their response.

Jonay Luis Alon · ‎02-21-2024

Hello,

I also for my part have an open case, but the weirdest thing for my part, some integrations if I force their execution if they go well but when I run "Tenable.sc Open Vulnerabilities Integration" it returns me that 403.

The credentials in Servicenow have been changed, but if the Tenable team checks the logs they get the following message:

API Key login denied. API key 'eed...' does not exist.

And these are the old credentials, and I don't understand why the old credential is used if the integration already has the new one saved.

Martin Dewit · ‎02-20-2024

I would make sure your credentials for the integration are populated and working and have the required permissions.

Per https://developer.tenable.com/docs/common-tio-api-errors

Code	Status	Description
403	Forbidden	Returned if you do not have sufficient permissions to access a resource or complete a task.