# ISO/IEC 27701:2025 A.3.16 — Compliance with policies

- Source: https://support.icompaas.com/compliance/iso-27701-2025/a-3-16-compliance-with-policies
- Section: [Compliance](https://support.icompaas.com/compliance) › [ISO/IEC 27701:2025 PIMS Controls](https://support.icompaas.com/compliance/iso-27701-2025) › Security considerations
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**ISO/IEC 27701:2025**·Annex A `A.3.16`·high·Component: **Security considerations**

## What this control requires

> Regularly review compliance with policies and standards. Implementation: Run compliance reviews, monitoring and periodic checks. Justification: Ensures adherence to governance and operational rules.
> 
> — ISO/IEC 27701:2025, Annex A A.3.16

### In plain English

Regularly review compliance with policies and standards. In practice, this means you can prove you implement compliance with policies-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 **Security considerations**, the assessor will trace your implementation back to the catalogue reference (Annex A A.3.16) 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.
-   **Monitor.** Document the trigger, the owner and the cadence.
-   **Scope:** compliance with policies.

## Evidence to collect

-   **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.
-   **Policy Document.** A signed and version-controlled policy / standard / procedure document.

Signed policies, procedures, and registers document the safeguard. Infrastructure posture tooling (AWS/Azure/GCP configuration, encryption, backup, logging) verifies technical enforcement. Focus: Compliance with policies.

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

-   [**SOC 2 (2017 TSC) CC4.1** — Control Monitoring](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc4-1-control-monitoring)
-   [**NIST SP 800-171 Rev. 3 3.11.4** — Risk Response](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-11-4-risk-response)
-   [**ISO/IEC 27001:2022 A.8.15** — Logging](https://support.icompaas.com/compliance/iso-27001-2022/a-8-15-logging)
-   [**ISO/IEC 42001:2023 A.2.2** — Policies for the responsible development or use of AI systems](https://support.icompaas.com/compliance/iso-42001-2023/a-2-2-policies-for-the-responsible-development-or-use-of-ai-systems)
-   [**NIST SP 800-53 Rev. 5 CM-11** — User-Installed Software](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-11-user-installed-software)

## Related controls in ISO/IEC 27701:2025

-   [**Annex A A.3.15** — Independent review](https://support.icompaas.com/compliance/iso-27701-2025/a-3-15-independent-review)
-   [**Annex A A.3.18** — Confidentiality agreements](https://support.icompaas.com/compliance/iso-27701-2025/a-3-18-confidentiality-agreements)
-   [**Annex A A.3.3** — Information security policies](https://support.icompaas.com/compliance/iso-27701-2025/a-3-3-information-security-policies)
-   [**Annex A A.3.25** — Logging](https://support.icompaas.com/compliance/iso-27701-2025/a-3-25-logging)
-   [**Annex A A.3.5** — Classification of information](https://support.icompaas.com/compliance/iso-27701-2025/a-3-5-classification-of-information)
-   [**Annex A A.3.4** — Information security roles & responsibilities](https://support.icompaas.com/compliance/iso-27701-2025/a-3-4-information-security-roles-responsibilities)

## References

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

Topics: governance risklogging monitoringcontinuous monitoringpolicy management