However when you are scanning over 1 million IPs to find 300,000 assets it takes a bit more strategy, especially if you need it to finish within 24 hours. Now this approach is solid for small deployments say up to 50,000 IPs. However, the problem they were having is the scans were not finishing in 24 hours. The approach they started with was very common in Vulnerability Management A discovery scan on their entire IP space then a credentialed vulnerability scan on those assets that were found during the discovery scan. Once the Tenable.sc tiers were in place we needed to collect all of the potential IP space for each data center. A reporting console could be used to aggregate all of their data, however they chose to integrate with their SIEM for aggregation of their Vulnerability data. The first set of actions was to tier Tenable.sc to different data centers, so one Tenable.sc console per data center. To scale to the massive level they required was going to take some math and a decent understanding of their network topology. Before purchasing Tenable.sc, formally Security Center, they utilized OpenVas and a few other VM solutions that could not scale to their demands A credentialed vulnerability scan on over 300,000 assets daily! Not an easy task. Nessus is the work horse behind Tenable.sc. If this is something you failed at in 2018, it's time to revisit your program and strategy.Ī few months ago, I got the pleasure of working with a very large corporation looking to scale their Cyber Exposure program utilizing Tenable.sc and our beloved Nessus. Scaling your Vulnerability Management and Cyber Exposure program is not something you want on your list of failures come this time next year. I spend time on deciding if my failures are worth revisiting in 2019 or if my direction has changed. I keep a list of all of my achievements and failures throughout the year and spend a good portion of today going over that list.

Tenable host discovery scan