Skip to content
CTEM Vendors

Home / Glossary / Control validation

Glossary, read 12 Nov 2026

Control validation, defined for a CTEM program

All termsStage Coverage Map

Control validation in practice

Control validation answers a narrower question than penetration testing: not whether an attacker can reach a target, but whether each control does its job against a named technique. Results are usually recorded per technique as prevented, detected, logged or missed, which is the scale Picus describes for its own security control validation product.

The output feeds two CTEM stages. Validated controls become credible compensating controls in prioritization. Failed controls become their own exposures, often with a vendor-specific fix such as a prevention signature or detection rule. Control validation should repeat on a schedule, since configuration changes and new detection content can silently break what passed last quarter.

An example

Advisory AA23-278A (NSA and CISA, October 5, 2023) recommends exercising, testing and validating the security program against the ATT&CK behaviors mapped in the advisory, continually and in production.

Source, read 12 Nov 2026.

Sources

  1. https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-278a, read 12 Nov 2026
  2. https://www.picussecurity.com/use-case/security-control-validation, read 12 Nov 2026

Last reviewed 12 Nov 2026.