# Proactive control

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

A control that checks a resource before it is deployed, usually inside an infrastructure-as-code pipeline, and fails the deployment if the resource would be noncompliant. It acts earlier than a preventive control but only on the paths it hooks. It acts earlier.

## An example, sourced

AWS Control Tower documents proactive controls as checks that run when resources are created or updated through CloudFormation stack operations, implemented as preCreate and preUpdate hook handlers. The page warns the controls may not affect requests made directly through the console, the AWS APIs, the SDKs or other infrastructure-as-code tools. The page also notes that secure strings and secrets are not resolved before they reach the hook, so a control cannot evaluate them.

## Why it matters here

A proactive control gives fast feedback to engineers who deploy through CloudFormation, and it leaves every other path open. Count it as a pipeline check, not as enforcement. It is an early signal for engineers using that tool and nothing more, so pair it with a preventive control for rules that must hold on every path.

## Related pages

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

## Sources

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

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