Terminology Index

Glossary

2953 terms

Open concept maps
R
32

Regression Testing

In detection engineering, retesting detections after changes to ensure they still work and don't break expected behavior, so improvements don't silently degrade coverage of existing threats.

Regression testing for detections borrows software-engineering discipline: keeping a set of known-true and known-benign scenarios that detections are run against after every change, so updates that improve one rule don't break another. It catches accidental regressions in detection logic and ensures the catalog continues to detect what it always did. As detection engineering matures toward detection-as-code, regression testing is a key practice that makes safe, rapid detection iteration possible.

Introduced in: Detection Engineering

Examples

  • Running every detection against known-true and known-benign cases after a change.
  • Catching a regression where an update broke detection of a known technique.
  • Building automated regression tests for the detection catalog.