PCI Compliance 101: Key Things that Matter.

What Is PCI DSS?

The Payment Card Industry Data Security Standard, commonly referred to as PCI DSS, is a set of mandatory requirements designed to ensure the protection of payment card data. Established by the PCI Security Standards Council (PCI SSC), which comprises major international card schemes, PCI DSS sets the global standard for securing cardholder information.

Why PCI Compliance Matters?

Compliance with PCI DSS is not only a requirement for merchants and service providers but also an integral aspect of your Agreement with your Acquirer or Payment Gateway. All businesses such as merchants (such as businesses that accept payments online), service providers (such as hosting providers and payment gateways), and financial institutions (such as banks) must achieve and maintain PCI Compliance.

Scope of PCI DSS

PCI DSS applies to all entities that store, process, or transmit payment card data, regardless of their size or volume of transactions.

This universal applicability ensures that every link in the payment chain is secure. While larger merchants may deal with complex environments and extensive cardholder data, smaller merchants often benefit from simpler setups, allowing for a potentially reduced effort in achieving compliance.

However, the level of effort required for compliance is influenced by various factors, including transaction volumes, payment channels, and the use of PCI DSS-compliant service providers.

Core Principles and Compliance Requirements

Main goal of PCI Compliance is to protect Payment Card Data.

PCI DSS is structured around six fundamental principles, which are further broken down into twelve detailed requirements. To become compliant, businesses must demonstrate adherence to all relevant requirements.

PCI Compliance Goals and Requirements
PCI Compliance: 6 Goals and 12 Requirements

Understanding and implementing these 12 requirements is crucial for businesses to not only comply with PCI DSS but to also ensure the highest level of security for their customer's data.

Your company must attest that it has achieved PCI Compliance by completing a Self-Assessment Questionnaire (SAQ) and forwarding it to your acquiring bank.

An acquiring bank is a bank or financial institution that processes credit or debit card payments on behalf of a merchant (i.e. your business). Most acquiring banks insist on their merchants being PCI-compliant.

What Is Cardholder Data?

Cardholder data (CHD) or Payment card data is any information associated with a person in possession of a credit or debit card. Cardholder data includes the primary account number (PAN) along with the cardholder's name, expiration date, and service code.

Payment Card Data

The following table describes which information you can store and which you cannot.

source: PCI SSC PCI DSS v4 Quick Reference Guide

Steps to Achieving PCI Compliance

Achieving PCI compliance may seem daunting, but breaking it down into steps can simplify the process. Here’s how businesses can approach compliance:

Step 1: Determine Your PCI Compliance Level

First, identify your business’s transaction volume over the past 12 months to determine your PCI DSS compliance level, ranging from 1 to 4. Your level dictates the specific requirements and reporting measures you must follow:

  • Level 1: Over six million annual card transactions
    • An annual Report on Compliance (ROC) and an Attestion of Compliance (AOC) by a Qualified Security Assessor (QSA) or an Internal Security Assessor (ISA)
    • A "Pass" quarterly network scan by an Approved Scanning Vendor (ASV)
  • Level 2: One to six million annual card transactions
    • An annual Self-Assessment Questionnaire (SAQ) and an Attestion of Compliance (AOC)
    • A "Pass" quarterly network scan by an Approved Scanning Vendor (ASV)
  • Level 3: Twenty thousand to one million annual card transactions
    • An annual Self-Assessment Questionnaire (SAQ) and an Attestion of Compliance (AOC)
    • A "Pass" quarterly network scan by an Approved Scanning Vendor (ASV)
  • Level 4: Fewer than twenty thousand annual card transactions
    • An annual Self-Assessment Questionnaire (SAQ) and an Attestion of Compliance (AOC)
    • A "Pass" quarterly network scan by an Approved Scanning Vendor (ASV)

Once you have confirmed your transaction numbers and compliance level. Next step is to understand which SAQ applies to your environment.

Determining applicable SAQ?

To determine your SAQ level, you need to consider the following factors:

  • The number of payment card transactions you process annually across all channels
  • The type of payment card processing environment you have (e.g., online, in-store, mail/telephone order, mobile)
  • Whether you outsource any of your payment card processing activities to third-party service providers

