A.5.15 Organizational
Access control
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 (30)
Our reading (mostly llm_verified) of how this ISO control and each NIST 800-53 control relate. Not an ISO or NIST product.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- AC-2mostlycovers — A.5.15's broad mandate to ensure authorized access and prevent unauthorized access accounts for the bulk of ac-2's account-type, user, group/role, and privilege specification requirements, but leaves a residual of procedural elements (assigning dedicated account managers, formal approval workflows) uncovered.
- AC-24mostlycovers — A.5.15's broad mandate to ensure authorized access and prevent unauthorized access accounts for the core of AC-24's requirement to make and apply access control decisions on every request, but leaves a residual on the specific 'prior to enforcement' sequencing and any organization-defined parameters not explicitly required by the ISO control.
- AC-3mostlycovers — ISO A.5.15 establishes the overarching access control policy and rules that enforce who may access what, directly fulfilling the core intent of AC-3.
- AC-6mostlycovers — A.5.15's broad mandate to ensure authorized access and prevent unauthorized access accounts for the bulk of AC-6's least-privilege requirement, but leaves a real residual: AC-6 explicitly requires the finer-grained 'only those accesses necessary for assigned tasks' (need-to-know / minimal rights), which A.5.15 does not itself mandate or detail.
- AC-5partialcovers — A.5.15's broad mandate for authorized access and preventing unauthorized access addresses only a slice of ac-5; it does not itself require identifying/documenting the specific duties or defining access authorizations explicitly to enforce separation of duties.
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 establishes and enforces policy-based access permissions, entitlements, and authorizations while incorporating the need-to-know principle, segregation of duties, and formal authorization processes.
- PR.AA-01domain mandateimplements — A.5.15's operational mechanisms for enforcing authorized access directly give effect to the identity/credential management outcome named in PR.AA-01 within the access-control domain (though PR.AA-01 does not cite A.5.15 by name)
- PR.AA-06domain mandateimplements — A.5.15's mandate to prevent unauthorized access to assets directly operationalizes physical-access enforcement as one core means within its broad access-control domain (the PR.AA-06 outcome names physical access to assets as the end, and A.5.15 supplies the technical mechanism that achieves it).
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.1fullcovers — The ISO control’s mandate to implement access rights and restrictions directly implements the ASVS requirement that function-level access be restricted to entities with explicit permissions.
- V8.2.2fullcovers — ISO’s requirement to map access rights to specific information assets aligns with the ASVS rule that data-specific access must be limited to consumers with explicit permissions for those items.
Related weaknesses / CWE (2554)
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-402mostlyblocks — Access-control mechanisms limit who can receive resources that should remain internal.
- CWE-921mostlyblocks — Access control policy directly requires protection of sensitive data wherever it is stored.
- CWE-219partialblocks — A.5.15 mandates access control rules that, if implemented at the web server layer, can block direct retrieval of sensitive files under the web root; however, the weakness is fundamentally about file placement and web server configuration (what the server serves from the document root), which A.5.15 does not directly reach, leaving a nameable remainder.
- CWE-256partialblocks — A.5.15's access control rules restrict who can read files or memory containing the plaintext password, blocking exploitation by unauthorized actors, but the weakness remains present and exploitable by authorized insiders (admins, developers) and through memory access paths that access control does not reach.
- CWE-257partialblocks — A.5.15 mandates implementation of access control rules that restrict who can reach the password store, blocking exploitation by unauthorized users; however, the recoverable-format weakness itself is unchanged, and authorized insiders (e.g. administrators with legitimate access to the credential store) can still recover and reuse passwords — the threat the CWE description explicitly names — so the control masks the vulnerability for a portion of the threat surface but does not address the underlying flaw.
- CWE-266partialprevents — A.5.15 requires least-privilege rights mapping, authorization, and segregation for access assignments, which prevents many administrative misassignments, but it does not stop incorrect privilege grants implemented inside application code.
- CWE-268partialblocks — Access control policies can limit the combination of privileges that enable unsafe actions.
- CWE-283partialblocks — Access control policies can require ownership verification before granting access to critical resources.
- CWE-286partialblocks — Access control policies rely on accurate user management but do not themselves define user lifecycle processes.
- CWE-312partialblocks — A.5.15 mandates a topic-specific access control policy and rules for authorizing access to information, but it does not itself encrypt stored data or prevent cleartext storage from being exploited once it exists.
- CWE-313partialblocks — A.5.15 defines a policy framework for access control rules but does not itself encrypt data at rest; cleartext storage in a file remains exploitable by anyone with file or disk access regardless of the policy.
- CWE-314partialblocks — A.5.15 restricts who can read the registry key, blocking exploitation by unauthorized users, but the cleartext data remains readable by any authorized process or user with registry access, and is still exposed via backups, exports, and memory — the weakness persists and is exploitable along those vectors.
- CWE-408partialblocks — Access control policies that enforce authentication before resource-intensive operations directly prevent early amplification.
- CWE-424partialblocks — Access control policy directly requires protection of all entry points to restricted functionality.
- CWE-527partialblocks — Access control policies directly prevent unauthorized actors from reaching version-control repositories.
- CWE-530partialblocks — Access control directly limits who can reach backup files, though it does not address how backups are created or stored.
- CWE-532partialblocks — A.5.15 mandates that access control rules be defined and implemented on assets including log files (it explicitly references logging under 8.15 and requires access rights and restrictions to be mapped to entities), so a well-implemented policy restricts who can read the log and blocks the exploitation; the actual enforcement, however, is performed by the access control implementation (A.8.3 and related), not by A.5.15 itself, which sits one step removed as the policy that requires the blocking to be set up.
- CWE-566partialblocks — Access-control policy sets the governance expectation that all data access must be authorized, indirectly supporting prevention of CWE-566.
Mitigated MITRE ATT&CK techniques (3701)
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
- T1078mostlyprevents — Formal authorization, role-based assignment, and periodic review of access rights directly constrain an adversary's ability to leverage stolen or guessed credentials by ensuring only explicitly approved entities retain access.
- T1078.002mostlyprevents — Mapping access rights to verified roles and enforcing need-to-know limits the scope of any compromised domain account.
- T1021partialprevents — A.5.15 mandates an access control policy that restricts remote service access to authorized entities, which prevents unauthorized use of T1021, but the control is a policy requirement rather than a technical enforcement mechanism, so its preventive effect depends on implementation and leaves room for policy gaps or misconfigurations.
- T1021.002partialprevents — A.5.15 mandates an access control policy that restricts access to information and assets, which can prevent unauthorized SMB share access, but the control is a policy requirement rather than a technical enforcement mechanism, so its preventive effect depends entirely on implementation and cannot guarantee the technique is blocked.
- T1021.004partialprevents — A.5.15 requires a topic-specific access control policy that determines which entities require which type of access and restricts privileged access, which can prevent SSH from being enabled or accessible to unauthorized entities, but the control sets policy requirements rather than enforcing technical restrictions, leaving implementation-dependent gaps.
- T1021.005partialprevents — A.5.15 mandates an access control policy that restricts connections to authorized entities, which can block unauthorized VNC access, but the control is a policy requirement rather than a technical enforcement mechanism and its effectiveness depends on implementation of the referenced technical controls (8.26, 8.2, 5.18).
- T1021.006partialprevents — A.5.15 mandates an access control policy that restricts access to authorized entities, which can prevent unauthorized WinRM use, but as a policy-level control it does not itself enforce the technical restrictions that would fully block the technique.
- T1021.008partialprevents — A.5.15 mandates an access control policy that restricts access to authorized entities, which can prevent direct cloud VM connections where the policy is enforced, but the control sets requirements rather than implementing mechanisms, leaving gaps where credentials are valid, cloud-native methods are permitted by policy, or enforcement is incomplete.
- T1059.009partialprevents — A.5.15 mandates substantive access-control requirements (restrictions to privileged access, segregation of duties, formal authorization, management of access rights) that, if implemented, would constrain who can invoke cloud APIs, but the clause is a policy/framework control that requires the capability rather than implementing the technical enforcement itself — the actual prevention lives in A.8.2/A.8.3/A.8.5, so only a slice of the prevention is attributable to A.5.15.
- T1078.001partialprevents — A.5.15 mandates an access control policy that includes restrictions to privileged access, management of access rights, and formal authorization of access requests — all of which directly address the conditions that enable default account abuse — but it is a framework/policy clause that says rules 'should be defined' and 'should be implemented', not the technical act of disabling or removing default accounts, which is performed by configuration management (A.8.9) or identity management (A.5.16) that A.5.15 itself references.
- T1098partialprevents — Segregation of access request, authorization, and administration functions makes it harder for an adversary to silently create or modify accounts without detection.
- T1098.003partialprevents — A.5.15 mandates segregation of access control functions (request/authorization/administration), formal authorization of access requests, and restrictions to privileged access — requirements that, if properly implemented, would prevent an adversary with a single compromised account from unilaterally adding cloud roles. However, A.5.15 is a governance/policy control that sets requirements without implementing them; the actual prevention lives in the referenced controls (8.2, 5.16, 5.18), and an adversary with sufficient existing permissions can still bypass the framework where the segregation is not enforced.
- T1098.006partialprevents — A.5.15 mandates specific governance requirements — segregation of access control functions, formal authorization of access requests, management of access rights, logging, and restrictions to privileged access — that, if properly implemented, constrain the ability to add container cluster roles. But the clause is a policy mandate rather than a technical implementation; the actual prevention is performed by the controls it points to (A.5.16, A.5.18, A.8.2), and an adversary with sufficient permissions can still bypass governance requirements short of full technical enforcement.
- T1098.007partialprevents — A.5.15 mandates access control rules including restrictions to privileged access, segregation of duties, formal authorization of access requests, and management of access rights — all directly relevant to preventing unauthorized group membership changes — but it is the policy/framework that requires these mechanisms, not the technical implementation itself; the actual prevention comes from the controls it references (A.5.16, A.5.18, A.8.2).
- T1112partialprevents — A.5.15 mandates access control rules — restrictions on privileged access, formal authorization of access requests, and management of access rights — which directly constrain who can modify the registry (the technique itself notes registry access depends on account permissions). However, A.5.15 is a policy/framework control that requires implementation; the actual prevention comes from the technical controls that enforce those rules (A.8.2, A.8.3, etc.), and adversaries operating within legitimate permissions or with valid accounts can still modify registry keys their access allows.
- T1133partialprevents — A.5.15 mandates an access control policy that restricts external remote services to authorized entities, which prevents unauthorized initial access, but the control is a policy requirement rather than a technical enforcement mechanism and cannot prevent an adversary from exploiting an exposed unauthenticated service or a misconfigured gateway.
- T1136.002partialprevents — A.5.15 mandates access control mechanisms — formal authorization of access requests, restrictions to privileged access, segregation of duties, and management of access rights — that, if implemented, constrain unauthorized domain account creation; but it is a policy/framework control that requires other controls (A.5.16, A.5.18, A.8.2) to perform the actual prevention, and an adversary with sufficient privileges can still create accounts where the policy is not enforced.
- T1136.003partialprevents — A.5.15 requires a policy that mandates access control rules, including formal authorization of access requests and management of access rights, which constrains the creation of unauthorized cloud accounts but does not eliminate the possibility when an adversary has already obtained sufficient privileges to bypass those rules.
- T1210partialprevents — A.5.15 mandates access control rules that, when implemented, constrain remote service exploitation through network segmentation (clause c on distributed environments and authorized network services), privileged access restrictions (e), and segregation of duties (f); but it is a governance clause that requires these controls rather than implementing them, and it does not address the underlying software vulnerabilities that T1210 exploits, so prevention is partial and depends on downstream technical controls.
- T1213partialprevents — A.5.15 mandates substantive access control requirements — need-to-know, formal authorization of access requests, management of access rights, and consistency between access rights and information classification — that, if implemented, directly constrain who can reach information repositories; but the clause is a policy/framework that delegates actual enforcement to A.5.16, A.5.18, A.8.2 and A.8.3, so it constrains the technique without performing the prevention itself.
- T1213.006partialprevents — A.5.15 mandates an access control policy that restricts database access to authorized entities, which prevents unauthorized collection, but the control is a policy requirement rather than a technical enforcement mechanism, so it reduces the attack surface without eliminating it.
- T1484.002partialprevents — A.5.15 mandates restrictions on privileged access (item e), segregation of duties (item f), formal authorization of access requests (item i), management of access rights (item j), and logging (item k) — all directly relevant to constraining who may modify domain or federation trust relationships. However, it is a policy/governance clause that requires these controls be defined and implemented rather than implementing them itself (the actual mechanisms sit in A.5.16, A.5.18, A.8.2, etc.), and T1484.002 specifically targets high-privilege operations (Domain Admin, federation admin) that policy requirements alone cannot fully prevent once such access is held.
- T1485partialprevents — A.5.15 mandates access control rules that, when implemented, restrict which entities can delete or overwrite data, preventing unauthorized data destruction; however, the clause is a governance/framework control that does not itself implement the technical mechanisms (those live in A.8.2, A.8.3, etc.), and authorized users, insiders, and adversaries operating with valid or compromised credentials can still execute T1485 within their granted rights.
- T1491.001partialprevents — A.5.15 mandates access control rules that restrict who can modify internal websites, login messages and desktop wallpaper, so unauthorized defacement is constrained where write access is properly limited; however, the technique typically occurs after the adversary has already established access (often via compromised credentials with legitimate write privileges), and A.5.15 is the policy/rules clause whose enforcement depends on A.5.16, A.5.18 and A.8.2, leaving a named remainder of defacement performed by authorized-but-compromised actors.
- T1491.002partialprevents — A.5.15 mandates access control rules that, when implemented, restrict who can modify external-facing systems and prevent unauthorized write access that enables defacement; however, it is the policy/framework layer and the actual prevention depends on dependent technical controls (A.8.2, A.8.3, A.8.5), and defacement can still occur via application-layer vulnerabilities or compromised credentials of authorized users.
- T1505partialprevents — A.5.15 is a governance/policy control that mandates access control rules — restrictions to privileged access, formal authorization of access requests, segregation of duties — which, if implemented, constrain who can install server components (the mechanism of T1505). Following the A.5.1 precedent (governance controls can hold `prevents` partial when they mandate handling that constrains the technique), this reaches partial. The remainder is that A.5.15 itself implements nothing: it requires the rules, and the actual prevention lives in A.8.2/A.8.3/A.5.16; authorized administrators can still abuse legitimate extensibility features; and the clause does not specifically address server software components.
- T1505.001partialprevents — A.5.15 mandates formal authorization of access requests, restrictions to privileged access, and management of access rights — requirements that, when implemented, constrain who can create or modify stored procedures. However, it is a governance/policy control that sets the framework rather than implementing the technical restrictions itself; DBAs and application accounts legitimately need stored-procedure creation rights, and the technique often leverages already-privileged or compromised accounts, so the prevention is a slice of the attack surface rather than a closure.
- T1530partialprevents — A.5.15 mandates substantive access control requirements — determining which entities need access, restricting privileged access, formal authorization, management of access rights, logging, and consistency between access rights and information classification — that, when implemented, constrain the misconfiguration and overly-broad access vectors common in T1530; but it is a policy/framework control that requires these things be done rather than implementing them itself, and it does not address the credential-leakage vector, so the prevention lives in the implementing controls (A.5.16, A.5.18, A.8.2, A.8.3).
- T1543.005partialprevents — A.5.15 mandates restrictions on privileged access, formal authorization of access requests, and management of access rights — requirements that, if implemented, would constrain who can reach container management tools (docker, kubelet, etc.) and thus prevent the persistence/privilege-escalation paths T1543.005 relies on; but the clause is a policy/requirements control that does not itself implement the technical mechanisms, so prevention depends on downstream controls (A.8.2, A.8.3) actually enforcing those rules.
- T1546.018partialprevents — A.5.15 mandates that access control rules be defined and implemented with restrictions on who can modify system resources (including Python installation directories), which if properly enforced would prevent unauthorized placement of .pth files or sitecustomize.py; however, it is a policy/framework clause that requires implementation by other controls (A.5.16, A.5.18, A.8.2, A.8.3) rather than itself enforcing the restrictions, and it cannot prevent the technique where the actor already has write access (e.g., privileged users, developers with legitimate Python directory access).
- T1548.005partialprevents — A.5.15 mandates access control rules whose specific guidance — restrictions to privileged access (e), segregation of access control functions (h), formal authorization of access requests (i), and management of access rights (j) — directly constrains the misconfigured permission paths that enable T1548.005, but the clause is the policy mandate and not the implementing mechanism (A.8.2, A.5.18, A.8.3 carry that), so the prevention is partial rather than full.
- T1553partialprevents — Access control restricts unauthorized changes to registry, file permissions, and certificate stores that trust-control subversion often requires, but it does not stop users with legitimate or already-compromised privileges from modifying user-level trust settings or abusing valid access.
- T1561.002partialprevents — A.5.15 mandates access control rules including restrictions on privileged access, segregation of duties, and formal authorization of access requests, which when implemented constrain who can write to disk structures; however, the clause is a policy/governance layer that requires implementation rather than implements it itself, and the technique can be performed by authorized users or malware operating with obtained credentials (T1078, T1003, T1021.002) that the access policy does not stop.
- T1565partialprevents — A.5.15 mandates access restrictions, segregation of duties, restrictions on privileged access, and formal authorization of access requests, which collectively prevent unauthorized entities from manipulating data; however, authorized users with write access can still manipulate data within their scope, and adversaries operating under compromised legitimate credentials bypass the control, so the prevention is bounded rather than complete.
- T1565.003partialprevents — A.5.15 is a governance/policy control that mandates an access control framework (restrictions on privileged access, segregation of duties, formal authorization, logging) which, if implemented, would restrict who can modify application binaries — but the clause itself defines and maps the rules rather than enforces them technically; the actual prevention comes from the controls it references (8.2, 8.26, 5.16, 5.18), so per the A.5.1 principle a policy mandating a capability is not the capability, and a bounded remainder (exploits bypassing ACLs, compromised authorized users, incomplete coverage) keeps this at partial.
- T1569.002partialprevents — A.5.15 mandates access control policies including restrictions on privileged access (8.2), segregation of duties, and management of access rights — all directly relevant to who can create or start Windows services, which is what T1569.002 abuses. Following the A.5.1 vs T1137.001 pattern, a policy that mandates restrictions on the mechanism the technique requires can constrain it. But A.5.15 is a governance/policy clause: it requires the policy to exist and the rules to be defined, it does not itself implement the technical enforcement, and authorized administrators can still create services, so the prevention is partial rather than full.
- T1574.011partialprevents — A.5.15 mandates that access rights be properly defined, authorized, and managed — requirements that, if implemented, would constrain weak Registry key permissions enabling T1574.011 — but the clause is a policy/governance artifact that requires implementation rather than implementing the ACLs itself, and it does not specifically address Registry key permissions on Windows services.
- T1586.003partialprevents — A.5.15's topic-specific policy, requirements for determining authorized entities/roles, need-to-know, segregation of duties/privileges, formal authorization, and consistent access rules directly constrain the acquisition and use of compromised cloud accounts as infrastructure or exfiltration resources, but do not address upstream credential compromise vectors (phishing, spraying, token theft) that enable the technique.
- T1601partialprevents — A.5.15 mandates access control rules — restrictions to privileged access, formal authorization of access requests, management of access rights — that, when implemented, prevent unauthorized modification of system images on network devices; however, it is a framework/policy control requiring implementation, and the technique can still succeed via exploitation of the device, compromised credentials, or abuse of already-authorized privileged access, leaving a bounded remainder.
- T1601.001partialprevents — A.5.15 governs access control rules and restricts who can access network devices, which directly addresses the technique's primary vectors (operator-level access via TFTP/FTP/SCP/console, and administrative access for in-memory patching); however, it is a policy/framework control that mandates rather than implements enforcement, cannot prevent authorized insiders from abusing legitimate access, and does not reach boot-loader-level compromise (ROMMONkit) which bypasses OS-level access controls.
- T1654partialprevents — A.5.15 is a governance/policy control that mandates access control rules which, if implemented, would prevent unauthorized log enumeration by restricting who can read log files, but the control itself does not implement those rules and the prevention depends on proper implementation of the access control policy.
- T1677partialprevents — A.5.15 mandates access control requirements (restrictions to privileged access, segregation of duties, formal authorization of access requests, management of access rights) that are the primary defense against unauthorized modification of CI/CD pipelines, but it is a policy/guidance control whose actual prevention depends on implementation in A.5.16, A.5.18, A.8.2 and A.8.3, and the Public Pipeline Execution scenario exploits fork-PR misconfigurations that access-control policy alone does not address.
- T1686partialprevents — A.5.15's substantive requirements on privileged access restrictions, segregation of duties, segregation of access control functions, and formal authorization meaningfully constrain who can modify firewall rules, but it is a policy/framework control whose technical enforcement lives in A.8.2/A.8.3 and the firewall's own ACLs, and it cannot stop an adversary who has already gathered sufficient privileges from tampering with firewall rules.
- T1686.003partialprevents — Access control can stop unprivileged or unauthorized users from modifying the Windows host firewall, but it does not prevent an adversary who holds or obtains valid privileged access rights, so the technique is only partly prevented.
- T1688partialprevents — Access control restricts the privileged access required to modify BCD/registry and force Safe Mode Boot, but an adversary with valid or compromised privileged access can still perform those modifications.
Prevented OWASP Web Top 10 (2025) risks (7)
OWASP Web Top 10 (2025) risk categories this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- A01partialblocks — A.5.15's purpose and guidance directly address determining, defining, and implementing access control rules, policies, and rights to ensure authorized access (covering authorization decisions, need-to-know, privileged restrictions, formal requests, and role-based mapping), which prevents many Broken Access Control instances like missing checks, IDOR, and improper authorization, but leaves out non-authorization members such as path traversal and CSRF as in the AC-3 vs A01 anchor.
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.