A.5.10 Organizational
Acceptable use of information and other associated assets
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 (18)
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
- MP-7partialcovers — A.5.10's broad acceptable-use rules for information and assets address a slice of MP-7's media-use restrictions and prohibitions (especially the portable-device owner rule), but leave the bulk of MP-7's specific media-type, system, and procedural controls uncovered.
- PS-6partialcovers — A.5.10's broad requirement to ensure assets are appropriately used and handled accounts for the slice of PS-6 that concerns acceptable-use content within access agreements, but leaves the bulk of PS-6 (developing, documenting, reviewing, signing, and re-signing formal access agreements) uncovered.
- PL-4explicit mandateimplements — Both controls require an organization-defined set of rules that explicitly state permitted and prohibited behaviors for users handling organizational assets.
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
- GV.PO-01domain mandateimplements — The ISO control requires creation and communication of a topic-specific acceptable-use policy that defines expected behaviors and permitted uses, directly satisfying the CSF outcome of establishing policy for managing cybersecurity risks based on organizational context and priorities.
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).
Mitigated MITRE ATT&CK techniques (3296)
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
- T1052partialprevents — A.5.10 establishes an acceptable-use policy that can prohibit unauthorized use of removable media and make personnel aware of monitoring, which shapes user behaviour around physical exfiltration; however, it is a policy/awareness control that cannot physically block USB ports, cannot stop adversary-introduced media (e.g., USBferry-style drops), and cannot move the rate of non-compliance to zero, leaving a named remainder analogous to the A.6.3 vs T1566.001 anchor.
- T1091partialprevents — A.5.10 establishes acceptable-use rules and raises awareness about handling of information assets, which can include restrictions on unauthorized removable media and personal device connections, measurably reducing the rate at which personnel insert unknown media or connect phones via USB; but it is a policy/awareness control that does not technically block USB ports, disable Autorun, or stop firmware-level media compromise, so the technique remains executable.
- T1176partialprevents — A.5.10's acceptable-use policy can prohibit unauthorized extension installation and communicate that prohibition to users, reducing the rate at which they install malicious extensions themselves; but it is a policy/awareness mechanism that cannot stop marketplace compromise, social engineering of users, or extensions installed by an adversary who already has access, so the technique is reduced, not closed.
- T1204partialprevents — A.5.10 establishes a topic-specific policy on acceptable use that can include prohibitions on executing untrusted code, opening suspicious files, or installing unauthorized software — rules that, if followed, constrain T1204's reliance on user action. But it is a policy/awareness instrument, not an enforcement mechanism: users can still violate it, and the clause does not block execution at the technical level, so the reduction is a rate rather than a closure.
- T1204.002partialprevents — A.5.10's topic-specific policy on acceptable use can include provisions about not opening suspicious or unauthorized files, and users made aware of these expectations may be less likely to execute malicious files; however, it is a policy/awareness mechanism rather than training or technical prevention, so users still open malicious files and the reduction is a rate, not a closure.
- T1204.003partialprevents — An acceptable use policy that includes rules on permitted sources of images and verification expectations measurably lowers the rate at which users deploy unverified or backdoored cloud/container images, but cannot fully prevent it because the technique specifically relies on users not realizing the image is malicious, and a policy relies on users reading and following it.
- T1552partialprevents — A.5.10's topic-specific policy on acceptable use can include rules prohibiting insecure credential storage (plaintext files, shell history, registry entries) and mandating secure handling, so following the policy reduces the surface for T1552; but it is a policy/awareness control that communicates expectations rather than enforces them, leaving a named remainder of credentials stored insecurely despite the policy.
- T1552.008partialprevents — A.5.10's acceptable-use policy can prohibit users from sharing credentials in chat services, removing the primary vector where credentials end up in chat logs; however, it does not prevent adversaries from collecting credentials already present in chat, accessing chat services via compromised accounts or admin portals, or abusing integration tools, and even the user-sharing vector depends on policy compliance rather than a technical mechanism.
- T1566.002partialprevents — A.5.10 establishes and communicates a topic-specific policy on acceptable use that includes expected and unacceptable behaviours from an information security perspective, which can include not clicking suspicious links; this raises user awareness and can lower click rates, but it is a policy/awareness mechanism that cannot eliminate user compliance failures or stop delivery of the technique.
- T1566.003partialprevents — A.5.10 establishes a topic-specific policy on acceptable use that can prohibit employees from using personal webmail or social media on work computers and from engaging with unknown third-party contacts for work purposes, which constrains the delivery and consumption surface of T1566.003; however, the technique operates through services outside enterprise control and the policy cannot stop the adversary from sending the message or compel compliance, so what is prevented is a slice of the technique's success path rather than the technique itself.
- T1598partialprevents — A.5.10 establishes a topic-specific policy on acceptable use that includes expected/unacceptable behaviours and permitted/prohibited use of information assets; if followed, users would not divulge credentials or sensitive information to unsolicited requesters, reducing phishing-for-information success. But it is a governance/policy control — it does not prevent the phishing attempt itself, depends on user compliance, and is weaker than active training (A.6.3) which holds partial on the related T1566.001.
- T1598.001partialprevents — A.5.10's acceptable-use policy can direct personnel not to discuss organizational services, policies or environment with unknown parties on personal channels, which lowers the rate at which a spearphishing-for-information attempt succeeds; it cannot stop the messages from being sent or received, and employees may still respond, so the reduction is a rate rather than a closure.
- T1598.004partialprevents — A.5.10 establishes a topic-specific policy on acceptable use that can include guidance on not divulging sensitive information via phone and verifying caller identity, which moves the rate at which personnel comply with vishing pretexts but cannot move it to zero — the same shape `partial` describes on a human-mechanism control, and the calls themselves are not stopped.
- T1684partialprevents — A.5.10 establishes an acceptable-use policy and communicates security requirements to personnel, which sets rules (e.g., do not share credentials, verify requests through official channels) that, if followed, constrain some social-engineering outcomes; however, the mechanism is policy communication rather than active training in recognition, so users can still be manipulated into violating the policy, leaving a substantial remainder where social engineering succeeds.
Prevented OWASP Web Top 10 (2025) risks (1)
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.