PCI DSS 4.0
Req 8: Identify and Authenticate Users

PCI DSS 4.0 8.3.5: 8.3.5 Initial and reset passwords unique and changed

Where passwords or passphrases serve as authentication factors under Requirement 8.3.1, they must be set and reset for each user so that they are: given a unique value when first issued and whenever reset; and forced to be changed immediately after first use. Customized approach objective: nobody unauthorized can make use of a starting or reset password or passphrase issued to a user.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 18 controls across 14 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 2 controls

  • IA-5 Authenticator Management
  • IA-5(1) Password-Based Authentication

FedRAMP Moderate · 2 controls

  • IA-5 Authenticator Management
  • IA-5(1) Password-Based Authentication

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

  • NIST800-IA-5 IA-5 Authenticator Management
  • SP800-53-IA Identification and Authentication Family

CIS Controls v8 · 1 control

CMMC 2.0 · 1 control

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 5.17 Authentication information

ISO 27002:2022 · 1 control

  • 5.17 Authentication information

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization

NIST SP 800-172 · 1 control

NIST SP 800-66 Rev 2 · 1 control

SOC 2 · 1 control

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Req 8: Identify and Authenticate Users

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 8.3.5 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.

If you hold ISO 27001:202249.6% covered · 141 gapsIf you hold FedRAMP Moderate49.3% covered · 142 gapsIf you hold NIST SP 800-53 Rev 547.5% covered · 147 gapsIf you hold ISO 27002:202243.2% covered · 159 gapsIf you hold CIS Controls v838.2% covered · 173 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 18 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls