What this policy is
States the organization's commitment to comply with applicable laws, regulations, contractual obligations, and industry standards — and defines how compliance status is tracked and reported.
Why every organization needs one
Boards and large customers expect a documented compliance posture. The policy is the artefact that makes that posture defensible.
What a competent Compliance Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Applicable-obligation register ownership
- Compliance-monitoring cadence
- Non-compliance escalation path
- External-reporting obligations
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_compliance_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.5.6 | Contact with special interest groups | Organizational controls |
| ISO/IEC 27001:2022 | A.5.31 | Legal, statutory, regulatory and contractual requirements | Organizational controls |
| ISO/IEC 27001:2022 | A.5.36 | Compliance with policies, rules and standards for information security | Organizational controls |
| ISO/IEC 27701:2025 | A.1.3.2 | Comply with obligations | Obligations to PII principals |
| ISO/IEC 27701:2025 | A.1.4.3 | Limit processing | Privacy by design / default |
| ISO/IEC 27701:2025 | A.1.4.8 | Retention schedule | Privacy by design / default |
| ISO/IEC 27701:2025 | A.1.5.2 | Basis for transfer | PII sharing, transfer & disclosure |
| ISO/IEC 27701:2025 | A.2.2.6 | Customer obligations | Conditions for collection and processing (processors) |
| ISO/IEC 27701:2025 | A.2.2.7 | Records related to processing PII | Conditions for collection and processing (processors) |
| ISO/IEC 27701:2025 | A.2.5.4 | Records of PII disclosures | PII sharing, transfer & disclosure (processors) |
| ISO/IEC 27701:2025 | A.2.5.6 | Legally binding disclosures | PII sharing, transfer & disclosure (processors) |
| ISO/IEC 27701:2025 | A.2.5.7 | Disclosure of subcontractors | PII sharing, transfer & disclosure (processors) |
| ISO/IEC 27701:2025 | A.2.5.8 | Engagement of subcontractor | PII sharing, transfer & disclosure (processors) |
| ISO/IEC 27701:2025 | A.3.13 | Legal, statutory, regulatory & contractual reqs | Security considerations |
14 controls across 2 frameworks reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.