A.8.1 Technological
User end point devices
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 (24)
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-19mostlycovers — Both controls establish requirements for managing and securing mobile and personally-owned endpoint devices, including registration, access controls, encryption, remote wipe, and separation of personal versus organizational use.
- CM-6mostlycovers — A.8.1's focus on securing endpoint devices (including their configuration against risks) accounts for the bulk of CM-6's requirement when the component is a user endpoint device, but leaves a real residual for non-endpoint system components and for the full organizational baseline/deviation process that CM-6 demands universally.
Aligned NIST CSF 2.0 outcomes (25)
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).
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 (3235)
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-512mostlyremoves — A.8.1 mandates protection against malware (item i) and remote disabling/deletion (item j) on endpoint devices; applied to a system that previously lacked it, anti-malware tools would scan and remove most existing spyware, with the remainder being sophisticated or zero-day spyware that evades detection — a bounded, nameable class.
- CWE-1125partialblocks — A.8.1 hardens user endpoints through software restrictions, patching, firewalls, access controls, malware protection, and port/wireless disabling, which blocks some exploitation of an excessive endpoint attack surface, but it cannot stop exploitation of the remaining permitted browser/application and user-facing surface.
- CWE-1266partialblocks — A.8.1's storage device encryption requirement (item h) blocks exploitation of CWE-1266 for user endpoint devices by ensuring data is encrypted at rest, so a decommissioned device with failed scrubbing still holds unreadable data; however, this is one item among many in a broad endpoint-policy clause, the underlying weakness (the product's missing scrubbing capability) is not addressed, and encryption can be bypassed via key recovery or pre-encryption data residue.
- CWE-256partialblocks — A.8.1's storage device encryption (item h) blocks exploitation of a plaintext password when the attacker reads the storage medium directly (the file is encrypted at rest), but the password remains plaintext in application memory and accessible via any application-level path, so the weakness is masked over only a portion of its existence — analogous to the A.8.20 vs CWE-523 partial-block pattern.
- CWE-312partialblocks — A.8.1 mandates access controls (g), physical protection (c), and remote disabling/deletion/lockout (j) for endpoint devices, which block some exploitation of cleartext storage by preventing unauthorized access to the device; however, the weakness remains present in the storage medium and can be exploited by removing the drive or bypassing access controls, and the storage device encryption item (h) is a removes/prevents mechanism rather than a blocks mechanism.
- CWE-313partialblocks — A.8.1 mandates a policy for secure configuration and handling of endpoint devices, including storage encryption, but the control itself does not stop an attacker with access to a file or disk from reading cleartext data that already exists; the weakness remains exploitable unless the encryption sub-control is separately implemented and enforced.
- CWE-314partialblocks — A.8.1's storage device encryption (h) and access controls (g) block exploitation of cleartext registry data when the device is at rest (theft, disk removal, offline attack) and against unauthorized local users, but the weakness remains present and is still readable by any process running with sufficient privilege on the live system -- malware, a logged-in attacker, or code executing as the user -- which the clause does not reach.
- CWE-508partialprevents — A.8.1 has preventive elements that reduce some introduction paths for non-replicating malicious code — restriction of software installation (d), USB/removable device controls (n), network connection rules including personal firewall (f), and update requirements (e) — but the clause's primary malware guidance (i) is endpoint protection software, which detects and removes rather than prevents introduction, and the clause does not reach email, web, or supply-chain vectors where most malicious code actually arrives.
- CWE-508partialblocks — A.8.1 item (i) mandates protection against malware on endpoint devices, which is the direct mechanism for blocking non-replicating malicious code from executing; items (d) software installation restriction and (j) remote disable/lockout also contribute. However, the clause is a broad endpoint-device policy where malware protection is one item among fifteen, the policy does not specify implementation rigour, and anti-malware is probabilistic — zero-day and sophisticated targeted code evade it — so a nameable class of exploitation remains unblocked.
- CWE-509partialblocks — A.8.1 mandates multiple mechanisms that block virus/worm execution and spread — item (i) protection against malware, item (d) software installation restrictions, item (f) network connection rules, item (n) removable device controls — but the actual blocking is performed by the implemented controls (anti-malware software, network controls), not by the policy clause itself, and residual vectors (zero-days, social engineering) remain.
- CWE-512partialblocks — A.8.1 mandates a policy for secure configuration and handling of user endpoint devices, but it does not itself stop spyware that is already present from collecting and exfiltrating information; the policy requires other controls (e.g., malware protection, access controls) to be configured and enforced to block exploitation.
- CWE-539partialblocks — A.8.1's storage device encryption (h), access controls (g), and malware protection (i) block some exploitation paths — physical theft of the device yielding direct cookie file access, and on-device malware reading the cookie jar — but the weakness is a web application design defect, and the main exploitation paths (XSS reading document.cookie, network interception, browser extensions) are not addressed by endpoint device controls.
- CWE-591partialblocks — A.8.1's storage device encryption requirement (item h) would encrypt the storage media where swap files reside, blocking direct exploitation of CWE-591 by making swap contents unreadable without the key; however, this is an indirect effect — the clause does not address memory locking itself, the weakness remains present, and the block depends on swap residing on the encrypted volume and on proper key management.
- CWE-613partialblocks — The user responsibility section's guidance to 'log-off active sessions and terminate services when no longer needed' is a user practice that, when followed, terminates sessions and prevents exploitation of those specific sessions, but it does not address the automatic session expiration logic in the application code where the weakness actually lives, and users do not always follow the practice.
- CWE-921partialblocks — A.8.1 mandates a policy covering device configuration and user responsibilities, but the policy itself does not stop an attacker from exploiting a storage mechanism that lacks built-in access control; the weakness remains exploitable until a technical control enforces the restriction.
- CWE-921partialremoves — A.8.1's storage-device encryption, removable-device/port restrictions, and local-storage disabling remove existing sensitive-data storage on user endpoint devices, but instances of the weakness outside the endpoint-device scope remain.
- CWE-921partialprevents — A.8.1 directly addresses storage mechanisms without access control through multiple guidance items: (h) storage device encryption, (n) restriction of removable devices and disabling physical ports, (o) partitioning to separate organizational data, and the explicit provision for disabling local storage (e.g., SD cards) when information is too sensitive to store on the device; well implemented and enforced through configuration management, the weakness is kept from arising in most cases, with the bounded remainder being storage paths the policy permits but does not adequately restrict or encrypt.
Mitigated MITRE ATT&CK techniques (3591)
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
- T1091mostlyprevents — A.8.1 directly addresses T1091's mechanism through guidance on disabling physical USB ports (n), restricting software installation including Autorun (d), and malware protection (i); the bounded remainder is that some USB functionality (keyboards, mice, charging) must remain and mobile-device-via-USB vectors are a specific concern not fully closed by the policy.
- T1003partialprevents — A.8.1's storage-device encryption (h) and malware protection (i) meaningfully prevent credential extraction from at-rest stores (SAM, /etc/shadow, cached creds) and some tooling, but the technique's primary vector — dumping credentials from process memory (LSASS, mimikatz-style) — is not reached by storage encryption, and access controls plus software restrictions do not stop an actor who already has the privileges the technique presupposes.
- T1003.002partialprevents — A.8.1 mandates measures (malware protection, software installation restrictions, access controls, storage encryption) that can partially prevent the initial compromise or tool execution needed for SAM extraction, but the technique requires SYSTEM-level access, at which point most endpoint policy controls are bypassed, and A.8.1 does not directly address credential store protection.
- T1005partialprevents — A.8.1's storage encryption (h), access controls (g), malware protection (i), and software installation restrictions (d) each constrain the technique's success — encrypted files are unreadable, access controls block unauthorized reads, malware protection can stop the searcher — but the technique itself (searching local file systems, configuration files, databases, process memory) can still execute and locate files of interest; the control reduces what an adversary can find and use, it does not stop the search.
- T1011partialprevents — A.8.1 directly addresses the mechanisms of T1011 through its wireless-connection configuration guidance (disabling vulnerable protocols), off-premises network rules, personal firewall requirements, software installation restrictions, and physical port disabling, but it is a policy layer that defers enforcement to A.8.9 (configuration management), and some exfiltration mediums (cellular, Bluetooth, other RF) are not fully covered by the wireless-configuration clause.
- T1011.001partialprevents — A.8.1's wireless-connection guidance explicitly addresses configuration of wireless connections including disabling vulnerable protocols, and its off-premises connection rules plus removable-device/port controls touch Bluetooth, but it is a policy framework that establishes requirements rather than a technical enforcement — actual Bluetooth disablement depends on A.8.9 configuration management, and Bluetooth often must remain enabled for legitimate peripherals, so the technique is constrained rather than prevented.
- T1014partialprevents — A.8.1 mandates endpoint measures directly relevant to rootkit prevention — restriction of software installation (d), update requirements (e), malware protection (i), and removable-device/port controls (n) — but it is a topic-specific policy that delegates enforcement to A.8.9 configuration management and automated tools, and rootkits specifically operate at kernel, hypervisor or firmware levels where standard endpoint malware protection and software installation restrictions are routinely bypassed, so the mandated measures reduce the attack surface without closing it.
- T1021.001partialprevents — A.8.1's requirements for personal firewalls (f), access controls (g), software installation restrictions (d), and configuration management enforcement can block or constrain RDP on endpoint devices, but the control is scoped to general endpoint security posture and does not address server-side RDP service hardening, network-level RDP blocking, or the authentication mechanisms that are the primary defense against T1021.001.
- T1021.004partialprevents — A.8.1 requires a policy covering access controls, software restrictions, and configuration management enforced through automated tools, which can disable the SSH server or restrict its use, but the control sets requirements rather than mandating a universal mechanism, leaving devices where SSH is legitimately needed or where policy exemptions exist still reachable.
- T1021.005partialprevents — A.8.1's policy framework can restrict VNC through software installation controls (d), access controls (g), connection rules (f), and remote disabling (j), and mandates enforcement via configuration management, but it is a policy-level control whose prevention depends on implementation and VNC is often legitimately required for remote administration, so the technique is constrained rather than eliminated.
- T1025partialprevents — A.8.1 requires a policy covering restriction of software installation, malware protection, and the disabling of physical ports including USB, which can prevent the technique from executing where those restrictions are enforced, but the control is a policy requirement rather than a universal mechanism and leaves room for removable media that are permitted or ports that remain open.
- T1036.007partialprevents — A.8.1's guidance on restriction of software installation (d), protection against malware (i), and end user behaviour analytics (m) addresses elements that can prevent execution of files masquerading via double extensions, but the control is policy-level guidance whose actual prevention depends on implementation through configuration management and technical controls, and it does not directly address the file-extension display behaviour the technique exploits.
- T1037partialprevents — A.8.1 mandates restriction of software installation, configuration management (cross-referenced to 8.9), access controls, and malware protection on user endpoint devices — all of which constrain where and how boot/logon initialization scripts can be placed. However, the control is a policy/guidance framework that requires implementation rather than a technical mechanism itself, and legitimate boot/logon scripts must still run for the system to function, so what is prevented is unauthorized script placement rather than the technique's whole surface.
- T1037.005partialprevents — A.8.1's guidance on restriction of software installation (d), protection against malware (i), and configuration management enforcement addresses the vectors by which startup items persistence is established on a managed endpoint, but the control is a topic-specific policy framework requiring implementation rather than a direct technical mechanism, and its general endpoint scope does not specifically target the macOS StartupItems directory mechanism.
- T1048partialprevents — A.8.1 mandates endpoint configurations that constrain exfiltration vectors — endpoint firewall rules (f), software installation restrictions (d), web service usage rules (l), and removable-device controls (n) — but it is a policy/guidance control whose prevention depends on implementation through configuration management (8.9) and other controls, and it does not cover all alternative-protocol channels (e.g., DNS tunneling, allowed web services).
- T1048.001partialprevents — A.8.1's malware protection, software installation restrictions, personal firewall requirements, and access controls can prevent some instances of the technique by blocking the tools and channels used for exfiltration, but the clause is endpoint-policy guidance rather than a dedicated DLP mechanism, and an adversary with established code execution can still reach permitted outbound channels or use allowed protocols to carry symmetrically encrypted data.
- T1048.002partialprevents — A.8.1 includes firewall requirements for off-premises connections, software installation restrictions, and access controls that can partially constrain exfiltration over encrypted protocols, but it is a general endpoint security policy rather than a dedicated DLP control and does not address the use of legitimate HTTPS/TLS channels for data theft.
- T1052partialprevents — A.8.1 requires a policy that can disable physical ports and restrict removable media, which prevents the technique where those restrictions are enforced, but the control is a policy requirement rather than a universal mechanism and leaves room for legitimate-use exemptions and unenforced devices.
- T1052.001partialprevents — A.8.1 requires a policy covering restriction of software installation, protection against malware, and the possibility of disabling physical ports including USB, which can prevent the technique where USB ports are disabled or controlled, but the control is a policy requirement rather than a universal technical enforcement, leaving devices with enabled ports and unmanaged software installation as a reachable remainder.
- T1056partialprevents — A.8.1's software installation restrictions, malware protection, access controls, and configuration management prevent many input capture vectors (unauthorized keyloggers, malicious capture tools), but credential API hooking can operate within legitimate processes and web portal capture relies on user deception — neither is reached by endpoint configuration policy alone.
- T1056.001partialprevents — A.8.1's malware protection (i), software installation restrictions (d), and update requirements (e) prevent software-based keyloggers, but hardware keyloggers, firmware/system image modifications, and some API hooking methods fall outside the control's scope, leaving a substantial remainder.
- T1056.004partialprevents — A.8.1 mandates malware protection (i), software installation restrictions (d), and update requirements (e) on endpoint devices, which can prevent the initial compromise that enables credential API hooking, but it is a topic-specific policy framework whose prevention depends on implementation in other controls (A.8.7, A.8.9) and does not directly address the in-process hooking mechanism itself.
- T1059partialprevents — A.8.1's restriction of software installation (d) and malware protection (i) can remove third-party interpreters and block some malicious scripts, but the built-in interpreters (PowerShell, cmd, bash) that adversaries most commonly use are part of the OS and cannot be removed through endpoint device policy, so what is prevented is a slice rather than the bulk.
- T1059.010partialprevents — A.8.1(d) restricts software installation on endpoint devices, which can prevent users from installing AutoHotKey/AutoIT interpreters, but the technique can still execute via pre-installed interpreters, compiled .exe payloads, or scripts delivered through phishing that run from temporary locations without installation — so what is prevented is a slice, not the bulk, mirroring the CM-7 vs T1059 anchor.
- T1059.011partialprevents — A.8.1's restriction of software installation (item d) and requirements for endpoint software (item e) can block standalone Lua interpreters from being installed on user endpoint devices, but Lua is frequently embedded in legitimate applications (network devices, games, Wireshark, Redis, etc.) and the control's scope is endpoint devices only — not network devices or servers — so embedded and pre-existing Lua execution paths remain reachable.
- T1068partialprevents — A.8.1 mandates software version requirements and active automatic updating (e), restriction of software installation (d), and malware protection (i), which directly address many exploitation vectors; however, the control is policy-level rather than a technical enforcement mechanism, and T1068 explicitly includes BYOVD and zero-day exploitation that bypass patching and installation controls.
- T1078.003partialprevents — A.8.1's access control requirements (g) and logical controls (user responsibility b: password access) on endpoint devices constrain local account abuse, and its malware protection (i) and software installation restrictions (d) impede credential-harvesting tooling, but the control is fundamentally about endpoint device configuration policy rather than authentication strength or account management, so it addresses a slice of the technique's surface rather than the bulk.
- T1090.001partialprevents — A.8.1's software installation restrictions (d), malware protection (i), and network access controls (g) can block some proxy tools and constrain some traffic patterns, but T1090.001 commonly uses built-in OS utilities (netsh portproxy, SSH tunnels) and existing peer-to-peer protocols (SMB) that the endpoint policy does not address, so the technique remains executable on a compromised endpoint.
- T1092partialprevents — A.8.1 restricts removable media use and can disable physical ports, which prevents the technique on devices where those restrictions are enforced, but the control is a policy requirement whose implementation varies across the estate and does not guarantee every port is disabled on every device.
- T1102.003partialprevents — A.8.1's mechanisms — firewall rules for off-premises connections (f), web service usage policies (l), UEBA (m), and malware protection (i) — can partially constrain an endpoint's ability to poll legitimate web services for C2 instructions, but the technique is specifically designed to blend with normal HTTPS traffic to popular sites that are typically allowlisted, so the control's framework cannot fully prevent it.
- T1111partialprevents — A.8.1's malware protection (i), software installation restrictions (d), and USB/port controls (n) can prevent the keylogger-based variant of T1111 on the endpoint, but the technique also runs through SMS interception at the carrier, email interception at the service, and compromise of the MFA provider itself — none of which endpoint policy reaches.
- T1114partialprevents — A.8.1's endpoint configuration mandate (access controls, storage encryption, malware protection, software installation restrictions) constrains the endpoint-side execution of email collection — local mail store access, malicious email-collection tools, and unprotected local caches — but does not reach server-side collection, forwarding-rule abuse at the mail server, or credential-based webmail access, so the technique's surface is only partially closed.
- T1114.001partialprevents — A.8.1's guidance specifies storage device encryption (h), access controls (g), and the explicit option to forbid storing sensitive information on endpoint devices — all of which, if implemented, would prevent an adversary from reading local Outlook .ost/.pst files. But A.8.1 is a policy/guidance control that mandates these protections rather than implementing them; the actual prevention is performed by the controls that realize encryption and access control, so the policy itself delivers only a slice of the prevention.
- T1115partialprevents — A.8.1's malware protection (i) and restriction of software installation (d) can prevent third-party tools and malware that collect clipboard data, but the control has no specific mechanism against clipboard access; built-in OS utilities (clip.exe, Get-Clipboard, pbpaste) and legitimate applications with clipboard permissions remain usable, so the technique is not closed.
- T1119partialprevents — A.8.1 includes provisions that constrain automated collection from endpoints — restricting what data may be stored locally, access controls, storage encryption, software installation restrictions, and the explicit guidance that sensitive information may be accessed but not stored on endpoints — but it is a broad endpoint-configuration policy whose many other provisions (physical protection, backups, wireless configuration, BYOD terms) do not address this technique, and an adversary with a foothold can still use legitimate scripting interpreters to collect data that is accessible.
- T1127.002partialprevents — A.8.1's guidance on restriction of software installation (d), protection against malware (i), and usage of web services and web applications (l) provides mechanisms that can prevent some ClickOnce abuse, but ClickOnce is a built-in Windows utility (DFSVC.EXE) that cannot be fully removed without breaking legitimate functionality, and the technique can still execute via user interaction with web content even under a restrictive policy.
- T1137partialprevents — A.8.1 mandates specific technical measures relevant to T1137 — particularly (d) restriction of software installation, (i) protection against malware, and (j) remote disabling — which, when implemented, would block malicious Office add-ins, templates, and Outlook persistence mechanisms; however, the control is a topic-specific policy and guidance framework, not the implementing mechanism itself, so the prevention it delivers is the policy mandate rather than the technical enforcement (which lives in A.8.9 configuration management, A.8.7 malware protection, etc.).
- T1137.001partialprevents — A.8.1 includes items that can constrain Office template macros — restriction of software installation (d), malware protection (i), configuration management enforcement, and update requirements (e) — but it is a general endpoint device policy that does not specifically target template-based persistence, and implementations focused on other endpoint risks will leave the technique reachable.
- T1137.002partialprevents — A.8.1's malware protection (i) and software installation restrictions (d) can incidentally prevent the malicious DLL from executing, but the control is a broad endpoint-device policy that does not directly address registry-based persistence: it neither restricts registry write access nor prevents the Office Test key from being created on a system where the adversary already has write access, so the prevention is incidental and incomplete.
- T1137.006partialprevents — A.8.1's guidance on restriction of software installation (d) and requirements for endpoint device software (e) directly addresses what can be installed on user devices, which includes Office add-ins; however, A.8.1 is a policy/guidance control whose enforcement depends on configuration management (8.9) and automated tools, and legitimate business add-ins cannot all be blocked, so the prevention is a slice rather than a closure.
- T1176partialprevents — A.8.1's item (d) on restriction of software installation and item (i) on malware protection can constrain which extensions are permitted on endpoint devices, but the control is a general endpoint policy that does not specifically address browser or IDE extensions; users commonly need extensions for legitimate work, official marketplaces are trusted channels the policy does not inherently block, and the clause sets requirements rather than mandating a specific mechanism against extensions, leaving a substantial slice of the technique reachable.
- T1176.001partialprevents — A.8.1 mandates restriction of software installation (item d), configuration management enforcement, and malware protection (item i), which together can prevent a meaningful slice of browser extension installations through allowlisting, MDM-controlled browser policies, and endpoint protection. However, the control is a policy framework rather than the technical enforcement itself, and multiple T1176.001 vectors bypass it: social engineering of users into installing legitimate-looking extensions, manipulation of Preferences/Secure Preferences files while the browser is not running, and installation on already-compromised systems where the policy no longer holds.
- T1176.002partialprevents — A.8.1(d) requires restriction of software installation on endpoint devices (e.g. remotely controlled by system administrators), which can prevent unauthorized IDE extensions from being installed, but the control is policy-level guidance that does not specifically address IDE extensions and developers typically need flexibility to install extensions for legitimate work, so what is prevented is a slice rather than the bulk with a bounded remainder.
- T1185partialprevents — A.8.1's guidance on software updates (e), restriction of software installation (d), malware protection (i), and network/firewall rules (f) addresses several browser session hijacking vectors (patched browser exploits, malicious extensions, injected malware), but the technique can still succeed via zero-day exploits that bypass patching, sophisticated malware evading endpoint protection, and abuse of legitimate browser functionality for pivoting — so the control reduces the attack surface without closing it.
- T1189partialprevents — A.8.1 mandates active automatic updating (e), malware protection (i), personal firewalls (f), and restrictions on web services (l), each of which reduces drive-by compromise success, but the control is a policy framework that does not mandate browser-specific hardening, exploit mitigation, or web-content filtering, and zero-days or novel payloads can still succeed against a fully conformant implementation.
- T1200partialprevents — A.8.1 mandates disabling physical ports (USB) and physical protection requirements that directly address USB-based hardware additions like keystroke injection devices, but it is a policy framework whose implementation depends on other controls, and it does not reach non-USB vectors such as rogue wireless access points, network taps, or DMA via other interfaces.
- T1203partialprevents — A.8.1 explicitly requires policies on software versions and active automatic updating, restriction of software installation, and malware protection — all direct prevention mechanisms for client-side exploitation. However, it is a topic-specific policy that mandates consideration and implementation rather than performing the prevention itself (which lives in A.8.9 configuration management and patch controls), and zero-day exploits are not addressed by version-pinning or signature-based defenses.
- T1204partialprevents — A.8.1's technical measures — software installation restrictions (d), malware protection (i), connection rules (f), end user behaviour analytics (m), and configuration management enforcement — prevent a slice of T1204 vectors (unauthorized installs, known malware payloads, connections to unapproved services), but the user remains the mechanism for opening documents, clicking links, enabling remote access tools, or pasting commands, none of which endpoint configuration alone eliminates.
- T1204.002partialprevents — A.8.1 includes restriction of software installation (d), malware protection (i), and rules for network connection (f) that can prevent some malicious files from executing on endpoint devices, but it is a broad endpoint-configuration control that does not specifically target user-initiated file execution and cannot prevent the user from opening the file in the first place.
- T1204.005partialprevents — A.8.1 mandates restriction of software installation (item d) and protection against malware (item i), which constrains user-driven library installation, but it is a topic-specific policy whose enforcement depends on A.8.9 configuration management and automated tools, and developers and other roles with legitimate installation needs remain reachable.
- T1210partialprevents — A.8.1's requirements for software updates (item e), restriction of software installation (item d), and access controls (item g) reduce the vulnerability surface of endpoint devices that may be targeted by T1210, but the control covers only endpoints while T1210 primarily targets servers (SMB, RDP, web servers, vCenter, ESXi), and even for endpoints the clause sets policy requirements rather than mandating complete patching of all exploitable services.
- T1211partialprevents — A.8.1's patching requirements (item e), software installation restrictions (item d), and malware protection (item i) reduce the endpoint-side vulnerability surface that T1211 could exploit, but the technique's core vectors — exploiting logging pipelines, security tools, and cloud/SaaS infrastructure to suppress telemetry — sit largely outside endpoint device policy, and zero-days remain reachable regardless of update cadence.
- T1212partialprevents — A.8.1's patching, software-restriction and configuration-management requirements reduce the exploitable vulnerability surface on user endpoint devices, but cannot prevent zero-day exploitation, exploitation of authentication services or cloud/identity-provider targets outside the endpoint scope, so the preventive effect is a slice rather than the bulk.
- T1216.001partialprevents — A.8.1's restrictions on software installation, malware protection, and configuration management provide a framework that could partially block PubPrn.vbs execution through application allowlisting or script-blocking policies, but PubPrn is a signed Microsoft system script that bypasses many standard application control solutions, and A.8.1 does not specifically mandate the technical controls (e.g., script execution policies, specific blocks of PubPrn.vbs) needed to fully prevent this technique.
- T1218.003partialprevents — A.8.1's clauses on restriction of software installation, malware protection, and configuration management can contribute to a hardened endpoint environment, but CMSTP.exe is a legitimate, signed Windows system binary that the technique abuses rather than installs; the control has no direct mechanism to block CMSTP invocation with a malicious INF, so what is prevented is a slice of the attack surface (e.g. where AppLocker-style enforcement is layered in via 8.9) rather than the technique itself.
- T1218.007partialprevents — A.8.1's guidance on restriction of software installation and protection against malware can constrain some abuse of msiexec.exe (e.g., blocking unauthorized MSI packages or detecting malicious installers), but msiexec.exe is a native, signed Windows binary that cannot be removed from the platform, and the technique is explicitly designed to bypass application control — so what is prevented is a slice, not the bulk, mirroring the cm-7 vs T1059 anchor's shape.
- T1219partialprevents — A.8.1's restriction of software installation (item d) and access controls (item g) can prevent unauthorized remote access tools from being installed on endpoint devices, but T1219 specifically involves abuse of LEGITIMATE remote access tools (RDP, EDR response features, Chrome Remote Desktop, etc.) that are already present and required for business operations — these cannot be removed without breaking the function they serve, so what is prevented is a slice of unauthorized tools rather than the technique's core mechanism.
- T1219.001partialprevents — A.8.1's restriction of software installation (d), rules for connection to information services (f), and malware protection (i) can constrain unauthorized IDE installations and outbound tunneling on non-developer endpoints, but developers legitimately require IDEs whose tunneling features are built-in, so the technique cannot be eliminated across the estate — only narrowed to approved, monitored developer machines.
- T1219.002partialprevents — A.8.1's restriction of software installation (item d) and malware protection (item i) can prevent unauthorized remote desktop tools from being installed on endpoint devices, but T1219.002 specifically abuses legitimate desktop support software (TeamViewer, AnyDesk, VNC, etc.) that organizations commonly allow for IT support purposes — software the control's policy framework would not, and often should not, prohibit. The control reduces the attack surface but cannot prevent abuse of allowed legitimate remote access tools.
- T1219.003partialprevents — A.8.1's guidance on registering endpoint devices, restricting software installation, and disabling physical ports (e.g., USB) can prevent unauthorized hardware peripherals from being attached, but the technique is often installed post-compromise when the adversary already has access, and network-based KVM devices may not connect through the ports the control addresses, leaving a substantial remainder.
- T1221partialprevents — A.8.1 includes network restrictions (f), malware protection (i), and software installation controls (d) that can block some template injection attempts by restricting outbound template fetches or catching the fetched payload, but the technique abuses legitimate OOXML/RTF template features that cannot be fully disabled without breaking normal document functionality, and the control is primarily policy-level guidance enforced through configuration management rather than direct technical prevention.
- T1491.001partialprevents — A.8.1's general endpoint security measures (access controls, malware protection, software installation restrictions, configuration management) can prevent some initial compromise vectors that lead to internal defacement, but the technique is a post-compromise action requiring the adversary to already have system access, and A.8.1 does not specifically prevent the defacement act (wallpaper replacement, website modification) once that access is obtained.
- T1495partialprevents — A.8.1 mandates general endpoint security measures—malware protection (i), access controls (g), physical protection (c), and software installation restrictions (d)—that could incidentally help prevent firmware corruption by closing some delivery and access vectors, but it does not specifically address firmware integrity, secure boot, or firmware write protection, so the prevention is incidental rather than targeted.
- T1496partialprevents — A.8.1 mandates concrete endpoint protections — malware protection (i), software installation restrictions (d), update requirements (e), access controls (g), and connection rules (f) — that collectively address the main vectors for resource hijacking (malware delivery, unauthorized miner/proxy installation, exploitation of unpatched vulnerabilities). However, it is a topic-specific policy/guidance rather than an implementing control, and browser-based cryptomining, supply-chain compromises, and zero-day exploits can bypass the mandated protections, leaving a nameable remainder.
- T1496.001partialprevents — A.8.1 mandates malware protection (i), software installation restrictions (d), updates (e), and access controls (g) — collectively addressing the main vectors for endpoint compute hijacking (cryptominers delivered as malware or via exploitation) — but it is a topic-specific policy that sets requirements rather than implementing them, and the actual prevention depends on A.8.7, A.8.9 and the configuration tools it references; cloud/container compute hijacking vectors also fall outside its endpoint scope.
- T1496.002partialprevents — A.8.1 mandates software installation restrictions, malware protection, firewall rules, software updates and access controls on endpoint devices — collectively these constrain the compromise pathway that enables bandwidth hijacking — but it is a topic-specific policy that requires other controls (A.8.7, A.8.9, A.8.20) to actually implement the prevention, so its direct preventive effect is partial.
- T1499.004partialprevents — A.8.1's requirement for current software versions and active automatic updating (item e) directly addresses exploitation of known vulnerabilities on user endpoint devices, but the control is policy-level guidance rather than enforcement, zero-day exploits remain reachable, and the scope is limited to user endpoint devices while T1499.004 also targets servers, IaaS and applications.
- T1539partialprevents — A.8.1 mandates storage device encryption (h), malware protection (i), software installation restrictions (d), personal firewalls (f), and user behaviour analytics (m), all of which constrain on-disk cookie theft and cookie-stealing malware; however, the technique also operates via process memory, adversary-in-the-middle network interception, and malicious JavaScript injection, none of which A.8.1's policy items reach, and as a topic-specific policy it mandates rather than implements the safeguards.
- T1543partialprevents — A.8.1 mandates restrictions on software installation, access controls, and malware protection on endpoint devices that, if implemented, would constrain unauthorized creation or modification of system services/daemons/agents; however, as a topic-specific policy and guidance control, the actual prevention depends on implementation through configuration management (A.8.9) and technical controls, and the technique can still succeed where the actor holds legitimate administrator privileges or where the mandated restrictions are not fully enforced.
- T1543.001partialprevents — A.8.1 mandates restrictions on software installation, malware protection, and configuration management enforcement on endpoint devices, which directly constrain the ability to create or modify launch agents for persistence; however, it is a topic-specific policy that requires implementation through A.8.9 and other technical controls, so the prevention is mandated rather than performed, leaving a bounded remainder where the policy's effect depends on faithful implementation of the controls it references.
- T1543.004partialprevents — A.8.1 mandates restrictions on software installation, access controls, malware protection, and configuration management enforcement on user endpoint devices — all of which, when implemented, can prevent unauthorized Launch Daemon creation on managed macOS endpoints. However, A.8.1 is policy-level guidance; the actual preventive mechanism lives in A.8.9 (configuration management) and the technical controls it directs, and a Launch Daemon installed via privilege escalation or poor configuration (e.g., world-writable /usr/local/bin) can still land despite a conformant A.8.1 policy.
- T1546.002partialprevents — A.8.1 mandates a topic-specific policy whose guidance items (d) software installation restriction, (g) access controls, and (i) malware protection directly address the mechanism of screensaver persistence, but the control is a policy that requires these be enforced through configuration management (A.8.9) or automated tools — the policy itself does not technically prevent the .scr placement or registry modification, so the prevention is partial and depends on downstream technical implementation.
- T1546.010partialprevents — A.8.1 mandates topic-specific policy items — restriction of software installation (d), malware protection (i), access controls (g), and configuration management enforcement — that, if implemented through downstream technical controls, would prevent AppInit DLLs by blocking the malicious DLL's installation and the registry modifications it requires; but A.8.1 is itself a policy/guidance control that does not directly implement those restrictions, and the technique can still succeed where the mandated controls are absent, bypassed, or where the attacker holds administrative rights.
- T1546.011partialprevents — A.8.1 includes restriction of software installation (d), malware protection (i), and software version/update requirements (e) that, if properly implemented through configuration management, could prevent installation of custom shim databases; however, the control is a policy/guidance framework that mandates these measures rather than implementing them, application shimming abuses legitimate Windows OS infrastructure that standard endpoint protection may not specifically target, and admin privileges (often present on endpoints) still permit shim installation.
- T1546.013partialprevents — A.8.1's topic-specific policy framework for endpoint devices includes elements relevant to PowerShell profile abuse — restriction of software installation (item d), malware protection (item i), and configuration management enforcement (see 8.9) — which can constrain who may modify profile.ps1 and detect tampering, but the control is a policy framework that mandates rather than implements these protections, and PowerShell profile persistence is not its specific target, leaving a bounded remainder.
- T1546.016partialprevents — A.8.1 explicitly addresses restriction of software installation (item d) and is meant to be enforced through configuration management tools, which directly constrains the installer-package mechanism; however, the technique abuses legitimate installation flows (OS updates, signed applications, MDM-deployed packages) that must remain functional, so what is prevented is the unauthorized-installer slice rather than the bulk of the technique.
- T1547partialprevents — A.8.1 mandates restriction of software installation (d), malware protection (i), update requirements (e), and enforcement through configuration management (8.9) — all of which constrain autostart persistence mechanisms. But it is a policy/guidance control whose prevention depends on implementation through other controls, and many autostart mechanisms are inherent to the OS and cannot be removed without breaking functionality, leaving a bounded remainder.
- T1547.004partialprevents — A.8.1 mandates restriction of software installation, malware protection, and configuration management enforcement on endpoint devices — all of which, if implemented, constrain the registration of unauthorized Winlogon helper DLLs and the persistence they enable — but the control is a topic-specific policy that delegates the actual prevention to dependent controls (A.8.9 configuration management, A.8.7 malware protection), so what it delivers is the framework that enables prevention rather than the mechanism itself.
- T1547.006partialprevents — A.8.1's policy framework includes restriction of software installation (d), malware protection (i), and configuration management enforcement, which when implemented can constrain unauthorized kernel module loading on managed endpoints; however, it is a policy-level control that does not itself implement the technical mechanisms (Secure Boot, module signing, SIP, SELinux/AppArmor) that actually prevent T1547.006, and kernel-level persistence is not its primary focus.
- T1547.008partialprevents — A.8.1's restrictions on software installation (item d), malware protection (item i), and configuration management enforcement can constrain unauthorized driver installation on endpoint devices, but the technique operates post-compromise with administrative privileges and the clause is a general endpoint policy that does not specifically target LSASS drivers, leaving a substantial remainder where the technique can still execute.
- T1547.009partialprevents — A.8.1 mandates restrictions on software installation, access controls, and malware protection on endpoint devices, which when implemented constrain the ability to create or modify malicious startup shortcuts; however, the control is a topic-specific policy whose enforcement depends on A.8.9 configuration management and A.8.7 malware protection, so the policy itself only partially prevents the technique.
- T1548.006partialprevents — A.8.1's general endpoint security measures — restriction of software installation (d), malware protection (i), access controls (g), and configuration management enforcement — can reduce the surface for TCC manipulation by limiting untrusted executables, but the control does not specifically address macOS TCC mechanisms and cannot prevent abuse of legitimate applications (e.g., Finder) that already hold TCC permissions, leaving a substantial remainder.
- T1550.004partialprevents — A.8.1 addresses some vectors of cookie theft through malware protection (i), storage encryption (h), software installation restrictions (d), and end-user behaviour analytics (m), but cannot prevent network-based interception, server-side compromise, browser vulnerabilities, or the fundamental replay of valid session cookies, leaving multiple paths by which T1550.004 still succeeds.
- T1552.004partialprevents — A.8.1's storage device encryption (h) and access controls (g) block offline extraction of private key files from a stolen or unattended device, but cannot prevent an adversary who has already compromised the running system from searching for and using keys accessible to the logged-in user — the keys must be usable, so they are reachable to the user's runtime context.
- T1553partialprevents — A.8.1's software installation restrictions (d), update requirements (e), malware protection (i), and configuration management enforcement touch on trust mechanisms by limiting what runs on endpoints, but the core of T1553 — stealing or forging code-signing certificates, modifying registry/permissions to bypass trust checks, and undermining the trust controls themselves — is not directly addressed by the clause.
- T1553.001partialprevents — A.8.1 mandates a topic-specific policy whose items (d) restriction of software installation, (i) protection against malware, and (e) software/update requirements are directly relevant to Gatekeeper Bypass, and the clause explicitly states these should be enforced through configuration management (8.9) or automated tools; however, the control is a policy mandate rather than the technical implementation, and T1553.001 is specifically designed to subvert Gatekeeper checks (e.g., via logic errors, unchecked file types, and external libraries), so the policy constrains the technique without fully preventing it.
- T1553.004partialprevents — A.8.1 mandates a topic-specific policy whose items (d) restriction of software installation, (g) access controls, and (i) protection against malware partially address root-certificate installation by limiting who can add to the trust store and by addressing the compromise vector, but the control is policy-level rather than technical, the technique presupposes a prior compromise where the adversary often holds the privileges needed to install certificates, and the actual enforcement depends on A.8.9 configuration management and other implementing controls.
- T1553.006partialprevents — A.8.1's requirements for restriction of software installation (d), access controls (g), and protection against malware (i) constrain who can modify code signing policies and what tools can run on the device, but the control is a broad endpoint policy that does not specifically address OS-level code signing enforcement (DSE, SIP, WDAC); the technique targets those mechanisms directly, and A.8.1 leaves a named remainder where privileged users or kernel-level attacks bypass the policy-level restrictions.
- T1554partialprevents — A.8.1's restrictions on software installation (d), malware protection (i), and enforcement via configuration management (8.9) partially prevent unauthorized binary modifications, but the control is a policy framework that does not specifically mandate binary integrity verification, code signing enforcement, or protection against patching of existing legitimate binaries — the core mechanics of T1554 (IAT hooking, entry point patching, binary replacement) — so what is prevented is a slice rather than the technique's bulk.
- T1555partialprevents — A.8.1 mandates a topic-specific policy whose required items directly address T1555 — storage device encryption (h) prevents reading credentials from disk, malware protection (i) blocks credential-stealing malware, access controls (g) limit who reaches stored credentials, and software installation restrictions (d) constrain what can run — but the control is a policy mandate whose prevention depends on implementation through other controls (A.8.9, A.8.7, A.8.24), and several of its sub-items (physical protection, backups, wireless procedures) do not bear on credential-store theft.
- T1555.001partialprevents — A.8.1's policy requirements on storage encryption (h), access controls (g), malware protection (i), and software installation restrictions (d) address relevant surfaces, but the keychain technique specifically exploits legitimate OS credential access by an authenticated user, which A.8.1's policy framework cannot fully prevent when the adversary already holds user-level credentials.
- T1555.005partialprevents — A.8.1's storage device encryption (h) prevents file-based extraction of the password manager database at rest, and its malware protection (i) and access controls (g) reduce some attack vectors, but the technique's memory-extraction path after the user unlocks the database and its brute-force path against the master password are not addressed by this clause, leaving a substantial remainder.
- T1556partialprevents — A.8.1's malware protection (i), software installation restrictions (d), access controls (g), and update requirements (e) constrain some vectors for modifying authentication processes, but the control is a broad endpoint policy that does not specifically target authentication-process integrity; techniques like LSASS process injection, PAM module modification, or SAM tampering on a compromised endpoint are not directly prevented by A.8.1's general endpoint configuration requirements.
- T1556.008partialprevents — A.8.1's software installation restrictions (d), malware protection (i), and configuration management enforcement can prevent a non-admin adversary from planting the malicious Network Provider DLL on user endpoint devices, but the technique's primary targets — servers and domain controllers with high logon activity — fall outside A.8.1's endpoint scope, and an adversary with administrative rights bypasses the installation restrictions entirely.
- T1557partialprevents — A.8.1 includes connection rules (e.g. personal firewall requirements for off-premises networks), wireless protocol configuration (disabling vulnerable protocols), and update requirements that can reduce AiTM exposure, but the control is fundamentally about endpoint device configuration and handling rather than network-traffic interception; core AiTM vectors (ARP/DNS/LLMNR poisoning, downgrade attacks) are not directly addressed, so prevention is indirect and limited.
- T1557.004partialprevents — A.8.1's wireless configuration guidance (disabling vulnerable protocols), rules for public network connection (personal firewall), and user awareness about using devices with care in public places reduce the rate at which users connect to evil twin APs, but the technique still runs — the fraudulent AP is still broadcast and devices can still associate with it, so the reduction is a rate and not a closure.
- T1561.001partialprevents — A.8.1's access controls (g), software installation restrictions (d), malware protection requirement (i), and physical protection guidance can prevent opportunistic or malware-driven disk wipes, but the technique can still execute via legitimate admin tools, kernel-level drivers (e.g. RawDisk), or once an adversary has obtained sufficient privileges — so the preventive mechanisms cover a slice rather than the bulk.
- T1563.001partialprevents — A.8.1's malware protection (i), access controls (g), and software installation restrictions (d) can prevent some initial compromises of the source endpoint that enable SSH hijacking, but the technique specifically requires root access on the source host to reach the SSH agent socket, and A.8.1 does not address SSH agent security, session isolation, or the lateral-movement mechanism itself.
- T1564.006partialprevents — A.8.1's restriction of software installation (item d) and policy framework can prevent installation of third-party virtualization tools (VirtualBox, QEMU), but built-in virtualization features like Hyper-V and Windows Sandbox are part of the platform and cannot be removed by this policy control, leaving a substantial remainder where the technique still runs.
- T1565.001partialprevents — A.8.1 mandates access controls, storage encryption, malware protection, and software installation restrictions that can prevent stored data manipulation on endpoint devices, but the control is a topic-specific policy whose preventive effect is indirect and depends on implementation through configuration management (8.9) and other technical controls rather than being a technical control itself.
- T1565.003partialprevents — A.8.1's restrictions on software installation, access controls, malware protection, and configuration management address some vectors leading to runtime data manipulation (unauthorized software, initial compromise), but the technique's core—modifying existing application binaries or display logic on a system the adversary already accesses—is not directly stopped by endpoint policy, leaving a substantial remainder.
- T1566.001partialprevents — A.8.1's malware protection (i), software installation restrictions (d), and patching requirements (e) can prevent some malicious payloads from executing after the attachment is opened, but the control does not address the email delivery vector or the social engineering step, so the technique can still be attempted and the user can still open the attachment.
- T1566.002partialprevents — A.8.1's malware protection (i), software installation restrictions (d), and web service rules (l) can prevent some payloads from executing after the link is clicked, but the control does not address the email delivery, the social engineering, or credential/OAuth-consent variants of the technique, so the prevention is a slice rather than comprehensive.
- T1566.003partialprevents — A.8.1 mandates malware protection, software restriction, and user awareness for endpoint devices, which can block or deter the execution of a malicious attachment delivered via a third-party service, but the control cannot prevent the adversary from sending the message or the user from receiving it on a personal account, leaving a significant and nameable remainder.
- T1567partialprevents — A.8.1 includes items directly relevant to T1567 — restrictions on web service usage (l), rules for connection to information services and public networks including personal firewalls (f), access controls (g), and software installation restrictions (d) — which can constrain which legitimate services an endpoint may reach and what data is accessible, but the technique specifically uses legitimate services that business operations require, and the control is an endpoint policy framework rather than network egress filtering or DLP, so a meaningful slice of exfiltration paths through allowed services remains.
- T1567.002partialprevents — A.8.1's guidance on restriction of software installation (d), rules for connection to information services (f), usage of web services and web applications (l), and access controls (g) directly addresses cloud-storage exfiltration, but the control is a topic-specific policy framework rather than a technical enforcement mechanism, and browser-based uploads to cloud services can bypass software-installation restrictions, leaving a meaningful remainder.
- T1567.004partialprevents — A.8.1 includes items that can contribute to preventing webhook exfiltration — malware protection (i) can block the malware that stages and posts data, web services usage rules (l) can restrict which SaaS endpoints are reachable, and personal firewall requirements (f) can constrain outbound traffic — but the technique is specifically designed to use HTTPS to legitimate SaaS services that blend with normal traffic, and the control is a topic-specific policy enforced through configuration management rather than a direct technical prevention, so what is prevented is a slice rather than the bulk.
- T1569partialprevents — A.8.1's restriction of software installation (d), requirements for endpoint software and updates (e), malware protection (i), and configuration management enforcement can prevent unauthorized services from being installed on endpoint devices, but T1569 specifically involves abusing existing system services/daemons or creating services locally or remotely — a vector the control does not directly address, so what is prevented is a slice rather than the technique's core mechanism.
- T1570partialprevents — A.8.1's restrictions on removable devices and physical ports (item n) and on software installation (item d) close off a slice of T1570's vectors (USB-based tool transfer, installing adversary tools on endpoints), but the bulk of the technique — SMB/Windows Admin Shares, RDP, scp, rsync, curl, sftp, ftp, and synced cloud folders — runs over network file-sharing and remote-access channels that A.8.1 does not address.
- T1574partialprevents — A.8.1's restriction of software installation (item d), malware protection (item i), access controls (item g), and update requirements (item e) constrain some vectors for execution-flow hijacking by limiting what runs on the endpoint and patching exploited software, but the control does not directly address the core mechanisms of T1574 — DLL search-order manipulation, path interception, registry poisoning, or service hijacking of already-trusted binaries — so a meaningful slice of the technique remains reachable.
- T1574.004partialprevents — A.8.1's guidance on restriction of software installation (d), malware protection (i), and partitioning (o) provides a policy framework that, if implemented through configuration management or automated tools, can constrain where dylibs can be placed and detect malicious ones; however, the control is fundamentally a policy mandate rather than a technical prevention mechanism, and dylib hijacking often exploits legitimate applications and writable search paths that general endpoint policies do not specifically address.
- T1574.008partialprevents — A.8.1 mandates restriction of software installation (d), access controls (g), and protection against malware (i), which can limit an adversary's ability to place a malicious executable in a target directory, but it does not directly address the Windows search-order behavior the technique exploits, and write access obtained through other vectors (exploits, misconfigured ACLs) bypasses the software-installation restriction.
- T1595partialprevents — A.8.1 can prevent active scanning from yielding useful endpoint information by requiring local firewalls, patching, disabling vulnerable protocols/ports, and restricting installed software, but active scanning against non-endpoint assets and exposed services remains outside its endpoint scope.
- T1653partialprevents — A.8.1 mandates endpoint protections directly relevant to T1653 — restriction of software installation (d), protection against malware (i), and configuration management enforcement — which constrain the tools and behaviours that manipulate power settings, but the control is a policy framework that depends on A.8.7, A.8.9 and A.8.16 to actually implement those requirements, and it does not specifically address power/hibernate/timeout settings that T1653 abuses via built-in utilities like powercfg.
- T1669partialprevents — A.8.1's wireless-configuration guidance (disabling vulnerable protocols) and rules for connecting to public networks (personal firewall) provide endpoint-side hardening that reduces the attack surface for Wi-Fi-based compromise, but the core of T1669 — the adversary connecting to the organization's Wi-Fi network — is governed by access-point and network-infrastructure controls outside A.8.1's scope, so what is prevented is a slice rather than the technique.
- T1674partialprevents — A.8.1 directly addresses physical HID injection via item (n) on disabling USB ports and removable devices, and addresses software-based injection via malware protection (i), software installation restrictions (d), and end-user behaviour analytics (m); however, USB ports cannot be universally disabled without breaking legitimate use, software-based keystroke simulation can still occur through legitimate OS APIs, and the clause sets policy requirements rather than mandating a universal mechanism, leaving a substantial remainder.
- T1686.003partialprevents — A.8.1 mandates a topic-specific policy that includes requiring personal firewall use (item f), access controls (g), and software installation restrictions (d), which are necessary preconditions for preventing firewall tampering, but the control itself is a policy that defers enforcement to A.8.9 configuration management and automated tools — so it shapes what must be prevented without performing the prevention.
- T1687partialprevents — A.8.1's requirements for software updates (e), restriction of software installation (d), and malware protection (i) reduce the attack surface of endpoint-resident defensive software, but the technique also targets network infrastructure and cloud/SaaS defenses outside the endpoint policy's scope, and zero-day exploitation of already-installed security tools remains reachable.
- T1689partialprevents — A.8.1 mandates a topic-specific policy requiring current software versions and active updating (item e), disabling vulnerable protocols (wireless section), and configuration management enforcement — all of which constrain downgrade attacks on endpoint devices. But it is a policy/governance control that mandates the capability rather than performs it; the actual prevention depends on A.8.9 configuration management and the technical implementations, and downgrade vectors outside endpoint policy scope (e.g., network protocol downgrade at the gateway) are not reached.
Prevented OWASP Web Top 10 (2025) risks (5)
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
- A02partialblocks — A.8.1's policy, configuration enforcement, software restrictions, updates, encryption, malware protection, and partitioning directly close many common misconfiguration vectors on endpoints (e.g., weak defaults, exposed services, unpatched software, open ports); residual attack surface remains in non-endpoint layers (servers, cloud, frameworks) and in incomplete policy implementation.
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.