Requirement
Rules to control physical and logical access to information and other associated assets shall be established and implemented based on business and information security requirements.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Required element 1 — any one of
access controlaccess policylogical access
Required element 2 — any one of
least privilegeneed to knowrole-basedrbacauthorisationauthorizationauthoris…authoriz…
Supporting terms — specificity signals
mfassoreviewapprovalprivilegedsegregation
Contradiction markers
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
no access control
shared accounts
everyone has access
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| HIPAA | 164.312(a)(1) | Access control — unique identification and emergency access (R/A) | access-control authentication |
| NIST CSF 2.0 | PR.AA-01 | Identities and credentials are managed | access-control authentication |
| SOC 2 | CC6.1 | Logical access provisioning and restriction | access-control authentication |
| GDPR | Art.29 | Processing under the authority of the controller | access-control |
| CCPA/CPRA | 1798.100(e) & 1798.150 | Reasonable security procedures | access-control |
| SOC 2 | CC6.2 | Registration and authorisation of new users | access-control |
| PCI DSS 4.0.1 | 7.2 | Access granted by least privilege and reviewed every six months | access-control |
| PCI DSS 4.0.1 | 8.2 | Unique IDs and user account lifecycle | access-control |