Skip to content
09/19StandardOut of scope

PCI DSS explained

The security standard for handling payment-card data.

See current catalog counts, technical check coverage, and remaining gaps

This reference explains the framework. Product coverage depends on the bundled catalog, connected evidence, and assessment scope; a technical mapping is not full compliance.

What it is

Maintained by the PCI Security Standards Council, PCI DSS is a framework for safely storing, processing, and transmitting cardholder data. Validation ranges from a Self-Assessment Questionnaire (SAQ) for smaller merchants to a Report on Compliance (ROC) by a QSA for large volumes.

Latest PCI DSS updates

Framework Watch →

Certifiable?

Validated compliance (SAQ or QSA-signed ROC), enforced by card brands/acquirers.

Where it's used

Any organization that touches cardholder data, worldwide.

Effort level

Scales with card volume and how much you can descope (e.g., via a payment processor).

Typical trigger

You start accepting or processing card payments.

Related frameworks

Overlaps with CIS/ISO on the technical controls, but is payment-specific.

Why it matters

PCI DSS protects payment-card data throughout its lifecycle. Compliance isn't optional if you process cards — the card brands enforce it, and breaches carry severe financial penalties, liability, and loss of the ability to process payments.

When is it needed?

As soon as your systems store, process, or transmit cardholder data. Even if you use a payment processor, you likely have some PCI DSS obligations depending on your integration method.

Use cases

  • E-commerce platforms processing payments
  • Payment service providers and gateways
  • Retail and hospitality point-of-sale environments
  • SaaS platforms with payment features
  • Any business handling card-present or card-not-present transactions

Who asks for it?

  • Card brands (Visa, Mastercard, Amex, Discover)
  • Acquiring banks and payment processors
  • Merchant service providers
  • Qualified Security Assessors (QSAs)
  • Customers trusting you with their card data

Benefits

  • Protects against payment-data breaches and associated liability
  • Required to maintain the ability to process card payments
  • Well-defined scope reduction techniques (tokenization, P2PE)
  • SAQ options for smaller merchants reduce assessment burden
  • Mature ecosystem of tools, assessors, and guidance
  • Clear, prescriptive requirements with testing procedures

Legal requirements

Mandated contractually by card brands through merchant agreements. While not a government law, failure to comply results in fines, increased transaction fees, and potential loss of card-processing privileges.

Key control areas

Build and maintain a secure network (firewalls, no defaults)
Protect cardholder data (encryption, key management)
Maintain a vulnerability management program
Implement strong access control measures
Regularly monitor and test networks
Maintain an information security policy

Want to see how WardBee maps your environment to PCI DSS?

What's new · v1.0.0

ScanComb and WardBee 1.0: compliance checks, TISAX and SOC 2 readiness, and a new public site

This is the first release of ScanComb and WardBee. WardBee brings automated compliance checks, framework workspaces, reports and task tracking for engineering, security and compliance teams. scancomb.com adds free checks and a TISAX readiness check, plus guides and news.

Highlights

  • TISAX readiness check Answer a public questionnaire and get a free readiness score by email. A paid report adds findings, an action plan for each chapter, a roadmap and a PDF. You can import the gaps into a WardBee workspace as tasks.
  • Dedicated TISAX section in WardBee Manage TISAX in one place. Set the scope, keep a self-assessment register, follow an action plan with tasks, track audits and labels, and manage suppliers and exports.
  • SOC 2 readiness Work through a readiness questionnaire, criterion guidance, a policy pack and reviews. Criteria are explained in plain words and questions can be answered in the side drawer. You can download a SOC 2 readiness report as a PDF.
  • Sovereignty Profile free check Run the free Sovereignty Profile check and get a report. The scores are explained in plain words.
  • Projects with a shared scan pool Run several projects or clients in separate workspaces that share one pool of scans. A For consultants page explains the setup.

Improvements

  • Resource inventory See an inventory of your resources with filters, saved views and notifications.
  • EU Cyber Resilience Act support Prepare for the EU Cyber Resilience Act with product classification and a continuous technical file.
  • NIS2 Supplier Check Assess suppliers against NIS2 with the NIS2 Supplier Check.
  • Free AI security check and AI Shield playbooks Take a free AI security check and read practical playbooks on AI agent permissions, prompt injection, shadow AI and more.
  • Manual control verification Verify controls that cannot be checked automatically, using a clearer drawer for manual controls.
  • Clearer controls and findings Findings and resource names are easier to read, you can filter to checks-only scans, and you can compare one scan with the previous one.
  • Faster control and dashboard pages Controls, the dashboard and risks load faster. App pages show a loading state right away.
  • Better start for new workspaces New workspaces start with ISO 27001 and SOC 2, with an explanation of what scans do. If no frameworks are chosen, a Choose frameworks step guides you.
  • Support tickets, announcements and notification bell Open support tickets inside WardBee and get email updates. Announcements appear in a header bell.
  • New site design, menu and guides scancomb.com has a new look and a grouped menu with News, Free checks and Guides. WardBee uses the same visual style, and the in-app docs are task-focused guides.
  • What's New and Framework Watch A What's New dialog shows release notes on scancomb.com. A weekly Framework Watch news issue is also published.
  • Team invitations and two-factor sign-in Invite teammates by email with consistent role names. Two-factor setup includes a QR code.

Fixes

  • Security improvements to sign-up and sign-in Sign-up and sign-in are now better protected.
  • More accurate AWS multi-factor authentication checks All MFA device types are now recognized, and users who only use programmatic access are no longer flagged.
  • Confirmed failures are shown correctly A confirmed failure now outranks an error in a control's status.
  • One critical-control email per scan You now get a single critical-control email per control for each scan.
  • Smoother onboarding and failed checks Workspaces without frameworks are sent to setup. Checks that fail are refunded, and queued checks show as Queued.
  • Correct access errors Signed-out or unauthorized requests now get a proper access error instead of a server error.