Requirements 7-8: Access Control and Identity
What you'll learn: How PCI-DSS Requirements 7 and 8 enforce the principle of least privilege and identity verification to protect cardholder data.
Why These Requirements Exist
Even with network segmentation, encrypted storage, and secure development, unauthorized insiders or compromised accounts remain a serious threat. PCI-DSS Requirements 7 and 8 address the who can access what and how we prove who they are.
Requirement 7: Restrict Access by Business Need-to-Know
Not every employee, contractor, or system account needs access to cardholder data. Requirement 7 mandates that access is granted only to individuals whose job functions require it.
Think of this like hospital records: only the attending physician, assigned nurse, and billing specialist should access a specific patient's file—not every employee in the building.
Key implementation points:
- Establish role-based access control (RBAC) defining job functions
- Default to "deny all" and grant specific permissions explicitly
- Document which roles need access to what data
- Regularly review and revoke unnecessary access
Requirement 8: Identify and Authenticate Access
Requirement 8 ensures every person and process accessing systems is uniquely identified and properly authenticated.
Core controls:
- Assign unique IDs to each user (no shared accounts)
- Enforce strong password policies or multi-factor authentication (MFA)
- Lock accounts after failed login attempts
- Require MFA for remote access to the cardholder data environment
- Log all authentication attempts for audit trails
This is the digital equivalent of showing a government-issued ID and providing a fingerprint—you must prove you are who you claim to be before accessing sensitive areas.
Key Takeaway: PCI-DSS Requirements 7 and 8 enforce least privilege and strong identity verification, ensuring only authorized individuals can access cardholder data and that all access is traceable to a specific person or system.