# Data perimeter

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

A set of preventive guardrails that keeps only trusted identities reaching trusted resources from expected networks. The aim is one always-on boundary around identities, resources and networks. Guardrails like these are always on, and they apply whatever teams build, so teams cannot opt out.

## An example, sourced

The AWS whitepaper "Building a Data Perimeter on AWS" says many organizations want perimeter controls to help protect against unintended access and configuration errors through always-on permissions guardrails. It outlines best practices and services for creating a perimeter around identities, resources and networks in AWS, and was first published on June 13, 2023. The library's RCP entries describe the resource side of it.

## Why it matters here

The perimeter is the main reason RCPs exist. A perimeter that uses SCPs alone covers your principals and leaves outside callers to resource policies. A perimeter turns many separate guardrails into one design goal. Name the objective each guardrail serves, whether identity, resource or network, so gaps become visible.

## Related pages

- [Azure Policy: meaning and an example](/glossary/azure-policy/)
- [Policy effect: meaning and an example](/glossary/policy-effect/)
- [Enforcement mode: meaning and an example](/glossary/enforcement-mode/)
- [All of them](/glossary/)

## Sources

- https://docs.aws.amazon.com/whitepapers/latest/building-a-data-perimeter-on-aws/building-a-data-perimeter-on-aws.html (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/glossary/data-perimeter/
