PCI DSS PTS Compliance for Service Providers and Merchants

Author

Reads 1.2K

Large container ship moored at Hamburg port terminal with cranes.
Credit: pexels.com, Large container ship moored at Hamburg port terminal with cranes.

PCI DSS PTS compliance is a must for service providers and merchants who handle credit card information.

Service providers and merchants must undergo a rigorous assessment to ensure they meet the PCI DSS standards.

The assessment process involves a thorough review of their systems, processes, and security controls to identify vulnerabilities and areas for improvement.

Service providers and merchants must also implement a comprehensive security program to protect sensitive cardholder data.

Check this out: Pci Dss Risk Assessment

PCI DSS Requirements

The PCI DSS has twelve requirements for compliance, organized into six related groups known as control objectives. These groups are: Build and maintain a secure network and systems, Protect cardholder data, Maintain a vulnerability management program, Implement strong access-control measures, Regularly monitor and test networks, and Maintain an information security policy.

Each of the twelve requirements has three sections: PCI DSS requirements, Testing, and Guidance. The PCI DSS requirements define the requirement, the Testing section outlines the processes and methodologies for confirming proper implementation, and the Guidance section explains the purpose of the requirement and provides corresponding content to assist in its proper definition.

The twelve requirements can be broken down into the following categories: Install and maintain network security controls, Protect stored account data, Protect cardholder data with strong cryptography during transmission over open, public networks, and others.

Explore further: Pci Dss Requirement 6

Requirements

Credit: youtube.com, The 12 PCI DSS Requirements: How to Ensure PCI Compliance

The PCI DSS has twelve requirements for compliance, organized into six related groups known as control objectives. These groups are: Build and maintain a secure network and systems, Protect cardholder data, Maintain a vulnerability management program, Implement strong access-control measures, Regularly monitor and test networks, and Maintain an information security policy.

Each of the twelve requirements is divided into three sections: PCI DSS requirements, Testing, and Guidance. The PCI DSS requirements define the requirement, the Testing section outlines the processes and methodologies for confirming proper implementation, and the Guidance section explains the purpose of the requirement and provides additional content to assist in its proper definition.

There are four different PCI compliance levels, typically based on the volume of credit card transactions your business processes during a 12-month period. The compliance levels are: Level 1, Level 2-3, Level 4, and SAQ D for Merchants and Service Providers.

The PCI DSS has different Self-Assessment Questionnaire (SAQ) types depending on your payment integration method. Here are the SAQ types for Level 2-4 merchants:

Companies that need to handle card data may be required to meet each of the 300+ security controls in PCI DSS. This can be a complex and costly process, but third-party solutions can securely accept and store the data, reducing the complexity and risk.

Related reading: First Data Pci Compliance

Card Brand Programs

Credit: youtube.com, What is PCI DSS? | A Brief Summary of the Standard

If you're a merchant who accepts a large number of transactions, you might be eligible for the Visa TIP program, which can save you time and money by exempting you from the annual PCI DSS revalidation process.

This program is especially beneficial for high-volume or geographically dispersed merchants who might otherwise face a more challenging and costly assessment process.

By using a PCI-validated P2PE solution, you can qualify for the Visa TIP program, which allows you to discontinue your annual assessment process to revalidate PCI DSS compliance.

Merchants of any size can apply for the Visa TIP program, but it's especially valuable for those who process a large volume of transactions.

In order to be eligible, you must use a PCI-validated P2PE solution and have documentation showing that 100% of transactions were accepted via this solution.

There is no separate application process for the Visa TIP program, but you should still strive to achieve full PCI DSS compliance.

Using a PCI-validated P2PE solution also provides safe harbor for fees in the event of a compromise for Level 3 and 4 card-present merchants.

Recommended read: Pci Dss P2pe

Reporting and Validation

Credit: youtube.com, Solving the PCI DSS Roc Report Beast

Companies subject to PCI DSS standards must be PCI-compliant, and how they prove and report their compliance is based on their annual number of transactions and how the transactions are processed. Merchant levels are categorized into four levels: Level 1, Level 2, Level 3, and Level 4.

Each card issuer maintains a table of compliance levels and a table for service providers. Compliance validation involves the evaluation and confirmation that the security controls and procedures have been implemented according to the PCI DSS.

Here are the different merchant levels:

  • Level 1: Over six million transactions annually
  • Level 2: Between one and six million transactions
  • Level 3: Between 20,000 and one million transactions, and all e-commerce merchants
  • Level 4: Less than 20,000 transactions

To prove compliance, organizations must complete a PCI validation form annually. The way PCI compliance is validated depends on a number of factors, which are outlined below.

Reporting Levels

Reporting Levels are determined by the annual number of transactions and how they're processed. Companies subject to PCI DSS standards must be PCI-compliant.

Merchant levels are based on the number of transactions, with Level 1 being over six million transactions annually. Level 2 is between one and six million transactions. Level 3 is between 20,000 and one million transactions, and all e-commerce merchants. Level 4 is less than 20,000 transactions.

Here's an interesting read: Pci Dss Level 4

Credit: youtube.com, Validation Reports While Using Level Data

An acquirer or payment brand can manually place an organization into a reporting level at its discretion. Each card issuer maintains a table of compliance levels and a table for service providers.

Here are the different merchant levels in a table for easy reference:

Annual Validation

Annual validation is a crucial step in maintaining PCI compliance. You're required to complete a PCI validation form annually, regardless of how card data is accepted.

Organizations are asked to show that they're PCI compliant in various scenarios. Payment processors may request it as part of their required reporting to the payment card brands. Business partners may request it as a prerequisite to entering into business agreements. Customers may request it to show their customers that they're handling data securely.

There are three scenarios in which an organization could be asked to show that it is PCI compliant:

  • Payment processors may request it as part of their required reporting to the payment card brands.
  • Business partners may request it as a prerequisite to entering into business agreements.
  • For platform businesses, customers may request it to show their customers that they're handling data securely.

It's essential to note that the way PCI compliance is validated depends on a number of factors.

Monitor and Maintain

Credit: youtube.com, Validation of LIMS is a part of the data integrity

Maintaining PCI compliance is an ongoing process that requires regular monitoring and maintenance to ensure your business remains compliant even as data flows and customer touchpoints evolve.

Some credit card brands may require you to submit quarterly or annual reports, or complete an annual on-site assessment to validate ongoing compliance, particularly if you process more than 6 million transactions each year.

PCI compliance is not a one-time event, it's a continuous process that needs to be managed throughout the year and year over year. This often requires cross-departmental support and collaboration, especially if you're processing a high volume of transactions.

A good starting point for maintaining PCI compliance would be to create a dedicated team internally to properly maintain compliance. This team should include representation from the following departments:

For more information about PCI compliance, head to the PCI Security Standards Council website.

Security and Compliance

To ensure PCI DSS compliance, organizations must have a strong access control system in place to protect sensitive card data. This includes implementing measures such as encryption and ongoing monitoring to prevent unauthorized access.

Credit: youtube.com, Certified PCI-DSS Security Compliance Professional

Storing data securely is a critical component of PCI DSS compliance. Organizations must define the scope of their cardholder data environment (CDE) and properly segment the payment environment from the rest of the business to limit the scope of PCI validation.

A list of the 12 security requirements for PCI DSS includes:

  • Encryption of sensitive card data
  • Ongoing monitoring of access to card data
  • Security testing of access to card data
  • Implementation of access control measures
  • Maintenance of an information security policy
  • Transport Layer Security (TLS) protocols
  • Key management practices and cipher strength
  • Certified key injection facilities (KIFs)
  • PTS-approved POI devices with encryption performed in the SRED (secure reading and exchange of data) tamper-resistant security module (TRSM)
  • Positive device identification prior to decryption
  • Key management/decryption in hardware security modules (HSMs) that have been validated by PCI and/or FIPS 140-2 Level 3

By implementing these security requirements, organizations can significantly reduce the risk of data breaches and ensure compliance with PCI DSS standards.

Security Assessors

