TenableSCAssetsIntegration Error 403

[Chris_Gitonga]

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]

Hello,

We have reviewed and secured the API KEY information three consecutive days.

We have even forced to update the configuration data by java code and the credentials are being saved correctly.

We have updated the Tenable plugins to their latest version thinking that we would get some feature.

But we don't understand how some integrations do use the correct credentials and others do not when they are all under Tenable.sc.

[Jonay Luis Alon · Accepted solution]

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

[Chris_Gitonga]

Thanks for this. Id noticed the same issue with the date, being that i was not able to adjust the date when i set it up. That fixed my issue. Thanks.