PCI DSS requirements

PCI DSS requirements

Published September 28, 2026

PCI DSS requirements

On this page

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:

  1. Requirement 1 - Install and Maintain Network Security Controls
  2. Requirement 2 - Apply Secure Configurations to All System Components
  3. Requirement 3 - Protect Stored Account Data
  4. Requirement 4 - Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks
  5. Requirement 5 - Protect All Systems and Networks from Malicious Software
  6. Requirement 6 - Develop and Maintain Secure Systems and Software
  7. Requirement 7 - Restrict Access to System Components and Cardholder Data by Business Need to Know
  8. Requirement 8 - Identify Users and Authenticate Access to System Components
  9. Requirement 9 - Restrict Physical Access to Cardholder Data
  10. Requirement 10 - Log and Monitor All Access to System Components and Cardholder Data
  11. Requirement 11 - Test Security of Systems and Processes Regularly
  12. 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.

RequirementWhat it asks or coversClue words in a scenario
1. Install and Maintain Network Security ControlsProtect network boundaries and traffic with maintained network security controls.firewall, network boundary, segmentation, inbound traffic
2. Apply Secure Configurations to All System ComponentsUse secure settings and remove unsafe defaults and unnecessary services.default password, hardening, secure setting, unnecessary service
3. Protect Stored Account DataProtect 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 NetworksProtect 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 SoftwareProtect systems and networks against malicious software.malware, malicious software, antivirus, malicious code
6. Develop and Maintain Secure Systems and SoftwareBuild, 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 KnowAllow access only when a business role requires it.business need to know, least privilege, role, permissions
8. Identify Users and Authenticate Access to System ComponentsIdentify each user and verify identity before access.user ID, unique account, password, authentication
9. Restrict Physical Access to Cardholder DataLimit 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 DataCreate and monitor records of access to systems and cardholder data.audit log, event log, review, access record
11. Test Security of Systems and Processes RegularlyRegularly test systems and processes for security weaknesses.vulnerability scan, penetration test, security test
12. Support Information Security with Organizational Policies and ProgramsSupport 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

Scan to download app

Scan to download
UNLOCK FREE ACCESS

