# ISO/IEC 27701 A.1.3.2 — Comply with obligations

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_iso27701_a132_7bdc95ce43-isoiec-27701-a132-comply-with-obligations
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [ISO/IEC 27701 (Privacy Information Management)](https://support.icompaas.com/support/solutions/c_gen_iso27701) › [Obligations to PII principals](https://support.icompaas.com/support/solutions/folders/f_gen_cgeniso27701_obligationstopiiprincipals)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

ISO/IEC 27701 · Control A.1.3.2 · Priority: high · Component: Obligations to PII principals

### What this control covers

Provide means to meet legal, regulatory and business obligations to PII principals. Implementation: Document obligations, implement mechanisms for access, correction, erasure, objections, portability. Justification: Ensures ability to respond to rights requests and obligations.

### Why it matters

Encryption and key management make data unreadable to attackers and unintelligible under data-breach safe-harbour clauses — a meaningful regulatory benefit.

### How to implement

#### AWS

Default to **SSE-KMS** with customer-managed keys for S3/EBS/RDS/Secrets Manager. Use **S3 Bucket Keys** and **S3 Block Public Access** at the account level, and turn on **S3 Object Lock** on backup buckets for ransomware resilience.

#### Azure

Store secrets in **Key Vault** (HSM-backed where required) with soft-delete + purge protection; use **customer-managed keys** for Storage, SQL, and Azure Disk Encryption. Tag PII data via **Microsoft Purview**.

#### GCP

Use **Cloud KMS** with customer-managed encryption keys (CMEK) for BigQuery, GCS, and Compute. **Sensitive Data Protection** (DLP API) inspects/de-identifies PII at scale.

#### Google Workspace

Enable **client-side encryption** for Drive/Docs and turn on **Drive Labels + DLP** rules to prevent external sharing of regulated data classes.

#### 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

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

Signed policies, procedures, and registers document the safeguard. Service management or request-handling tickets prove timely handling. Focus: Comply with obligations.

### Quick checklist

-   Implement — Comply With Obligations
-   Document — Comply With Obligations
-   Ensure — Comply With Obligations

### Related articles on this site

-   [Ensure to Implement Identity and Access Management (IAM)](https://support.icompaas.com/support/solutions/articles/62000234479-ensure-to-implement-identity-and-access-management-iam-)
-   [NIST 800-171 3.1.9 Provide privacy and security notices consistent with applicable CUI rules.](https://support.icompaas.com/support/solutions/articles/62000229233-nist-800-171-3-1-9-provide-privacy-and-security-notices-consistent-with-applicable-cui-rules-)
-   [NIST 800-171 3.1.13 Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.](https://support.icompaas.com/support/solutions/articles/62000229245-nist-800-171-3-1-13-employ-cryptographic-mechanisms-to-protect-the-confidentiality-of-remote-access-s)
-   [NIST 800-171 3.13.8 Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.](https://support.icompaas.com/support/solutions/articles/62000229258-nist-800-171-3-13-8-implement-cryptographic-mechanisms-to-prevent-unauthorized-disclosure-of-cui-duri)