| name | implementing-pci-dss-compliance-controls |
| description | PCI DSS 4.0.1 establishes 12 requirements across 6 control objectives for organizations that store, process, or transmit cardholder data. With PCI DSS 3.2.1 retiring April 2024 and 51 new requirements |
| domain | cybersecurity |
| subdomain | compliance-governance |
| tags | ["compliance","governance","pci-dss","payment-security","cardholder-data"] |
| nist_csf | ["GV.PO-01","PR.DS-01","PR.AA-01","DE.CM-01","ID.RA-01"] |
| version | 1.0 |
| author | mahipal |
| license | Apache-2.0 |
| mitre_attack | ["T1078","T1530","T1685.002"] |
| source | https://github.com/mukul975/Anthropic-Cybersecurity-Skills |
| source_commit | 04450304b12645cb2b974ab96d28c0664758a88d |
Implementing PCI DSS Compliance Controls
Overview
PCI DSS 4.0.1 establishes 12 requirements across 6 control objectives for organizations that store, process, or transmit cardholder data. With PCI DSS 3.2.1 retiring April 2024 and 51 new requirements becoming mandatory March 31, 2025, this skill covers implementing all requirements including the new customized validation approach, enhanced authentication, and continuous monitoring controls.
When to Use
- When deploying or configuring implementing pci dss compliance controls capabilities in your environment
- When establishing security controls aligned to compliance requirements
- When building or improving security architecture for this domain
- When conducting security assessments that require this implementation
Prerequisites
- Understanding of payment card processing flows and cardholder data environment (CDE)
- Knowledge of network segmentation and security architecture
- Access to cardholder data environment for scoping
- Understanding of PCI compliance validation levels (merchant levels 1-4, service provider levels 1-2)
Core Concepts
12 PCI DSS Requirements by Control Objective
Build and Maintain a Secure Network and Systems
- Install and maintain network security controls (firewalls, NSCs)
- Apply secure configurations to all system components
Protect Account Data
3. Protect stored account data (encryption, tokenization, truncation)
4. Protect cardholder data with strong cryptography during transmission
Maintain a Vulnerability Management Program
5. Protect all systems and networks from malicious software
6. Develop and maintain secure systems and software
Implement Strong Access Control Measures
7. Restrict access to system components and cardholder data by business need to know
8. Identify users and authenticate access to system components
9. Restrict physical access to cardholder data
Regularly Monitor and Test Networks
10. Log and monitor all access to system components and cardholder data
11. Test security of systems and networks regularly
Maintain an Information Security Policy
12. Support information security with organizational policies and programs
Key PCI DSS 4.0 Changes
- Customized Approach: Alternative to defined approach, allowing custom control design with objective-based validation
- MFA for all CDE access: Extended beyond admin to all access to cardholder data (Req 8.4.2)