The PCI Security Standards Council maintains a program to certify companies and individuals to perform assessment activities. This program is designed to ensure that security assessors have the necessary expertise to evaluate an organization's compliance with PCI DSS.

An Internal Security Assessor (ISA) is an individual who has earned a certificate from the PCI Security Standards Council for their sponsoring organization. ISAs can conduct PCI self-assessments for their organization and propose security solutions and controls for PCI DSS compliance.

Credit: youtube.com, PCI DSS Compliance Unveiling the Role of a Qualified Security Assessor QSA

ISAs are responsible for cooperation and participation with Qualified Security Assessors (QSAs). QSAs, on the other hand, are experts who have been certified to conduct PCI DSS assessments for organizations.

Here are some key facts about ISAs and QSAs:

Check Security Controls

To check security controls, you need to ensure the right configurations and protocols are in place to secure the transmission of data. This includes protocols like Transport Layer Security (TLS).

The 12 security requirements for PCI DSS are designed to protect sensitive data for any business. They overlap with requirements for other privacy mandates like GDPR and HIPAA, so some of these controls may already be in place in your organization.

To map out the potential touchpoints for credit card data, work with IT and security teams to identify all systems, laptops, and devices that store, process, or transmit credit card data. This is known as the cardholder data environment (CDE).

See what others are reading: Card Data Covered by Pci Dss Includes

Hand inserting card into contactless payment terminal for secure online transaction.
Credit: pexels.com, Hand inserting card into contactless payment terminal for secure online transaction.

Proper segmentation of the payment environment from the rest of the business is crucial to limit the scope of PCI validation. If this can't be done with granular segmentation, the PCI security controls would apply to every system, laptop, and device on the corporate network.

Here are the 12 security requirements for PCI DSS:

  • Build and maintain a secure network and systems
  • Protect sensitive cardholder data
  • Implement strong access control measures
  • Regularly monitor and test networks
  • Implement a robust incident response plan
  • Restrict access to cardholder data
  • Assign a unique ID to each person with computer access
  • Restrict physical access to cardholder data
  • Track and monitor all access to network resources and cardholder data
  • Regularly update and patch systems and applications
  • Restrict vendor access to cardholder data
  • Implement a strong information security policy

Stripe Helps Achieve and Maintain

Stripe significantly simplifies the PCI burden for companies that integrate with Checkout, Elements, mobile SDKs, and Terminal SDKs. This is because Stripe Checkout and Stripe Elements use a hosted payment field for handling all payment card data, so the cardholder enters all sensitive payment information in a payment field that originates directly from Stripe's PCI DSS–validated servers.

Stripe acts as a PCI advocate and can help in a few different ways. We'll analyze your integration method and advise you on how to reduce your compliance burden. We'll notify you ahead of time if a growing transaction volume will require a change in how you validate compliance.

For large merchants (Level 1), if you need to work with a PCI QSA, there are more than 350 such QSA companies around the world, and Stripe can connect you with several auditors that deeply understand the different Stripe integration methods.

Additional reading: Is Stripe Hipaa Compliant

Frequently Asked Questions

What is the PCI PTS version of a terminal?

A terminal that meets PCI PTS requirements is a secure device for handling PINs, ensuring compliance with industry standards for payment card security.

What PCI DSS means?

PCI DSS stands for Payment Card Industry Data Security Standard, a set of rules to protect sensitive credit card information from data breaches and fraud. It's a crucial standard for organizations handling credit card data to ensure security and compliance.

How to find PCI PIN transaction security pts device?

Check the PCI SSC website for a list of approved PCI PTS HSM devices, which have passed compliance testing and been approved by the PCI SSC

Adrian Fritsch-Johns

Senior Assigning Editor

Adrian Fritsch-Johns is a seasoned Assigning Editor with a keen eye for compelling content. With a strong background in editorial management, Adrian has a proven track record of identifying and developing high-quality article ideas. In his current role, Adrian has successfully assigned and edited articles on a wide range of topics, including personal finance and customer service.

Love What You Read? Stay Updated!

Join our community for insights, tips, and more.