# Guardrail

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

A policy that sets limits on what identities or resources in a cloud estate can do, without granting any permission itself. Guardrails are written once at a high level, such as an organization root or management group, and apply to everything beneath it.

## An example, sourced

AWS Organizations documentation describes a service control policy as defining "a permission guardrail, or sets limits" on the actions IAM users and roles can perform. The page adds that no permissions are granted by an SCP: administrators must still attach identity-based or resource-based policies. The guardrail only narrows what those other policies can allow in member accounts. The library applies the term across all three clouds.

## Why it matters here

The word covers several mechanisms across three clouds, and each blocks differently. Knowing that a guardrail grants nothing tells you where to look when a request fails: the cap is lower than the grant, and the cap is what to change.

## Related pages

- [Preventive control: meaning and an example](/glossary/preventive-control/)
- [Detective control: meaning and an example](/glossary/detective-control/)
- [Proactive control: meaning and an example](/glossary/proactive-control/)
- [All of them](/glossary/)

## Sources

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

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/glossary/guardrail/
