WithPCI Logo
WithPCI.com

8.3.7 Individuals are not allowed to submit a new password/passphrase that is the same as any of the last four passwords/passphrases used.

Original requirement from PCI DSS v4.0.1

Defined Approach Requirements

8.3.7 Individuals are not allowed to submit a new password/passphrase that is the same as any of the last four passwords/passphrases used.

Customized Approach Objective

A previously used password cannot be used to gain access to an account for at least 12 months.

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.

Defined Approach Testing Procedures

8.3.7 Examine system configuration settings to verify that password parameters are set to require that new passwords/passphrases cannot be the same as the four previously used passwords/passphrases.

Purpose

If password history is not maintained, the effectiveness of changing passwords is reduced, as previous passwords can be reused over and over. Requiring that passwords cannot be reused for a period reduces the likelihood that passwords that have been guessed or brute-forced will be re-used in the future.

Passwords or passphrases may have previously been changed due to suspicion of compromise or because the password or passphrase exceeded its effective use period, both of which are reasons why previously used passwords should not be reused.

purpose

Ensure MFA mechanisms are not susceptible to replay attacks.

compliance strategies

  • Use time-based tokens
  • One-time passwords

typical policies

  • MFA Security Policy

common pitfalls

  • Static codes used
  • Replayable tokens

type

Technical Control

difficulty

Moderate

key risks

  • Session hijacking

recommendations

  • Use TOTP or hardware tokens

Eligible SAQ

  • SAQ-A
  • SAQ-A-EP
  • SAQ-C
  • 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