# Detective control

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

A control that finds noncompliance after a resource exists and reports it through a dashboard or alert, without stopping the change. Detective controls show state, so they suit rules that are still being learned and the gaps a preventive control leaves.

## An example, sourced

AWS Control Tower documents that "a detective control detects noncompliance of resources within your accounts" and alerts through the dashboard. Its status is clear, in violation or not enabled. The page says detective controls are implemented using AWS Config rules, and that their names typically begin with the word Detect. The page says most of the strongly recommended controls, and many of the elective controls, that AWS Control Tower owns are detective.

## Why it matters here

Detective controls are how you test a rule on real resources before you turn it into a block, and how you find what a block did not cover, such as the management account. They also show what a block missed, which makes them a companion to any preventive rule you ship.

## Related pages

- [Proactive control: meaning and an example](/glossary/proactive-control/)
- [Service control policy: meaning and an example](/glossary/service-control-policy/)
- [Resource control policy: meaning and an example](/glossary/resource-control-policy/)
- [All of them](/glossary/)

## Sources

- https://docs.aws.amazon.com/controltower/latest/controlreference/detective-controls.html (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/glossary/detective-control/
