Forum Discussion
Improvement: Handling Component Installs for Vulnerability Assessment
Hi A-GoodSloth ! Yes, this will be coming to Tenable Security Center. It will not require a version update as similar to Nessus, TSC gets policy updates via a separate feed. There is a slight backlog on the SC for template updates like this, but we are doing everything we can get this pushed through. I will update again once i get confirmation.
My apologies A-GoodSloth - confirming this feature is now available in Tenable SC - no version update required.
- george_mentetak20 days agoConnect Contributor
Can someone please confirm that this is indeed working as it should for tenable.sc ?From our experience being on tenable.sc 6.8.0, we can see the new "Is Component" reporting within our respective plugin reporting but we don't get all the results unless we're running Paranoid scans.
- rmoody19 days agoProduct Team
Hi george_mentetak ,
Yes, this appears to be working in SC v6.8.0. Please make sure that the scanner has both its plugins and templates updated to the latest (SC should handle this for managed scanners).
Can i ask, which vulnerabilities (plugins) are missing in your normal scan reports - i.e plugins you feel should not require paranoid mode? Please attach a scan result (diag scan DB) if you are comfortable doing so here, or else you can always log a ticket with our tech support team if needed.
- george_mentetak19 days agoConnect Contributor
I can confirm that we are using the latest, i.e. Plugin Set 202603230317 and Policy Template Version 202603191049 yet unless we're running Paranoid scans, we don't see the Curl (240632, 30277, etc), OpenSSL (266297, 296297, etc) ones as an example.