That’s how detective controls prove their worth. They don’t prevent the mistake—that’s the job of preventive controls. They catch it fast, before it becomes a disaster. In the Microsoft Security Assessment (MSA) framework, detective controls are a core layer of operational defense. They shine when preventive measures fail.
Detective controls in MSA work by actively monitoring systems, applications, and processes to spot deviations, anomalies, or breaches. They respond to the unknown unknowns—the gaps you can’t predict during design. This makes them critical for transition points in deployment pipelines, identity and access checks, and network security monitoring.
Every effective MSA detective control follows three rules:
- Continuous monitoring – Never rely on point-in-time checks. Stay operational 24/7.
- Actionable alerts – Noise kills efficiency. Alerts must be relevant, clear, and time-bound.
- Traceable evidence – Store logs with enough context to reconstruct events.
Common examples in the MSA model include SIEM log analysis, privileged account usage tracking, endpoint threat detection, and data loss monitoring. Each aligns with risk categories: identity, endpoints, apps, data, and infrastructure.