# ISO/IEC 27701:2025 A.1.3.4 — Providing info to PII principals

- Source: https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-4-providing-info-to-pii-principals
- Section: [Compliance](https://support.icompaas.com/compliance) › [ISO/IEC 27701:2025 PIMS Controls](https://support.icompaas.com/compliance/iso-27701-2025) › Obligations to PII principals
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**ISO/IEC 27701:2025**·Annex A `A.1.3.4`·high·Component: **Obligations to PII principals**

## What this control requires

> Provide clear, accessible information identifying controller and describing processing. Implementation: Publish privacy notices; ensure "just-in-time" and persistent access. Justification: Supports informed consent and rights exercise.
> 
> — ISO/IEC 27701:2025, Annex A A.1.3.4

### In plain English

Provide clear, accessible information identifying controller and describing processing. In practice, this means you can prove you implement providing info to pii principals-level controls on a defined cadence.

## Why it matters

ISO 27701 is the international way to evidence the GDPR principle of accountability: certified PIMS controls translate directly into the records, contracts and rights-handling that supervisory authorities want, and into the privacy-engineering evidence SOC 2 + Privacy auditors and enterprise procurement teams ask for.

This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

## What an auditor looks for

PIMS auditors expect ISO 27001 to be implemented first and then the 27701-additional controls tested. For PII controllers they look at lawful-basis and rights-handling evidence; for PII processors they look at customer-instructions, sub-processor controls and return/transfer/disposal evidence.

Within **Obligations to PII principals**, the assessor will trace your implementation back to the catalogue reference (Annex A A.1.3.4) and look for objective evidence on the latest two assessment cycles.

## How to implement

#### Policy Management

**Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

### Operational checklist

-   **Implement.** Document the trigger, the owner and the cadence.
-   **Ensure.** Document the trigger, the owner and the cadence.
-   **Provide.** Document the trigger, the owner and the cadence.
-   **Scope:** providing info to pii principals.

## Evidence to collect

-   **Ticketing Workflow.** `ticketing_workflow` evidence
-   **Policy Document.** A signed and version-controlled policy / standard / procedure document.

Signed policies, procedures, and registers document the safeguard. Service management or request-handling tickets prove timely handling. Focus: Providing info to PII principals.

## Common pitfalls

-   Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

## How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

-   [**India DPDP Act 2023 DS-005** — Consent Withdrawal Mechanism](https://support.icompaas.com/compliance/india-dpdp-act-2023/ds-005-consent-withdrawal-mechanism)
-   [**SOC 2 (2017 TSC) P3.2** — Consent Management for Personal Information Collection](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p3-2-consent-management-for-personal-information-collection)
-   [**GDPR Article 2** — Material Scope](https://support.icompaas.com/compliance/gdpr/article-2-material-scope)

## Related controls in ISO/IEC 27701:2025

-   [**Annex A A.1.3.3** — Information for PII principals](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-3-information-for-pii-principals)
-   [**Annex A A.1.3.9** — Providing copy](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-9-providing-copy)
-   [**Annex A A.1.3.2** — Comply with obligations](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-2-comply-with-obligations)
-   [**Annex A A.1.3.6** — Mechanism to object](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-6-mechanism-to-object)
-   [**Annex A A.1.3.10** — Handling requests](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-10-handling-requests)
-   [**Annex A A.1.2.7** — Contracts with PII processors](https://support.icompaas.com/compliance/iso-27701-2025/a-1-2-7-contracts-with-pii-processors)

## References

-   [ISO/IEC JTC 1/SC 27 — ISO/IEC 27701:2025](https://www.iso.org/standard/85819.html)
-   Catalogue identifier: `Annex A A.1.3.4`

Topics: data protectiongovernance riskprivacy managementpolicy management