Practice Questions: PCI DSS requirements

  1. 1. A company subject to the EU General Data Protection Regulation plans to use customer transaction histories and location data to assign automated credit limits. The resulting limits may prevent customers from obtaining credit, and the processing will occur on a large scale. Which action should the company take before implementing the system?

    • A. Perform a data protection impact assessment addressing the risks and planned safeguards.
    • B. Prepare a process for notifying individuals after a confirmed personal-data breach.
    • C. Establish a process for responding to authenticated requests for copies of personal data.
    • D. Obtain assurance that the system's encryption keys are stored separately from the data.
    Show answer

    Answer: A. Perform a data protection impact assessment addressing the risks and planned safeguards.

    Perform a data protection impact assessment addressing the risks and planned safeguards. - Under the GDPR, automated evaluation that may significantly affect individuals requires a data protection impact assessment before processing begins. - The assessment should address the risks of using transaction histories and location data to set credit limits, along with the safeguards planned to reduce those risks. Prepare a process for notifying individuals after a confirmed personal-data breach. - Breach notification addresses a breach after it occurs, not the risks of the proposed credit-limit system before implementation. - A notification process does not replace the required assessment of processing that may prevent customers from obtaining credit. Establish a process for responding to authenticated requests for copies of personal data. - Responding to access requests supports customers’ data-access rights under the GDPR. - It does not assess the risks and safeguards of large-scale automated credit-limit decisions before processing starts. Obtain assurance that the system's encryption keys are stored separately from the data. - Separating encryption keys from data is a security safeguard for customer information. - That safeguard alone does not assess the risks to individuals from automated credit limits or whether the planned safeguards adequately address them.

  2. 2. BrightPath Benefits, Inc. administers employee wellness plans and determines the purposes and means of processing participant information. CloudMetrics LLC processes that information solely under BrightPath's instructions. On April 14, 2026, BrightPath received notice that a CloudMetrics API token had been exposed. You are assisting BrightPath's incident-response coordinator in determining the affected population, applicable notification obligations, response sequence, and documentation conclusion. Use all exhibits; contractual and legal timing requirements supplied in the exhibits govern the case.

    • 3. A payroll system no longer receives security patches. The company's policy requires the payroll process owner and chief information security officer to document proposed risk acceptance, and requires cybersecurity committee approval when residual risk exceeds the company's risk appetite. The unsupported system's residual risk is rated high, while the approved appetite is medium. An IT operations manager requests continued use. What should occur next?

      • A. Obtain the process owner's and CISO's documented recommendation and cybersecurity committee approval
      • B. Obtain the CISO's approval and schedule a vulnerability scan after the exception begins
      • C. Obtain the IT operations manager's acceptance and record the exception in the asset inventory
      • D. Obtain internal audit's approval and report the exception during the next annual audit
      Show answer

      Answer: A. Obtain the process owner's and CISO's documented recommendation and cybersecurity committee approval

      Obtain the process owner's and CISO's documented recommendation and cybersecurity committee approval - Company policy requires the payroll process owner and CISO to document proposed risk acceptance before continued use of the unsupported system. - Because high residual risk exceeds the medium risk appetite, the cybersecurity committee must approve the exception. Obtain the CISO's approval and schedule a vulnerability scan after the exception begins - The CISO participates in documenting the recommendation but cannot independently approve an above-appetite exception under the stated policy. - A scan after the exception begins does not replace the required committee approval before continued use. Obtain the IT operations manager's acceptance and record the exception in the asset inventory - The IT operations manager requested continued use but has no risk-acceptance authority assigned by the stated policy. - An asset-inventory entry does not substitute for the process owner's and CISO's documentation or committee approval. Obtain internal audit's approval and report the exception during the next annual audit - Internal audit may assess the risk-acceptance process but should not assume management's responsibility for accepting the payroll system's risk. - Reporting at the next annual audit would not satisfy the policy's required approval for residual risk above appetite.

    • 4. Authentication logs show repeated login attempts that apply one commonly used password to hundreds of employee accounts, with only one or two attempts per account. Which control would most directly prevent the attacker from using a correctly guessed password to access the company's remote-access portal?

      • A. Alert when one account generates 50 failed login attempts
      • B. Lock an account after three consecutive failed login attempts
      • C. Require users to change their passwords every 90 days
      • D. Require phishing-resistant multifactor authentication for remote access
      Show answer

      Answer: D. Require phishing-resistant multifactor authentication for remote access

      Require phishing-resistant multifactor authentication for remote access - The pattern is password spraying: one commonly used password is tried against hundreds of accounts, with only one or two attempts per account. - Phishing-resistant multifactor authentication prevents a correctly guessed password alone from granting access to the remote-access portal. Alert when one account generates 50 failed login attempts - The alert watches for 50 failures on one account, while the logs show only one or two attempts per account. - It would not directly prevent access if one of those attempts uses the correct password. Lock an account after three consecutive failed login attempts - One or two attempts per account would not trigger a three-failure lockout. - A correct guess could grant access before any lockout occurs. Require users to change their passwords every 90 days - A scheduled change does not stop an attacker from using a currently valid password. - Unlike multifactor authentication, password rotation still leaves the remote-access portal accessible with a correctly guessed password alone.

    • 5. A payroll system requires remote users to enter a password and a six-digit PIN. The security policy requires authentication using two independent factor categories. Which change would satisfy the policy?

      • A. Replace the PIN with a code generated by an authenticator application
      • B. Replace the PIN with the answer to a personal security question
      • C. Replace the password with an employee number while retaining the PIN
      • D. Replace the password and PIN with fingerprint and facial recognition
      Show answer

      Answer: A. Replace the PIN with a code generated by an authenticator application

      Replace the PIN with a code generated by an authenticator application - The password is a knowledge factor, while a code generated by an authenticator application provides a possession factor through the user's device. - These are two independent factor categories, satisfying the payroll system’s policy. Replace the PIN with the answer to a personal security question - A security-question answer, like a password, is a knowledge factor. - Replacing the PIN with another fact the user knows still leaves the system with only one factor category. Replace the password with an employee number while retaining the PIN - An employee number and a PIN are both information the user knows; an employee number may also be readily available to others. - This change does not add an independent possession or inherence factor. Replace the password and PIN with fingerprint and facial recognition - Fingerprints and facial features are different biometric characteristics, but both belong to the inherence category. - Using two biometrics therefore does not meet the requirement for two independent factor categories.

    • 6. A health plan subject to HIPAA intends to provide identifiable claims records to an outside billing consultant that will use the records to perform services for the plan. The consultant is not otherwise legally authorized to receive the records. Before providing access, which action should the health plan take?

      • A. Execute a business associate agreement and limit the disclosure to the minimum necessary information.
      • B. Obtain a separate written authorization from every plan participant whose claims appear in the records.
      • C. Remove direct identifiers from the records so that no written agreement with the consultant is required.
      • D. Revise the plan's privacy notice after the consultant begins processing the claims information.
      Show answer

      Answer: A. Execute a business associate agreement and limit the disclosure to the minimum necessary information.

      Execute a business associate agreement and limit the disclosure to the minimum necessary information. - The outside billing consultant will use identifiable claims records to perform services for the health plan, making it a business associate under HIPAA. - Before providing access, the plan must execute a business associate agreement and limit the records disclosed to what the consultant needs for those services. Obtain a separate written authorization from every plan participant whose claims appear in the records. - HIPAA does not ordinarily require each participant’s authorization for a permitted disclosure to a business associate performing services for the plan. - Individual authorizations do not replace the agreement required for this consultant’s access to identifiable claims records. Remove direct identifiers from the records so that no written agreement with the consultant is required. - HIPAA does not require deidentification before the plan discloses records to a consultant under a compliant business associate agreement. - Removing only direct identifiers may leave information that can identify participants, so it does not necessarily make the claims records deidentified. Revise the plan's privacy notice after the consultant begins processing the claims information. - A privacy notice revision does not replace the business associate agreement required before the consultant receives access. - Revising the notice after processing begins would not authorize the consultant’s earlier access to identifiable claims records.

    • 7. A company relies on immutable backups to recover its billing system from ransomware. Daily reports show that backup jobs completed successfully, but the company has never attempted to restore the application and database in an isolated environment. Which test would provide the most relevant evidence that the recovery control can meet its objective?

      • A. Periodically restore the application and data from immutable backups and reconcile selected records
      • B. Inspect daily backup completion reports and investigate jobs marked as unsuccessful
      • C. Scan the production billing servers for operating-system vulnerabilities each month
      • D. Conduct annual employee training on recognizing ransomware-related email attachments
      Show answer

      Answer: A. Periodically restore the application and data from immutable backups and reconcile selected records

      Periodically restore the application and data from immutable backups and reconcile selected records - An isolated restoration tests whether the immutable backups can actually recover the billing application and database after ransomware. - Reconciling selected records provides evidence that the restored billing data is complete and accurate, not merely accessible. Inspect daily backup completion reports and investigate jobs marked as unsuccessful - Daily reports show whether backup jobs completed, but job completion does not prove the application and database can be restored. - Investigating failed jobs is useful, but it does not address the company’s lack of a restoration test. Scan the production billing servers for operating-system vulnerabilities each month - Vulnerability scans identify weaknesses that could increase the risk of compromise; they do not test recovery from ransomware. - Scanning production servers provides no evidence that the immutable backups can restore the billing application and database. Conduct annual employee training on recognizing ransomware-related email attachments - Employee training may help prevent a ransomware infection, but the control in question is recovery using immutable backups. - Recognizing suspicious attachments does not demonstrate that the billing system can be restored or its records reconciled.

    • 8. Authentication logs show attempts against 8,000 employee accounts from rotating internet addresses. Each account received only two attempts, but the same three commonly used passwords were tried across nearly all accounts. Which control would most directly prevent the attacker from accessing an account when one of the passwords is valid?

      • A. Encrypt stored authentication logs using a centrally managed key.
      • B. Lock each account after five consecutive unsuccessful login attempts.
      • C. Require a phishing-resistant second authentication factor for remote access.
      • D. Review privileged-user access rights at the end of each quarter.
      Show answer

      Answer: C. Require a phishing-resistant second authentication factor for remote access.

      Require a phishing-resistant second authentication factor for remote access. - The attempts across 8,000 accounts indicate password spraying, so a commonly used password may be valid for an employee. - A phishing-resistant second factor prevents a valid password alone from completing remote authentication. Encrypt stored authentication logs using a centrally managed key. - Encrypting logs protects their confidentiality, not the login process. - It would not stop an attacker who has guessed a valid employee password from accessing that account. Lock each account after five consecutive unsuccessful login attempts. - Each account received only two attempts, below the five-failure lockout threshold. - A valid password could therefore grant access without triggering this control. Review privileged-user access rights at the end of each quarter. - A quarterly review addresses whether users retain appropriate privileges, not whether a login uses stolen or guessed credentials. - It would not prevent immediate access when the attacker enters a valid password.

    Flashcards: PCI DSS requirements

    1. 1. What does an output control ensure in a data system?

      Show answer

      Output control ensures data is valid, properly distributed, and used with authorization.

    Everything you need for CPA prep

    Get full Oncourse access with lessons, practice questions, flashcards and AI study tools.

    GET STARTED FOR FREE
    75% OFFLimited time offer
    GET 75% OFF