A.5.23 Organizational
Information security for use of cloud 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
- AC-20partialcovers — A.5.23 addresses the full slice of cloud-service security requirements within ac-20's broader external-system usage policy, but leaves the non-cloud external systems, trust-relationship establishment, and outright prohibition options uncovered.
- SA-9domain mandateimplements — Both controls require organizations to define security responsibilities, obtain assurance, and manage risks when relying on external service providers for information processing.
Aligned NIST CSF 2.0 outcomes (27)
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
- GV.SC-01domain mandateimplements — The ISO control establishes a dedicated program, policies, and processes for managing cybersecurity risks arising from cloud service providers, which directly fulfills the CSF outcome of creating a supply-chain risk management program.
- GV.SC-05domain mandateimplements — By requiring the organization to define security requirements, responsibilities, and controls in cloud service agreements, the ISO control satisfies the CSF outcome of embedding cybersecurity requirements into supplier contracts.
- GV.SC-06domain mandateimplements — A.5.23 operationalizes the supplier/cloud due-diligence outcome that GV.SC-06 names within the broader governance/supply-chain-risk domain; the link is by subject membership rather than explicit citation of planning steps.
- GV.SC-07domain mandateimplements — The ISO control mandates risk assessments, residual-risk acceptance, and ongoing monitoring of cloud providers, aligning with the CSF outcome of understanding, recording, and prioritizing supplier risks.
Related OWASP ASVS 5.0 requirements (4)
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 (3234)
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-1357partialblocks — Cloud-service security partially overlaps when the untrusted component is cloud-hosted.
Mitigated MITRE ATT&CK techniques (3315)
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).
Why these map — rationale
- T1530mostlyprevents — Mandating contractual controls on data location, encryption, and access restrictions directly constrains an attacker’s capacity to collect data stored in cloud object storage without detection.
- T1199partialprevents — A.5.23 directly addresses cloud-based trusted relationships — a primary T1199 vector — by requiring review of cloud service agreements, definition of access controls, management of sub-contracting, and ongoing monitoring of cloud providers, but it is a governance/process control that mandates these capabilities rather than implementing them, and it does not cover non-cloud third-party vectors (HVAC, IT contractors, managed security providers) that T1199 also exploits.
Prevented OWASP Web Top 10 (2025) risks (3)
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).
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.