A.5.22 Organizational
Monitoring, review and change management of supplier services
Structured attributes from ISO/IEC 27002:2022 — control type · CIA properties · cybersecurity concept · operational capability · security domain. What do these mean?
Mapped NIST 800-53 r5 controls (14)
Our reading (mostly llm_verified) of how this ISO control and each NIST 800-53 control relate. Not an ISO or NIST product.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- CA-7domain mandategoverns — A.5.22's governance of supplier service monitoring, review, and change directly requires the kind of ongoing metrics-driven system-level continuous monitoring that ca-7 operationalizes within the supplier-agreement domain
- SR-2domain mandategoverns — A.5.22's mandate to monitor/review/change supplier services to maintain agreed security levels directly sits inside the supply-chain risk management domain that SR-2 requires a plan for, without naming the specific plan artifact.
- SR-6domain mandategoverns — Both controls establish ongoing supplier assessment and review activities to verify that external providers continue to meet security and service obligations.
Aligned NIST CSF 2.0 outcomes (20)
NIST CSF 2.0 outcomes this ISO control aligns with — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- DE.CM-06mostlycovers — A.5.22's monitoring/review/change-management of supplier services to maintain agreed security levels directly accounts for the bulk of DE.CM-06's requirement to monitor external providers for adverse events; a residual of DE.CM-06's broader 'potentially adverse events' scope (including non-contractual indicators) sits outside A.5.22's agreement-centric focus
- GV.SC-03domain mandategoverns — GV.SC-03 names the integration of supply-chain risk into enterprise processes; A.5.22's monitoring/review/change-management of supplier services is a principal technical means that sits inside that exact domain, reached by subject membership rather than explicit naming of the requirement.
Related OWASP ASVS 5.0 requirements (6)
Application-security verification requirements (OWASP ASVS 5.0) this ISO control aligns with; links open the ASVS chapter. Our analysis (mostly llm_verified) — many ISO controls have no ASVS counterpart.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Related weaknesses / CWE (3236)
Weakness classes this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- CWE-1104partialfinds — A.5.22's monitoring of supplier relationships can surface unmaintained components through supplier disclosures (end-of-life announcements, change notifications under items b/c), audits (item e), and review of supplier reports (item d), but its reach is disclosure-based and bounded by what the supplier relationship surfaces — it has no source-level or runtime reach into the supplier's components, so unmaintained components that are not formally announced or caught in audit remain invisible, leaving a large unnamed remainder.
- CWE-1329partialfinds — A.5.22's supplier audits, service reports, and vulnerability identification can surface unsupported or unpatchable components, but only those covered by supplier agreements or disclosed by suppliers, which is a minority of latent CWE-1329 instances.
- CWE-1357partialfinds — Ongoing monitoring and change management of supplier services mitigates drift in component trustworthiness.
- CWE-284partialfinds — Ongoing audits and performance reviews of suppliers detect and correct situations where access controls or privilege assignments are weaker than contractually required, limiting an attacker's ability to exploit improper access control in the supplier's environment.
- CWE-623partialfinds — A.5.22's supplier audits and vulnerability-identification requirement can surface disclosed or reported ActiveX-control flaws, but without source-level or runtime security testing it misses most latent unlisted instances of CWE-623.
Mitigated MITRE ATT&CK techniques (457)
Adversary techniques (MITRE ATT&CK Enterprise) this ISO control helps mitigate; links open attack.mitre.org. Our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Prevented OWASP Web Top 10 (2025) risks (7)
OWASP Web Top 10 (2025) risk categories this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- A03partialfinds — A.5.22 explicitly requires monitoring supplier changes, conducting audits of suppliers/sub-suppliers, reviewing audit trails/records/incidents/vulnerabilities, and evaluating security levels, which surfaces vulnerable/outdated/compromised dependencies and related supply-chain issues (the category's largest slice) but does not address build pipelines or signing infrastructure at all.
- A03partialremoves — A.5.22 requires monitoring/review of supplier services plus follow-up actions on identified issues (including new/changed controls for incidents, vulnerability management, and ensuring adequate security levels), which can lead to remediation of vulnerable/outdated supplier dependencies or sub-supplier issues but does not itself perform the removal and stops short of build pipelines or signing infrastructure.
- A09partialfinds — A.5.22 explicitly requires monitoring supplier service performance, reviewing reports/audit trails/events, conducting audits, identifying vulnerabilities, and managing incidents, which surfaces logging/alerting failures when they affect the supplier relationship or service delivery.
Control IDs, short titles and the structured attribute table (control type, CIA properties, cybersecurity-concept, operational capability, security domain) are facts from ISO/IEC 27001:2022 Annex A / ISO/IEC 27002:2022. The full implementation guidance prose lives in ISO/IEC 27002:2022 — not reproduced here. Cross-walks to NIST 800-53, NIST CSF 2.0, OWASP ASVS, CWE, MITRE ATT&CK and OWASP Web Top 10 are our own analysis (mostly llm_verified), not an ISO, NIST, MITRE or OWASP product — how ours compare.