# Implicit deny

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

The default outcome when no policy allows an action. In AWS, anything not explicitly allowed is denied. Allow-list SCPs depend on it: an action missing from the allow list at any level is blocked without any deny statement being written.

## An example, sourced

AWS documents that SCP evaluation "follows a deny-by-default model, meaning that any permissions not explicitly allowed in the SCPs are denied." If an allow statement is missing at the root, at the Production OU or at the account, access is denied. The page also notes that relying solely on allow statements can lead to unintended access because overlapping allows can override narrower ones.

## Why it matters here

Implicit deny is why removing FullAWSAccess without a replacement makes every action in member accounts fail. Know which of your SCPs rely on it. A new AWS service is blocked under such an SCP until someone names it, which makes the allow-list pattern safer but more work. Choose it deliberately.

## Related pages

- [Organizational unit: meaning and an example](/glossary/organizational-unit/)
- [Management account: meaning and an example](/glossary/management-account/)
- [Delegated administrator: meaning and an example](/glossary/delegated-administrator/)
- [All of them](/glossary/)

## Sources

- https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps_evaluation.html (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/glossary/implicit-deny/
