# Data perimeter

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

A data perimeter is a set of always-on permissions guardrails around identities, resources and networks that helps prevent unintended access. In AWS it is built from policies that fix who may reach which data from where. The perimeter works as a second layer, because it holds even when a role is broader than intended.

## An example, sourced

The AWS whitepaper Building a Data Perimeter on AWS, dated June 13, 2023, describes perimeter controls that protect against unintended access and configuration errors for identities, resources and networks.

## Why it matters here

A perimeter caps the damage when an individual policy is too loose. It complements least privilege on each identity.

## Related pages

- [Built-in role: meaning and an example](/glossary/built-in-role/)
- [Eligible assignment: meaning and an example](/glossary/eligible-assignment/)
- [Active assignment: meaning and an example](/glossary/active-assignment/)
- [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 16 Nov 2026)

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