A.5.20 Organizational
Addressing information security within supplier agreements
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 (15)
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
- PS-7mostlycovers — A.5.20's focus on embedding and maintaining information security requirements (including personnel security aspects) within supplier agreements accounts for the bulk of PS-7's external-provider personnel-security obligations, but leaves a residual slice of general (non-information-security) personnel screening, roles documentation, and notification mechanics that sit outside A.5.20's explicit scope.
- SA-9domain mandategoverns — Both controls require formal agreements that define security obligations, access rules, monitoring rights, and incident responsibilities when an organization relies on external providers.
- SR-3domain mandategoverns — A.5.20's policy-level mandate to maintain agreed security levels in supplier agreements directly requires establishing processes to identify/address supply-chain weaknesses (the core of SR-3), operating as domain-mandate governance over the technical control without naming it verbatim.
Aligned NIST CSF 2.0 outcomes (23)
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-05fullcovers — Embedding security obligations, access rules, incident procedures, and audit rights directly into supplier contracts satisfies the CSF requirement to establish and integrate cybersecurity requirements into supplier agreements.
- GV.SC-03domain mandategoverns — GV.SC-03 names the outcome of integrating supply-chain cybersecurity risk into enterprise processes; A.5.20 directly operationalizes that outcome by mandating supplier agreements address information security, which is the principal technical means within the supply-chain-risk domain.
- ID.RA-10domain mandategoverns — A.5.20's governance mandate to maintain agreed security levels in supplier relationships directly encompasses the supplier assessment outcome named in ID.RA-10 as a core means within that domain
Related OWASP ASVS 5.0 requirements (10)
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 (3237)
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-359partialprevents — A.5.20 carries specific security requirements into supplier agreements — PII handling (d), access control (e), information transfer controls (w), secure disposal (y) — and where the supplier implements them, CWE-359 is prevented; but the clause does not itself implement those controls, the supplier can still fail to implement them properly, and not all pathways to PII exposure (e.g. logging PII in application code) are reached by the contractual terms, so only a minority of instances are kept from arising.
Mitigated MITRE ATT&CK techniques (429)
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 (6)
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.