Glossary, read 12 Nov 2026

# Re-validation, defined for a CTEM program

**In short:** Re-validation reruns the original test after a fix to prove the exposure is actually closed, and repeats tests over time to catch regression. Picus says every failed test can be re-run after its suggested mitigation to confirm the gap closed, and Horizon3 offers a Quick Verify step for NodeZero, as each vendor describes.

[All terms](https://ctemvendors.com/glossary/) | [Stage Coverage Map](https://ctemvendors.com/stage-coverage-map/)

## Re-validation in practice

Closing a ticket is a claim; re-validation is the evidence. Patches fail to deploy, configuration changes get reverted, and compensating controls get disabled during troubleshooting. Running the same technique or path again, with the same scope, turns remediation status into a tested result that can stop the MTTR clock. Use the same credentials, entry point and test version as the original run.

Re-validation also guards against drift. A control that passed a year ago may fail now after policy updates or log source changes. Mature CTEM programs schedule recurring tests against previously fixed items and treat any regression as a new exposure. Gartner's guidance on agreeing remediation triggers in advance applies equally to re-validation failures.

## An example

Picus's security control validation page (read 12 Nov 2026) describes re-running the same attack after applying a fix to confirm the control now holds.

[Source](https://www.picussecurity.com/use-case/security-control-validation), read 12 Nov 2026.

## Related terms

- [Validation (CTEM stage 4)](https://ctemvendors.com/glossary/validation/)
- [Security control drift](https://ctemvendors.com/glossary/security-control-drift/)
- [Control validation](https://ctemvendors.com/glossary/control-validation/)
- [Mean time to remediate (MTTR)](https://ctemvendors.com/glossary/mean-time-to-remediate/)

## Sources

- [https://www.picussecurity.com/use-case/security-control-validation](https://www.picussecurity.com/use-case/security-control-validation), read 12 Nov 2026
- [https://horizon3.ai/nodezero/](https://horizon3.ai/nodezero/), read 12 Nov 2026
- [https://web.archive.org/web/20260110234446/https://www.gartner.com/en/articles/how-to-manage-cybersecurity-threats-not-episodes](https://web.archive.org/web/20260110234446/https://www.gartner.com/en/articles/how-to-manage-cybersecurity-threats-not-episodes), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://ctemvendors.com/glossary/re-validation/
