A.7.5 Physical
Protecting against physical and environmental threats
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 (26)
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
- PE-3mostlycovers — A.7.5's broad mandate to prevent/reduce physical and environmental threat consequences accounts for the bulk of PE-3's physical access enforcement, verification, ingress/egress control, and logging requirements; a residual of scoped facility-area controls sits outside the source.
- PE-13partialcovers — A.7.5's broad requirement to protect against physical/environmental threats (including fire) accounts for a slice of PE-13's specific fire-detection-and-suppression mandate, but the bulk of the target's prescriptive implementation, maintenance, and independent-power details sit outside the source.
- PE-14partialcovers — A.7.5's broad objective to prevent/reduce physical/environmental threats accounts for only a slice of PE-14's specific requirements to maintain and monitor defined temperature/humidity levels; the bulk of the target's parametric implementation detail sits outside the source.
- PE-15partialcovers — A.7.5's broad mandate to prevent/reduce physical-and-environmental consequences accounts for a slice of PE-15's specific water-leakage valve requirement, but the bulk of the target's concrete mechanism (master shutoff valves, accessibility, verification, key-personnel knowledge) sits in other controls such as PE-3 or PE-13.
- PE-23partialcovers — A.7.5's requirement to prevent/reduce physical and environmental threat consequences accounts for the bulk of PE-23's planning and risk-strategy consideration of those same hazards; a residual slice of pure site-selection geography remains uncovered by the ISO control's focus on protective measures.
- PE-9partialcovers — A.7.5's broad mandate to protect against physical/environmental threats addresses a slice of PE-9 (power-specific damage protection) but leaves the bulk of the target's explicit power-equipment-and-cabling requirements uncovered.
Aligned NIST CSF 2.0 outcomes (18)
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
- PR.IR-02fullcovers — The ISO control's risk-based identification and implementation of safeguards against physical and environmental threats directly fulfills the CSF outcome of protecting technology assets from environmental threats.
- DE.CM-02domain mandateimplements — A.7.5's physical/environmental protection directly operationalizes monitoring the physical environment for adverse events as a core means within its domain (though not the only means, and not explicitly named by the control text)
Related weaknesses / CWE (4)
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).
Mitigated MITRE ATT&CK techniques (3111)
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
- T1486mostlyresponds — A.7.5's purpose is to prevent/reduce consequences of physical/environmental events and its guidance explicitly requires implementing safeguards (fire detection/suppression, flood detection/pumps, surge protection) plus monitoring for changes in threats; this directly matches the EVENT-LANE definition of `responds` (technique ran; contained and eradicated once underway) for a realized ransomware encryption event by bounding damage and enabling eradication via early detection and suppression before full propagation/impact.
- T1200partialdetects — A.7.5 explicitly calls for early detection systems (fire/flood sensors, random inspections for explosives/weapons on personnel/vehicles/goods entering facilities) that surface physical introduction attempts; this covers only a narrow slice of T1200 vectors such as obvious hardware carried by people, not passive taps, DMA devices, or wireless implants once inside.
- T1200partialprevents — A.7.5 requires risk-driven physical safeguards (site selection, inspections, environmental sensors) that can stop unauthorized hardware additions at the facility perimeter or during entry; this covers only a minority slice of the technique because it is silent on post-entry abuse of added devices already inside the authorized perimeter and on non-facility vectors such as supply-chain or remote-site insertions.
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.