What this policy is
Extends supplier management to the technical supply chain — code dependencies, container images, build pipelines, SBOM tracking, and provenance verification.
Why every organization needs one
Software-supply-chain attacks (SolarWinds, Codecov, …) have made SBOM and provenance a core control. The policy is the basis for vendor demands and pipeline gating.
What a competent Supply Chain Security Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- SBOM generation + retention
- Dependency-update policy
- Image-signing + provenance verification
- Build-pipeline hardening
- 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_supply_chain_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 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.21 | Managing information security in the ICT supply chain | Organizational controls |
1 control across 1 framework 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.