WithPCI Logo
WithPCI.com

8.3.3 User identity is verified before modifying any authentication factor.

Original requirement from PCI DSS v4.0.1

Defined Approach Requirements

8.3.3 User identity is verified before modifying any authentication factor.

Customized Approach Objective

Unauthorized individuals cannot gain system access by impersonating the identity of an authorized user.

Defined Approach Testing Procedures

8.3.3 Examine procedures for modifying authentication factors and observe security personnel to verify that when a user requests a modification of an authentication factor, the user's identity is verified before the authentication factor is modified.

Purpose

Malicious individuals use "social engineering" techniques to impersonate a user of a system — for example, calling a help desk and acting as a legitimate user—to have an authentication factor changed so they can use a valid user ID.

Requiring positive identification of a user reduces the probability of this type of attack succeeding.

Good Practice

Modifications to authentication factors for which user identity should be verified include but are not limited to performing password resets, provisioning new hardware or software tokens, and generating new keys.

Examples

Methods to verify a user's identity include a secret question/answer, knowledge-based information, and calling the user back at a known and previously established phone number.

purpose

Use MFA for all remote access to the CDE by personnel and third parties.

compliance strategies

  • MFA for vendors, contractors, and staff

typical policies

  • Third-Party Access Policy

common pitfalls

  • Vendors bypassing MFA

type

Technical Control

difficulty

Moderate

key risks

  • Third-party credential theft

recommendations

  • Require MFA for all third-party remote access

Eligible SAQ

  • 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