# Information Security Policy - Source: https://support.icompaas.com/compliance/policy-docs/information-security-policy - Section: [Compliance](https://support.icompaas.com/compliance) › [Policy Documents](https://support.icompaas.com/compliance/policy-docs) › All policy documents - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **Policy Document**·23 mapped controls ## What this policy is The top-level statement of management's commitment to information security — the policy every other security policy in the organization derives its authority from. ISO 27001 calls this 'policies for information security' (Annex A.5.1) and the entire ISMS hinges on its existence, approval, and communication. ## Why every organization needs one Without a signed top-level policy, every downstream control is unmanaged: auditors cannot trace a single control back to executive authorisation, and personnel have no documented basis for what is and is not acceptable. ## What a competent Information Security Policy typically contains - Purpose and scope - Roles and responsibilities - Definitions - Information security objectives aligned to business strategy - Management commitment and authority - ISMS scope statement - Policy hierarchy and how topic-specific policies derive from it - 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_information_security_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](https://support.icompaas.com/compliance) 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.1](https://support.icompaas.com/compliance/iso-27001-2022/a-5-1-policies-for-information-security) | [Policies for information security](https://support.icompaas.com/compliance/iso-27001-2022/a-5-1-policies-for-information-security) | Organizational controls | | ISO/IEC 27001:2022 | [A.5.4](https://support.icompaas.com/compliance/iso-27001-2022/a-5-4-management-responsibilities) | [Management responsibilities](https://support.icompaas.com/compliance/iso-27001-2022/a-5-4-management-responsibilities) | Organizational controls | | ISO/IEC 27001:2022 | [A.5.32](https://support.icompaas.com/compliance/iso-27001-2022/a-5-32-intellectual-property-rights) | [Intellectual property rights](https://support.icompaas.com/compliance/iso-27001-2022/a-5-32-intellectual-property-rights) | Organizational controls | | ISO/IEC 27001:2022 | [A.5.36](https://support.icompaas.com/compliance/iso-27001-2022/a-5-36-compliance-with-policies-rules-and-standards-for-information-security) | [Compliance with policies, rules and standards for information security](https://support.icompaas.com/compliance/iso-27001-2022/a-5-36-compliance-with-policies-rules-and-standards-for-information-security) | Organizational controls | | ISO/IEC 27001:2022 | [A.6.3](https://support.icompaas.com/compliance/iso-27001-2022/a-6-3-information-security-awareness-education-and-training) | [Information security awareness, education and training](https://support.icompaas.com/compliance/iso-27001-2022/a-6-3-information-security-awareness-education-and-training) | People controls | | ISO/IEC 27001:2022 | [A.6.4](https://support.icompaas.com/compliance/iso-27001-2022/a-6-4-disciplinary-process) | [Disciplinary process](https://support.icompaas.com/compliance/iso-27001-2022/a-6-4-disciplinary-process) | People controls | | ISO/IEC 27001:2022 | [A.8.3](https://support.icompaas.com/compliance/iso-27001-2022/a-8-3-information-access-restriction) | [Information access restriction](https://support.icompaas.com/compliance/iso-27001-2022/a-8-3-information-access-restriction) | Technological controls | | ISO/IEC 27001:2022 | [A.8.24](https://support.icompaas.com/compliance/iso-27001-2022/a-8-24-use-of-cryptography) | [Use of cryptography](https://support.icompaas.com/compliance/iso-27001-2022/a-8-24-use-of-cryptography) | Technological controls | | ISO/IEC 27701:2025 | [A.1.3.5](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-5-modify-withdraw-consent) | [Modify/withdraw consent](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-5-modify-withdraw-consent) | Obligations to PII principals | | ISO/IEC 27701:2025 | [A.1.3.7](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-7-access-correction-erasure) | [Access / correction / erasure](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-7-access-correction-erasure) | Obligations to PII principals | | ISO/IEC 27701:2025 | [A.1.3.8](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-8-inform-third-parties) | [Inform third parties](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-8-inform-third-parties) | Obligations to PII principals | | ISO/IEC 27701:2025 | [A.1.3.10](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-10-handling-requests) | [Handling requests](https://support.icompaas.com/compliance/iso-27701-2025/a-1-3-10-handling-requests) | Obligations to PII principals | | ISO/IEC 27701:2025 | [A.1.4.5](https://support.icompaas.com/compliance/iso-27701-2025/a-1-4-5-pii-minimization-objectives) | [PII minimization objectives](https://support.icompaas.com/compliance/iso-27701-2025/a-1-4-5-pii-minimization-objectives) | Privacy by design / default | | ISO/IEC 27701:2025 | [A.1.5.2](https://support.icompaas.com/compliance/iso-27701-2025/a-1-5-2-basis-for-transfer) | [Basis for transfer](https://support.icompaas.com/compliance/iso-27701-2025/a-1-5-2-basis-for-transfer) | PII sharing, transfer & disclosure | | ISO/IEC 27701:2025 | [A.1.5.4](https://support.icompaas.com/compliance/iso-27701-2025/a-1-5-4-records-of-transfer) | [Records of transfer](https://support.icompaas.com/compliance/iso-27701-2025/a-1-5-4-records-of-transfer) | PII sharing, transfer & disclosure | | ISO/IEC 27701:2025 | [A.3.9](https://support.icompaas.com/compliance/iso-27701-2025/a-3-9-access-rights) | [Access rights](https://support.icompaas.com/compliance/iso-27701-2025/a-3-9-access-rights) | Security considerations | | ISO/IEC 27701:2025 | [A.3.26](https://support.icompaas.com/compliance/iso-27701-2025/a-3-26-use-of-cryptography) | [Use of cryptography](https://support.icompaas.com/compliance/iso-27701-2025/a-3-26-use-of-cryptography) | Security considerations | | ISO/IEC 42001:2023 | [A.2.2](https://support.icompaas.com/compliance/iso-42001-2023/a-2-2-policies-for-the-responsible-development-or-use-of-ai-systems) | [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) | Organizational controls | | ISO/IEC 42001:2023 | [A.4.2](https://support.icompaas.com/compliance/iso-42001-2023/a-4-2-resources-documentation) | [Resources documentation](https://support.icompaas.com/compliance/iso-42001-2023/a-4-2-resources-documentation) | Organizational controls | | ISO/IEC 42001:2023 | [A.6.2.4](https://support.icompaas.com/compliance/iso-42001-2023/a-6-2-4-data-acquisition) | [Data acquisition](https://support.icompaas.com/compliance/iso-42001-2023/a-6-2-4-data-acquisition) | Technological controls | | ISO/IEC 42001:2023 | [A.8.2](https://support.icompaas.com/compliance/iso-42001-2023/a-8-2-system-documentation-and-information-for-users) | [System documentation and information for users](https://support.icompaas.com/compliance/iso-42001-2023/a-8-2-system-documentation-and-information-for-users) | Organizational controls | | ISO/IEC 42001:2023 | [A.8.5](https://support.icompaas.com/compliance/iso-42001-2023/a-8-5-information-for-interested-parties) | [Information for interested parties](https://support.icompaas.com/compliance/iso-42001-2023/a-8-5-information-for-interested-parties) | Organizational controls | | ISO/IEC 42001:2023 | [A.9.4](https://support.icompaas.com/compliance/iso-42001-2023/a-9-4-intended-use-of-ai-systems) | [Intended use of AI systems](https://support.icompaas.com/compliance/iso-42001-2023/a-9-4-intended-use-of-ai-systems) | Organizational controls | 23 controls across 3 frameworks reference this policy. ## About this page This article is part of the iCompaas [Policy Documents](https://support.icompaas.com/compliance/policy-docs) 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. ## Related compliance guidance - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): SOC 2 auditors test that policies like this one exist, are approved, and are reviewed on schedule; the guide lists the full set. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 clause 5.2 and Annex A.5.1 require a documented, approved policy set; the guide shows how it fits the ISMS.