← PCI DSS 4.0.1 · Req 7 — Restrict access by need to know

7.2 — Access granted by least privilege and reviewed every six months

critical access-controlaccess-review

Requirement

Access to system components and cardholder data is defined and assigned by job classification and function, on least privilege; privileged access is limited to what is required; and all user accounts and their access privileges are reviewed at least once every six months.

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
least privilegeneed to knowrole-basedrbacjob functionjob classification
Required element 2 — any one of
reviewreviewedevery six monthssix monthssemi-annual…approvedapproval
Supporting terms — specificity signals
7.2.17.2.27.2.47.2.5privilegeddeny all
Contradiction markers

Finding any of these outranks coverage — a policy that admits the gap is worse than silence.

everyone has admin all users have admin

Equivalent controls elsewhere

Matched on shared topics. Satisfying this control usually moves these too.

FrameworkControlTitleShared topics
ISO 27001 A.5.18 Access rights review access-review access-control
HIPAA 164.308(a)(4)(ii)(C) Access establishment and modification (A) access-review access-control
GLBA 314.4(c)(1) Access controls on customer information access-control access-review
SOC 2 CC6.3 Access modification and removal access-control access-review
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
ISO 27001 A.5.3 Segregation of duties access-control