Scoping and Segmentation
Clear network diagrams, account-data flow maps, third-party responsibility matrices, and firewall or VPC isolation rules that hold up under assessor scrutiny.
Led by former Level 1 payment gateway CIO and CISO David Burroughs, our engineers shrink cardholder data scope first, build the technical controls your environment actually needs, and manage audit evidence alongside your independent QSA through a signed Report on Compliance or SAQ.
When teams start preparing for PCI DSS, the first instinct is often to download a policy binder or buy a compliance dashboard. Starting there usually creates months of avoidable work. Every server, container, admin workstation, CI runner, and browser script connected to your Cardholder Data Environment (CDE)—or able to affect its security—falls into scope unless verified segmentation keeps it out.
Maybe the first question isn't how to harden dozens of application servers, but rather why payment data or checkout scripts touch most of them at all? So we begin by tracing every card-number and authentication path across web checkouts, mobile SDKs, APIs, webhooks, logs, and backups. Moving capture to hosted fields or isolating tokenization routinely pulls whole clusters out of audit scope before fieldwork starts. Read our PCI DSS scoping guide for SaaS teams and Level 1 ROC preparation guide.
Clear network diagrams, account-data flow maps, third-party responsibility matrices, and firewall or VPC isolation rules that hold up under assessor scrutiny.
Instead of handing over a spreadsheet and walking away, our engineers configure centralized logging, phishing-resistant MFA, checkout script controls, and host hardening with you.
Written policies that match how your team actually deploys code, paired with asset-specific Targeted Risk Analyses (Req 12.3.1) and named owners for every recurring record.
Whether you attest through a Level 1 Report on Compliance or a Self-Assessment Questionnaire, we assemble the evidence package and coordinate directly with your QSA or acquirer.
PCI DSS v4.0.1 future-dated controls took effect on March 31, 2025. Assessors no longer treat checkout script inventories, tamper detection, annual scope confirmation, or Targeted Risk Analyses as upcoming items; they ask for dated operating evidence.
| v4.0.1 requirement | What assessors test | How briskData implements and documents it |
|---|---|---|
| Req 6.4.3 Payment-Page Scripts |
Every JavaScript file loaded in the customer's browser on payment pages must be inventoried, authorized with written business justification, and checked for integrity. | Remove unnecessary ad and analytics tags from checkout routes, maintain a signed script inventory tied to change control, and enforce strict Content-Security-Policy allowlists and Subresource Integrity (SRI) or script monitoring. |
| Req 11.6.1 Tamper & Header Monitoring |
Automated detection must alert staff to unauthorized changes in security-impacting HTTP headers and payment-page content as received by the browser at least weekly (or per a TRA). | Deploy synthetic checkout checks and header/DOM comparison alerts wired to your incident queue, and retain alert-verification logs for QSA sampling. |
| Req 12.5.2 Annual Scope Confirmation |
Organizations must formally verify and document PCI DSS scope every 12 months and after major changes across data flows, segmentation controls, and service providers. | Run card-data discovery checks, validate firewall and VPC segmentation rules, reconcile TPSP AoCs and Req 12.8.5 responsibility matrices, and sign off a clean scope package. |
| Req 12.3.1 Targeted Risk Analyses |
Controls with risk-defined frequencies (such as Req 11.6.1 check intervals or Req 8.6.3 service-account rotation) require an annually reviewed Targeted Risk Analysis. | Write asset-specific risk analyses documenting threat likelihood, technical safeguards, and justified check intervals for executive sign-off. |
Compliance guidance looks different when it comes from someone who has sat on the operator side of the audit table. briskData CEO David Burroughs previously served as CIO and CISO of a Level 1 PCI DSS payment gateway, running production payment infrastructure, cryptographic key management, network segmentation, and QSA assessments firsthand.
Today our team leads PCI DSS Level 1 ROC and SOC 2 Type II programs for payment processors, SaaS platforms, and merchants across the United States. The people organizing your audit evidence are the same engineers who tighten the VPC rules, logging pipelines, and checkout headers. Read about our Level 1 payments compliance work.
Program leadership through the signed Report on Compliance
Hands-on implementation of post-March 2025 checkout and scope controls
Engineers who remediate VPCs, checkout scripts, logging, and IAM directly
Year-round evidence upkeep for steady annual re-attestations
Confirm the validation path, trace payment flows and TPSP boundaries, and tighten checkout or network segmentation to shrink the CDE.
Inspect live controls, policies, TRAs, ASV and penetration test status (Req 11.4), and operating records against v4.0.1 procedures.
Configure segmentation, logging, MFA, checkout protections, and Req 12.6 staff training while accumulating clean operating history.
Manage the evidence request list, join technical walkthroughs with your independent QSA, and close open items through final sign-off.
That depends on your annual transaction volume, how cardholder data moves through your checkout or APIs, acquiring-bank rules, and whether you validate as a merchant or a third-party service provider. Run your payment flow through our PCI SAQ Selector first, and we will confirm the exact path with your acquirer or QSA.
They still require attention. Even under PCI DSS v4.0.1 updates for SAQ A and SAQ A-EP, merchants embedding payment iframes or redirects have obligations around protecting the parent checkout page from unauthorized script tampering and confirming eligibility with their acquirer. We inspect your live checkout DOM and HTTP headers before you attest.
No. Under PCI SSC independence rules, the team building and operating your controls should not also sign the formal assessment. We handle architecture changes, technical remediation, and the evidence package while working directly alongside your independent QSA firm.
Starting four to six months ahead of assessment fieldwork gives you breathing room. Quarterly ASV scans, penetration test remediation, periodic access reviews, and checkout script monitoring all require dated operating history that cannot be backfilled the week before an audit.
Yes. Roughly two-thirds of the operational records, including change tickets, access reviews, MFA enforcement, vulnerability remediation, incident response drills, vendor reviews, and staff training, serve both PCI DSS v4.0.1 and SOC 2 Type II when collected on one calendar.
Most engagements start with a fixed-fee PCI DSS Scoping and Gap Assessment quoted after a short call. Hands-on remediation and year-round compliance upkeep are billed at our published $150/hour engineering rate or under a monthly retainer. See our pricing page.
Tell us how your business takes or routes payments, whether you expect an SAQ or a Level 1 ROC, and when your acquirer or customer needs attestation.
Best fit: upcoming Level 1/2 ROC or SAQ deadlines, SaaS service-provider attestations, or closing findings from a gap report.
A 30-minute conversation with an engineer about what you need and next steps.
Times shown in Eastern Time
Available dates will appear here.
No time that works?