
We use NodeZero for ongoing penetration testing across our corporate and manufacturing networks. Instead of testing once a year, we now validate our security every week. It regularly finds exploitable weaknesses we would otherwise have missed, which makes it worth having.
What we like
It finds real problems. A recent test found the management interfaces of our perimeter firewalls exposed to critical vulnerabilities. That started a firmware upgrade right away. The findings are attack paths you can act on, not theoretical scanner noise.
Weekly testing. Scheduled weekly site tests run on their own. We approved weekly testing at a new production facility before it went live, and running it there hasn't caused any operational problems.
Several vantage points. Runners in different trust zones and subnets let us see what an attacker could reach from each part of the network. We can run authenticated, unauthenticated and segment-specific tests.
Results ready to prioritize. Reports show attack chains and risk trends, so we can focus on high and critical issues and accept lower-risk findings where that makes sense.
Flexible in sensitive areas. We can tune scope, exclude fragile equipment and stop a test at any time. That made it workable on manufacturing floors.
Manual testing from the same vendor. The vendor's offensive security team ran a manual pentest from our existing runners, with no extra hardware to set up.
A good roadmap. Web app testing, cloud coverage, ticketing for remediation and imports from other vulnerability scanners all expand what it can do.
Responsive customer success team. Regular meetings, clear action items and quick answers to configuration questions. Review collected by and hosted on G2.com.
Runner reliability: containers sometimes hang between scheduled runs and need a reboot. Shortening the maximum test duration has helped.
License usage: our asset count quickly went over the licensed limit, so plan for growth.
Security alerts: the service account can set off your own security alerts, so tell your security operations team before tests run.
Segmentation work: you may need firewall changes to keep tests away from sensitive systems. Review collected by and hosted on G2.com.