Once you have considered these factors, you can use the following list to determine your SAQ level:

  • SAQ A is for online and mail/phone order merchants
    • have outsourced all credit card processing to a third party and do not store any credit card data on their own systems.
  • SAQ A-EP is for online merchants
    • that use a third party to process credit card payments and who have a website that does not handle credit card data, but could still affect the security of the payment transaction.
  • SAQ B is for merchants
    • that use manual imprinting machines or standalone dial-out terminals and do not electronically transmit, process, or store credit card data.
  • SAQ B-IP is for merchants
    • that use only standalone, PTS-approved payment terminals with an IP connection to the payment processor and do not electronically store credit card data.
  • SAQ C-VT is for merchants
    • that use a virtual terminal on a single computer that is only used to process credit card payments. Credit card data is not stored on the computer.
  • SAQ C is for any merchant
    • that accepts credit card payments online, but does not store credit card data on its own systems.
  • SAQ P2PE is for merchants
    • that use approved point-to-point encryption (P2PE) devices and do not store credit card data on their own systems.
  • SAQ D-Merchant is for merchants
    • that do not outsource their credit card processing or use a P2PE solution, and may store credit card data electronically.
  • SAQ D-Service Provider is for service providers that are eligible to complete an SAQ.

If you are still unsure which SAQ level applies to you, you can contact your acquirer or payment brand for assistance.

Here are some additional tips for determining your SAQ level:

  • Review the PCI DSS Self-Assessment Questionnaire (SAQ) Instructions and Guidelines document to understand the different types of SAQs and the criteria for each level.
  • If you outsource any of your payment card processing activities to third-party service providers, make sure to obtain documentation of their PCI DSS compliance status.
  • Consult with your acquirer or payment brand if you have any questions about determining your SAQ level.

Step 2: Assess Your Current Security Posture

Evaluate your current payment card operations and security practices. Identify all systems and processes that handle cardholder data and assess them against PCI DSS requirements.

Step 3: Remediate Any Vulnerabilities

Address any vulnerabilities uncovered during the assessment. This could mean updating software, changing processes, or eliminating the storage of cardholder data unless absolutely necessary.

Step 4: Compile and Submit Compliance Reports

After remediation, compile a Report on Compliance (ROC) or complete a Self-Assessment Questionnaire (SAQ), depending on your compliance level. Submit the required documentation to the appropriate card brands and acquire a vulnerability scan from an Approved Scanning Vendor (ASV) if necessary.

Step 5: Maintain Compliance and Monitor Security

Compliance is not a one-time event but an ongoing process. Regularly monitor and test your security systems, maintain robust access control measures, and keep your staff trained on PCI DSS policies and procedures.

By following these steps, a business can not only achieve but also maintain PCI DSS compliance, thereby securing cardholder data and sustaining customer trust.

The Benefits of PCI Compliance

Compliance with PCI DSS can bring major benefits to your company, while failure to comply can have serious and long-term negative consequences. Achieving PCI Compliance means that:

  • systems are secure, and members can trust you with their sensitive payment card information.
  • less risk of security breaches and theft of payment card data, not just today, but in the future.
  • better reputation with banks and payment brands -the partners you need in order to do business.

The Consequence of Non-Compliance

Non-compliance with PCI DSS can have serious consequences for any business that accepts payment cards, including:

  • Just one security breach can severely damage your organization's reputation and its ability to conduct business effectively, now and in the future.
  • Data breaches can lead to catastrophic loss of customers and sales.
  • Other consequences include lawsuits, insurance claims, canceled memberships, payment card issuer fines and government fines.

Below are some recent examples that highlight the importance of adherence to these standards.

Magecart Attack on Warner Music Group

In late 2020, Warner Music Group was targeted by Magecart, resulting in exposed customer payment information over three months. This breach emphasized the need for stringent PCI DSS compliance to safeguard against sophisticated supply chain attacks​​.

Adobe’s Data Breach Settlements

Adobe suffered a breach affecting 38 million users, with three million credit card records compromised. The company faced legal penalties and had to settle for violations of the Customer Records Act, illustrating the legal and financial stakes at play​​.

Heartland Payment Systems Penalized

Heartland Payment Systems experienced an SQL injection attack, leading to a breach of payment card data. The breach led to a 14-month ban from processing payments and roughly $145 million in compensation to affected parties, showcasing the operational consequences of non-compliance​​.

The Equifax Data Breach

Equifax’s 2017 breach affected 143 million Americans and disclosed sensitive information, including credit card numbers. The incident resulted in a $425 million settlement and highlighted the extended liability and customer impact a breach can carry​​.

These incidents underscore the critical nature of PCI DSS compliance in protecting against data breaches and the severe outcomes of non-compliance.

Maintaining Ongoing PCI Compliance

