PCI DSS 4.0
Req 8: Identify and Authenticate Users

PCI DSS 4.0 8.3.2: 8.3.2 Authentication factors unreadable with strong cryptography

Strong cryptography must be used to make all authentication factors unreadable both in transit and at rest on every system component. The testing procedures examine factor repositories and data transmissions. The guidance explains that some network devices and applications have sent or stored passwords in cleartext, letting an attacker capture them with a sniffer or read the files where they sit and then reuse them. Customized approach objective: nobody can obtain, derive or reuse a cleartext authentication factor by intercepting traffic or reading stored data.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 43 controls across 21 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 · 4 controls

  • AC-17(2) Protection of Confidentiality and Integrity Using Encryption
  • IA-5(1) Password-Based Authentication
  • IA-5(2) Public Key-Based Authentication
  • IA-5(6) Protection of Authenticators

FedRAMP Moderate · 4 controls

  • AC-17(2) Protection of Confidentiality and Integrity Using Encryption
  • IA-5(1) Password-Based Authentication
  • IA-5(2) Public Key-Based Authentication
  • IA-5(6) Protection of Authenticators

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 controls

  • SOC2-C1.1 C1.1 Identifying and maintaining confidential information
  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal
  • ASBv3-IM-2 Protect identity and authentication systems
  • ASBv3-IM-8 Restrict the exposure of credential and secrets
  • DP-3 Encrypt sensitive data in transit
  • NIST-CSF-PR.AA-04 Identity assertions are protected, conveyed, and verified
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
  • NIST-CSF-PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected

C5 (Germany) · 2 controls

  • C5-IDM-08 Confidentiality of authentication information
  • C5-PSS-07 Confidentiality of Authentication Information

CIS Controls v8 · 2 controls

  • CIS-3.10 Encrypt Sensitive Data in Transit
  • CIS-3.11 Encrypt Sensitive Data at Rest

ISO 27001:2022 · 2 controls

  • 5.17 Authentication information
  • 8.24 Use of cryptography

ISO 27002:2022 · 2 controls

  • 5.17 Authentication information
  • 8.24 Use of cryptography
  • ASD37-23 Protect authentication credentials (Excellent)

CMMC 2.0 · 1 control

HIPAA Security Rule · 1 control

ISO 27701:2019 · 1 control

  • 6.7.1 Cryptographic controls

NIST SP 800-172 · 1 control

  • P1-5.2.3 P1-5.2.3 Accounts and credentials kept confidential and intact

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.2 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.

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.

Query this from an agent

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