WithPCI Logo
WithPCI.com

8.3.6 If passwords/passphrases are used as authentication factors to meet Requirement 8.3.1, they meet the following minimum level of complexity:

Original requirement from PCI DSS v4.0.1

Defined Approach Requirements

8.3.6 If passwords/passphrases are used as authentication factors to meet Requirement 8.3.1, they meet the following minimum level of complexity:

  • A minimum length of 12 characters (or IF the system does not support 12 characters, a minimum length of eight characters).
  • Contain both numeric and alphabetic characters.

Customized Approach Objective

A guessed password/passphrase cannot be verified by either an online or offline brute force attack.

Applicability Notes

This requirement is not intended to apply to:

  • User accounts on point-of-sale terminals that have access to only one card number at a time to facilitate a single transaction.
  • Application or system accounts, which are governed by requirements in section 8.6.

This requirement is a best practice until 31 March 2025, after which it will be required and must be fully considered during a PCI DSS assessment.

Until 31 March 2025, passwords must be a minimum length of seven characters in accordance with PCI DSS v3.2.1 Requirement 8.2.3.

Defined Approach Testing Procedures

8.3.6 Examine system configuration settings to verify that user password/passphrase complexity parameters are set in accordance with all elements specified in this requirement.

Purpose

Strong passwords/passphrases may be the first line of defense into a network since a malicious individual will often first try to find accounts with weak, static, or non-existent passwords. If passwords are short or easily guessable, it is relatively easy for a malicious individual to find these weak accounts and compromise a network under the guise of a valid user ID.

Good Practice

Password/passphrase strength is dependent on password/passphrase complexity, length, and randomness. Passwords/passphrases should be sufficiently complex, so they are impractical for an attacker to guess or otherwise discover its value. Entities can consider adding increased complexity by requiring the use of special characters and upper- and lower-case characters, in addition to the minimum standards outlined by this requirement. Additional complexity increases the time required for offline brute force attacks of hashed passwords/passphrases.

Another option for increasing the resistance of passwords to guessing attacks is by comparing proposed password/passphrases to a bad password list and having users provide new passwords for any passwords found on the list.

purpose

Ensure MFA systems are implemented securely and cannot be bypassed.

compliance strategies

  • MFA system hardening
  • Bypass prevention

typical policies

  • MFA Implementation Policy

common pitfalls

  • MFA can be disabled by users
  • Insecure MFA integrations

type

Technical Control

difficulty

High

key risks

  • MFA bypass leads to unauthorized access

recommendations

  • Regularly test MFA effectiveness

Eligible SAQ

  • SAQ-A
  • SAQ-A-EP
  • SAQ-C
  • SAQ-C-VT
  • SAQ-D MERCHANT
  • SAQ-D SERVICE PROVIDER

Your perspective on this PCI DSS requirement matters! Share your implementation experiences, challenges, or questions below. Your insights help other organizations improve their compliance journey and build a stronger security community.Comment Policy