A.5.19 Organizational
Information security in supplier relationships
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 (23)
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.19's broad requirement to maintain agreed security levels in all supplier relationships fully accounts for the external-provider compliance, notification, and documentation aspects of PS-7, but leaves a residual slice (explicitly establishing the organization's own internal personnel security roles/responsibilities that providers must then follow) uncovered by the supplier-relationship control.
- SA-9mostlycovers — A.5.19's broad requirement to maintain agreed security levels in all supplier relationships accounts for the bulk of SA-9's provider-compliance and oversight mandates, but leaves a residual slice (explicit privacy requirements, defined monitoring processes/techniques, and user-role documentation) uncovered by the ISO control's wording.
- SR-2domain mandategoverns — Both controls require the organization to develop and maintain a documented plan that identifies, assesses, and manages supply-chain security risks throughout the supplier lifecycle.
- SR-3domain mandategoverns — Both controls mandate the selection and implementation of specific security controls and processes that suppliers must satisfy before products or services are accepted.
- SR-6domain mandategoverns — Both controls require ongoing monitoring, assessment, and review of supplier performance against established security requirements.
- SR-8domain mandategoverns — A.5.19's broad governance mandate for maintaining agreed security levels in all supplier relationships directly encompasses the supply-chain notification agreements required by SR-8 as one subject within that domain.
Aligned NIST CSF 2.0 outcomes (17)
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-01mostlycovers — The ISO control establishes a comprehensive supplier-relationship policy and lifecycle processes that directly instantiate the CSF requirement for a documented supply-chain risk-management program.
- GV.SC-05mostlycovers — By requiring security requirements to be defined, communicated, and embedded in supplier contracts and onboarding, the control fulfills the CSF outcome of integrating cybersecurity requirements into supplier agreements.
- GV.SC-06mostlycovers — The guidance on pre-engagement due diligence, supplier evaluation, and risk assessment before formal relationships begin aligns with the CSF expectation for planning and due diligence prior to supplier onboarding.
- GV.SC-07mostlycovers — The control’s explicit risk-assessment steps for supplier products, services, and personnel map to the CSF requirement to understand, record, and prioritize risks posed by each supplier.
- GV.SC-10mostlycovers — Detailed termination procedures—including de-provisioning, asset return, and ongoing confidentiality—directly satisfy the CSF requirement for post-contract supply-chain risk-management provisions.
- GV.SC-08partialcovers — A.5.19's broad requirement to maintain agreed security levels in supplier relationships can include clauses on incident planning/response/recovery, addressing a slice of GV.SC-08 but not its full scope of explicit inclusion and operational integration in those activities.
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 (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-1104partialprevents — A.5.19's supplier evaluation and selection processes (b, c, e, f) can require maintenance status as a criterion, keeping some unmaintained components out at procurement; but the clause governs the supplier relationship framework, not the technical decision to use a specific component, so an organization under it can still acquire unmaintained components within an otherwise-approved supplier's offerings or through channels the relationship processes don't reach.
- CWE-1357partialblocks — Supplier-relationship controls directly address vetting and trust of external components.
Mitigated MITRE ATT&CK techniques (420)
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 (4)
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
- A03partialremoves — A.5.19 explicitly requires identifying, assessing, mitigating non-compliance, handling incidents, and implementing secure termination/transfer/recovery processes that include replacing or switching suppliers (including advance identification of alternatives), which removes the vulnerable/outdated/compromised dependency or pipeline element from the organization's environment.
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.