Skip to content
CTEM Vendors

Home / Glossary / Automated penetration testing

Glossary, read 12 Nov 2026

Automated penetration testing, defined for a CTEM program

All termsStage Coverage Map

Automated penetration testing in practice

The main change from manual testing is frequency. Horizon3 says NodeZero tests can be scheduled to run every day, and SafeBreach describes its Propagate product as testing from an assumed breach to measure post-breach blast radius, as each vendor states. Daily runs turn a yearly report into a trend line that can catch regressions.

Automation does not replace scoping discipline. NIST SP 800-115 (September 2008) still frames testing as work that is planned, conducted and analyzed, with mitigation strategies drawn from the findings, and the NCSC warns a penetration test should confirm vulnerability management, not be the main way to find flaws. Set safe-execution limits, exclude fragile systems, and agree in advance who receives findings.

An example

Horizon3 describes a Quick Verify step in NodeZero that reruns a test after remediation to confirm the fix worked (vendor page, read 12 Nov 2026).

Source, read 12 Nov 2026.

Sources

  1. https://www.ncsc.gov.uk/guidance/penetration-testing, read 12 Nov 2026
  2. https://csrc.nist.gov/pubs/sp/800/115/final, read 12 Nov 2026
  3. https://www.safebreach.com/propagate-attack-path-validation/, read 12 Nov 2026
  4. https://horizon3.ai/nodezero/, read 12 Nov 2026

Last reviewed 12 Nov 2026.