Skip to content
Compliance · PCI DSS v4.0.1

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.

FAQ

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

  1. PCI Security Standards Council, PCI DSS v4.0.1 (Document Library), 2024-06
  2. PCI SSC blog, Just Published: PCI DSS v4.0.1, 2024-06-11
  3. 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.

Ask an Autharva SME

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.
Bigger than a question?Share a problem statement or use case with the team that plans our roadmap →
0/2000

We use these details only to reply. Privacy statement

Next step

What can your identities really reach?

Find out before an attacker or an examiner does.