PCI DSS v4.0 Compliance & CDE Scoping

PCI DSS v4.0 (effective March 2025) scoping, CDE design, and SAQ A-D delivery -- with cardholder data environments engineered to minimize PCI footprint.

PCI DSS compliance badge

Why PCI DSS Matters

PCI DSS v4.0 became fully effective March 31, 2025, replacing v3.2.1 with 64 sub-requirement updates and a new option for Customized Approach (the Defined Approach remains the default). The standard is structured around six goals and 12 requirements, with controls covering everything from network segmentation (Requirement 1) to access control (Requirements 7-9) to logging and monitoring (Requirement 10) and a documented information security policy (Requirement 12). The compliance burden depends entirely on how your Cardholder Data Environment (CDE) is scoped.

Smart CDE scoping is the single biggest cost lever. Most SaaS shouldn't store, process, or transmit primary account numbers (PANs) directly -- using a tokenization provider (Stripe, Braintree, Adyen) drops you from SAQ D (the most demanding self-assessment, ~330 questions) to SAQ A (the lightest, ~22 questions). For products that genuinely require PAN handling, network segmentation, point-to-point encryption, and tokenization-at-edge can keep most of your infrastructure out of scope -- but the architecture needs to be designed for it from the start.

Our team includes engineers with PCI assessor experience, so we know what evidence works under audit. Annual SAQ submission is straightforward when controls are continuous; the painful path is treating PCI as a once-a-year scramble. We integrate PCI controls with your existing observability stack (Datadog, Splunk, or CloudWatch for Requirement 10 logging), implement quarterly internal scans plus the required external ASV scans, and run penetration testing per Requirement 11.3 with a CREST or OSCP-credentialed team.

PCI DSS process diagram

Why Choose Our PCI DSS v4.0 Compliance & CDE Scoping

Engineering rigor, audit-ready process, and operational depth across cloud, SaaS, and software delivery

Data Security

Cardholder data environment designed for minimum scope -- tokenization at edge, network segmentation enforced via VPC and Service Control Policies, encryption-at-rest and in-transit per Requirement 3 and 4.

Data Security

Risk Reduction

Quarterly internal vulnerability scans plus ASV-required external scans, annual penetration testing per Requirement 11.3, and continuous control monitoring -- not just an annual SAQ submission scramble.

Risk Reduction

Ongoing Support

Annual SAQ preparation and submission, change management for any CDE modification, and breach response runbook tested twice a year. Compliance evidence accumulates continuously.

Ongoing Support

Our PCI DSS Compliance Process

A structured approach to payment security from scoping to ongoing compliance.

1

Scoping & SAQ Determination

Two-to-four weeks: data flow analysis (where PANs touch your systems), CDE boundary documentation, SAQ type determination (A through D, depending on PAN handling), and a remediation plan to minimize scope where possible.

2

Control Implementation

Two to four months: implement required technical controls in Terraform (network segmentation, encryption, IAM, logging), administrative controls in policy (information security policy per Requirement 12, role-based access), and operational controls in runbooks (incident response, vulnerability management, secure SDLC).

3

SAQ Submission & Continuous Compliance

Quarterly internal scans, ASV external scans, annual penetration test, and SAQ submission to acquirer/processor. Change management runs through compliance review for any CDE-touching deployment so scope creep is caught at PR review, not at year-end.

In-House vs. Managed PCI DSS

Why managed PCI DSS is easier.

CDE Scoping

In-House
Default to SAQ D; entire infrastructure pulled in scope
Jacobian Services
Designed for SAQ A or A-EP via tokenization and segmentation

Vulnerability Management

In-House
Annual scans, remediation backlog grows
Jacobian Services
Continuous scanning with severity-based remediation SLAs
PCI DSS Compliance Guide
Whitepaper

PCI DSS Compliance Guide

A guide to PCI DSS compliance for fintech.

Read the whitepaper

PCI DSS-Compliant AI for Financial Services

Fintech companies deploying AI for fraud detection, transaction scoring, and automated underwriting need AI systems that operate within PCI DSS boundaries. When machine learning models process or derive from cardholder data, they become part of your CDE and must meet the same rigorous controls as any other in-scope system. TrustEdge.ai, our AI services division, builds payment-aware AI solutions with PCI DSS compliance embedded from the architecture level up.

Explore Financial Services AI Solutions

PCI DSS FAQs

Common questions about PCI DSS compliance.

Get PCI DSS Compliant

Book a free scoping assessment with our payment security experts.