PCI DSS protects account data
PCI DSS provides a common baseline for protecting payment account data from theft or misuse. It covers technical, physical, and organizational controls across the security environment.
The standard applies to entities that store, process, or transmit account data. It also applies to entities that can affect the security of that data. The ISC blueprint places this task in Security, Confidentiality and Privacy, under Regulations, standards and frameworks.
Payment-data rules differ from health-information rules in HIPAA covered entities and disclosures. Account-data controls also differ from the personal-data scope and principles in GDPR scope and principles.
The problem is broader than protecting a card number in one database. PCI DSS therefore uses requirements covering networks, system settings, stored and transmitted data, software, access, physical security, monitoring, testing, and organizational support.
The twelve PCI DSS requirements
PCI DSS presents a set of requirements, not a sequence of decisions. The rule card gives the complete structure before each requirement is matched with its focus and scenario clues.
🔑 RULE: “PCI DSS provides a baseline of technical and operational requirements designed to protect account data.”
PCI DSS v4.0.1 requirements:
- Requirement 1 - Install and Maintain Network Security Controls
- Requirement 2 - Apply Secure Configurations to All System Components
- Requirement 3 - Protect Stored Account Data
- Requirement 4 - Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks
- Requirement 5 - Protect All Systems and Networks from Malicious Software
- Requirement 6 - Develop and Maintain Secure Systems and Software
- Requirement 7 - Restrict Access to System Components and Cardholder Data by Business Need to Know
- Requirement 8 - Identify Users and Authenticate Access to System Components
- Requirement 9 - Restrict Physical Access to Cardholder Data
- Requirement 10 - Log and Monitor All Access to System Components and Cardholder Data
- Requirement 11 - Test Security of Systems and Processes Regularly
- Requirement 12 - Support Information Security with Organizational Policies and Programs
The numbers label the requirements from 1 through 12. They do not show a calculation, a pass rate, or a decision path.
What each requirement protects
Each row pairs the official requirement title with its focus and the words that identify it in a scenario. The distinctions between stored data, transmitted data, access, authentication, monitoring, and testing are especially important.
| Requirement | What it asks or covers | Clue words in a scenario |
|---|---|---|
| 1. Install and Maintain Network Security Controls | Protect network boundaries and traffic with maintained network security controls. | firewall, network boundary, segmentation, inbound traffic |
| 2. Apply Secure Configurations to All System Components | Use secure settings and remove unsafe defaults and unnecessary services. | default password, hardening, secure setting, unnecessary service |
| 3. Protect Stored Account Data | Protect account data while stored, including the primary account number, or PAN. | database, file, retention, deletion, PAN at rest |
| 4. Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks | Protect cardholder data while it moves across an open or public network. | in transit, public Wi-Fi, open network, encryption |
| 5. Protect All Systems and Networks from Malicious Software | Protect systems and networks against malicious software. | malware, malicious software, antivirus, malicious code |
| 6. Develop and Maintain Secure Systems and Software | Build, maintain, update, and change systems and software securely. | application development, patch, secure coding, software update |
| 7. Restrict Access to System Components and Cardholder Data by Business Need to Know | Allow access only when a business role requires it. | business need to know, least privilege, role, permissions |
| 8. Identify Users and Authenticate Access to System Components | Identify each user and verify identity before access. | user ID, unique account, password, authentication |
| 9. Restrict Physical Access to Cardholder Data | Limit physical entry to systems, facilities, and media containing cardholder data. | door, visitor, badge, media, server room |
| 10. Log and Monitor All Access to System Components and Cardholder Data | Create and monitor records of access to systems and cardholder data. | audit log, event log, review, access record |
| 11. Test Security of Systems and Processes Regularly | Regularly test systems and processes for security weaknesses. | vulnerability scan, penetration test, security test |
| 12. Support Information Security with Organizational Policies and Programs | Support the requirements with policies and security programs. | security policy, training, incident response, governance |
The official titles become easier to recall when connected to the event or condition they describe.
Matching situations to requirements
Match each situation to one PCI DSS requirement. The answer depends on the focus of the situation, not on a control number or implementation judgment.
Practice
A retailer reviews the rules that control traffic between its cardholder data environment and other networks and updates those network security controls. Which PCI DSS requirement applies?
A payment application is installed with a vendor's default administrator password, and services that the system does not need remain enabled. Which PCI DSS requirement applies?
A checkout terminal sends cardholder data across airport Wi-Fi. The control question concerns protecting the data while it moves across that open public network. Which PCI DSS requirement applies?
A security team runs recurring tests of systems and security processes to find weaknesses. Which PCI DSS requirement applies?
The key contrasts are network controls versus cryptography, secure configuration versus software maintenance, and testing versus monitoring.
PCI DSS requirements at a glance
- Requirement 1. Install and maintain network security controls.
- Requirement 2. Apply secure settings to every system component.
- Requirement 3. Protect account data while it is stored.
- Requirement 4. Use strong cryptography over open or public networks.
- Requirement 5. Protect systems and networks from malicious software.
- Requirement 6. Develop, update, and maintain systems and software securely.
- Requirement 7. Restrict access by business role and need to know.
- Requirement 8. Identify users and authenticate access.
- Requirement 9. Restrict physical entry to cardholder data and related systems or media.
- Requirement 10. Record and monitor access to systems and cardholder data.
- Requirement 11. Test systems and processes for security weaknesses regularly.
- Requirement 12. Support information security with organizational policies and programs.
Unlock the full lesson and continue reading
Signup to continue reading this lesson and unlimited access questions, flashcards, AI notes, and more