Once a business achieves PCI DSS compliance, the work isn't over. Maintaining compliance is a continuous effort to protect cardholder data effectively. Here’s how to stay on top of compliance requirements:

  • Continuous Monitoring and Testing Continuous vigilance is key to maintaining PCI DSS compliance. Businesses must implement regular system testing to uncover vulnerabilities that could be exploited by cybercriminals
  • Implement Regular System Scans Regular scans by an Approved Scanning Vendor (ASV) are required for most merchants. These scans help identify potential vulnerabilities in your system.
  • Conduct Internal and External Penetration Testing Annual penetration testing helps simulate an attack on your systems to identify and fix security weaknesses.
  • Ongoing Training for Staff Employees play a crucial role in maintaining PCI compliance. Continuous education on security policies and procedures is necessary to prevent accidental or deliberate data breaches.
  • Develop Regular Training Programs Schedule periodic training sessions to keep staff updated on the latest security practices and compliance procedures.
  • Incident Response Planning Prepare for the worst-case scenario by having an incident response plan in place. This ensures that your business can react swiftly and effectively to any security breach.
  • Create a Comprehensive Incident Response Plan Your plan should outline clear steps for addressing a breach, including containment strategies, notification procedures, and methods to prevent future incidents.
  • Documentation and Policy Maintenance Maintaining a secure environment for cardholder data involves keeping all policies and documentation up to date with the latest PCI DSS requirements.
  • Review and Update Security Policies Regularly review and adjust security policies to reflect changes in technology, business processes, or threats.

By staying proactive with these measures, businesses can ensure they remain PCI DSS compliant and uphold the trust placed in them by customers and partners.

Advanced Considerations in PCI DSS Compliance

As businesses evolve and technology advances, maintaining PCI DSS compliance becomes both more complex and more critical. Here are some advanced considerations to keep in mind:

  • Working with Qualified Security Assessors (QSAs) Qualified Security Assessors are professionals certified by the PCI Security Standards Council to help businesses assess and maintain compliance. Engaging a QSA can provide expert guidance and simplify the compliance process.
  • Embracing Tokenization and Encryption Tokenization and encryption are advanced methods to secure cardholder data. By substituting sensitive data with a unique identifier or encrypting it in a way that only authorized individuals can decipher, these technologies reduce the risk of data breaches.
  • PCI DSS in Cloud Computing Cloud computing introduces new challenges and considerations for PCI compliance. Businesses must ensure that their cloud services provider meets PCI DSS requirements and that data is protected in transit, at rest, and during processing.
  • Staying Ahead of Emerging Threats Cyber threats are constantly evolving, requiring businesses to be vigilant and proactive in updating their security measures. Regularly reviewing and improving security protocols in light of new threats is essential for continued compliance.

By considering these advanced factors, businesses can bolster their defense against security threats and ensure ongoing PCI Compliance.

PCI DSS 4.0: The Latest Version of the Payment Card Industry Data Security Standard

PCI DSS 4.0, the latest version of the Payment Card Industry Data Security Standard, was introduced in March 2022. It builds on the 12 core PCI DSS requirements, adding new and updated requirements for mobile payments, contactless payments, cloud computing, software development, and third-party relationships.

The four objectives of PCI DSS 4.0 are to:

  • Ensure that the standard continues to meet the security needs of the payments industry and maintain secure systems
  • Add flexibility and support for additional security methodologies
  • Encourage businesses to view security as a continuous process and regularly test security systems
  • Enhance validation methods and procedures

PCI DSS 4.0 is designed to help businesses protect cardholder data and meet their obligations under the PCI DSS. It also aligns the standard with the latest security threats and trends.

Key changes in PCI DSS 4.0:

  • Expanded requirements for mobile payments, contactless payments, cloud computing, software development, and third-party relationships
  • Increased focus on risk management and continuous security
  • More flexible requirements to support a variety of business models and technologies
  • Enhanced validation methods and procedures

Benefits of PCI DSS 4.0:

  • Improved protection for cardholder data
  • Reduced risk of data breaches and other security incidents
  • Increased compliance with other industry regulations
  • Enhanced reputation and trust with customers and partners

How to comply with PCI DSS 4.0:

  • Conduct a gap assessment to identify any areas where your business needs to improve its security posture
  • Implement the required controls and processes
  • Have your compliance validated by a Qualified Security Assessor (QSA)

PCI DSS 4.0 is an important update to the PCI DSS standard that reflects the evolving security landscape. By complying with the latest PCI Compliance standard, businesses can help protect cardholder data and reduce the risk of security incidents.

Wrap up

PCI compliance is crucial for safeguarding payment data:

  • Understand the Requirements: Grasp the 12 PCI DSS requirements to build a secure payment environment.
  • Implement Advanced Security: Use technologies like tokenization and encryption to protect cardholder data.
  • Choose the Right Partners: Work with service providers that adhere to PCI DSS standards.
  • Stay Updated: Keep systems patched with the latest security updates.
  • Monitor and Respond: Establish continuous monitoring and a proactive incident response plan.
  • Educate Your Team: Regularly train staff on PCI DSS guidelines and security best practices.

By prioritizing these actions, businesses reinforce their defense against data breaches and maintain the trust of their customers and partners.

For more insights click here.

Scroll to Top