What this control covers
This control requires the controller to implement appropriate technical and organizational measures to ensure processing complies with GDPR. These measures should be regularly reviewed and updated based on processing activities and risks. The controller may also use approved codes of conduct or certification mechanisms to demonstrate compliance. This control addresses Accountability.
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.
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: Responsibility of the controller.
Quick checklist
- Responsibility — Controller / Conduct
- Processor — Controller / Conduct
- Codes — Controller / Conduct
- Certification — Controller / Conduct
Related articles on this site
- Ensure Diagnostic Setting captures appropriate categories from the control/management plane
- Ensure IAM password policy requires at least one uppercase letter
- Ensure IAM password policy requires minimum length of 14 or greater
- 1.8 Ensure IAM Password Policy Requires Minimum Length of 14 or Greater (Automated)