I want to make a case for building a security program, but the organization is reluctant to invest in security. Are there vulnerability scanning tools that are simpler to get started with than building OpenVAS from scratch?
What's easier to use than OpenVAS for vulnerability scanning?
Answers
Nessus is worth a look if ease of use is the priority. Its interface is simpler to get started with than an OpenVAS build, though commercial licensing can get expensive. Check the current free edition limits and licensing before assuming it will cover your environment.
Some Nessus offerings can also assess configurations against security benchmarks such as CIS. That's useful if you want to show more than a list of missing patches, but configuration findings still need review before anyone starts changing settings.
Reply to this answer
If cost is the main reason you're considering OpenVAS, you don't have to build it from source. Greenbone Community Edition has a container setup using Docker Compose. The initial feed synchronization can take a while, so don't expect useful scans immediately after the containers start.
It's still not the easiest option to administer, but that route avoids some of the pain of a source build.
Reply to this answer
Before adding another product, check what your existing endpoint security, VPN, or other management agents already report. Some include basic vulnerability reporting or patching features, and that might be enough to start a conversation without deploying a separate scanner.
Wazuh is another option to investigate for vulnerability detection and compliance reporting. It's not quite the same thing as a dedicated network vulnerability scanner, so check whether its coverage fits what you're trying to assess.
Reply to this answer
Get explicit management approval before scanning, including agreement on the systems and timing. Scans can disrupt production or sensitive devices, and running one without permission is a bad way to build support for a security program.
Start with a small, agreed scope and review the results with the people responsible for those systems. If you're going to use authenticated scans, arrange appropriate credentials for the Windows and Linux hosts in scope. They can give you better visibility than scanning from the outside alone.
Reply to this answer
A scanner can help make the case, but it won't do the work of a security team. Someone has to validate findings, decide what matters, and coordinate fixes.
Don't present every result as an emergency. For example, an enabled TCP timestamp might appear in a report, but disabling it everywhere isn't automatically a meaningful security improvement. Pick a few relevant, actionable findings rather than handing management a huge unfiltered report.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Zavdrix-4m:
External visibility can be useful too, but agree on the scope and authorization for that as well. It only shows part of the environment.