A.8.3 Technological
Information access restriction
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 (32)
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-3fullcovers — Both controls require the system to enforce access decisions that limit what subjects can do to objects based on policy-defined rules and attributes.
- AC-2mostlycovers — A.8.3's requirement to restrict access to authorized users and assets is largely met by ac-2's detailed account provisioning, role/group membership, privilege specification and approval workflow; a residual of ac-2's account-type definition and manager-assignment obligations sits outside A.8.3's focus on enforcement.
- AC-6mostlycovers — A.8.3's requirement to restrict access to only what is authorized and prevent unauthorized access accounts for the bulk of AC-6's least-privilege mandate, but a real residual remains because AC-6 explicitly requires the finer-grained 'necessary to accomplish assigned tasks' analysis that A.8.3 does not mandate.
Aligned NIST CSF 2.0 outcomes (17)
NIST CSF 2.0 outcomes this ISO control aligns with — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- PR.AA-05fullcovers — The ISO control's core requirement to define, enforce, and review access permissions and entitlements directly fulfills the CSF outcome of managing authorizations according to policy.
- PR.AA-01domain mandateimplements — A.8.3's operational mechanism of restricting access to only authorized identities directly operationalizes the management of those identities/credentials required by PR.AA-01 within the access-control domain
- PR.AA-03explicit mandateimplements — A.8.3 directly operationalizes authentication of users/services/hardware as the core mechanism to enforce authorized access and prevent unauthorized access, matching PR.AA-03 exactly
Related OWASP ASVS 5.0 requirements (14)
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).
Why these map — rationale
- V8.2.1mostlycovers — The ISO control's requirement to restrict function-level access according to established policies directly implements the ASVS mandate that applications enforce function-level authorization based on explicit consumer permissions.
- V8.2.2mostlycovers — By controlling which data items a given user or identity may access, the ISO guidance aligns with the ASVS requirement that applications restrict data-specific access to only those consumers holding explicit permissions for those items.
- V8.3.1mostlycovers — Requiring that access decisions be enforced through trusted configuration mechanisms and service-layer controls matches the ASVS rule that authorization must be performed at a trusted service layer rather than relying on untrusted client-side enforcement.
Related weaknesses / CWE (2596)
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-425fullremoves — A.8.3 mandates access controls on information in systems, applications and services (guidance items b, c, d), and when applied to a web application with CWE-425 flaws, requires authorization checks on all restricted URLs/scripts/files, removing the weakness.
- CWE-552fullremoves — CWE-552 is the absence of access control on files/directories (web roots without restrictions, cloud storage open to public, archives exposing sensitive files); A.8.3 mandates access restriction mechanisms (configuration controls, per-user/per-identity permissions, isolation of sensitive data), so applying it where it was not applied before configures those controls and the unauthorized accessibility stops being present — nothing of the weakness is left over.
- CWE-639fullremoves — A.8.3 mandates that access to information be restricted based on user identity and permissions, directly addressing the missing authorization check that defines CWE-639; when applied, it removes the vulnerability by requiring that such checks be implemented.
- CWE-1220mostlyremoves — A.8.3 mandates configuration mechanisms, per-user/group rights, isolation, and dynamic access management that directly supply the missing granularity for this weakness; well-implemented, the flaw (over-broad policy) stops being present in the product, with only a bounded remainder (e.g. certain physical or non-dynamic edge cases) left over.
- CWE-1230mostlyblocks — A.8.3 restricts access to 'information and other associated assets,' which a well-implemented policy reaches metadata, search indices and statistical reports alongside the original data; the remainder is metadata exposed through channels that are not access decisions (timing, error responses, public-by-design headers), the same shape of remainder that bounds A.8.3 -> CWE-200 at `mostly`.
- CWE-1230mostlyremoves — A.8.3 mandates access restrictions on information and other associated assets, and metadata derived from sensitive information falls under that scope; applying it where it was not applied before results in access controls being placed on metadata resources (search indices, statistical reports, etc.), removing most CWE-1230 instances, with the remainder being metadata exposure through inference or side channels that access controls do not reach.
- CWE-1259mostlyblocks — Information access restriction directly limits which entities can obtain or use security tokens.
- CWE-1323mostlyblocks — Technical access restrictions directly prevent unauthorized access to trace storage.
- CWE-200mostlyblocks — Restricting anonymous or unknown access and encrypting high-value information limits the exposure of sensitive data that would otherwise be obtainable by unauthorized actors.
- CWE-219mostlyblocks — A.8.3's access controls — authentication requirements, configuration mechanisms to control access in systems and services, and isolation of sensitive data — block most exploitation of files stored under the web root by preventing unauthorized retrieval; the remainder is the web server's default behavior of serving static files directly from its document root without traversing application-level access controls, which is a configuration concern A.8.3 alone does not fully reach.
- CWE-220mostlyremoves — A.8.3 applied to a system where sensitive data sits under FTP root with insufficient access control adds the access restrictions the weakness describes as missing, so the practical exposure to untrusted parties is removed; the remainder is the underlying design choice of placing sensitive data under FTP root, which A.8.3 does not relocate.
- CWE-220mostlyblocks — A.8.3's access restriction mechanisms (configuration of access in systems/applications/services, per-user data controls, isolation of sensitive data) directly address the 'insufficient access control' half of CWE-220, and a well-implemented deployment would configure the FTP service so the sensitive file is not reachable by unauthorized parties; the remainder is bounded -- FTP servers with their own authentication model that does not fully integrate with the organization's access control infrastructure, and cases where the file is served by the FTP daemon in a way that bypasses the configured access rules.
- CWE-256mostlyblocks — A.8.3's access controls block unauthorized reading of files containing plaintext passwords, which is the primary exploitation path for CWE-256; the weakness remains present (password still in plaintext) but exploitation is denied to unauthorized readers, with the remainder being memory-resident passwords and cases where the application process itself is compromised.
- CWE-260mostlyblocks — A.8.3 restricts access to information including files in systems and applications, so well implemented it blocks unauthorized actors from reading the configuration file and learning the stored password; the remainder is bounded and nameable -- the file in backups, version control, deployment artifacts, or staging environments where access controls are not consistently applied, plus authorized insiders who misuse their read access.
- CWE-274mostlyblocks — Information-access-restriction mechanisms enforce least-privilege checks that mitigate the weakness at runtime.
- CWE-276mostlyremoves — A.8.3 mandates access restriction including read/write/execute permissions per identity (guidance items b–d), so applying it to a system whose files were installed world-writable requires tightening those permissions, which removes the weakness as it exists in the operational system; the remainder is the product's installation process itself, which A.8.3 does not govern and which can re-introduce the flaw on reinstall or upgrade.
- CWE-284mostlyblocks — A.8.3 is the direct access-restriction control and, well implemented, blocks exploitation of most CWE-284 instances by enforcing per-identity/per-data access rules, isolation, and dynamic access management; the remainder is enforcement errors in the product's own code where A.8.3's policy is correct but the application fails to enforce it.
- CWE-284mostlyremoves — Applied where it was not applied before, A.8.3 mandates access restriction policies, configuration mechanisms, per-identity rights, and isolation — which removes the 'no access control' and 'misconfigured access control' instances of CWE-284. The bounded remainder is code-level enforcement bugs in the product's access control mechanism (ACL parse errors that fail open, privilege-raising without rollback, etc.), which a policy/configuration control does not reach.
- CWE-285mostlyblocks — A.8.3's access restriction mechanisms — configuration controls, per-identity permissions, dynamic access management with authentication requirements — block most exploitation of missing or incorrect authorization checks at the system and configuration layer even when the application code itself has CWE-285; the remainder is application-level authorization flaws whose specific code paths are not fully covered by the system-level access controls A.8.3 mandates.
- CWE-291mostlyremoves — A.8.3 mandates authentication via credentials or certificates and identity-based access control; applied to a system relying on IP-based authentication, it requires replacement with proper credential-based authentication, removing the weakness. The remainder is bounded: systems where IP remains a primary factor despite the policy, or where implementation is incomplete.
- CWE-306mostlyremoves — A.8.3 mandates authentication for access to information and associated assets (explicit in the dynamic access management section: 'requiring authentication, appropriate credentials or a certificate'), so implementing it where it was not applied before adds authentication to critical functions that lacked it, removing most CWE-306 instances; the remainder is nameable — secondary channels that bypass the primary authentication path, debug/UART ports, and protocol-level gaps in OT/embedded systems where access restriction is enforced at a different layer than the clause reaches.
- CWE-306mostlyblocks — A.8.3's access restriction mechanisms — including the explicit requirement to authenticate before accessing information and the controls on which identities may invoke which functions — sit in front of an unauthenticated critical function and block its exploitation, while the underlying missing-authentication defect remains in the product. The remainder is bounded and nameable: physical interfaces (UART/debug ports), secondary channels that bypass the access layer, and OT/ICS protocols where the access control cannot be interposed without redesign.
- CWE-312mostlyblocks — A.8.3 restricts who can reach the storage location, which blocks exploitation of the cleartext by unauthorized actors; the remainder is bounded and nameable — insider threats with legitimate access, compromised credentials, and access-control misconfigurations — where the cleartext is immediately readable once the access boundary is crossed.
- CWE-313mostlyblocks — A.8.3's access restriction mechanisms (per-identity read/write controls, isolation of sensitive data, configuration of access to information) block most exploitation of a cleartext file by preventing unauthorized users from reading it, but the weakness explicitly contemplates attackers with physical or administrator access to the raw disk, and authorized insiders (admins, backup operators) remain able to read the unencrypted data — a nameable remainder that keeps this from `full`.
- CWE-314mostlyblocks — A.8.3 restricts who can read the registry, which blocks the principal exploitation path for cleartext registry data; the remainder is bounded — authorized processes/accounts that are compromised, registry exports/backups that carry the cleartext out, and any read access the access policy itself grants to legitimate users.
- CWE-359mostlyblocks — A.8.3 restricts access to information based on identity and authorization, which directly blocks unauthorized actors from accessing private personal information; the remainder is exposures that are not access decisions, such as information leaked through error messages or metadata.
- CWE-425mostlyblocks — Information access restriction implements the technical enforcement that directly blocks unauthorized direct requests.
- CWE-527mostlyblocks — A.8.3's access restriction mechanisms (per-identity rights, isolation, configuration controls) block unauthorized actors from reaching an exposed version control repository, denying exploitation of the weakness even though the repository remains in an accessible location; the remainder is bounded — repositories mirrored, downloaded, or shared outside the access control plane, and access bypassed via compromised credentials.
- CWE-528mostlyblocks — A.8.3 well implemented restricts access to the directory/archive where core dumps are stored, blocking unauthorized read of the file in its primary location; the remainder is nameable — core dumps transferred to less-protected systems, included in backups with different access controls, or briefly exposed during transfer before access controls apply.
- CWE-528mostlyremoves — A.8.3 restricts access to information assets including core dump files; applied where it was not, it removes the exposure by ensuring the core dump location is not reachable by unauthorized actors, with remainder in cases where the dump is generated in a path the access policy does not cover or is transferred to a system outside its scope.
- CWE-529mostlyblocks — A.8.3's access restriction mechanisms (configuration controls, identity-based access, isolation of sensitive applications/data) directly block unauthorized reading of ACL files even when stored in a broadly accessible directory; the remainder is misconfigured access rules and cases where the directory's access control is not properly applied to the ACL files themselves.
- CWE-529mostlyremoves — A.8.3 restricts access to information and associated assets; applied to a system where ACL files are stored in an accessible directory, it requires those files to be placed under access restriction, removing the exposure. The remainder is bounded: cases where the ACL files must remain in a location with some broader accessibility for the system to function, or where access control is imperfectly implemented.
- CWE-530mostlyblocks — A.8.3's access restriction mechanisms (per-identity rights, isolation, configuration controls) directly block unauthorized actors from reading the backup file even when it sits in a nominally accessible location; the remainder is bounded and nameable -- backup files whose access path bypasses the access control (e.g., served through a web server that does not honor the access rule, or accessible via a separate channel like an FTP share outside the controlled scope), where the clause's mechanism does not reach.
- CWE-541mostlyblocks — A.8.3's access restriction blocks the canonical exploitation of CWE-541 — direct retrieval of the include file by an unauthenticated requester — by controlling who can read the file (file system permissions, web server configuration, the (b)/(d) guidance on controlling access to information). The weakness remains (credentials still sit in the include file), but the attacker cannot reach it. The remainder is bounded and nameable: include files whose contents leak through other channels (backup archives, misconfigured replicas, developer copies outside the access-controlled estate) where A.8.3's restriction does not reach.
- CWE-552mostlyblocks — A.8.3's access restriction mechanisms (no anonymous access, per-identity controls, configuration mechanisms, isolation of sensitive applications/data) directly block most exploitation of CWE-552 by denying unauthorized actors access to files and directories; the remainder is misconfigurations of the access control itself and files placed in locations outside the controlled scope.
- CWE-566mostlyblocks — A.8.3's per-user, per-data access control mechanisms (items c and d) directly address the weakness by enforcing authorization at the record level, blocking the unauthorized primary-key access; the remainder is bounded cases where access control granularity is coarser than per-record or where the application bypasses the system-level controls.
- CWE-602mostlyblocks — Information access restriction is undermined when the client is trusted to enforce it.
- CWE-612mostlyremoves — A.8.3 mandates access restriction on information assets; CWE-612 is the absence of proper access restriction on a search index. Applying A.8.3 where it was not applied before configures access controls on the index, removing the flaw. The remainder is cases where the index itself is structurally flawed (indexing content that should not be indexed at all, or leaking content through index metadata regardless of access enforcement), which is a data minimization/design issue outside A.8.3's reach.
- CWE-639mostlyblocks — Information access restriction explicitly enforces that users may only retrieve data they are authorized to see, directly addressing user-controlled key bypass.
- CWE-65mostlyblocks — Access-control rules can restrict which files a process may open, limiting the impact of hard-link redirection.
- CWE-651mostlyblocks — A.8.3 restricts access to information that exists, but CWE-651 is about the WSDL file being exposed to a wider audience than intended in the first place; the control does not stop the file from being reachable, so the weakness can still be exploited.
- CWE-784mostlyblocks — Information access restriction requires proper validation of identity tokens before granting access.
- CWE-862mostlyblocks — A.8.3's purpose is to ensure only authorized access, and its guidance directly mandates the authorization checks that CWE-862 describes as missing, so a well-implemented access restriction control fully blocks exploitation of the missing authorization weakness.
- CWE-863mostlyblocks — A.8.3's access restriction mechanisms, including granular per-user and per-identity controls, directly enforce correct authorization checks, preventing exploitation of incorrect authorization flaws.
- CWE-921mostlyremoves — A.8.3, when applied to a system with existing CWE-921 instances, configures access controls on the storage mechanism (per-user/identity permissions, isolation, authentication, and encryption under dynamic access management), removing the weakness in most cases; the bounded remainder is storage media that are physically portable and accessed outside the system's access-control plane, though A.8.3's encryption guidance partially addresses this.
- CWE-926mostlyblocks — Enforcing information-access restrictions on exported Android components directly prevents unauthorized launch or data access.
- CWE-939mostlyblocks — Enforces explicit authorization checks on which actors may invoke handlers, directly addressing the missing restriction on custom-URL-scheme access.
- CWE-1125partialblocks — A.8.3 can deny unauthorized actors access to some protected interfaces and assets, but it does not reduce the excessive number of input/output points and leaves publicly exposed, authorized, and pre-authorization paths exploitable.
- CWE-1220partialblocks — Directly requires information-access restriction at the level of individual assets and operations, addressing the granularity gap.
- CWE-1257partialblocks — Enforcing information access restrictions on memory-mapped regions directly mitigates inconsistent alias permissions.
- CWE-1262partialblocks — Information access restriction explicitly limits software access to memory-mapped register interfaces.
- CWE-1268partialblocks — Implements technical restrictions on information access that can prevent inconsistent privilege enforcement.
- CWE-1274partialblocks — Information access restriction directly addresses unauthorized access to volatile memory holding boot code.
- CWE-1280partialblocks — Enforces access restrictions before asset use, directly addressing the timing flaw.
- CWE-1299partialblocks — Information access restriction mandates controls on every path to protected assets, mitigating bypass via shadow or external interfaces.
- CWE-13partialblocks — A.8.3 restricts access to information that exists, but CWE-13 is a configuration defect that embeds a plaintext password in a file, and access controls do not stop anyone who can read the file from exploiting the stored credential.
- CWE-214partialblocks — A.8.3's isolation of sensitive applications/systems (item e) and access controls on who can view process information can block some exploitation of CWE-214 by restricting other users' ability to list sensitive processes, but the clause's primary scope is application/business-layer access control rather than OS-level process visibility, so it does not comprehensively block this specific exposure mechanism.
- CWE-257partialblocks — A.8.3 restricts who can reach the password store, blocking external attackers from exploiting the recoverable format, but the CWE explicitly names the insider threat (system administrators with legitimate access can still recover passwords), and access restriction does not stop those with authorized read access from exploiting the recoverability.
- CWE-261partialblocks — A.8.3 blocks exploitation by parties who lack authorized access to the storage location holding the weakly-encoded password, but the CWE example explicitly shows a 'devious employee' with legitimate access to config.properties or the registry key still trivially decoding the password -- so authorized insiders remain a nameable remainder that access restriction does not reach.
- CWE-266partialblocks — Information-access-restriction mechanisms enforce the correct privilege boundaries once assignment rules are defined.
- CWE-269partialblocks — A.8.3's access restriction mechanisms (per-identity rights, dynamic access management, isolation) block exploitation of improperly assigned privileges when the mis-assignment sits in a layer A.8.3's own authorization decisions override, but many CWE-269 instances are the access control itself being wrong (role definitions, self-grant, setuid programs, privilege-not-reset), where A.8.3 IS the defective layer and cannot block its own failure.
- CWE-270partialblocks — Information-access-restriction rules help limit privileges but do not cover dynamic switching errors.
- CWE-277partialblocks — A.8.3's access control mechanisms (identity-based permissions, configuration controls, dynamic access management) can block exploitation of insecure inherited permissions at higher layers (network, application, service), but the inherited permissions remain the primary access control on the objects themselves, so local or direct exploitation paths are not reached by the clause.
- CWE-278partialblocks — Information access restriction mechanisms can enforce least-privilege checks during object creation or archive extraction.
- CWE-288partialblocks — A.8.3 requires access restrictions (including no anonymous access and configuration mechanisms controlling access in systems, applications and services), which if well implemented would demand authentication on all paths and so block exploitation of an unauthenticated alternate channel; however, the weakness is a design flaw where the developer omitted authentication on a path, and A.8.3 is a policy/requirement clause whose blocking effect depends on the implementation of authentication mechanisms it does not itself enforce, leaving a nameable remainder of cases where the alternate path slips through.
- CWE-289partialblocks — Information-access-restriction mechanisms can implement canonical-name checks to prevent bypass.
- CWE-290partialblocks — Information access restriction relies on proper authentication but does not implement it.
- CWE-291partialblocks — Information-access-restriction mechanisms must authenticate subjects before granting access.
- CWE-32partialblocks — Information-access-restriction policies limit which files can be reached, mitigating impact but not the traversal vector itself.
- CWE-378partialblocks — Information access restriction can limit exposure but does not address file creation itself.
- CWE-424partialblocks — A.8.3's access restriction mechanism blocks exploitation via the paths it covers (the main, intended paths), but CWE-424 is specifically about alternate paths that bypass the access control — those paths are outside A.8.3's enforcement, so the control does not block the exploitation that constitutes the weakness itself.
- CWE-433partialblocks — A.8.3's access controls (requiring authentication, denying anonymous access to sensitive paths, configuring access to information in applications) can block exploitation of CWE-433 by preventing unauthenticated requesters from retrieving the raw file, but the underlying weakness — sensitive content placed under the web root with an unhandled extension — is a file-placement and server-configuration issue that access restriction does not directly address, and a misconfigured or bypassed access rule leaves the raw content exposed.
- CWE-524partialblocks — A.8.3 restricts access to information and assets, but CWE-524 is a code-level defect where a cache itself contains sensitive data readable by an unauthorized actor; access controls do not prevent the cache from being read once the data is placed there.
- CWE-532partialblocks — A.8.3 restricts who may access information that exists, but CWE-532 is about the product writing sensitive information into a log file in the first place; access restriction does not stop the log entry from being created or read by an attacker who reaches the log through a different path.
- CWE-548partialblocks — A.8.3 blocks exploitation by unauthenticated/unauthorized users through its access enforcement mechanisms (authentication requirements, per-identity access rights), but the directory listing weakness itself remains present and exploitable by any authenticated user with legitimate access to that directory — the control does not address the root cause of directory indexing being enabled, so the information exposure (file names, structure, creation times) survives for users who pass the access check.
- CWE-553partialblocks — A.8.3 restricts who can reach the directory containing the shell, blocking exploitation by anonymous and unauthorized external users, but the weakness (shell in an externally accessible directory) remains present and exploitable by authorized users, by anyone who bypasses or misconfigures the access control, or via any path the access policy does not cover.
- CWE-555partialblocks — A.8.3 restricts who can read the configuration file, blocking exploitation by anyone without file access, but the weakness remains present and exploitable by anyone with legitimate read access (admins, the application process itself at runtime, backup operators), so the block is real but partial.
- CWE-57partialblocks — Enforces access-control rules on files and directories, directly blocking unauthorized path traversal.
- CWE-612partialblocks — A.8.3 restricts access to information based on identity and permissions, which blocks unauthorized access to the search index itself, but it does not prevent the index from being created with improper authorization in the first place, leaving the weakness exploitable if access controls are misconfigured or bypassed.
- CWE-638partialblocks — A.8.3 governs whether access is granted at all, not whether the check is repeated on every access; CWE-638 is a flaw in the mediation logic itself, and an access restriction policy that permits a resource to be accessed once will permit it again, so the weakness remains exploitable.
- CWE-64partialblocks — Information access restriction can limit the impact of unauthorized file operations triggered by malicious shortcuts.
- CWE-647partialblocks — Enforcing strict access-control rules on canonical resource identifiers directly prevents authorization bypass via non-canonical URLs.
- CWE-654partialblocks — Information access restriction can require multi-factor checks, yet the control is wider than authentication.
- CWE-689partialblocks — Enforces access restrictions on resources, reducing exposure during copy operations.
- CWE-708partialblocks — Information-access-restriction mechanisms rely on correct ownership; eliminating incorrect ownership strengthens this control.
- CWE-732partialblocks — Requiring explicit configuration of access controls and permissions for files, applications and services counters the assignment of overly permissive default or incorrect file-system rights.
- CWE-749partialblocks — A.8.3 restricts access to information and assets, but CWE-749 is a design/implementation flaw where a dangerous method is exposed in the product's API; access restriction does not prevent the exposed method from being called by an authorized user or stop its exploitation once exposed.
- CWE-8partialblocks — A.8.3's access restriction mechanisms (authentication, authorization, per-identity rights) can block unauthorized callers from invoking the exposed remote interface methods, but the misconfiguration itself — the bean declared remote — remains present, and authorized callers can still reach the methods the weakness exposed.
- CWE-842partialblocks — Information access restriction is enforced via groups, but the control addresses restriction mechanisms, not membership correctness.
- CWE-9partialremoves — A.8.3 mandates access restriction configuration (per-identity rights, configuration mechanisms in systems/applications/services), so applying it to a J2EE application with ANYONE-role EJB permissions would require those permissions to be reviewed and properly restricted; however, the clause is a governance/policy control that mandates the configuration without itself editing the deployment descriptor, and the specific EJB misconfiguration sits in application-level deployment descriptors that A.8.3 reaches only as part of broader access-control configuration rather than as a named target.
- CWE-915partialblocks — Information access restriction limits who can modify objects but does not address which attributes may be changed.
Mitigated MITRE ATT&CK techniques (3274)
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
- T1021mostlyprevents — Enforcing explicit read/write/execute rights and device or location checks on remote services makes it harder for an adversary to abuse RDP, SMB shares, or similar channels with stolen credentials.
- T1078mostlyprevents — Requiring authenticated, non-anonymous identities and enforcing per-user or per-group permissions directly prevents adversaries from leveraging stolen or default credentials to gain unauthorized access.
- T1213mostlyprevents — Enforcing per-user read/write controls and encryption on information repositories limits the data an adversary who has gained a foothold can silently collect from collaboration platforms or databases.
- T1213.003mostlyprevents — A.8.3's access restrictions (identity-based permissions, authentication requirements, read/write/delete controls, dynamic access management) prevent unauthorized access to code repository contents once an adversary is inside the network, but the technique can still succeed if the adversary has compromised an account with legitimate repository access — a named remainder analogous to the exempted identities and service accounts on A.8.5's T1110.001 anchor.
- T1213.006mostlyprevents — A.8.3's purpose is explicitly to prevent unauthorized access to information assets, and databases are information assets; properly implemented access restriction (authentication, per-identity read/write controls, dynamic access management) prevents an adversary without authorized access from mining the database. The remainder is the same shape as A.8.5 vs T1110.001: the clause sets requirements rather than a universal mechanism, so compromised credentials of authorized users, misconfigured grants, service accounts with standing access, and authorized insiders abusing legitimate access remain reachable.
- T1530mostlyprevents — Granular, time-bound, and identity-based restrictions on cloud storage objects reduce the ability of compromised accounts to freely enumerate or exfiltrate data from cloud repositories.
- T1565mostlyprevents — A.8.3 restricts who can read, write, delete or execute on data, so an adversary without authorized access cannot reach the data to manipulate it — the unauthorized-access vector is comprehensively blocked. The named remainder is the authorized path: insiders with legitimate write permissions, and any account whose credentials are compromised, retain the access the control grants, and application-layer attacks that bypass access controls are outside its scope.
- T1565.001mostlyprevents — A.8.3 restricts who can access and modify stored data, so unauthorized actors without write permissions cannot reach the data to manipulate it; the remainder is the bounded set of authorized insiders and compromised credentials that legitimately hold write access and bypass the restriction.
- T1003.002partialprevents — A.8.3 can restrict file-level access to the SAM database for non-privileged identities via ACLs and access control mechanisms, but the technique requires SYSTEM-level access which the OS inherently grants to the SYSTEM context for legitimate operation — and governing who reaches SYSTEM is A.8.2's domain, not A.8.3's. The control addresses a slice (non-SYSTEM access paths) while the primary vector (SYSTEM-level extraction via Mimikatz, reg save, etc.) is outside its reach.
- T1003.003partialprevents — A.8.3's access restriction mechanisms (identity-based ACLs, configuration controls, isolation of sensitive applications/data) do constrain who can reach NTDS.dit and prevent casual or non-privileged access, but the technique specifically requires SYSTEM-level compromise of the domain controller, which bypasses the file-level access controls A.8.3 primarily governs; the control does not address the privilege escalation that enables the technique, so prevention is real but bounded.
- T1003.006partialprevents — A.8.3's access restriction mechanisms (dynamic access management, configuration controls, authentication requirements, time/identity-based constraints, alerting on misuse) can constrain DCSync by adding layers around replication operations and sensitive credential data, but the technique specifically requires accounts that already hold legitimate replication privileges (Domain Admins, Enterprise Admins, or computer accounts on the DC), so the underlying authorization is by design — A.8.3 reduces the attack surface and adds friction but cannot prevent the technique where the privilege is granted.
- T1003.008partialprevents — A.8.3 restricts access to information based on identity and permissions, which can prevent unauthorized reading of /etc/shadow by non-root users, but the technique can still be executed by an adversary who has obtained root access, so the prevention is limited to non-privileged contexts.
- T1005partialdetects — A.8.3 includes logging of access events and alerts on misuse of protected information, which surfaces some instances of T1005 when the adversary accesses restricted resources, but its primary purpose is access restriction (prevention) and its detection scope is limited to access events on protected assets rather than the broader file-system searching, configuration reading, and local database querying that T1005 encompasses.
- T1005partialprevents — A.8.3's access controls prevent unauthorized identities from reading sensitive data on local systems, but the technique of searching local sources still runs and still yields data the searcher is authorized to access; the prevention covers the unauthorized-access slice, not the search activity itself.
- T1021.001partialprevents — A.8.3 restricts which identities can access which systems and information, so it can block RDP access for accounts not authorized for the target system; however, the technique explicitly uses valid accounts that may be authorized, and A.8.3 governs information access rather than the authentication or service-enablement mechanisms that would fully prevent an authorized credential from establishing an RDP session.
- T1021.002partialprevents — A.8.3 provides mechanisms to restrict which identities can access shares (including disabling admin shares, controlling read/write/execute permissions, and isolating sensitive systems), but the technique explicitly uses valid accounts — if a compromised account legitimately holds access to a share, A.8.3's restrictions do not stop the technique from running, and admin shares are often required for legitimate operations so they typically remain enabled for some accounts.
- T1021.003partialprevents — A.8.3 restricts access to information and assets, which can limit which identities can remotely activate DCOM objects, but DCOM's default ACL already restricts remote activation to Administrators and the technique operates within that boundary, so the control constrains rather than eliminates the attack surface.
- T1021.004partialprevents — A.8.3 restricts access to authorized identities and can block anonymous or unauthorized SSH access, but T1021.004 specifically uses valid accounts — the technique runs when the adversary holds legitimate credentials, and A.8.3's access restrictions do not stop valid-account SSH any more than they stop any other authorized action.
- T1021.005partialprevents — A.8.3 can prevent VNC where the access restriction policy excludes VNC as an authorized remote access mechanism, restricts it to specific identities, or requires authentication mechanisms the adversary lacks; but the technique explicitly uses valid accounts, so where VNC is an authorized access path for those identities the control does not stop the technique from running.
- T1021.006partialprevents — A.8.3 restricts access to information and assets through identity-based controls, which can prevent WinRM use by accounts lacking permission on the target system; however, the technique explicitly uses valid accounts that may legitimately hold the access being exercised, so the control only blocks the slice where the valid account lacks authorization rather than the technique as a whole.
- T1021.007partialprevents — A.8.3's access restrictions (identity-based controls, authentication requirements, time/device/location restrictions, permission granularity) can prevent unauthorized cloud access via federated valid accounts, but the technique specifically abuses accounts that are legitimately synchronized/federated and authorized for cloud access, so where those accounts hold valid permissions the restrictions do not stop the access.
- T1021.008partialprevents — A.8.3's access restrictions (identity-based, device/location/time-bound, credential/certificate requirements) can prevent unauthorized identities from using cloud-native VM connection methods, but the technique explicitly leverages valid accounts that are by definition authorized, so where those accounts legitimately hold the relevant permissions the restriction permits rather than blocks the connection.
- T1025partialprevents — A.8.3's access controls (authentication requirements, encryption of information, identity-based restrictions) can prevent the adversary from reading protected data on removable media, but the technique still runs against data the compromised user has legitimate access to and against unenforced media, so the prevention is a slice rather than the bulk.
- T1037partialprevents — A.8.3's access restriction mechanisms (controlling which identities have write/execute rights, configuration controls, isolation) can prevent unauthorized modification of boot/logon script locations when applied to them, but the clause is general-purpose access restriction rather than specifically targeting script paths, and any identity with sufficient administrative privileges bypasses it.
- T1037.003partialprevents — A.8.3's access restriction mechanisms — particularly controlling which identities have write access — can limit who can create or modify logon scripts in AD/GPO, but the control's primary purpose is restricting access to information assets, not preventing persistence mechanisms; logon script assignment is a configuration concern more directly addressed by privileged access rights (A.8.2) controls.
- T1037.005partialprevents — A.8.3's access controls (particularly clause d on read/write/delete/execute permissions) can restrict who may write to /Library/StartupItems, preventing non-root adversaries from creating persistence items, but the technique executes as root and a root-level adversary bypasses these controls, so prevention is partial rather than full.
- T1039partialdetects — A.8.3's dynamic access management provisions include recording who accesses information and how, monitoring use, and raising alerts on misuse attempts — real detection capabilities against unauthorized access to network shares. However, these are conditional on dynamic access management being implemented, the primary purpose of the clause is prevention, and a compromised legitimate account exercising its granted access to shares will not trigger misuse alerts.
- T1039partialprevents — A.8.3 restricts access to information based on identity and policy, which can prevent an unauthorized user from reaching a network share, but once a system is compromised the adversary may operate with the identity of a legitimate user who has access, leaving a reachable remainder.
- T1047partialprevents — A.8.3 restricts which identities have access to systems and what privileges they hold (including execute), so it can prevent WMI abuse by users who lack administrative rights; however, WMI is a legitimate administration tool that authorized users need, and the control addresses information access rather than restricting system management interfaces, so it cannot prevent WMI abuse by any account with the necessary privileges.
- T1052partialprevents — A.8.3 restricts who can access information, which prevents exfiltration by users without access to the data, and its physical access controls (e) can limit introduction of removable media; however, it does not control removable-media ports/devices or prevent authorized users (or those who have compromised valid credentials) from copying data they can already access, so the physical-medium vector itself is not stopped.
- T1053partialprevents — A.8.3 restricts access to information and associated assets including execute permissions and identity-based controls, which provides some prevention against unauthorized task scheduling, but it is a general access control rather than one specifically targeting task scheduling abuse, and authorized users with appropriate privileges can still create and execute scheduled tasks.
- T1053.005partialprevents — A.8.3(d) explicitly covers controlling 'execute' access and A.8.3(b) covers configuration mechanisms to control access to systems, so restricting who can create scheduled tasks partially prevents the technique; however, the technique commonly runs under SYSTEM or Administrator privileges that A.8.3 does not restrict, and administrators legitimately need scheduled task access, so the prevention is bounded.
- T1053.007partialprevents — A.8.3's access restriction mechanisms (authentication requirements, identity-based controls, prohibition of anonymous access) can prevent unauthorized identities from reaching the Kubernetes API and creating CronJobs, but the technique is executed through legitimate orchestration functionality by accounts that may already be authorized, and A.8.3 governs information access rather than execution/scheduling controls, leaving a named remainder of authorized-account abuse and compromised service-account paths.
- T1059partialprevents — A.8.3 restricts access to information and systems, which can prevent an adversary from reaching an interpreter, but the interpreters required for legitimate administration cannot be removed and remain available for abuse.
- T1059.008partialprevents — A.8.3 restricts who can access network devices and at what permission level via authentication, identity-based controls, and read/write/delete/execute permissions, which prevents anonymous and unauthorized CLI access; however, the CLI must remain available for legitimate administration, authorized users can still abuse their access, and compromised credentials bypass the control — so the technique is constrained, not eliminated.
- T1059.009partialprevents — A.8.3's access restrictions (identity-based controls, authentication requirements, no anonymous access) prevent unauthorized cloud API abuse, but the technique explicitly operates 'with proper permissions' via valid credentials/tokens, so when an adversary holds authorized credentials A.8.3 does not stop the API calls from executing — the technique runs and the control's restrictions are already satisfied.
- T1059.012partialprevents — A.8.3's access restriction mechanisms (authentication requirements, identity-based access controls, restricting access to specified time frames) can prevent unauthorized users from reaching the hypervisor CLI, but the CLI is a required management tool for ESXi administration and cannot be removed or fully restricted without breaking operations; authorized administrators — or attackers who have compromised their credentials — retain the ability to invoke esxcli/vim-cmd, so the technique is constrained to a slice rather than prevented outright.
- T1059.013partialprevents — A.8.3 can restrict which identities may reach the Docker daemon API, Kubernetes API server, or kubectl, denying the technique to unauthorized users; but the control governs access to information rather than command-execution surfaces, container CLIs/APIs are typically required for legitimate operations and cannot be fully closed, and authorized identities with management access can still abuse these tools to run commands.
- T1069.003partialprevents — A.8.3 restricts access to information including group/permission metadata, so users without enumeration rights cannot successfully discover cloud groups; however, the technique requires authenticated access and cloud platforms commonly grant authenticated users visibility into their own group memberships and roles, so authorized enumeration is not stopped — the prevention covers the unauthorized slice, not the technique as a whole.
- T1070partialprevents — A.8.3 restricts who can read, write, delete or modify information and assets, so it prevents unauthorized tampering with logs and artifacts by identities without those permissions; however, T1070 presupposes the adversary already has a foothold and often operates with elevated or system-level privileges that bypass access restrictions, and many logs require write access by processes the adversary can abuse, so the technique is not prevented as a whole.
- T1070.006partialprevents — A.8.3's write-permission controls (clause d) prevent unauthorized identities from modifying file metadata, so an outsider without write rights cannot timestomp; however, timestomping is a post-compromise action typically performed by an adversary who has already obtained authorized or system-level access, which A.8.3 does not stop.
- T1070.008partialprevents — A.8.3 restricts who has delete/modify permissions on mailbox data, preventing unauthorized identities from clearing mailboxes, but the technique uses legitimate APIs and tools (ExchangePowerShell, mail utilities) by users and admins who inherently hold delete rights on mailboxes they own or administer — that legitimate-access remainder cannot be restricted without breaking mail functionality.
- T1074partialprevents — A.8.3 prevents unauthorized access to information, which blocks staging of access-controlled data the adversary cannot read; however, once an adversary has compromised a system or identity, A.8.3 cannot prevent staging within the scope of that legitimate access, so the prevention covers a slice rather than the technique's full surface.
- T1074.001partialprevents — A.8.3's access restrictions (read/write/delete/execute controls, isolation of sensitive data) can prevent staging in protected locations and limit what data a compromised identity can collect and consolidate, but once an adversary has any foothold on the system they can typically stage in some accessible location (temp dirs, user-writable space), so the technique is constrained rather than stopped.
- T1078partialdetects — A.8.3's dynamic access management subsection includes recording who accesses information, monitoring use, and raising alerts on misuse — capabilities that can surface anomalous activity from valid (compromised) accounts against high-value information. However, these detection features are scoped to a narrow subset of the control (information under dynamic access management), while the bulk of A.8.3 is access restriction without detection instrumentation, so the verb holds only partially.
- T1078.004partialprevents — A.8.3 restricts which identities can access which information and with what permissions, so a compromised cloud account constrained by least-privilege role assignments and access controls cannot reach sensitive data or perform privileged actions — the technique runs but is bounded. It does not prevent the adversary from obtaining or using valid cloud accounts in the first place (that is A.8.5's lane), and over-privileged or misconfigured roles remain reachable, so the prevention is a slice rather than a closure.
- T1080partialprevents — A.8.3's controls on write access (item d: read/write/delete/execute permissions) directly prevent unauthorized identities from tainting shared content, but shared storage typically requires broad write access for legitimate use, so an adversary compromising any authorized writer can still taint — the control addresses the access mechanism, not the content itself.
- T1083partialprevents — A.8.3 restricts access to information storage locations and prevents unauthorized identities from reaching sensitive assets at all, so enumeration of properly protected resources cannot succeed; however, the technique itself (running `ls`, `dir`, `find`, etc.) is not stopped, and any directory the adversary has any access to remains enumerable, including file/directory names visible without read permission.
- T1087partialprevents — By tying access to verified identities and groups rather than anonymous or broad permissions, the control shrinks the attack surface that account-discovery techniques rely on to map usable targets.
- T1087.002partialprevents — A.8.3 explicitly blocks anonymous and unknown-identity access to information (clause a), which prevents the unauthenticated variant of domain account enumeration, but the bulk of the technique runs from any authenticated domain user via net user /domain, Get-ADUser, ldapsearch and similar — and A.8.3 restricts what those users can ACCESS, not whether they can issue enumeration queries, so the technique still succeeds for the common case.
- T1087.003partialprevents — A.8.3's access restrictions can prevent T1087.003 when directory/GAL access is scoped to specific identities rather than granted to all authenticated users, but the technique runs with any valid authenticated session and the GAL is typically accessible to all authenticated users by default, so the control's preventive effect depends on implementation choices rather than being inherent to the clause.
- T1087.004partialprevents — A.8.3's mechanisms for controlling which identities have which access (read, list, enumerate) directly limit who can perform cloud account discovery, and requiring authentication means the technique cannot run anonymously; however, many cloud IAM roles include enumeration permissions by default, so an adversary holding any role with listing rights can still execute the technique despite the control's restrictions.
- T1098partialprevents — A.8.3's access restriction mechanisms — controlling which identities have which access (read/write/delete/execute), requiring authentication for sensitive operations, and enforcing least privilege on information assets — partially prevent account manipulation by limiting who holds permissions to modify accounts and constraining the access a manipulated account can obtain, but the control is scoped to information access rather than account lifecycle management, leaving the manipulation itself largely unaddressed (the domain of A.5.16/A.5.17).
- T1098.001partialprevents — A.8.3's access restriction mechanisms — particularly controlling which identities have which access rights (read/write/execute) and least-privilege configuration — can constrain which accounts hold permissions to add cloud credentials, but the technique specifically exploits accounts that already possess those permissions via legitimate API calls, so the control cannot prevent the technique once such an account is compromised.
- T1098.002partialprevents — A.8.3 restricts access to information based on identity and permissions, which can prevent an unauthorized user from granting additional mailbox delegate permissions, but the control does not inherently stop an already-authorized administrator or a compromised privileged account from performing the action.
- T1098.003partialprevents — A.8.3's access restriction (least privilege, controlling which identities have which access) prevents the technique for accounts that lack role-modification permissions, but the technique specifically targets accounts that legitimately hold those permissions — admins and service principals that A.8.3 itself must grant the capability to — so the prevention reaches the bulk of identities while leaving the actual targets reachable.
- T1098.004partialprevents — A.8.3 restricts write access to sensitive files including authorized_keys via identity-based controls, preventing modification by unprivileged accounts, but cannot stop adversaries who already hold root/admin on the host or who modify keys via cloud provider APIs (GCloud add-metadata, Azure PATCH) that operate outside file-level access controls.
- T1098.006partialprevents — A.8.3's access restriction framework — controlling which identities have which access and requiring authentication/authorization for modifications — constrains who can alter RBAC bindings in container orchestration systems, preventing unauthorized role additions; however, the technique explicitly describes adversaries with sufficient permissions to create or modify RoleBindings/ClusterRoleBindings, so A.8.3's restrictions do not reach the case where the adversary operates within authorized access to escalate.
- T1105partialprevents — A.8.3's controls on write and execute permissions (item d) and isolation of sensitive applications/systems (item e) can prevent an adversary from persisting transferred tools to disk or executing them in privileged contexts, but the clause governs access to information rather than network egress or process execution, so the download itself and in-memory tool transfer remain reachable.
- T1112partialprevents — A.8.3 restricts who can access and modify information assets including registry keys, preventing unauthorized users from performing T1112, but cannot prevent registry modification by legitimate administrators (who must retain this capability for system administration) or by adversaries operating under compromised admin credentials, leaving a named remainder.
- T1114.001partialprevents — A.8.3's access restrictions (file-level permissions, encryption at rest, identity-based controls) prevent cross-user access to local mail stores and constrain which processes can read them, but the technique runs in the context of the user whose mail is being collected, and that user must be able to read their own .ost/.pst — so the primary attack vector is not closed by this control.
- T1114.002partialprevents — A.8.3 prevents unauthorized/anonymous access to email systems and restricts which identities can read mail, but T1114.002's primary mechanism is leveraging valid (compromised) credentials or access tokens to interact with Exchange/O365/GWorkspace as an authorized user — access controls do not stop a request that presents legitimate credentials, so the credentialed variant the technique describes is not prevented.
- T1119partialdetects — A.8.3's dynamic access management guidance includes recording who accesses information and raising alerts on misuse, which can surface automated collection activity, but detection is a secondary, conditional function of a control whose primary purpose is access restriction, and the logging/alerts only apply where dynamic access management is implemented and only catch access-pattern anomalies rather than the scripting behaviour itself.
- T1119partialprevents — A.8.3's access restrictions (identity-based controls, permissions on read/write/delete/execute, authentication requirements) directly limit what an automated collection script can reach, but the technique still runs — scripts execute and can collect any data the compromised or authorized identity can access, and the clause does not remove that access.
- T1133partialprevents — A.8.3 restricts access to information through configuration mechanisms, authentication requirements, and identity-based access controls, which constrains what an adversary reaching the internal network via a remote service can do; however, it does not prevent the remote service itself from being exposed externally, does not address services that don't require authentication (explicitly noted in T1133), and the technique of leveraging the remote service as an entry point can still execute even when information access is restricted.
- T1136.001partialprevents — A.8.3 restricts access to information and assets, which can limit the ability to create a local account, but the technique's execution depends on the adversary already having sufficient access, which this control does not directly prevent.
- T1213partialdetects — A.8.3 includes detection elements (recording who accesses information and how, raising alerts on misuse attempts) but these are scoped to dynamic access management systems for high-value information, not the core access restriction mechanism; for typical repositories exploited in T1213, the control is primarily preventive.
- T1213.002partialprevents — A.8.3 restricts access to information based on identity and policy, which can prevent unauthorized users from reaching a SharePoint repository, but the control's scope is access enforcement rather than content removal, so sensitive information already posted to an accessible location remains reachable.
- T1213.004partialdetects — A.8.3's dynamic access management provisions explicitly include recording who accesses information and how it is used, and raising alerts on misuse attempts — genuine detection mechanisms. However, these are conditional on dynamic access management being applied to information classified as high value, and the clause's primary purpose is preventive (access restriction), so detection is a secondary, conditional capability rather than the control's main act.
- T1213.005partialprevents — A.8.3 restricts who can access information and messaging platforms, preventing unauthorized identities from reading chat content, but the technique typically relies on already-granted access (legitimate users or stolen credentials) and A.8.3 does not constrain what authorized users can read within broadly-accessible messaging applications, nor does it address content-level classification of chat messages.
- T1213.006partialdetects — A.8.3's dynamic access management section mandates recording who accesses information and raising alerts on misuse attempts, but these detection capabilities are conditional on implementation for high-value information and are secondary to the clause's primary preventive purpose of access restriction.
- T1218.014partialprevents — A.8.3 can restrict which identities may execute mmc.exe or access .msc files, stopping unauthorized or low-privileged users, but it cannot prevent an adversary with authorized credentials from abusing a permitted MMC instance.
- T1222partialprevents — A.8.3 restricts which identities can modify access rights (per guidance item d), so users without permission-modification rights cannot perform T1222; however, the technique can still be executed by users who legitimately hold those rights (file owners, administrators), and A.8.3 does not protect the access-control mechanism itself from being modified by those authorized to modify it.
- T1222.001partialprevents — A.8.3 mandates access restrictions that limit which identities can modify permissions, but the technique targets discretionary ACLs where the file owner retains the right to change them, so the control constrains who can reach the modification step rather than removing the ability to modify permissions altogether.
- T1222.002partialprevents — A.8.3's access restrictions (controlling which identities have which access rights, including write/execute) can limit who is able to invoke chmod/chown to alter file permissions, but the clause governs access to information rather than the integrity of the permission structures themselves; an adversary with sufficient existing privileges can still modify ACLs to evade the controls A.8.3 establishes, so what is prevented is a slice of the technique's preconditions rather than the technique itself.
- T1482partialprevents — A.8.3 can deny anonymous or unauthorized identities access to directory/trust information and restrict which accounts can read it, but domain trust enumeration typically remains available to authenticated domain users with normal permissions, so prevention is only partial.
- T1484partialprevents — A.8.3 restricts access to information and configuration mechanisms, which can prevent unauthorized modification of domain policies by limiting who can reach the GPO or tenant settings, but the control governs access rather than eliminating the technique entirely, and an identity with sufficient legitimate privileges can still perform the modification.
- T1484.001partialprevents — A.8.3 restricts access to information and assets, which can limit which identities have write access to GPOs, but the technique can still be executed by identities with legitimate delegated permissions or through privilege escalation from a compromised account.
- T1484.002partialprevents — A.8.3's access restriction mechanisms (controlling which identities have write access, dynamic access management with authentication requirements, restricting access to specified time frames) can be applied to the trust configuration interfaces and federation settings that T1484.002 manipulates, but the technique is executed by actors who already hold administrative-level access to identity infrastructure, and A.8.3 is a general information-access control rather than a control specifically targeting privileged identity-administration actions, so it constrains rather than prevents the technique.
- T1485partialprevents — A.8.3 prevents unauthorized data destruction by restricting who can write/delete, but the technique explicitly leverages valid accounts and authorized contexts, and authorized users with delete permissions can still destroy data they legitimately access — so what is prevented is the unauthorized slice, not the bulk.
- T1485.001partialprevents — A.8.3 restricts access to information and configuration mechanisms, which can limit who can modify lifecycle policies, but the control does not inherently prevent an authorized user with legitimate access from making such modifications.
- T1486partialprevents — A.8.3 restricts who can access and modify information, so unauthorized users without valid credentials cannot reach the data to encrypt it; however, modern ransomware typically arrives via valid accounts, credential theft, or exploitation that bypass access controls, and the clause does not address the initial-access vector or constrain an actor who already holds write permission.
- T1489partialprevents — Access restriction can block unauthorized identities from reaching service-control actions, but adversaries with valid privileged credentials or compromised admin accounts can still stop services.
- T1491partialprevents — A.8.3 restricts write/delete/execute access to information and isolates sensitive applications, which prevents unauthorized modification of content by identities without those permissions, but the control governs access rather than eliminating every path to defacement—an identity with legitimate write access who is compromised or misuses it can still deface, so the prevention is a slice and not a closure.
- T1491.001partialprevents — A.8.3's write-access restrictions (clause d) and configuration mechanisms (clause b) can prevent defacement by limiting which identities can modify web content, login banners, and desktop settings, but the technique typically occurs after the adversary has already accomplished other intrusion goals and holds privileged access sufficient to bypass these restrictions, so prevention is bounded.
- T1491.002partialprevents — A.8.3's access restriction (requiring authentication, controlling write/modify permissions, blocking anonymous access) directly prevents unauthorized modification of external-facing content, but the technique can still occur when authorized credentials are compromised or when application-layer exploits (CMS vulnerabilities, SQL injection) bypass the access control mechanism.
- T1505partialprevents — Access restriction blocks unauthorized identities from writing or executing server components, but it does not stop adversaries or processes that already hold authorized access to the server application.
- T1505.001partialprevents — A.8.3 restricts who can write to the database and create stored procedures, preventing unauthorized identities from doing so, but cannot prevent authorized users (or those with compromised credentials) from crafting malicious stored procedures since the technique presupposes some level of database access for persistence.
- T1505.004partialprevents — A.8.3's access restrictions (controlling write/execute permissions, isolating sensitive applications) can prevent unauthorized identities from installing IIS components by restricting write access to IIS directories, but the technique presupposes the adversary has already compromised an authorized account with sufficient privileges to install components, in which case A.8.3's restrictions do not stop them.
- T1505.006partialprevents — A.8.3 restricts access to systems and information, so it can prevent unauthorized users from reaching the ESXi management plane and installing VIBs; however, the technique is a persistence mechanism that runs with privileged access already obtained, and A.8.3 does not constrain what a privileged user (or an attacker who has reached that level) can do with the esxcli interface, nor does it address the integrity of the in-memory filesystem or VIB acceptance levels.
- T1525partialprevents — A.8.3's access restriction mechanisms (controlling which identities have write/modify permissions, requiring authentication, restricting access to sensitive systems) can prevent unauthorized implants to image registries, but the control is general-purpose and does not specifically address container/image registry integrity; an adversary with compromised credentials holding legitimate push permissions, or exploiting a misconfigured registry outside the access policy's scope, can still implant images.
- T1529partialprevents — A.8.3 restricts access to information and associated assets including execute permissions, which prevents unauthorized users from initiating shutdown/reboot commands; however, the technique can still be performed by authorized users with SeShutdownPrivilege or via compromised credentials with appropriate privileges, and the clause focuses on information access rather than comprehensively restricting all system operations.
- T1537partialprevents — A.8.3 prevents the unauthorized-access vector of T1537 (anonymous file shares, unknown identities, uncredentialed API calls) by requiring authentication and controlling which identities have which access, but it does not prevent the technique's primary vector: an adversary using a compromised or authorized account to invoke legitimate cloud-provider APIs (sharing, SAS URIs, cross-account backup) to move data to an account they control, since the access control governs who reaches the data, not what they do with it once reached.
- T1542.004partialprevents — A.8.3's access restrictions on network device management interfaces (authentication requirements, no anonymous access, physical/logical access controls) can prevent unauthorized ROMMON firmware loading through normal management channels, but the technique specifically targets the boot loader layer where access controls are often bypassed (TFTP loading, console access during boot, ROMMON's own weak default protections), and A.8.3 does not mandate firmware integrity verification or secure boot that would comprehensively block the technique.
- T1542.005partialprevents — A.8.3 restricts access to configuration mechanisms and sensitive information, which can prevent unauthorized changes to the TFTP boot configuration, but the technique can also be executed through physical access or by compromising a legitimate TFTP server, which access restrictions alone do not fully prevent.
- T1543partialprevents — A.8.3 restricts access to information and assets, which can prevent unauthorized modification of system process configurations, but the control governs access rather than directly blocking process creation or modification mechanisms.
- T1543.002partialprevents — A.8.3's access restriction mechanisms (controlling write access to directories) can prevent unauthorized users from creating or modifying systemd service files in system-level locations, but the control is designed for information access rather than system configuration integrity; root-level actors and user-level service directories remain reachable, so only a slice of the technique is prevented.
- T1546.004partialprevents — A.8.3's access restriction prevents unauthorized identities from modifying shell configuration files they do not own (e.g., cross-user writes to another user's dotfiles, or unprivileged writes to /etc/profile), but the technique's primary vectors — user-owned files modified by the file owner and system files modified by root — operate within the access control model A.8.3 enforces, so the control bounds rather than blocks the technique.
- T1546.006partialprevents — A.8.3's access restriction mechanisms (write permissions, identity-based controls) can prevent unauthorized modification of Mach-O binaries by limiting who has write access to executable files, but the clause targets information access broadly rather than binary integrity specifically, and an adversary with sufficient privileges (e.g., administrator) can still modify binaries and strip code signatures to perform the technique.
- T1546.013partialprevents — A.8.3's access controls (write permissions on profile files/directories) can prevent modification of system-wide or other users' PowerShell profiles, but a user typically retains write access to their own user-level profile, which is sufficient for the persistence technique to succeed.
- T1547.001partialprevents — A.8.3 restricts write access to the Registry and startup folders for non-administrative users, which prevents those users from creating persistence entries, but administrative accounts and processes running with elevated privileges can still write to those locations.
- T1547.013partialprevents — A.8.3's access controls (write restrictions on autostart directories) can prevent non-admin modifications to /etc/xdg/autostart, but the user-level ~/.config/autostart directory is inherently writable by the user, so the primary attack vector remains reachable; the clause addresses access to information rather than execution mechanisms, leaving a substantial remainder.
- T1548.001partialprevents — A.8.3 restricts access to information and assets, which can prevent unauthorized users from executing setuid/setgid binaries, but it does not address the binaries themselves or users with legitimate access who abuse them.
- T1548.003partialprevents — A.8.3's access restriction principles (controlling which identities have which access, including execute) can be applied to sudoers configuration to limit who may elevate, but the clause targets information access rather than the specific sudo mechanisms T1548.003 abuses — timestamp_timeout caching, tty_tickets, and NOPASSWD entries — so only a slice of the technique is prevented.
- T1548.005partialprevents — A.8.3 restricts access based on identity and policy, which can limit the initial permissions an adversary needs to abuse temporary elevation mechanisms, but it does not directly control the misconfigured just-in-time, impersonation, or pass-role features that the technique exploits.
- T1548.006partialprevents — A.8.3 restricts access to information and assets, which can prevent unauthorized processes from reading TCC-protected data, but the technique's core mechanism—abusing an already-authorized application's permissions or manipulating the TCC database—bypasses the access control layer by inheriting or injecting permissions rather than requesting new ones.
- T1550.001partialprevents — A.8.3 restricts access based on identity and credentials, but a stolen application access token is a valid credential that satisfies those checks, so the control prevents only the subset of token abuse that its dynamic access management extensions (time-bound, device-bound, location-bound rules) can constrain.
- T1550.004partialprevents — A.8.3 restricts access based on identity and credentials, but a stolen session cookie presents an already-authenticated session that bypasses the identity check at the point of use, so the control prevents access only where dynamic re-authentication or session binding is enforced and not where the cookie alone suffices.
- T1552.001partialprevents — A.8.3 restricts who can read files, so an unauthorized identity cannot browse a file share or local filesystem for credential files — that path is closed. But the technique still succeeds where the adversary has compromised an authorized identity (the access restriction does not stop a legitimate user from reading files they are entitled to read), and where credentials must be stored in files readable by services or applications that use them, which is the common case for config files and cloud credential stores.
- T1552.005partialprevents — A.8.3 restricts access to information and can block anonymous or unauthorized access to the metadata API at the network or identity layer, but the API is a legitimate service accessible from the instance itself, so an adversary with a presence on the instance can still query it directly.
- T1552.007partialprevents — A.8.3's access restriction requirements (authentication, identity-based controls, configuration mechanisms) would prevent unauthorized access to container APIs, but the technique typically involves adversaries with legitimate credentials (e.g., pod service accounts) making authorized API calls to retrieve credentials — a scenario A.8.3's generic information-access controls do not specifically address, and the clause is not container-specific.
- T1552.008partialprevents — A.8.3 restricts who can read chat channels and messages, so where access controls are properly applied to collaboration tools the technique cannot reach the credentials; however, the technique also succeeds through compromised legitimate credentials, authorized users sharing secrets inappropriately, and admin portal/integration access paths that A.8.3's configuration mechanisms do not fully close, leaving a named remainder.
- T1553.002partialprevents — A.8.3 restricts access to information and associated assets, which includes code signing certificates/keys held by the organization, so it can prevent the theft portion of T1553.002; however, the technique also covers adversaries creating or acquiring certificates from external CAs, which A.8.3 cannot reach, leaving a substantial remainder.
- T1553.003partialprevents — A.8.3's access restriction mechanisms (controlling write access to system locations, restricting which identities can modify configuration) can limit who has the privileges needed to alter the SIP/trust provider registry values and drop malicious DLLs, but the control's primary focus is information access rather than system-integrity controls, and an actor with sufficient privileges to reach HKLM\...\Cryptography can still execute the hijack regardless of A.8.3's information-access rules.
- T1553.004partialprevents — A.8.3's access restrictions (controlling which identities have write access, configuration mechanisms to control access) can limit which users can modify system trust stores and install root certificates, but the technique operates on already-compromised systems where the attacker has obtained sufficient privileges to bypass these restrictions, and the control is primarily about access to information rather than certificate store management specifically.
- T1553.006partialprevents — A.8.3's access restriction mechanisms — particularly controlling which identities have write/execute permissions on system configuration — can prevent non-administrative users from modifying code signing policies, but the clause is scoped to information access rather than system security configuration integrity, and the technique is typically executed by users who already hold elevated permissions the clause does not restrict.
- T1554partialprevents — A.8.3 restricts write and execute access to binaries, which prevents unauthorized modification of those it covers, but the control governs access rather than integrity verification, so binaries writable by a compromised account or process remain reachable.
- T1555partialprevents — A.8.3 restricts access to information including credential stores through identity-based controls, encryption, and access logging, which can prevent unauthorized retrieval of stored credentials; however, the technique has multiple vectors (memory scraping, legitimate-process abuse, cloud vault access) and A.8.3 is a general access-restriction framework rather than a credential-store-specific control, so a bounded remainder of the technique survives conformant implementations.
- T1555.001partialprevents — A.8.3's access restriction mechanisms (file-level permissions, configuration controls, dynamic access management) can constrain who reads keychain files and how the keychain is configured, but the technique typically runs with the user's own login context — the keychain's own authentication (the user's login password) is the primary gate, and A.8.3 does not govern that mechanism, so a substantial share of the technique remains reachable.
- T1555.006partialprevents — A.8.3's access restriction mechanisms (controlling which identities have which access, dynamic access management) directly apply to the secrets manager's own access controls, preventing unauthorized retrieval when the adversary lacks sufficient privileges; however, the technique specifically describes adversaries who have already obtained high-privileged cloud credentials or compromised a service with retrieval rights, so prevention only holds when the adversary's privileges are properly restricted and not when they have already bypassed initial access boundaries.
- T1556.003partialprevents — A.8.3's access restrictions (controlling read/write/execute on system files) can limit which identities may modify PAM configuration and library files, preventing unauthorized tampering by non-privileged accounts; however, it does not stop modification by an adversary operating as a privileged administrator (the typical threat for this technique), nor does it address credential theft from legitimate PAM exchanges, leaving a large remainder.
- T1556.005partialprevents — A.8.3 requires access restriction and configuration mechanisms that can prevent the adversary from enabling AllowReversiblePasswordEncryption, but the control does not guarantee the property is disabled on every account or block all paths an adversary with sufficient privilege could use to set it.
- T1560.001partialprevents — A.8.3 prevents unauthorized access to information, which is the prerequisite for archiving it — if the adversary cannot read the data, they cannot archive it. However, the technique itself (running tar, zip, 7-Zip, etc.) is not what A.8.3 addresses; once access is gained through other means, A.8.3 has nothing to say about the archiving act, and many of these utilities are preinstalled and legitimate.
- T1561partialprevents — A.8.3 restricts who has write access to disks and other assets, which prevents unauthorized actors from performing disk wipes, but it does not stop authorized administrators, compromised privileged accounts, or malware running with elevated credentials from executing the technique — the access prerequisite is gated, not the destructive operation itself.
- T1561.001partialprevents — A.8.3 restricts access to information and associated assets, which prevents disk wiping by adversaries without authorized access; however, the technique explicitly leverages valid accounts, credential dumping, and SMB shares to propagate, and adversaries with any form of authorized or physical access can still execute it, so the prevention covers only the unauthorized-access slice rather than the bulk of execution paths.
- T1561.002partialprevents — A.8.3's access restrictions (write/execute controls, authentication requirements, identity-based permissions) prevent unauthorized actors from reaching disk structures, but the technique explicitly leverages Valid Accounts, credential dumping and admin shares to obtain authorized-level access first, and once that access is held the access-restriction mechanism is bypassed — so what is prevented is the unauthorized-access path while the credentialed path remains open.
- T1565partialdetects — A.8.3's dynamic access management provisions include recording who accesses information and how it is used, plus alerts on misuse attempts, which can surface some data manipulation; however, the clause's primary purpose is access restriction (prevention), and its detection mechanisms focus on access misuse rather than integrity violations, leaving manipulation by authorized insiders or through exploitation largely undetected.
- T1565.001partialdetects — A.8.3 includes detection-adjacent elements — alerting on misuse attempts, recording who accessed information and how it was used, and monitoring use — particularly in the dynamic access management section, but these are conditional on implementation choices and surface access events rather than data-integrity violations; an adversary manipulating stored data through authorized access or by bypassing access controls is not caught by the control's detection mechanisms.
- T1565.002partialprevents — A.8.3's encryption, authentication and access-control mechanisms prevent a slice of transmitted-data manipulation by blocking unauthorized interception tools and protecting confidentiality in transit, but the clause is scoped to access restriction rather than mandating integrity protection (no explicit MAC/signature requirement), leaves authorized insiders and compromised credentials able to manipulate, and does not reach process-to-process manipulation where the data crosses trust boundaries inside a system.
- T1565.003partialprevents — A.8.3's access restriction (read/write/delete/execute controls, isolation of sensitive applications) prevents unauthorized modification of application binaries and data files, but runtime data manipulation can still occur via insiders with legitimate write access, in-memory manipulation outside the file-access control surface, and through configuration changes that access restriction alone does not catch.
- T1567.002partialprevents — A.8.3 restricts which identities can access which data and, via dynamic access management, can grant access based on application context — so a cloud storage client or browser upload path may not be an authorized application for sensitive data, and encryption-at-rest can render exfiltrated content unusable. But the clause governs access to information, not network egress or cloud-service communications; an adversary operating under a compromised legitimate identity with authorized access to the data can still move it to a cloud service the controls do not see, so the technique is constrained rather than blocked.
- T1570partialprevents — A.8.3 restricts which identities have read/write/execute access to which data and isolates sensitive systems, so it blocks lateral tool transfer to locations the compromised identity cannot write — but the technique runs on authenticated connections and the typical lateral-movement scenario uses compromised credentials that already hold the access being exercised, so the transfer proceeds wherever the identity is privileged.
- T1574.005partialprevents — A.8.3's guidance on controlling which identities have write/execute access applies to file system permissions on installer binaries, so proper implementation restricts the overwrite step; however, the clause is framed around information access rather than executable file integrity, and the installer-side behavior of creating subdirectories with weak permissions in %TEMP% is not directly addressed by access restriction requirements.
- T1574.008partialprevents — A.8.3 restricts access to directories and files through identity-based permissions and isolation, which can prevent an adversary from placing a malicious executable in the target directory, but it does not address the underlying vulnerability of the calling program's unqualified path, leaving the technique reachable wherever write access is legitimately granted.
- T1574.010partialprevents — A.8.3 mandates access restriction including write/execute permissions on assets, which if properly applied to service binary directories would prevent unauthorized replacement; however, the clause is a general access-restriction framework rather than one specifically targeting service file permissions, so prevention depends on correct implementation at the relevant file paths and does not address the broader weakness class of service misconfigurations.
- T1574.011partialprevents — A.8.3's guidance on controlling which identities have which access rights (read, write, execute) and restricting access to sensitive system components maps directly to the ACLs on service registry keys that this technique exploits; however, the clause is a general access-restriction policy aimed at information assets, not a specific mandate to harden registry permissions, so its preventive effect depends on implementation extending the principle to system configuration stores.
- T1574.014partialprevents — A.8.3 restricts access to information and configuration mechanisms, which can prevent unauthorized modification of .config files and environment variables used in AppDomainManager injection, but does not prevent an already-authorized process from loading a malicious assembly into its own application domain.
- T1578.001partialprevents — A.8.3 restricts who can perform operations like snapshot creation through access controls on identities and permissions, so unauthorized identities cannot create snapshots; however, the technique specifically involves adversaries who have already leveraged permissions (compromised credentials, insider access, or over-privileged accounts), and A.8.3 does not prevent abuse by parties who hold the necessary authorized permissions.
- T1578.003partialprevents — A.8.3 restricts delete permissions on assets (item d: read, write, delete, execute), so an adversary without those rights cannot delete a cloud instance; however, the technique typically involves an adversary operating with compromised or valid credentials that already carry delete authority, and A.8.3 does not stop that actor from exercising permissions it has already granted.
- T1578.004partialprevents — A.8.3's access restriction mechanisms (authentication, identity-based permissions, configuration controls) govern who can invoke cloud management APIs and dashboards to revert snapshots or restart instances, so unauthorized identities are blocked from performing the technique; however, the technique runs unimpeded when the adversary operates under compromised or already-privileged credentials with snapshot/VM management rights, which A.8.3 alone does not prevent.
- T1578.005partialprevents — A.8.3's access restrictions (controlling which identities have which access, including write/modify permissions) can prevent unauthorized modification of cloud compute configurations, but the technique specifically describes adversaries who have already compromised the cloud environment and possess credentials with sufficient privileges to make these changes — access restriction cannot stop an authorized (or compromised-authorized) identity from modifying settings it is permitted to modify.
- T1580partialprevents — A.8.3's access restrictions (least privilege, identity-based controls, no anonymous access) constrain what a compromised identity can enumerate, but T1580 operates through legitimate API calls using valid (compromised) credentials, so any resource the identity is authorized to see remains discoverable; the control reduces the surface but cannot prevent discovery within the authorized scope.
- T1589partialprevents — A.8.3 prevents unauthorized access to identity information stored in the organization's systems (e.g., probing authentication services, accessing internal directories), but T1589 has many vectors that bypass access controls entirely — social media, public websites, third-party breaches, and direct elicitation via phishing — so only a slice of the technique's surface is closed.
- T1589.001partialprevents — A.8.3 restricts access to information (including credentials) via policies, auth requirements, dynamic controls, encryption, monitoring and alerts, which stops some gathering vectors (e.g. anonymous leaks, unauthorized repository access, or real-time misuse of stored creds) but leaves most of the described collection methods (phishing, site compromise, dark-web purchase, breach dumps, infostealer logs) untouched.
- T1590.002partialprevents — A.8.3 can prevent unauthorized zone transfers and access to non-public DNS data, but most of T1590.002's information is gathered from public DNS records and passive DNS datasets that must remain queryable, so prevention is only partial.
- T1593.002partialprevents — A.8.3 restricts access to sensitive information and prevents anonymous/public access to storage containing sensitive data, which stops search engines from indexing that material and so prevents the technique from succeeding in its sensitive-spillage harvest (credentials, network details). It does not prevent the adversary from running search queries, nor from finding non-sensitive public information about the victim (websites, employee presence, filings), so the technique still runs and still partially succeeds.
- T1601partialprevents — A.8.3's access restriction mechanisms (authentication requirements, write/delete/execute controls, isolation of sensitive systems) can be applied to limit who can modify network device OS images, but the control is framed around information access rather than system image integrity, and T1601's in-memory modification path and specialized network device management interfaces leave a meaningful remainder that access restriction does not reach.
- T1601.001partialprevents — A.8.3's access restriction mechanisms (authentication, identity-based access controls, configuration mechanisms) directly address the prerequisite for T1601.001, which requires administrative-level access to the network device or operator-level procedures to modify the OS image; however, the control does not prevent authorized insiders from performing the modification, does not address the boot loader compromise path (T1542.004) that bypasses access controls, and its primary scope is information access rather than network device OS integrity specifically.
- T1601.002partialprevents — A.8.3's access restrictions (controlling write access, logical/physical access controls for isolation, configuration mechanisms) can prevent unauthorized modification of a network device's storage and boot configuration, which is what the downgrade requires; however, the clause targets information access rather than system image integrity, and an adversary with valid administrative credentials or access through a management interface not covered by the restriction can still perform the downgrade.
- T1602partialprevents — A.8.3 restricts access to information and associated assets, which can prevent unauthorized access to configuration repositories, but the control's scope depends on implementation and does not guarantee complete prevention against all methods of accessing such repositories.
- T1602.001partialprevents — A.8.3 restricts access to information, and where SNMP community strings are treated as access credentials and restricted accordingly, unauthorized MIB dumps are prevented; however, the control does not mandate SNMP-specific hardening, so default or weak community strings on managed devices remain reachable.
- T1602.002partialprevents — A.8.3 mandates access restriction to information assets including configuration mechanisms, identity-based controls, and authentication requirements, which if applied to network devices would block unauthorized SNMP/SMI access to configuration files; however, the clause is a general access-restriction framework rather than a network-device-specific control, and the technique exploits legitimate management protocols that may remain enabled for operations or retain weak defaults, leaving a meaningful remainder where the control's requirements are not fully realized against this specific vector.
- T1606.001partialprevents — A.8.3 can restrict access to the secret values (private keys, cryptographic seeds, passwords) that T1606.001 requires to forge valid cookies, and its identity-based access controls limit who can reach that material, but the control does not address cookie-signing integrity or token validation directly, and the technique is explicitly designed to bypass the MFA and authentication mechanisms A.8.3 supports.
- T1609partialprevents — A.8.3's access restriction mechanisms (no anonymous access, configuration controls, identity-based permissions, isolation) apply to container administration services like the Docker daemon, Kubernetes API server, and kubelet, and where properly implemented prevent unauthorized identities from reaching them; the remainder is that legitimate administrators require access by design, compromised credentials bypass the restrictions, and the clause is framed around information access rather than service administration specifically, so it cannot reach the bulk of the technique.
- T1610partialprevents — A.8.3's access restriction mechanisms (controlling which identities have which access, configuration mechanisms for systems and services) can prevent unauthorized users from deploying containers by restricting access to the container orchestration APIs, but it does not prevent authorized users from deploying malicious containers and does not address container-platform-specific security controls, so the prevention is indirect and incomplete.
- T1612partialprevents — A.8.3 restricts access to associated assets including services like the Docker daemon/socket via identity-based controls and configuration mechanisms, which can prevent unauthorized users from issuing build requests; however, the technique presupposes the adversary already has some foothold on the host, and A.8.3 does not specifically address container runtime controls, so prevention holds only against adversaries without legitimate access credentials.
- T1613partialprevents — A.8.3 restricts access to container APIs and dashboards (blocking anonymous/unauthorized discovery per clauses a, b, c, d), but cannot prevent discovery by any identity granted legitimate access to the container environment — and container platforms require broad API access for developers, services and CI/CD, so a substantial slice of identities can still perform T1613.
- T1647partialprevents — A.8.3 restricts read/write/delete/execute access to information assets, so properly configured write protections on plist files prevent unauthorized modification; however, the technique frequently targets user-writable plist files (e.g., ~/Library/Preferences/) that the adversary can modify within their own execution context, and A.8.3 does not typically restrict a user's access to their own files, leaving a substantial remainder.
- T1648partialprevents — A.8.3 restricts which identities can access systems and what actions (including execute) they can perform, so it can constrain who is permitted to create or invoke serverless functions; however, the control targets access to information rather than compute-resource provisioning, does not address IAM permission management (e.g. PassRole), and cannot stop a user with legitimate function-creation rights from abusing serverless execution, leaving a substantial remainder.
- T1649partialprevents — A.8.3 restricts access to certificate stores, CA private keys, and enrollment endpoints, which blocks several T1649 vectors (unauthorized file access, anonymous certificate retrieval, uncontrolled enrollment), but it does not address certificate-template misconfigurations, CA key compromise through other paths, abuse of legitimately granted enrollment rights, or the cryptographic protections certificates themselves require — so the technique is constrained, not prevented.
- T1651partialprevents — A.8.3's access restriction mechanisms (identity-based controls, authentication requirements, time/identity-based constraints on who can invoke cloud administration services) directly constrain the surface T1651 abuses, but the technique specifically requires administrative access to begin with and explicitly notes trusted-relationship and delegated-administrator vectors that bypass these restrictions, so the control cannot prevent the technique when credentials are valid or the abuse comes through a provider relationship.
- T1657partialprevents — A.8.3's access restrictions, authentication requirements and dynamic access management can prevent technical financial theft that requires unauthorized access to financial systems or sensitive monetary information, but the control does not address the dominant vectors of T1657 — business email compromise, pig butchering, social engineering of authorized users into initiating transfers, or ransomware extortion — which use legitimate channels or human deception rather than unauthorized information access.
- T1666partialprevents — A.8.3's access restriction mechanisms (identity-based controls, configuration mechanisms for systems/services, controlling which identities have which access) apply to cloud resource hierarchy modifications as administrative operations on systems and services, but the technique specifically involves adversaries who have already gained the necessary permissions (e.g., Global Administrator), so the control's effectiveness is bounded by what it can restrict at the identity level once those permissions exist.
- T1673partialprevents — A.8.3's access restrictions (identity-based controls, configuration mechanisms, isolation of sensitive systems) can prevent unauthorized users from reaching the hypervisor or host to run discovery commands, but the technique presupposes the adversary already has access, and any identity with legitimate administrative access to the hypervisor can still enumerate VMs; compromised credentials and insider access bypass the restriction entirely.
- T1675partialprevents — A.8.3's access restriction mechanisms (controlling which identities have which access, configuration mechanisms, logical access controls) apply to ESXi administration services and can prevent unauthorized invocation of StartProgramInGuest and related APIs, but the control is a general framework that depends on implementation and does not address credential compromise or misuse of legitimate admin credentials, which is the primary vector for this technique.
- T1677partialprevents — A.8.3's access restrictions (controlling which identities have write access to CI configuration files and referenced build files) prevent the direct and indirect pipeline poisoning scenarios where the adversary needs write access to the repository, but the public pipeline execution scenario exploits legitimate CI/CD triggers (e.g., pull_request_target from forks) and is not addressed by access restriction alone — it requires pipeline security configuration outside A.8.3's scope.
- T1685partialprevents — A.8.3's access restriction mechanisms (controlling which identities have read/write/execute access, restricting access to configuration mechanisms) can prevent unauthorized modification of security tool configurations and prevent non-privileged actors from disabling tools, but the control is scoped to information access rather than security tool integrity, does not address process/service protection, driver integrity, or anti-tampering, and cannot prevent an actor with sufficient privileges from stopping services, killing processes, or modifying registry keys.
- T1685.002partialprevents — A.8.3 restricts who can modify logging configuration (via access controls on systems and services), preventing unauthorized identities from disabling or tampering with cloud logs, but the technique explicitly requires 'sufficient permissions' — an adversary who has compromised an authorized administrator's credentials can still execute it, so the prevention is bounded by the permissions model rather than universal.
- T1685.005partialprevents — A.8.3 can prevent non-administrator attempts to clear event logs by restricting access to log management tools (wevtutil, PowerShell) and to the log files themselves, but the technique specifically requires administrator privileges, meaning the actor has already passed A.8.3's access control; the clause does not constrain what an authorized administrator can do with logs they have been granted access to.
- T1685.006partialprevents — A.8.3 restricts who can modify or delete information assets including log files, so unauthorized identities cannot clear them; but the technique typically requires elevated privileges, and a compromised admin account bypasses the access restriction, while A.8.3 does not mandate log immutability or write-once protection.
- T1686.002partialprevents — A.8.3 restricts access to information and configuration mechanisms, which can prevent unauthorized changes to firewall rules, but the control does not directly harden the network device management interface against exploitation or credential theft, leaving a path for adversaries to gain the access needed to disable or modify the firewall.
Prevented OWASP Web Top 10 (2025) risks (19)
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
- A02mostlyblocks — A.8.3 directly mandates configuration mechanisms, access controls, least-privilege rules on identities/groups/operations, isolation, and dynamic techniques that close the bulk of weak-default and incomplete-hardening misconfigurations; residual attack surface from misconfigurations outside the access-restriction slice (e.g. error handling, header settings) keeps it from full.
- A07mostlyblocks — A.8.3 directly mandates restricting access to information via configuration, identity/group controls, authentication requirements, dynamic rules based on identity/device/location, and isolation of sensitive data — squarely addressing the dominant authentication-failure mechanisms (bypassing, brute-force, hijacking, weak reset, session mistakes) that enable unauthorized access; the bounded remainder is pure credential-stuffing against external leaked passwords, which lives one layer upstream in A.8.5 rather than here.
- A01partialblocks — A.8.3 directly mandates access restriction mechanisms (config, identity/group controls, dynamic techniques, auth, encryption, monitoring) that squarely address the authorization-decision slice of A01 (missing checks, IDOR, improper enforcement), but leaves path traversal, CSRF, and several other listed members untouched.
- A04partialblocks — A.8.3 explicitly lists using encryption (and dynamic access techniques that require credentials/certificates) to restrict access to sensitive information throughout its lifecycle, which directly prevents the absent/weak/misused cryptography that exposes data in the A04 class; however this is only a slice of the target (e.g. it does not address algorithm selection, key management, or non-access-control misuses).
- A05partialblocks — A.8.3's access restriction, configuration mechanisms, dynamic techniques, authentication, encryption and isolation directly prevent several injection shapes (XSS via output controls, SSRF via dynamic rules on location/app, command/LDAP via restricted identities and monitoring) but leave the dominant SQL-injection and many template-injection cases untouched.
- A06partialblocks — A.8.3 directly mandates access restriction mechanisms (configuration controls, identity/group permissions, isolation, dynamic techniques with auth/encryption/time-bound rules) that close many design-level gaps in access enforcement and data protection, but leaves untouched other insecure-design members such as flawed business logic, missing rate limiting, or unsafe workflows that do not hinge on access restriction.
- A10partialblocks — A.8.3's access restriction (including dynamic techniques, auth requirements, encryption, and isolation) directly blocks many error-path leaks and fail-open states that expose or mishandle sensitive information, but leaves untouched the inconsistent-state and logic-flaw slices of the category.
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.