A.8.2 Technological
Privileged access rights
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 (16)
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-2mostlycovers — A.8.2's focus on provisioning and restricting privileged access rights directly accounts for the privileges, group/role membership, and authorization-specification portions of ac-2, but leaves a real residual (account types, account managers, approval workflows, and non-privileged accounts) uncovered.
- AC-3mostlycovers — A.8.2's focus on provisioning and restricting privileged rights accounts for the bulk of ac-3's enforcement of approved authorizations (especially for elevated privileges), but leaves a residual of ac-3's broader non-privileged logical access enforcement untouched.
- AC-6mostlycovers — Both controls focus on restricting elevated privileges to the minimum necessary for role-based duties and enforcing separate identities for privileged versus ordinary tasks.
Aligned NIST CSF 2.0 outcomes (21)
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.AA-01domain mandateimplements — A.8.2 operationalizes privileged-access management (a core subset of identity/credential lifecycle for authorized users/services) that PR.AA-01 requires; the link is within the identity-and-access domain but the outcome does not name privileged rights explicitly
- PR.AA-05explicit mandateimplements — A.8.2 directly operationalizes the management and enforcement of privileged access rights (least privilege, authorization, review) that PR.AA-05 names as its outcome
Related OWASP ASVS 5.0 requirements (13)
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 (2548)
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-15mostlyblocks — Privileged access rights reduce the number of users who can alter configuration.
- CWE-269mostlyblocks — A.8.2 directly controls the identification, allocation, review, expiry, temporary use, and separation of privileged rights per policy, which prevents most improper privilege management (CWE-269) by design; the bounded remainder is flawed tracking/checking logic inside the product's own enforcement code (the AC-3 slice of 269).
- CWE-270mostlyblocks — Privileged-access-rights control directly addresses improper privilege elevation during context switches.
- CWE-274mostlyblocks — Privileged-access-rights control directly limits the situations in which insufficient privileges can occur.
- CWE-419mostlyblocks — Privileged access rights directly restrict who can use the primary administrative channel.
- CWE-424mostlyblocks — Privileged access rights must be enforced on every possible route to privileged functions.
- CWE-612mostlyblocks — Privileged access rights may be used to enforce index restrictions but are not the primary control.
- CWE-1262partialblocks — Privileged access rights directly restrict who can read/write hardware registers.
- CWE-1268partialblocks — Specifies management of privileged access rights, mitigating discrepancies between control-plane and data-plane privileges.
- CWE-223partialprevents — A.8.2 item (j) requires logging all privileged access for audit purposes, which prevents omission of security-relevant information about privileged access events — a narrow slice of CWE-223; the weakness's broader scope (login attempts, email headers, general authentication events) is untouched by this clause, whose primary purpose is authorization of privileged access rather than comprehensive security-relevant logging.
- CWE-288partialblocks — Privileged access rights control reduces risk of bypass through elevated or alternate paths.
- CWE-290partialblocks — Privileged access rights reduce attack surface but do not prevent spoofing of authentication.
- CWE-308partialremoves — A.8.2(f) explicitly addresses authentication strength for privileged access, stating that authentication requirements for privileged access rights can be higher (including re-authentication or step-up), so implementing the clause where single-factor auth was used for privileged access removes CWE-308 in that context; however, CWE-308 also arises in non-privileged contexts (normal user access, remote access, sensitive operations) that A.8.2's privileged-access scope does not reach.
- CWE-309partialblocks — A.8.2 item (f) addresses authentication strength for privileged access, permitting requirements higher than normal access (e.g., step-up authentication), which can block password-only authentication in the privileged-access context; however, the clause only governs privileged access rights, the language is permissive ('can be higher' rather than mandatory), and CWE-309 applies to authentication systems broadly, leaving the majority of instances outside the clause's reach.
- CWE-408partialblocks — Privileged access rights limit who can perform costly actions but do not enforce authentication order.
- CWE-708partialblocks — Privileged-access rules often include ownership checks, yet the control focuses on elevated rights rather than ownership correctness.
- CWE-749partialblocks — Privileged access rights limit who can invoke dangerous methods, but do not address whether the method itself should exist.
- CWE-778partialblocks — A.8.2 item (j) mandates logging of privileged access events, which blocks the exploitation of insufficient logging for that subset; the remainder is the broader set of security-critical events (failed logins, general authentication, etc.) that A.8.2 does not reach.
- CWE-782partialblocks — Privileged access rights directly restrict who may invoke sensitive IOCTLs.
- CWE-842partialremoves — A.8.2's review process (item g) and authorization requirements catch and correct administrator-placed incorrect group memberships in privileged groups when applied to a previously uncontrolled system, but it does not address product-introduced misplacements (e.g., CVE-2008-5397 where code itself assigns users to wrong groups) which require a code fix, not an administrative control.
Mitigated MITRE ATT&CK techniques (2172)
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
- T1078.002fullprevents — Domain accounts granted privileged rights must be individually authorized, time-limited, and reviewed, reducing the window and scope for domain-level abuse.
- T1078mostlyprevents — Requiring explicit authorization, time-bound allocation, separate privileged identities, and regular reviews sharply limits the ability of an adversary to abuse valid accounts with elevated rights.
- T1098mostlyprevents — Any manipulation or addition of privileged rights must pass the same authorization and logging controls, limiting an adversary’s ability to persist via account changes.
- T1136mostlyprevents — Privileged account creation is gated by an authorization process and recorded, preventing attackers from creating stealthy new privileged accounts without detection.
- T1548mostlyprevents — Stronger authentication, step-up re-authentication, and separate privileged identities raise the bar for bypassing or abusing elevation mechanisms.
- T1556mostlyprevents — Elevated authentication requirements and step-up re-authentication for privileged rights hinder attempts to weaken or bypass authentication processes.
- T1003.001partialprevents — A.8.2 constrains who holds the privileged access (admin/SYSTEM) that T1003.001 requires to dump LSASS — minimum-requirement allocation, just-in-time provisioning, and authorization reduce the population of accounts that can perform the technique — but admins must exist, an adversary who compromises any one of them can still dump LSASS, and the control does not address the code-execution or SSP-modification paths that the technique also uses.
- T1003.002partialprevents — A.8.2 constrains who is granted SYSTEM-level access (the prerequisite for T1003.002) through authorization, minimum-need allocation, temporary grants, and reviews, which reduces the attack surface and the population able to execute the technique; however, it does not prevent the technique from running when someone with the necessary access attempts it, since the SAM database remains readable by any process holding SYSTEM privileges and A.8.2 governs authorization rather than blocking the technique's execution.
- T1003.003partialprevents — A.8.2 constrains who holds privileged access to domain controllers (minimum requirement, JIT, separate admin identities, re-authentication, logging), reducing the population that can read NTDS.dit, but it does not prevent the technique from running by anyone who legitimately holds that access — the file is still readable to authorized admins, and a compromised privileged identity still satisfies the technique's precondition.
- T1003.004partialprevents — A.8.2 constrains who is granted privileged access (including SYSTEM) through authorization, step-up authentication, and review, which prevents unauthorized users from being allocated the access the technique requires; but it does not prevent the extraction itself once SYSTEM is obtained, whether through compromise of an authorized account or privilege escalation, so the technique's mechanism remains reachable.
- T1003.005partialprevents — A.8.2 constrains who holds SYSTEM/sudo access — the prerequisite for extracting cached credentials — by limiting allocation, requiring step-up authentication, logging use and avoiding generic admin IDs, but it does not remove the cached credentials themselves (a design feature of domain authentication) nor prevent an adversary who obtains privileged access through other means from running Mimikatz/secretsdump to extract them.
- T1003.006partialprevents — A.8.2 constrains who holds the privileged group memberships (Domain Admins, Enterprise Admins) and computer-account privileges DCSync requires, and its JIT, expiry, review and no-shared-identity clauses shrink the standing attack surface; but the technique also runs under specific AD replication rights (Replicating Directory Changes/All) that A.8.2 does not directly govern, and any compromised account that legitimately holds the privilege still permits DCSync, so the control reduces rather than eliminates the technique's feasibility.
- T1003.007partialprevents — A.8.2 constrains who holds the root/privileged access that T1003.007 requires to read other processes' memory, reducing the attack surface through authorization, just-in-time grants, logging and avoidance of generic admin IDs; but it does not prevent the technique from running by anyone who obtains those privileges (authorized insider, compromised credential, vulnerability-based escalation), and the no-root variant reading own-process memory remains unaffected.
- T1003.008partialprevents — A.8.2 constrains who holds privileged access (minimum privilege, authorization, expiry, reviews, no shared identities, separate admin identities), shrinking the population that can read /etc/shadow, but it does not remove the technique — any account that legitimately or illegitimately obtains root can still dump the files, and the control's logging/review clauses are detective rather than preventive.
- T1006partialprevents — T1006 requires privileged access to bypass file system controls and access logical volumes directly; A.8.2 controls the allocation of privileged access rights, so it constrains who can perform the technique, but authorized privileged users can still execute it — the technique is restricted, not prevented.
- T1020.001partialprevents — A.8.2 constrains who can hold the privileged access on network devices and cloud infrastructure required to configure traffic mirroring, so unauthorized users cannot easily enable it; however, authorized administrators (insiders or compromised valid accounts) can still configure mirroring, and supply-chain compromises of device firmware (ROMMONkit, system image) bypass the control entirely, leaving a substantial remainder.
- T1021partialprevents — A.8.2 constrains the privileged-access dimension of T1021 — separate admin identities, higher authentication, minimum-requirement allocation, authorization gating, and logging all block the path where a compromised account is used for privileged remote lateral movement — but it does not prevent T1021 with non-privileged valid accounts, which remains the technique's bulk.
- T1021.001partialprevents — A.8.2 constrains privileged access through authorization, review, and temporary grants, which reduces the pool of accounts usable for RDP but does not eliminate the technique because valid non-privileged accounts can also use RDP for lateral movement.
- T1021.002partialprevents — A.8.2 constrains who holds privileged access and when (minimum privilege, JIT/break-glass, expiry, re-authentication step-up), so an adversary with only a non-privileged compromised account cannot reach C$/ADMIN$/IPC$ — the technique runs and fails. It does not, however, prevent the technique when an adversary has compromised an admin credential inside its valid window, when NTLM hashes are replayed (pass-the-hash), or when admin shares exist on the system; those remain reachable, so the prevention is a slice rather than the bulk.
- T1021.003partialprevents — A.8.2 constrains who holds privileged access rights through authorization, minimum-requirement allocation, review and expiry, which reduces the population of accounts capable of remotely activating DCOM objects; however, DCOM is a legitimate Windows mechanism that administrators require, and an attacker who compromises any authorized privileged account can still execute the technique, so the control limits the attack surface without preventing the technique from running.
- T1021.004partialprevents — A.8.2 constrains who holds privileged access and under what conditions, which reduces the pool of accounts usable for SSH-based lateral movement, but SSH itself remains available and a compromised privileged account still permits the technique.
- T1021.006partialprevents — A.8.2 constrains the privileged-access dimension of T1021.006 — authentication step-up (f), separate admin identities (l), logging (j), and minimum privilege (b) make it harder for an adversary to abuse a privileged account over WinRM — but the technique can run with any valid non-privileged account, and A.8.2 does not restrict the WinRM protocol itself, so the prevention is a slice rather than a closure.
- T1021.007partialprevents — A.8.2's requirements for higher authentication on privileged access (item f), just-in-time provisioning (item i), separate identities for admin tasks (item l), and avoidance of generic admin IDs (item h) constrain an adversary's ability to use federated valid accounts to reach privileged cloud management actions, but the technique itself — logging into cloud services with valid federated credentials — still executes; non-privileged cloud access and application access tokens remain reachable, so the control reduces rather than eliminates the technique's viability.
- T1021.008partialprevents — A.8.2's authorization process, minimum-privilege allocation, step-up authentication (f), avoidance of generic admin IDs (h), and event-by-event granting (b),(i) constrain the attack surface and prevent many instances where the adversary lacks authorized, non-expired credentials with appropriate privileges — but the technique's premise is valid accounts, so when an adversary holds legitimately authorized privileged credentials, A.8.2 does not stop the cloud-native connection from succeeding.
- T1036.010partialprevents — A.8.2's authorization process (c), prohibition on generic admin IDs like 'root' (h), and per-person identity rule (k) prevent a meaningful slice of masquerade account creation for privileged accounts, but the technique also applies to non-privileged and service accounts outside A.8.2's scope, and an adversary with sufficient system access can still create or rename accounts to bypass the authorization gate.
- T1037partialprevents — A.8.2 constrains who holds privileged access (just-in-time provisioning, no generic admin IDs, separate identities, logging), which is required to modify system-level boot/logon scripts, shrinking the pool of accounts that can plant T1037 persistence — but it does not remove the technique itself: authorized privileged users can still create such scripts, and several T1037 variants (user-level logon scripts, per-user startup items) do not require privileged access at all.
- T1037.001partialprevents — A.8.2 restricts privileged access to authorized users on a need-to-have basis and prohibits generic admin IDs, which reduces the set of accounts that can write to the logon script registry key, but the technique can still be executed by any account that legitimately holds those rights or by an adversary who has already compromised one.
- T1037.002partialprevents — A.8.2 constrains who holds privileged access and when (minimum requirement, temporary grants, separate admin identities, logging), shrinking the pool of accounts that can write to com.apple.loginwindow.plist, but it does not stop the file modification itself — any identity that legitimately holds root can still create the hook, so the technique remains possible for those with admin rights.
- T1037.003partialprevents — A.8.2 constrains who holds privileged access rights and logs their use, which blocks the administrator-account path to modifying AD/GPO-assigned logon scripts, but the technique explicitly also works with local credentials and A.8.2 does not directly address logon-script configuration as a persistence surface.
- T1037.004partialprevents — A.8.2 controls allocation of privileged access, so users without authorized root cannot modify RC scripts; however, any authorized administrator with root privileges can still legitimately modify these scripts, and A.8.2 does not constrain what authorized privilege holders do with their access, leaving a substantial remainder.
- T1037.005partialprevents — A.8.2 constrains privileged access through authorization, review, and temporary grants, which reduces the window for an adversary to write to /Library/StartupItems, but the technique can still be executed by any process or user that already holds root, and the control does not remove the directory or block the write itself.
- T1047partialprevents — A.8.2 constrains who holds privileged access rights, which limits the accounts that can use WMI for administrative operations, but it does not remove WMI as a capability — WMI is a built-in Windows feature that cannot realistically be stripped, and non-privileged users can still invoke WMI for local execution and discovery, so the technique remains reachable through any compromised account.
- T1053partialprevents — A.8.2 constrains the privileged-access vector of T1053 — remote scheduling, elevated execution context, and abuse of generic admin identities — through authorization, just-in-time allocation, step-up authentication, and logging, but it does not remove the local task-scheduling capability that any standard user can still invoke, so a meaningful slice is prevented while the local non-privileged path remains intact.
- T1053.002partialprevents — A.8.2 constrains who holds the privileged access (local Administrators on Windows, superuser on Linux/macOS) that T1053.002 requires, so a well-implemented control reduces the population able to invoke `at` and adds step-up auth and logging; but it does not remove the `at` binary, does not configure `at.allow`/`at.deny`, and any account that legitimately holds admin rights — or one compromised at that level — can still schedule tasks, so the technique is constrained, not prevented.
- T1053.005partialprevents — A.8.2 constrains who holds privileged access and how it is granted (least privilege, JIT, separate admin identities, step-up auth), so an adversary without authorized privileged rights cannot create scheduled tasks; but the technique requires SYSTEM/administrator rights and A.8.2 does not remove the Task Scheduler itself, so an adversary who has compromised or holds authorized admin credentials can still execute it.
- T1053.006partialprevents — A.8.2 restricts privileged access to authorized users and requires separate identities for administrative tasks, which prevents non-privileged users from writing to privileged timer paths, but user-level timers in ~/.config/systemd/user/ remain reachable without privileged access.
- T1053.007partialprevents — A.8.2 constrains who holds the cluster-admin or namespace-admin privileges required to create CronJobs/Jobs in Kubernetes, so unauthorized identities cannot reach the technique; however, any authorized user with legitimate privileged access can still author a malicious CronJob, and compromised credentials of those users bypass the authorization process entirely, so the technique remains executable by a bounded but real population.
- T1059.008partialprevents — A.8.2 constrains who can exercise privileged access on network devices through authorization, authentication step-up, logging and time-bound grants, which blocks unauthorized users from reaching privileged CLI modes; however, the CLI must remain available for legitimate administration, authorized users can still abuse it, and adversaries exploiting vulnerabilities or using compromised credentials can still execute commands — so the technique is constrained, not prevented.
- T1059.009partialprevents — A.8.2 constrains who holds privileged access rights and how those rights are allocated, reviewed, and used (items a, b, f, i, l), which limits the set of identities that can invoke privileged cloud API operations — but it does not remove the cloud APIs themselves or prevent the technique from running, since adversaries with valid (possibly stolen) credentials can still call the APIs; the technique executes, it just may lack the privileges to do damage.
- T1059.012partialprevents — A.8.2 controls the allocation and lifecycle of privileged access, which is the precondition for T1059.012 — the hypervisor CLI requires admin-level access to run. Time-bound provisioning, authorization requirements, expiry, and stronger authentication reduce the population and window of accounts that can invoke esxcli/vim-cmd, but the CLI must exist for legitimate administration and cannot be removed, and if an adversary obtains valid credentials through other means A.8.2 does not stop the technique from executing.
- T1059.013partialprevents — A.8.2 constrains privileged access through authorization, review, and temporary grants, which reduces the attack surface for container CLI/API abuse, but the technique can still be executed by any user with legitimate container access or through compromised non-privileged accounts.
- T1070.008partialprevents — A.8.2 restricts who holds privileged access to mail systems and reduces the attack surface (just-in-time grants, no generic admin IDs, separate identities for admin tasks), so non-privileged users and compromised day-to-day accounts cannot run the technique; however, when an authorized privileged account is compromised or abused, the technique still executes, so the prevention is bounded rather than complete.
- T1072partialprevents — A.8.2 constrains who can access the centralized deployment tools (authorization, minimum requirement, stronger authentication, no generic admin IDs, logging, review), shrinking the population that can run the technique, but it does not prevent an adversary who has compromised a privileged account or who legitimately holds one from using SCCM/Intune/etc. to execute commands — the technique's mechanism is the legitimate use of these tools, which A.8.2 governs rather than blocks.
- T1078.001partialprevents — A.8.2 element (h) directly addresses avoiding generic administration user IDs like 'root', and the broader authorization framework constrains which identities receive privileged access, but the clause manages allocation rather than the existence of default accounts — it does not require disabling or removing them, so a default account that is not used for legitimate privileged access can still be abused by an adversary who reaches it.
- T1078.003partialprevents — Local privileged accounts are issued only after authorization, with expiry and non-sharing rules, making long-term or shared local-admin compromise harder.
- T1078.004partialprevents — A.8.2 prevents abuse of over-privileged, shared, and standing cloud accounts via minimum privilege, MFA/step-up auth, JIT access, and prohibition of generic admin IDs, but it does not prevent the initial compromise of a cloud account (phishing, brute force) nor abuse of non-privileged cloud accounts, which the technique also covers.
- T1098partialdetects — A.8.2's logging of privileged access (j) and periodic reviews of privileged users (g) provide some detection of account manipulation, but the control's primary mechanism is preventive (authorization, allocation rules), and its logging captures use of privileges rather than the manipulation events themselves, leaving significant gaps for detecting credential or permission-group changes.
- T1098.001partialprevents — A.8.2's minimum-privilege and authorization requirements reduce the number of accounts that can add credentials and require approval for privileged actions, which prevents some instances of T1098.001; however, accounts that legitimately need to add credentials (service principal management, key creation) must retain those permissions, and if such an account is compromised the technique still runs, so the preventive effect is bounded.
- T1098.002partialprevents — A.8.2's authorization process, minimum-requirement principle, and review requirements can prevent unauthorized delegate permission grants, but once an adversary compromises an account that already holds the authority to grant mailbox permissions, the control's governance does not stop the technique from executing.
- T1098.003partialprevents — A.8.2's authorization process (c), step-up authentication (f), event-by-event allocation (b), and expiry (d) constrain how privileged roles are granted and can require approval or additional authentication before role additions, which prevents some instances; however, an adversary who has already compromised a sufficiently privileged cloud account can use APIs like AttachUserPolicy or CreatePolicyVersion to add roles, bypassing the allocation controls, so the technique is reduced rather than eliminated.
- T1098.004partialprevents — A.8.2 restricts privileged access to authorized users through an authorization process and requires regular review, which reduces the set of accounts an adversary can reach to modify authorized_keys, but the control does not prevent modification of the file by an already-privileged user or through a compromised account that retains legitimate access.
- T1098.006partialdetects — A.8.2 requires logging all privileged access for audit purposes, which surfaces the creation of a new RoleBinding or ClusterRoleBinding as an auditable event, but the control's mechanism is a record-keeping requirement rather than active monitoring, so detection depends on the audit process being reviewed and correlated.
- T1098.006partialprevents — A.8.2's authorization process (c), review requirements (g), and expiry rules (d) constrain the addition of new role bindings by requiring approval and periodic re-validation, but the technique presupposes an adversary with sufficient permissions — often a compromised authorized account — so the control shapes the process without preventing execution when authorization rights are already held.
- T1098.007partialdetects — A.8.2's logging of privileged access (item j) and records of allocated privileges (item c) provide some signal that could surface unauthorized group membership changes — an adversary adding accounts to privileged groups must use privileged access to do so, and reconciliation of authorized vs. actual group membership would reveal the discrepancy — but the control is primarily preventive (authorization-based) and its logging captures privileged access use rather than the specific group-manipulation action, so detection is indirect and depends on correlation rather than being a direct observation of the technique.
- T1098.007partialprevents — A.8.2's authorization process, review requirements, expiry of privileged access, and avoidance of generic admin IDs constrain the legitimate path for group membership changes and limit persistence duration, but cannot prevent an adversary who has already obtained privileged credentials from using them to add accounts to groups — the technique executes against the control's own allocation framework.
- T1110partialprevents — A.8.2's requirements for higher authentication on privileged accounts (f), avoidance of generic admin IDs (h), and time-windowed/temporary privileged grants (i) constrain brute force against privileged accounts, but the control governs allocation and management of privileged rights rather than authentication mechanisms, and does not address brute force against non-privileged accounts, password complexity, lockout, or rate limiting.
- T1110.001partialprevents — A.8.2 addresses password guessing only against the privileged-account subset: higher authentication requirements (f), avoidance of generic admin IDs like root (h), and step-up/re-authentication reduce the guess surface for privileged credentials, but the control does not address password complexity, lockout, or rate-limiting and does not cover non-privileged accounts, which are the bulk of T1110.001's target space.
- T1110.003partialprevents — A.8.2 governs privileged access rights specifically, and within that scope its mechanisms — higher authentication requirements (f), avoidance of generic admin IDs (h), just-in-time privileged access (i), and separate admin identities (l) — prevent password spraying from succeeding against privileged accounts. However, the technique's primary targets are the many regular user accounts being sprayed, which fall outside A.8.2's scope and are governed by other access control clauses.
- T1110.004partialprevents — A.8.2 prevents credential stuffing against privileged accounts specifically — separate identities for admin work (item l), stronger authentication and step-up (item f), and authorization gating mean a stuffed credential rarely yields privileged access — but the technique's bulk targets regular user accounts, which fall outside this clause's scope, so only a slice of the technique's surface is prevented.
- T1112partialprevents — A.8.2 restricts privileged access to authorized users on a need-to-have basis and requires separate non-privileged identities for day-to-day tasks, which reduces the window where an adversary with a foothold can reach registry keys requiring administrator-level access, but the technique also operates on user-accessible keys and the control does not remove the need for privileged accounts to exist.
- T1114.002partialprevents — A.8.2 constrains privileged access through authorization, just-in-time grants, and separate admin identities, which reduces the window and scope of access an adversary can exploit, but it does not eliminate the technique because credentials can still be stolen from an authorized privileged user or obtained through other means.
- T1133partialprevents — A.8.2 constrains who is granted privileged access via remote services and requires stronger authentication for that access, preventing unauthorized privileged entry through those services; however, T1133 also operates via valid non-privileged accounts, unauthenticated exposed services (Docker/Kubernetes APIs, RDP), and Tor hidden services — none of which A.8.2's privileged-access controls reach.
- T1134partialprevents — A.8.2 reduces the attack surface for token theft by limiting who holds privileged tokens (minimum requirement, no generic admin IDs, separate identities for admin vs day-to-day, step-up authentication), but it does not prevent the technique itself — token manipulation APIs remain callable by any process and standard users can use runas, so the mechanism is constrained, not blocked.
- T1134.002partialprevents — A.8.2 constrains the conditions T1134.002 needs — minimum privilege, expiry, no shared/generic admin IDs, separate identities for admin vs day-to-day, and higher authentication — which reduces the pool of stealable tokens and limits their lifetime, but the technique's mechanism (CreateProcessWithTokenW, runas) is not blocked and still executes against any compromised privileged account, so the control shapes the attack surface rather than preventing the technique from running.
- T1134.005partialprevents — A.8.2 reduces the preconditions for T1134.005 by limiting who holds privileged access, enforcing separate identities for admin tasks, requiring review and expiry, and logging privileged use — shrinking the set of accounts from which Domain Admin rights can be harvested — but it does not address Active Directory attribute manipulation directly, so an adversary who has already obtained the necessary privileges can still execute the technique.
- T1136.001partialprevents — A.8.2 constrains who can create accounts and requires authorization, logging, and review, which reduces the chance an adversary with existing access can silently add a local account, but it does not prevent the creation itself once privileged access is obtained.
- T1136.002partialprevents — A.8.2 controls the allocation of privileged access through authorization, review, and temporary grants, which constrains the creation of unauthorized domain accounts but does not prevent an adversary with already-compromised privileged credentials from performing the action.
- T1136.003partialprevents — A.8.2's authorization process and event-by-event allocation of privileged access (b, c, i) constrain what privileges a newly created cloud account can receive without approval, but the control governs allocation of privileged rights rather than account creation itself — an adversary who has the technical means to create the account can still do so, and the account may be granted non-privileged or scoped access that still serves the technique's persistence goal.
- T1185partialprevents — A.8.2's restrictions on privileged access (least privilege, separate admin identities per item l, step-up authentication per item f) prevent the variant of T1185 that requires SeDebugPrivilege or high-integrity/administrator rights to pivot into an authenticated intranet, but the core session-hijacking mechanism — inheriting cookies, HTTP sessions and SSL client certificates within the user's existing browser security context — operates without elevated rights and is untouched by this control.
- T1199partialprevents — A.8.2 constrains what a compromised third-party account can do through minimum-privilege allocation, time-bound access, step-up authentication, logging and review, so some abuses of the trusted relationship are prevented or bounded; but the clause governs how the organization manages privileged access, not whether third-party trust relationships exist or how the third party is secured, so the technique as a class still runs and many instances still succeed.
- T1205.002partialprevents — T1205.002 explicitly requires elevated permissions to install socket filters, and A.8.2 constrains who holds privileged access (authorization, minimum requirement, no generic admin IDs, separate identities, review), shrinking the set of accounts that can execute the technique; but the clause grants privileged access to authorized users by design, so any account that legitimately or through compromise holds those rights can still install filters, leaving the technique reachable.
- T1207partialprevents — A.8.2 constrains the allocation of the Administrator privileges T1207 requires — minimum-requirement grants, just-in-time allocation, avoidance of shared admin IDs, and logging — which reduces the attack surface and the window of opportunity, but it does not prevent the technique from being executed by anyone who legitimately or illegitimately holds those privileges, and the KRBTGT-hash path is outside the clause's scope.
- T1213.006partialprevents — A.8.2 limits who holds privileged database access through authorization, expiry, separate identities and step-up auth, which reduces the attack surface for broad data mining, but the technique can run with non-privileged read credentials that A.8.2 does not govern, so the prevention is a slice rather than a closure.
- T1222.001partialprevents — A.8.2 constrains who is granted the privileged access needed to modify DACLs through authorization, minimum-requirement allocation, expiry, higher authentication, and avoidance of generic admin IDs, which reduces the population able to run icacls/takeown against protected objects; but it does not stop an authorized privileged user — or an adversary who has compromised one — from using those privileges to alter file/directory permissions, and it does not address file-level ACL management itself, so a bounded remainder of the technique remains reachable.
- T1222.002partialprevents — A.8.2 restricts who is granted privileged access rights and under what authorization, which constrains an adversary's ability to chmod/chown protected files outside their ownership; however, the technique can be executed by any user on files they already own without needing elevated rights, so the control bounds the technique's reach against protected resources without eliminating it.
- T1484partialprevents — A.8.2 constrains who is granted privileged access (authorization, minimum requirement, JIT/break-glass, regular review, avoidance of generic admin IDs), which reduces the population of accounts that can be abused to modify domain or tenant policy; but once an identity holds the necessary privileges — whether legitimately or via compromise — A.8.2 does not stop that identity from executing the modification, so the technique remains possible for those with access.
- T1484.001partialprevents — A.8.2 restricts who is granted write access to GPOs through its authorization process, minimum-privilege allocation, and review requirements, which reduces the population of accounts that can perform T1484.001; however, it does not prevent the technique from executing once an adversary has compromised any account holding that delegated write access, so the prevention is a reduction in attack surface rather than a closure of the technique.
- T1484.002partialprevents — A.8.2 constrains who holds privileged access and how it is granted, reviewed and logged, which raises the bar for modifying domain trusts but does not eliminate the technique because a compromised privileged account or an insider with legitimate access can still perform the modification.
- T1485.001partialprevents — A.8.2 constrains who holds the privileged access (e.g., PutLifecycleConfiguration) the technique requires, mandates stronger authentication for it, and limits it via JIT/break-glass and reviews, which shrinks the attack surface; but privileged access is necessary for legitimate operations and cannot be removed, so an authorized administrator can still execute the API call, leaving a substantial remainder the control does not reach.
- T1489partialprevents — A.8.2 restricts who holds privileged access rights, and T1489 requires privileged access (local admin/root, cloud IAM, or service admin) to stop or disable services; the control prevents unauthorized users from executing the technique, but authorized users — including compromised or malicious insiders with legitimately granted privileges — can still stop services, so the prevention is bounded by the authorization boundary the control itself creates.
- T1490partialprevents — T1490 requires privileged access to execute (vssadmin, wmic, wbadmin, bcdedit, etc.), and A.8.2 constrains who holds those rights, requires authorization, logs use, and limits grant duration — so an attacker without privileged credentials cannot run the technique. But the control does not prevent the technique itself: an adversary who has obtained privileged credentials (legitimately or through compromise) can still execute it, and A.8.2 governs allocation, not the underlying capability.
- T1491.002partialprevents — A.8.2 prevents defacements that require unauthorized privileged access to the web server or CMS (via strong authentication, limited admin accounts, no shared identities, logging), but many external defacements exploit web application vulnerabilities or compromised service accounts that bypass the privileged-access control surface, leaving a substantial remainder.
- T1495partialprevents — A.8.2 restricts who can hold privileged access rights and logs their use, so firmware writes requiring OS-level admin/root privileges are gated behind authorization, expiry and review; however, firmware corruption can also occur via physical access, vendor management interfaces (e.g. network device consoles), or supply-chain compromise, none of which A.8.2 reaches.
- T1496.004partialprevents — A.8.2's privileged access controls (strong authentication, no shared identities, regular reviews, logging, temporary access) reduce the risk of privileged credential compromise leading to SaaS abuse, but the technique can execute with non-privileged SaaS credentials and A.8.2 does not specifically govern SaaS API keys or service-level access controls that are the actual attack surface for T1496.004.
- T1505partialprevents — A.8.2 constrains one path to T1505 by tightly controlling who holds privileged access rights (authorization, minimum requirement, review, separate admin identities), so an adversary who compromises a normal account cannot install server components requiring OS-level privilege; however, T1505 frequently executes through application-level extension mechanisms (web shells via vulnerable apps, plugins via admin panels) that do not require OS privileged access, and an authorized administrator can still install a malicious component, so the control reduces a slice of the attack surface without preventing the technique.
- T1505.001partialprevents — A.8.2 constrains who can create or modify stored procedures by controlling allocation of the elevated database privileges the technique requires (authorization, minimum-need, review, no generic admin IDs, stronger authentication), but it does not remove stored procedures as a feature and cannot stop an authorized insider or an attacker who has compromised an authorized account from crafting malicious ones — so the technique remains possible, just gated.
- T1505.002partialprevents — A.8.2 controls who holds privileged access rights (authorization, review, logging, just-in-time grants), and registering a transport agent requires Exchange Organization Management-level privilege, so a properly implemented control prevents unauthorized identities from installing one; however, an adversary who has compromised valid admin credentials or an insider with legitimate privileged access can still register the agent, leaving a meaningful remainder the clause does not reach.
- T1505.004partialprevents — A.8.2 constrains who holds privileged access required to install IIS components, blocking unauthorized users from executing the technique, but it does not prevent an authorized administrator (or an attacker who has compromised privileged credentials) from installing a malicious ISAPI extension, filter, or module — the technique still runs whenever the actor has the access A.8.2 grants.
- T1505.005partialprevents — A.8.2 restricts who holds privileged access through authorization, JIT allocation, reviews and step-up authentication, and the technique requires privileged access to modify termsrv.dll or its ServiceDll registry value; this reduces the standing pool of accounts that can perform the modification, but A.8.2 does not control what authorized privileged users do with system files, so an attacker (or compromised admin) with valid privileged access can still execute the technique.
- T1505.006partialprevents — A.8.2 constrains who holds privileged ESXi access and how it is exercised (authorization, step-up auth, JIT, logging, no shared admin IDs), which reduces the attack surface for unauthorized VIB installation, but it cannot prevent an authorized privileged user from installing a malicious VIB nor an attacker who has compromised legitimate credentials, and the `--force` flag bypass remains available to anyone with `esxcli`.
- T1525partialprevents — A.8.2 constrains who holds the privileged rights needed to list and modify container/VM images in a registry through authorization processes, minimum privilege, expiry, and logging, which reduces the population able to implant images; however, it does not prevent the technique if an adversary compromises a legitimately privileged identity, and it does not address the initial access required to reach the registry in the first place.
- T1529partialprevents — A.8.2 restricts who holds privileged access (SeShutdownPrivilege, root, admin equivalents) needed for T1529, so unauthorized users cannot perform it, but the technique remains a legitimate admin function that any authorized privileged user can still execute — the control governs access to the capability rather than removing it.
- T1538partialdetects — A.8.2's logging requirement (j) creates audit records of privileged access that could surface unauthorized dashboard use, but the control is primarily preventive (authorization, minimum privilege, step-up auth) and does not mandate analysis of those logs for anomalous activity — detection of stolen-credential dashboard access is performed by monitoring controls (A.8.16), not by A.8.2 itself.
- T1538partialprevents — A.8.2's step-up authentication (f), time-limited/JIT privileged access (i), and separation of admin from day-to-day identities (l) can prevent an adversary with stolen credentials from reaching a privileged cloud dashboard, but the technique fundamentally relies on credential theft which A.8.2 does not address, and the clause sets requirements rather than mandating universal mechanisms, so a meaningful slice of instances still succeed.
- T1542.001partialprevents — A.8.2 constrains who can perform privileged operations, which blocks the unauthorized-OS-level path to flashing firmware, but it does not prevent authorized admins (legitimate or compromised) from flashing, does not address physical-access attacks, and does not stop firmware-level exploits — so the technique remains reachable through several paths the clause does not cover.
- T1542.003partialprevents — A.8.2 restricts who holds admin/root privileges and logs privileged use, which blocks the software path to writing boot sectors or modifying the EFI System Partition — those operations require elevated rights. It does not, however, address physical/raw access to the boot drive or firmware-level vectors that bypass OS privilege controls, so the prevention is bounded.
- T1543partialprevents — A.8.2 constrains who holds privileged access rights through authorization, review, expiry, and logging, which reduces the population able to create or modify system services/daemons; however, any authorized privileged account (insider abuse or compromised credential) can still execute T1543, and A.8.2 does not address the technique's mechanics directly, so prevention is a slice rather than a closure.
- T1543.002partialprevents — A.8.2 restricts privileged access to authorized users through an authorization process, which prevents an unprivileged adversary from creating or modifying systemd services that require root, but the control does not prevent a user with legitimately granted privileges from abusing them to establish persistence.
- T1543.003partialprevents — A.8.2 constrains who holds the privileged access required to create or modify Windows services (minimum privilege, authorization, JIT, logging, no shared admin IDs), shrinking the attacker pool, but it does not remove the capability itself — any authorized administrator can still register a malicious service, and the clause governs access rather than the action performed with it.
- T1543.004partialprevents — A.8.2 constrains who holds privileged access and logs/reviews its use, which reduces the surface for obtaining the elevated privileges T1543.004 requires to install a Launch Daemon, but it does not stop an authorized administrator (or anyone who has already obtained privileged credentials) from writing the plist — the technique remains executable by anyone who passes the authorization gate.
- T1543.005partialprevents — A.8.2's authorization, minimum-privilege, stronger-authentication, no-generic-admin-ID, and review controls prevent unauthorized users from reaching container services (Docker daemon, kubelet, etc.), but the technique's core mechanism — an authorized user abusing legitimate privileged access to create malicious containers or DaemonSets for persistence/escalation — is not stopped by access controls alone, leaving a named remainder.
- T1546partialprevents — A.8.2 constrains privileged access rights through authorization, review, and temporary grants, which reduces the attack surface for creating or modifying event triggers that require elevated permissions, but does not eliminate the technique because triggers can be established with non-privileged access or through unpatched vulnerabilities.
- T1546.003partialprevents — A.8.2 constrains who holds privileged access, and creating a WMI event subscription requires admin/SYSTEM rights, so non-privileged users are blocked from establishing the persistence; however, an authorized administrator can still create the subscription using legitimate privileged access, and A.8.2 does not restrict the use of WMI as a system mechanism by those it has authorized.
- T1546.004partialprevents — A.8.2 constrains who can modify system-level shell config files (/etc/profile, /etc/profile.d/*, /etc/zshenv) by controlling privileged access, but the technique also works at the user level via ~/.bashrc, ~/.zshrc, ~/.bash_profile and similar files that only require the user's own write permissions — a domain A.8.2 does not reach.
- T1546.007partialprevents — A.8.2 restricts and audits who holds privileged access, and registering a Netsh helper DLL requires modifying HKLM\SOFTWARE\Microsoft\Netsh, which needs admin rights — so the control reduces the population that can establish this persistence. But it does not prevent the technique itself: an authorized administrator (or an attacker who has compromised one) can still register a malicious helper, and the clause governs allocation and review of privileges rather than blocking specific registry writes.
- T1546.008partialprevents — A.8.2 restricts privileged access to authorized users and mandates separate identities for administrative tasks, which reduces the attack surface for accessibility feature hijacking, but the technique's core mechanism—replacing binaries or registry pointers—does not require privileged access to the files or keys in many Windows configurations, so the control constrains a slice rather than the bulk of the technique.
- T1546.009partialprevents — A.8.2 restricts who holds privileged access rights, and writing the AppCertDLLs Registry value requires elevated privileges, so the control constrains the population that can establish this persistence — but it does not prevent an authorized privileged user (or a compromised admin account) from setting the key, and the clause addresses access allocation rather than the specific DLL-loading mechanism.
- T1546.010partialprevents — A.8.2 constrains who can hold the admin privileges required to write the AppInit_DLLs registry value, narrowing the pool of accounts that can deploy this persistence mechanism, but it does not disable the AppInit DLLs mechanism itself, does not prevent a compromised or authorized admin from registering a malicious DLL, and leaves the technique fully effective once any admin-level write occurs.
- T1546.011partialprevents — A.8.2 constrains who holds administrator privileges, which the technique requires to install a shim, so tight allocation, JIT grants and avoidance of generic admin IDs reduce the population that can execute it; but the control does not prevent an authorized administrator from installing a shim, nor does it address the shimming mechanism itself, so the technique remains reachable to anyone legitimately privileged.
- T1546.012partialprevents — A.8.2 restricts privileged access rights through authorization, review, and temporary grants, which reduces the ability to write to the IFEO Registry keys that require administrator privileges, but does not eliminate the technique because an adversary who obtains privileged access through other means can still perform the modification.
- T1546.014partialprevents — A.8.2 restricts and logs who can perform privileged actions like writing emond rule files to /etc/emond.d/rules/, so unauthorized users cannot abuse the daemon, but the technique remains fully available to anyone who obtains root through any other path — A.8.2 constrains the user surface, not the mechanism itself.
- T1546.016partialprevents — A.8.2 constrains who can run an installer with elevated rights and requires temporary, event-by-event grants, but a user with legitimate temporary privilege can still execute a modified installer, so the technique is narrowed rather than blocked.
- T1546.017partialprevents — A.8.2 constrains who holds the root privilege required to write udev rule files and logs privileged actions, shrinking the attack surface, but it does not stop an authorized privileged user—or an adversary who has compromised one—from creating a malicious udev rule, so the technique remains executable by anyone legitimately holding the privilege.
- T1547.001partialprevents — A.8.2 restricts who can write to persistence locations by requiring least-privilege, separate admin identities, and temporary elevation, which blocks the write for non-privileged users but leaves the technique available to anyone who already holds or obtains the necessary rights.
- T1547.003partialprevents — A.8.2 restricts who holds administrator privileges (minimum requirement, JIT, break-glass, review), so an unauthorized user cannot register a malicious time provider DLL; but administrators must exist for functional reasons and those authorized admins can still execute the technique, so what is prevented is the unauthorized slice rather than the technique itself.
- T1547.004partialprevents — A.8.2 restricts who holds privileged access, which constrains the HKLM\Winlogon modification path (admin required), but the HKCU\Winlogon path is writable by any logged-in user without elevated rights, and authorized privileged users can still be compromised or coerced into making the registry change.
- T1547.005partialprevents — A.8.2 constrains privileged access to the registry keys that configure SSPs, but the technique can still be executed by an adversary who has already obtained the necessary privileges through other means.
- T1547.006partialprevents — A.8.2 constrains who can load a kernel module through privileged access management and authorization, but the technique can still be executed by an adversary who has already obtained root or kernel-level access through other means, so the prevention is a slice rather than a closure.
- T1547.008partialprevents — A.8.2 restricts and tightly controls who holds the privileges required to modify or add LSASS drivers, so an adversary holding only a standard account cannot execute the technique; however, any account that legitimately holds privileged access (or one compromised at that level) can still load a malicious LSASS driver, and A.8.2 adds no technical control that blocks driver modification itself.
- T1547.012partialprevents — A.8.2 restricts privileged access to authorized users on a need-to-have basis, which reduces the pool of accounts that can install a print processor, but the technique can still be executed by any account that retains SeLoadDriverPrivilege or equivalent rights.
- T1547.013partialprevents — A.8.2 constrains who can write to the system-wide `/etc/xdg/autostart` directory by limiting and reviewing privileged access, but it does not address the user-level `~/.config/autostart` variant (which any compromised user account can write to) and does not stop an attacker who has already obtained privileged access through other means from abusing it.
- T1547.014partialprevents — A.8.2 constrains who holds privileged access rights, and writing to HKLM Active Setup keys requires administrative privileges, so the authorization process, reviews, logging and least-privilege allocation narrow who can plant the StubPath value; however, any legitimately privileged user can still create the entry, and A.8.2 does not address the persistence mechanism itself, so the technique remains executable by authorized admins and by anyone who compromises a privileged account.
- T1548.002partialprevents — A.8.2 reduces the attack surface for UAC bypass by restricting who holds privileged rights (a, b), requiring step-up authentication (f), avoiding generic admin IDs (h), and separating privileged from daily-use identities (l) — so fewer accounts can click through UAC prompts and fewer cached credentials are exposed. It does not, however, configure UAC itself or prevent the auto-elevate and COM-based bypass mechanisms that are the core of T1548.002, which can still execute against a properly managed privileged-access regime.
- T1548.003partialdetects — A.8.2 item (j) mandates logging all privileged access for audit purposes, which captures sudo invocations and provides the raw data needed to detect sudo caching abuse (e.g., anomalous timestamp patterns, NOPASSWD entries, tty_tickets changes), but the control specifies logging rather than analysis or alerting, so the detection itself depends on monitoring controls (A.8.16) interpreting those logs.
- T1548.003partialprevents — A.8.2 requires least-privilege allocation, separate admin identities, and temporary grants, which constrain the sudoers configuration and reduce the attack surface, but the technique can still succeed against a compliant system through cached credentials within the timeout window or a misconfiguration that the review cycle has not yet caught.
- T1548.005partialdetects — A.8.2 includes logging of privileged access (j) and periodic review of privileged users (g), which create audit trails that can surface abuse of just-in-time access and impersonation mechanisms, but the control's primary purpose is preventive (authorizing and constraining privilege allocation), and the logging/review elements generate records rather than perform active analysis — real-time detection of anomalous JIT requests or impersonation belongs to A.8.16 monitoring those logs.
- T1548.005partialprevents — A.8.2's authorization process, minimum-privilege allocation, expiry, and review directly address the misconfigured permissions that enable T1548.005, but the technique can still execute when an adversary compromises an account that legitimately holds JIT, impersonation, or PassRole rights — a path A.8.2 does not close.
- T1548.006partialprevents — A.8.2 constrains the allocation and use of privileged accounts, which reduces the attack surface for TCC manipulation that requires elevated rights, but the technique can also be executed through non-privileged process injection into already-authorized applications, leaving a reachable path.
- T1550partialprevents — A.8.2's guidance on step-up/re-authentication before privileged work (f), time-bound temporary access (i), expiry of privileged rights (d), and separation of admin from day-to-day identities (l) can prevent some uses of alternate authentication material against privileged resources, but the clause is permissive ('should be considered') rather than mandating these mechanisms, and T1550 extends to lateral movement against non-privileged systems and contexts where step-up is not enforced.
- T1550.001partialprevents — A.8.2's minimum-privilege and authorization-process clauses (b, i) can limit the scope of what a stolen application access token can reach, so the technique is constrained rather than fully effective; however, A.8.2 governs allocation of privileged rights, not token issuance, rotation, revocation, or theft, and the technique explicitly bypasses the stronger-authentication measures (f) that A.8.2 would otherwise mandate.
- T1550.003partialprevents — A.8.2 constrains the value of stolen tickets through identity separation (l), minimum privilege (a,b), and temporary privileged access (i), so PtT with a day-to-day identity cannot yield admin tickets and standing privileged tickets are rarer; however, the technique still runs — Kerberos tickets remain stealable from memory and any captured ticket still enables lateral movement within the holder's actual privilege, so the control reduces impact rather than preventing execution.
- T1552.007partialprevents — A.8.2 constrains who may hold privileged access to the container API through authorization, authentication, logging and avoidance of generic admin IDs, which prevents unauthorized adversaries from reaching the API; however, the technique can still be executed by authorized identities (including compromised service accounts with API access) and via implementation gaps such as unsecured Docker daemons that the clause does not address.
- T1553partialprevents — A.8.2 restricts who holds privileged access, which blocks non-privileged adversaries from modifying system-level trust settings (registry, certificate stores, security policies) that most T1553 sub-techniques require; however, authorized privileged users can still abuse their access, certificate theft/creation does not require privileged access on the target, and some user-level trust bypasses remain, so the technique is reduced, not eliminated.
- T1553.004partialprevents — A.8.2 constrains who holds the privileged access required to install a root certificate (authorization, just-in-time allocation, separate admin identities, logging), reducing the attack surface, but it does not prevent the action itself when privileged access is held — a legitimate admin or a compromised privileged account can still install certificates, and the control manages allocation rather than blocking the specific write to the trust store.
- T1553.006partialprevents — A.8.2 constrains who holds the elevated permissions required to modify code signing policies (authorization process, minimum requirement, expiry, logging, no shared admin IDs), reducing the population that can execute the technique, but it does not prevent those who legitimately or compromised hold privileged access from running bcdedit/csrutil or otherwise altering signing policy, and it does not address the kernel-memory path via a vulnerable signed driver.
- T1554partialprevents — A.8.2 controls allocation of privileged access rights, which is a prerequisite for modifying host software binaries; by restricting and authorizing who holds privileged access, it reduces the attack surface. But it does not directly prevent binary modification — authorized privileged users (or attackers who compromise their credentials) can still patch, replace, or backdoor binaries, and the actual prevention of the technique lies in file integrity monitoring, application whitelisting, or code signing rather than in access-rights allocation.
- T1555.002partialprevents — A.8.2 constrains who holds privileged access and how (just-in-time grants, avoidance of generic root, separate admin identities, logging), which reduces the likelihood an adversary obtains the root access T1555.002 requires, but the technique itself — reading securityd's memory — is not addressed by access-control policy and remains fully executable by any account that does hold root.
- T1555.006partialprevents — A.8.2 constrains who is granted privileged access and requires stronger authentication (including step-up) for privileged operations, which reduces the attack surface for T1555.006 by limiting standing access to secrets managers and making credential compromise harder; however, once an adversary has obtained valid privileged cloud credentials, A.8.2 does not block the API call to retrieve secrets, so the technique can still execute.
- T1556.002partialprevents — A.8.2 constrains who holds the privileges needed to register a password filter DLL and logs privileged access, reducing the attack surface and creating an audit trail, but it does not address DLL registration, LSA integrity, or code execution controls — so an adversary who obtains privileged access through other means can still execute the technique.
- T1556.003partialprevents — A.8.2 restricts privileged access through authorization, review, and temporary grants, which reduces the attack surface for PAM modification, but an adversary who already has the required access or exploits a flaw in the authorization process can still modify PAM modules.
- T1556.004partialprevents — A.8.2's privileged access controls (authorization, review, temporary grants, separate identities) reduce the attack surface for implanting a modified system image, but the technique's core mechanism—patching the OS image itself—bypasses the access control layer entirely once executed, leaving a bounded remainder.
- T1556.005partialprevents — A.8.2 constrains who can be granted the privileged access needed to set AllowReversiblePasswordEncryption and logs privileged actions, but it does not prevent an authorized privileged administrator from enabling the property (e.g., for legacy software), nor does it address environments where the property is already enabled — the technique's preconditions are partly outside the clause's scope.
- T1556.006partialprevents — A.8.2's step-up authentication (f), JIT/break-glass provisioning (i), authorization process (c), and avoidance of generic admin IDs (h) constrain who can modify MFA configuration and add authentication friction before privileged changes, but the technique runs once an adversary has compromised an authorized privileged account — A.8.2 governs allocation and use of privileged rights, it does not stop a valid holder of those rights from disabling or modifying MFA mechanisms.
- T1556.007partialprevents — A.8.2 constrains parts of the attack surface — fewer standing privileged accounts, step-up authentication, avoidance of generic admin IDs, JIT allocation, and logging of privileged use — which limits who can register a new PTA agent or modify AD FS, but the core technique (DLL injection into PTA agents, modification of Microsoft.IdentityServer.Servicehost config) is tampering with authentication infrastructure that A.8.2 does not protect; the technique still runs against any reachable on-premises server.
- T1556.008partialprevents — A.8.2's requirement for separate privileged and non-privileged identities (k) and restricting privileged accounts to administrative tasks only (l) reduces the attack surface by preventing an adversary from planting a malicious DLL during a day-to-day user session, but the technique can still be executed if an administrator's separate privileged account is compromised or if the DLL is planted through other means.
- T1556.009partialprevents — A.8.2's authorization process, least-privilege assignment, and review requirements reduce the attack surface for conditional access policy modification, but the control governs who gets privileged access rather than directly preventing a privileged user from altering policies once access is granted.
- T1558.001partialprevents — A.8.2's controls on privileged access (authorization, minimum privilege, logging, avoiding shared admin IDs, re-authentication) reduce the attack surface for obtaining the KRBTGT hash from a domain controller, but the clause does not specifically protect the KRBTGT account or prevent ticket forging once the hash is already in hand, so the technique can still run.
- T1561partialprevents — A.8.2 constrains who holds privileged access (the mechanism disk wipe requires) through authorization, least privilege, expiry, review and avoidance of generic admin IDs, shrinking the population that can perform the technique; it does not prevent authorized privileged users from misusing their access, compromised privileged accounts from being wielded, or attackers reaching raw disk write through vulnerabilities that bypass the access-control path.
- T1561.001partialprevents — A.8.2 constrains the privileged-access path the technique often travels (valid accounts, admin shares, credential reuse) by limiting who holds privileged rights, expiring them, and requiring step-up auth, but it does not prevent the technique itself: an adversary who has obtained privileged credentials — legitimately or by compromise — can still wipe disk contents, and physical/raw-disk access bypasses the control entirely.
- T1561.002partialprevents — A.8.2 constrains who can hold the privileges needed to corrupt disk structures (least privilege, just-in-time allocation, step-up authentication, separate admin identities, avoidance of generic admin IDs), which reduces the attack surface for unauthorized disk wipes; however, the technique can still execute once an actor has obtained the necessary privileges through other means, and A.8.2 governs authorization rather than blocking the destructive action itself.
- T1563.001partialprevents — A.8.2 reduces some SSH hijacking vectors — avoiding generic root IDs (h), re-authentication/step-up (f), separate admin identities (l), and time-bound privilege (i) — but the technique's core mechanism is hijacking an already-authenticated session via the SSH agent or socket, which A.8.2's access-allocation controls do not directly address; the initial compromise that yields agent/socket access is outside this clause's scope.
- T1563.002partialprevents — A.8.2 constrains who holds SYSTEM-level privileges (the prerequisite for tscon-based session hijacking) via minimum-privilege allocation, step-up authentication, separate admin identities, and authorization processes, which reduces the attack surface; however, the technique can still execute against any session once SYSTEM access is obtained through other means, and the clause sets requirements rather than mandating a universal mechanism, so prevention is a slice rather than a closure.
- T1565partialprevents — A.8.2 constrains who holds privileged system access and logs its use, which reduces the surface for system-level data manipulation, but T1565 is reachable through application-level write paths and authorized privileged insiders acting within scope, neither of which A.8.2 closes.
- T1565.001partialprevents — A.8.2 constrains who holds privileged access and how it is allocated, reviewed, and logged, which prevents the subset of T1565.001 executed through abuse of administrative rights (e.g., a DBA or sysadmin manipulating records or files outside their role). It does not reach the broader technique: stored data can be manipulated by any user with legitimate write access, through normal application interfaces, or via compromised non-privileged accounts, none of which A.8.2 addresses.
- T1569partialprevents — A.8.2 constrains who can create or modify services by requiring authorization, least privilege, and temporary grants, but it does not remove the ability of an already-privileged actor to abuse a service they are authorized to manage.
- T1569.002partialprevents — A.8.2 constrains who can create or modify services by requiring authorization, least privilege, and temporary grants, but a user with legitimate privileged access can still abuse that access to execute a service, so the technique is narrowed rather than blocked.
- T1569.003partialprevents — A.8.2 constrains who holds privileged access (just-in-time grants, higher authentication, no shared admin IDs, authorization process), which is the prerequisite for systemctl abuse, but systemctl is a required system tool that cannot be removed, so once an attacker obtains privileged access through any vector, A.8.2 does not stop them from invoking it.
- T1574.008partialprevents — A.8.2 restricts privileged access to authorized users and enforces least privilege, which prevents an adversary from writing a malicious executable into a directory the calling program searches, but the technique can still succeed through writable directories accessible to unprivileged users.
- T1574.011partialprevents — A.8.2 limits who holds privileged access rights, which reduces the population able to modify service Registry keys under an administrative context, but the technique can also be executed by accounts granted specific Registry ACL permissions (e.g., Create Subkey on the Performance key) without full privileged status, and A.8.2 does not directly govern those Registry permissions.
- T1574.012partialprevents — A.8.2 constrains who can set system-scope COR_PROFILER (which requires registry modification and thus privileged access), closing that persistence path, but the technique also runs via user-scope and process-scope environment variables that any user can set without privileged rights, so the mechanism is only partially closed.
- T1578partialprevents — A.8.2 constrains who can hold privileged access and under what conditions, which reduces the pool of identities an adversary can compromise to reach cloud infrastructure modification, but it does not eliminate the technique because a compromised privileged identity that passes the authorization process can still perform the modification.
- T1578.001partialprevents — A.8.2 reduces the attack surface by restricting who holds snapshot-creation privileges through authorization, minimum-requirement allocation, just-in-time grants, and higher authentication, but it does not prevent the technique itself: any account that legitimately holds the privilege can still create a snapshot, and a compromised authorized account retains the capability, so the control constrains rather than blocks execution.
- T1578.003partialprevents — A.8.2 constrains who is granted the privileged access required to delete cloud instances (authorization, minimum requirement, separate admin identities, higher authentication, logging), so unauthorized actors cannot perform the technique; but the technique requires legitimate privileged access, and an authorized user or compromised credential can still execute the deletion, which A.8.2 does not stop.
- T1578.004partialprevents — A.8.2 constrains who can perform the cloud management operations the technique requires (authorization, just-in-time allocation, step-up authentication, avoidance of generic admin IDs, logging), reducing the likelihood an adversary obtains the necessary access, but it does not prevent the revert action itself by any identity that legitimately holds privileged access.
- T1578.005partialprevents — A.8.2's authorization process, temporary privilege grants, identity separation, and review requirements constrain who can hold the privileged access needed to modify cloud compute configurations, preventing unauthorized privilege allocation; however, if an adversary compromises valid privileged credentials (the typical scenario for this technique), A.8.2 governs but does not stop the modification itself, leaving a bounded remainder.
- T1599partialprevents — A.8.2 constrains credential-based abuse of privileged access on network devices (stronger auth, no generic admin IDs, separate identities, JIT access, logging), but the technique also succeeds by exploiting device vulnerabilities or misconfigurations that A.8.2 does not address, so it reduces rather than eliminates the attack surface.
- T1599.001partialprevents — A.8.2 controls who can hold privileged access to network devices and requires authorization, stronger authentication, logging, and time-bound grants — directly constraining the prerequisite for modifying NAT configurations. However, the technique can still be reached via compromised legitimate credentials, exploitation of device software vulnerabilities, or insider abuse of authorized access, so the control addresses the main vector without closing all paths.
- T1600partialprevents — A.8.2 constrains who can obtain privileged access to network devices through authorization, stronger authentication, logging, and identity separation, which blocks the unauthorized-credential path to manipulating device encryption; however, it does not address vulnerability exploitation that bypasses access controls, authorized insiders who choose to weaken crypto, or supply-chain compromise of device firmware, so the prevention is a slice rather than the bulk of the technique's attack surface.
- T1600.001partialprevents — A.8.2 constrains who can hold privileged access on network devices (authorization, strong authentication, no generic admin IDs, JIT access, logging), which raises the bar for an adversary to reach the CLI commands that reduce key space; but it does not prevent an adversary who has compromised a privileged account or exploited a vulnerability from performing the technique, so the prevention is a slice rather than a closure.
- T1601partialprevents — A.8.2 constrains who can modify a system image through authorization, least-privilege, and temporary access rules, but the technique can still be executed by an authorized insider or through a compromised privileged account that passes those checks.
- T1601.001partialprevents — A.8.2 constrains who holds administrative-level access on network devices (the prerequisite for the in-memory debug-command method and the standard operator procedures used for storage modification), but it does not prevent authorized administrators from legitimately using those procedures to patch the OS, and it does not address the boot loader / ROMMONkit path which is a separate compromise of the device.
- T1601.002partialprevents — A.8.2's authorization process, just-in-time access, and review requirements constrain who can modify system images, but the control governs access rights rather than the integrity of the image itself, so a privileged user with legitimate access can still perform the downgrade.
- T1602.002partialdetects — A.8.2(j) requires logging all privileged access for audit purposes, which would record an administrator-level dump of network device configuration files; however, the logging captures access events rather than the technique itself, requires analysis to identify the dump, and does not cover non-privileged vectors like SNMP or Smart Install that the technique explicitly names.
- T1602.002partialprevents — A.8.2 constrains who holds privileged access to network device management (SNMP, SMI, etc.) and requires authorization, logging, and avoidance of generic admin IDs, which reduces the paths by which T1602.002 succeeds; however, the technique can still run via compromised authorized credentials, protocol-level exploitation, or misconfigured management services that A.8.2 does not address, so prevention is partial rather than mostly.
- T1606partialprevents — A.8.2 restricts and controls privileged access and protects privileged authentication material, so it can prevent forged web credentials that depend on privileged APIs or admin-only secrets, but not forgery using stolen or low-privilege user secrets.
- T1609partialprevents — A.8.2 constrains who is granted privileged access to container administration services (Docker daemon, Kubernetes API, kubelet) through authorization, minimum-requirement allocation, expiry, review, and avoidance of generic admin IDs — so unauthorized identities cannot reach the mechanism T1609 abuses. It does not reach `mostly` because the technique remains fully executable by any authorized privileged identity, and a compromised authorized credential still drives the technique; the control governs allocation, not the technique's existence.
- T1610partialprevents — A.8.2's authorization process, minimum-privilege requirements, and review of privileged access rights directly constrain who can deploy privileged containers (a core variant of T1610, especially the Kubernetes escape path), but the control does not prevent container deployment by users with legitimate, scoped container-deployment rights, deployment via web UIs with their own access paths, or abuse of compromised credentials of authorized users — so it constrains a meaningful slice of the technique without closing it.
- T1611partialprevents — A.8.2's minimum-requirement and authorization controls reduce the privileged-container escape vector (one of several named in T1611), but the technique's other vectors — bind mounts, system-call abuse (unshare/keyctl), docker.sock exploitation, kernel and hypervisor vulnerabilities — are not addressed by privileged-access allocation, so only a slice is prevented.
- T1612partialprevents — A.8.2 restricts who can hold privileged access and requires authorization, logging, and step-up authentication for privileged operations, so an unauthorized user cannot reach the Docker daemon to issue a build request; however, the technique is a legitimate administrative action that authorized privileged users can still perform, and a compromised privileged account is not stopped, so the control prevents the technique only for the unauthorized slice.
- T1647partialprevents — A.8.2 constrains who can hold privileged access and requires authorization, logging and time-bound grants, which raises the bar for system-level plist modification by unauthorized users; however, much of T1647 (user-level Launch Agents, ~/Library/Preferences, info.plist within user-writable app bundles) requires no privileged access at all, and A.8.2 does not stop an adversary who has compromised an authorized privileged identity from using those rights.
- T1648partialprevents — A.8.2 constrains the privileged-access paths the technique relies on (e.g. IAM:PassRole, iam.serviceAccounts.actAs, attaching Additional Cloud Roles/Credentials to functions) through authorization, minimum-requirement, review and logging, but T1648 can also be executed by non-privileged identities with legitimate function-creation rights (a developer deploying a Lambda, a user authoring a Power Automate flow or Apps Script), which A.8.2 does not reach.
- T1649partialprevents — A.8.2 constrains who can hold privileged access and how those rights are granted, reviewed and logged, which reduces the pool of identities an adversary can compromise to reach certificate material but does not stop certificate theft or forgery once a privileged identity is obtained or a misconfiguration exists.
- T1651partialprevents — A.8.2 constrains who holds privileged access and under what conditions, which reduces the pool of identities an adversary can compromise to reach cloud administration commands, but the technique still runs on any privileged identity that is legitimately granted or already compromised before the control is applied.
- T1666partialprevents — A.8.2's minimum-privilege allocation, authorization process, expiry, and review controls reduce the population holding the Global Administrator or account-level permissions T1666 requires, but the control governs who holds privileged rights rather than blocking the cloud API calls themselves — a compromised authorized identity can still execute LeaveOrganization, CreateAccount, or subscription transfers, so the technique is constrained, not prevented.
- T1671partialprevents — A.8.2 constrains the vector where a privileged user account is used to grant OAuth consent to a malicious application (authorization process, minimum privilege, review, separate admin identities), but the technique also executes via non-privileged user consent, direct adversary-controlled application registration, and co-option of existing integrations — none of which A.8.2 addresses, since the clause governs user privileged access rather than application/service-principal management.
- T1673partialprevents — A.8.2 restricts who holds privileged access on hypervisors/hosts, and the technique's primary mechanisms (`esxcli`, `vim-cmd`, vCenter GUI) require privileged access to enumerate VMs, so unauthorized users are blocked; however, the technique still runs against any account that has been granted privileged access, including compromised or malicious insiders, so the prevention is a slice of the attack surface rather than a closure.
- T1675partialprevents — A.8.2 prevents unauthorized users from obtaining the privileged ESXi access the technique requires through authorization, minimum-privilege, strong authentication, and avoidance of generic admin IDs, but it cannot prevent abuse by users who legitimately hold those rights, nor credential compromise of authorized accounts, nor exploitation of vulnerabilities in the ESXi services themselves.
- T1685partialprevents — A.8.2 constrains who holds privileged access and how it is used (authorization, time-limiting, step-up auth, logging), which is the prerequisite for disabling security tools, but it does not protect the tools themselves — an adversary with legitimately granted or otherwise obtained privileged credentials can still stop services, modify configs, or kill processes, so the technique remains executable by anyone who reaches admin-level access.
- T1685.001partialprevents — A.8.2 restricts who is granted Administrator privileges, which is the prerequisite for the full version of T1685.001 (modifying HKLM\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System and EventLog-Application requires admin); unauthorized users are blocked from obtaining the privilege needed, but authorized administrators retain the ability to perform the technique using their legitimately granted privileges, and the clause does not constrain what an authorized admin does with those privileges.
- T1685.002partialprevents — A.8.2's minimum-privilege allocation, JIT/break-glass, re-authentication, and authorization requirements reduce the set of identities that hold the permissions needed to disable or modify cloud logging, but the control governs WHO gets privileged access rather than constraining what a privileged identity can do — an authorized cloud admin can still disable CloudTrail or mailbox auditing, so the technique is constrained, not closed.
- T1685.004partialprevents — A.8.2 constrains who is granted root and under what conditions (minimum privilege, authorization, time-bound access, logging of privileged use, step-up authentication), which reduces the likelihood an adversary obtains the root access T1685.004 requires, but the technique is about what root CAN do once held — disabling auditd is not itself blocked by A.8.2, and authorized administrators or compromised privileged accounts can still execute it.
- T1686partialprevents — A.8.2 constrains the prerequisite for T1686 — privileged access — by limiting who holds it, requiring authorization, time-bounding it, and logging its use, which reduces the attack surface; but it does not prevent the technique from being executed by anyone who legitimately holds or obtains privileged access through other means, so the prevention is a reduction in likelihood rather than a closure.
- T1686.001partialprevents — A.8.2 reduces the attack surface by limiting who holds the privileged permissions needed to modify cloud firewall rules, requiring authorization, and logging usage, but it does not prevent an adversary who has obtained valid privileged credentials from using those permissions to alter firewall configurations — the technique explicitly requires 'appropriate permissions,' and A.8.2 governs the granting of those permissions rather than blocking their malicious use.
- T1686.002partialprevents — A.8.2 constrains who holds privileged access to network devices through authorization, just-in-time allocation, separate admin identities and regular review, which blocks the Valid Accounts path to T1686.002; however, it does not prevent the technique when adversaries obtain privileged access by exploiting vulnerabilities in public-facing management interfaces (T1190) or when a legitimate privileged user abuses standing access, so the prevention is real but bounded.
- T1686.003partialprevents — A.8.2 constrains who can hold and exercise privileged access, and modifying the host firewall requires those rights, so the control reduces the set of identities that can perform the technique without eliminating it for identities that legitimately hold privilege.
Prevented OWASP Web Top 10 (2025) risks (9)
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
- A01partialblocks — A.8.2 directly controls the allocation, review, temporary use, and separation of privileged rights (and associated authentication), squarely preventing the authorization-decision slice of A01 (CWE-862/863/284/732); it leaves untouched the non-authorization members (path traversal, CSRF, SSRF, information exposure) that dominate the 2025 category.
- A02partialblocks — A.8.2's authorization, allocation, review, temporary-grant, non-generic-ID and separate-identity rules directly stop many common misconfigurations (e.g. default admin accounts left enabled, permanent broad privileges, shared root) that are the largest slice of A02; residual misconfigs (e.g. unhardened framework flags, exposed debug modes, insecure cloud IAM defaults) lie outside privileged-access rights and are untouched.
- A07partialblocks — A.8.2's authorization, allocation, review, temporary-grant, non-shared-identity and higher-authentication rules for privileged accounts directly block several authentication-failure vectors (e.g. generic/root accounts, permanent elevated sessions, shared credentials, insufficient re-auth), but leave the bulk of A07 (credential stuffing, weak password reset, most session-management flaws, brute-force on normal accounts) untouched.
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.