PCI 3DS Core Security Standard P1-5.2.2: P1-5.2.2 Unique account ID per individual

What else in your programme already covers this

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

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 Part 1 Requirement P1-5: Manage access – PCI 3DS Core Security Standard

• P1-5.1.1 P1-5.1.1 Access-assignment policy and procedures
• P1-5.1.2 P1-5.1.2 Roles and responsibilities defined for groups and accounts
• P1-5.1.3 P1-5.1.3 Least privilege by job function, reviewed periodically
• P1-5.2.1 P1-5.2.1 Account-management policy and procedures
• P1-5.2.3 P1-5.2.3 Accounts and credentials kept confidential and intact
• P1-5.2.4 P1-5.2.4 Account misuse prevented
• P1-5.2.5 P1-5.2.5 Third-party access identified, controlled and monitored
• P1-5.3.1 P1-5.3.1 Strong authentication for all access to 3DS systems