BSI C5 · Control PSS-12 · Priority: critical · Component: Platform & Service Security

What this control covers

Enables customers to specify data processing/storage locations per contractual options, enforced by cloud architecture. Ensures compliance with geographic requirements, protecting cloud customer data sovereignty and regulatory obligations.

Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

How to implement

AWS

Codify the policy intent as SCPs, AWS Config conformance packs, and Security Hub standards so the cloud enforces what the document says.

Azure

Codify in Azure Policy initiatives (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

GCP

Org Policy Service for guardrails and Config Validator in CI to pre-check Terraform plans against policy as code (Rego).

On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

Evidence to collect

  • policy_document — A signed, version-controlled policy stating leadership intent and the named owner.
  • infra_scan — See the iCompaas Evidence library for the canonical source for this evidence type.

Signed policy or standard documents the safeguard. Focus: Locations of Data Processing and Storage.

Quick checklist

  • Risk — Cloud Customer Data / Management
  • Security — Cloud Customer Data / Management
  • Data — Cloud Customer Data / Management
  • Policy — Cloud Customer Data / Management
  • Contractual — Cloud Customer Data / Management
  • Locations — Cloud Customer Data / Management

Related articles on this site