# Risk Management Policy - Source: https://support.icompaas.com/compliance/policy-docs/risk-management-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**·9 mapped controls ## What this policy is Defines the risk-management methodology — how risks are identified, assessed, treated (avoid / mitigate / transfer / accept), and reviewed — and who owns each step. ## Why every organization needs one Every ISMS, every privacy programme, every BCP grounds itself in a risk register. The policy is the procedural backbone that makes the register defensible. ## What a competent Risk Management Policy typically contains - Purpose and scope - Roles and responsibilities - Definitions - Risk-assessment methodology (qualitative, quantitative) - Acceptable-risk threshold + sign-off authority - Treatment-plan tracking - Re-assessment cadence - 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_risk_management_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.8](https://support.icompaas.com/compliance/iso-27001-2022/a-5-8-information-security-in-project-management) | [Information security in project management](https://support.icompaas.com/compliance/iso-27001-2022/a-5-8-information-security-in-project-management) | Organizational controls | | ISO/IEC 27701:2025 | [A.1.2.6](https://support.icompaas.com/compliance/iso-27701-2025/a-1-2-6-privacy-impact-assessment) | [Privacy impact assessment](https://support.icompaas.com/compliance/iso-27701-2025/a-1-2-6-privacy-impact-assessment) | Conditions for collection and processing | | ISO/IEC 27701:2025 | [A.1.4.2](https://support.icompaas.com/compliance/iso-27701-2025/a-1-4-2-limit-collection) | [Limit collection](https://support.icompaas.com/compliance/iso-27701-2025/a-1-4-2-limit-collection) | Privacy by design / default | | ISO/IEC 27701:2025 | [A.1.4.3](https://support.icompaas.com/compliance/iso-27701-2025/a-1-4-3-limit-processing) | [Limit processing](https://support.icompaas.com/compliance/iso-27701-2025/a-1-4-3-limit-processing) | Privacy by design / default | | ISO/IEC 27701:2025 | [A.2.4.4](https://support.icompaas.com/compliance/iso-27701-2025/a-2-4-4-pii-transmission-controls) | [PII transmission controls](https://support.icompaas.com/compliance/iso-27701-2025/a-2-4-4-pii-transmission-controls) | Privacy by design / default (processors) | | ISO/IEC 42001:2023 | [A.5.2](https://support.icompaas.com/compliance/iso-42001-2023/a-5-2-process-for-impact-assessment) | [Process for impact assessment](https://support.icompaas.com/compliance/iso-42001-2023/a-5-2-process-for-impact-assessment) | Organizational controls | | ISO/IEC 42001:2023 | [A.5.5](https://support.icompaas.com/compliance/iso-42001-2023/a-5-5-assessment-of-societal-impact) | [Assessment of societal impact](https://support.icompaas.com/compliance/iso-42001-2023/a-5-5-assessment-of-societal-impact) | Organizational controls | | ISO/IEC 42001:2023 | [A.7.4](https://support.icompaas.com/compliance/iso-42001-2023/a-7-4-quality-of-data) | [Quality of data](https://support.icompaas.com/compliance/iso-42001-2023/a-7-4-quality-of-data) | Technological controls | | ISO/IEC 42001:2023 | [A.10.3](https://support.icompaas.com/compliance/iso-42001-2023/a-10-3-suppliers) | [Suppliers](https://support.icompaas.com/compliance/iso-42001-2023/a-10-3-suppliers) | Organizational controls | 9 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.