iac.htora.dev · security templates

Home/Refreshers/Data that cannot leave your organisation: refresher

Data that cannot leave your organisation

Perimeter policies so stolen credentials cannot copy data to an attacker's own account or project.

Remember

  1. A request with valid credentials: possibly stolen.
  2. The perimeter checks both ends: whose identity, whose resource, which network.
  3. Crossing the edge is refused: whatever the credentials allow.
  4. The attempt is logged: for the responders.
PlatformUsesThe part that catches people
AWSService and resource control policies keyed on the organisation IDResource control policies stay off until switched on for the organisation.
Google CloudVPC Service Controls perimeter around sensitive projectsA perimeter refuses you too when you work from outside it, including in the console.
AzureA network security perimeter around the resources, with Azure Policy behind itAzure has no tenant-wide rule that keys on whose identity and whose resource, the way AWS and Google Cloud do.
Oracle CloudA deny policy keyed on a network source, with a security zone behind itOracle Cloud policies are allow-only until deny policies are on, so without that one-time switch the statements here are refused as invalid.

Run the quick start

Download providersterraform init
Previewterraform plan
Applyterraform apply

Watch out

  • Stolen credentials keep their permissions.
  • AWS services acting for you, such as CloudTrail writing to its bucket, pass the identity perimeter.
  • Only AWS and Google Cloud have a tenancy-wide rule that keys on whose identity and whose resource.
Check it worked

With valid credentials, try to copy an object to a bucket in another organisation. It is refused.

Read the full pageDownload PDF

Registry 0.23.0. Built 2026-11-17.

Made by Habibullah Tora. Source on GitHub. Code under the MIT licence, writing under CC BY 4.0.