PCI DSS 4.0.1 Requirements 7 and 8: access control and authentication
PCI DSS 4.0.1 Requirements 7 and 8 require least-privilege access, a review of all user accounts every six months (7.2.4), periodic review of system and application accounts (7.2.5), immediate removal of terminated users and MFA for all non-console access into the cardholder data environment (8.4.2). Assessors ask for review records, system account inventories with owners, and termination evidence, which Autharva supports by showing what each account can reach and who owns it.
Who it applies to: All entities that store, process or transmit cardholder data or sensitive authentication data, or could affect its security, including merchants, processors, acquirers, issuers and other service providers.
What the rule asks for
- Requirements 7.2.1 and 7.2.2Access control model and least privilege. Define an access control model and assign access, including privileged access, based on job classification, function and the least privileges needed.
- Requirement 7.2.4Six-month user account review. Review all user accounts and related privileges, including third-party and vendor accounts, at least once every six months, address inappropriate access, and have management acknowledge the result.
- Requirements 7.2.5 and 7.2.5.1Application and system accounts. Assign application and system account privileges on least privilege, and review that access periodically at a frequency set by the entity's targeted risk analysis.
- Requirements 8.2.5 and 8.2.6Terminated and inactive accounts. Revoke access for terminated users immediately, and remove or disable user accounts within 90 days of inactivity.
- Requirement 8.4.2MFA into the CDE. Implement MFA for all non-console access into the cardholder data environment.
- Requirement 8.6.1Interactive use of system accounts. Prevent interactive login with system or application accounts except for documented, management-approved exceptions, with every action attributable to an individual user.
- Requirements 8.6.2 and 8.6.3System account passwords. Do not hard-code passwords for interactive-capable system accounts in scripts, files or code, and change system account passwords at a risk-defined frequency and on suspected compromise.
Dates that matter
- PCI SSC publishes PCI DSS v4.0.1, a limited revision with no added or deleted requirements.
- PCI DSS v4.0 is retired, leaving v4.0.1 as the supported version.
- Future-dated requirements become mandatory, including 7.2.4, 7.2.5, 7.2.5.1, 8.4.2 and 8.6.1 to 8.6.3.
Where access evidence usually falls short
- Six-month reviews leave out third-party and vendor accounts that 7.2.4 explicitly includes.
- Application and system accounts have no owner, so no one can confirm their access is still appropriate.
- The targeted risk analysis that sets the system account review and password-change frequency is missing or not followed.
- Terminated users are revoked in the directory, but local accounts in CDE systems remain.
- System accounts are used for interactive login without documented approval or attribution to an individual.
How Autharva helps
- Shows what every user, service account, OAuth grant and AI agent can actually reach, including through the apps it administers and the keys it holds.
- Assigns a named owner and a scope to every service account, vendor login and OAuth grant.
- Closes access no one should still have, only with the owner's approval.
- Hands exceptions back to your IGA certification campaigns for the six-month review.
- Produces continuous access-control evidence for PCI DSS 4.0.1 from inside your own network.
Autharva produces evidence that supports these controls. It does not by itself make an organization compliant; your auditor or examiner decides.
Evidence your examiner or auditor will ask for
- Documented access control model and role definitions
- Six-month user account review records, including vendor accounts and management acknowledgment
- Application and system account inventory with owners, privileges and review dates
- Targeted risk analysis setting system account review and password-change frequency
- Termination and 90-day inactivity reports with removal dates
- MFA configuration records for non-console access into the CDE
Questions.
Are the future-dated requirements in force now?+
Yes. They were best practices until 31 March 2025 and are now assessed. That includes 7.2.4, 7.2.5, 7.2.5.1, 8.4.2 and 8.6.1 to 8.6.3.
How often must application and system accounts be reviewed?+
Requirement 7.2.5.1 leaves the frequency to the entity's targeted risk analysis, performed under Requirement 12.3.1. The assessor will expect to see that analysis and reviews that follow it.
Do vendor accounts need the six-month review?+
Yes. Requirement 7.2.4 covers all user accounts, including third-party and vendor accounts.
Does Autharva make us PCI compliant?+
No. Autharva produces evidence for the access-control parts of Requirements 7 and 8. Network, data protection, testing and other requirements are outside it.
Sources
- PCI Security Standards Council, PCI DSS v4.0.1 (Document Library), 2024-06
- PCI SSC blog, Just Published: PCI DSS v4.0.1, 2024-06-11
- PCI SSC blog, Now is the Time for Organizations to Adopt the Future-Dated Requirements of PCI DSS v4.x, 2024-08-20
Summaries are in our own words for orientation, not legal advice. Read the official text and check with your counsel.
Have a requirement we haven't covered?
Describe your environment, a system you're unsure about, or an audit finding. An Autharva SME reads every message and replies by email.
- Answered by a person, not a script.
- Please don't include passwords, customer data or account numbers.
What can your identities really reach?
Find out before an attacker or an examiner does.