Skip to content

Payment Card Industry Data Security Standard

PCI DSS
compliance.

PCI DSS applies to anyone that stores, processes, or transmits cardholder data. Version 4.0.1 is now fully in force with new requirements for authentication, scripts, and targeted risk analysis. We scope your cardholder data environment tightly and get you to a clean assessment.

Issued by

PCI Security Standards Council

Type

Industry standard

Jurisdiction

Global, contractual

Structure

12 requirements

Understanding PCI DSS

Scope is
everything.

PCI DSS is enforced through your card brand and acquirer agreements rather than by a government. The level of validation depends on transaction volume: larger merchants and service providers need a Qualified Security Assessor to produce a Report on Compliance; smaller ones complete a Self Assessment Questionnaire.

Version 4.0 became mandatory in March 2024 and was replaced by 4.0.1 at the end of 2024, with future dated requirements effective March 2025. Key changes include stronger MFA, targeted risk analyses for control frequency, payment page script management, and a customized approach option. The single biggest lever on cost and risk is scoping: reducing where cardholder data lives.

What PCI DSS asks for

Twelve requirements.
Six goals.

The standard groups its twelve requirements under six control objectives, from network security to policy.

What it requires

Requirements 1 and 2: network security controls and secure configuration of all system components.

How ForgePath helps

We assess segmentation to shrink the cardholder data environment and harden configurations against the standard.

What it requires

Requirements 3 and 4: protect stored account data and encrypt cardholder data in transit over open networks.

How ForgePath helps

We inventory where cardholder data actually lives, eliminate it where possible, and validate encryption and key management.

What it requires

Requirements 5 and 6: protect against malware and develop and maintain secure systems and software, including payment page scripts.

How ForgePath helps

We deliver vulnerability management, application security testing, and the script inventory 4.0 requires.

What it requires

Requirements 7, 8, and 9: restrict access by need to know, identify and authenticate users with MFA, and restrict physical access.

How ForgePath helps

We assess access and authentication against the strengthened 4.0 MFA requirements and close the gaps.

What it requires

Requirements 10, 11, and 12: log and monitor access, test security regularly including penetration testing and segmentation testing, and maintain an information security policy.

How ForgePath helps

We deliver the annual penetration test and segmentation validation the standard requires, and build the policy and targeted risk analyses.

Trusted by industry leaders.

Client case studies

Real engagements.
Documented outcomes.

YHB | CPAs & Consultants testimonial

In their words

"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."

Cyrus Kapadia
Chief Technology & Information Officer, YHB | CPAs & Consultants

PCI DSS explained

Frequently asked
questions.

Straight answers from the practitioners who do the work. If yours is not here, ask us directly.

It depends on your merchant or service provider level, set by transaction volume and your acquirer. We help you determine the level and either prepare you for a QSA assessment or complete the SAQ correctly.

Segmentation, tokenization, and using a validated payment processor so card data never touches your systems. Scope reduction is usually the highest return work in a PCI program.

Stronger MFA, payment page script management, targeted risk analyses to set control frequencies, and a customized approach for meeting requirements differently. The future dated requirements became mandatory in March 2025.

No. Independence matters, so the certificate, report, or assessment comes from an accredited third party. We prepare you, help select the assessor, sit beside you during the audit, and close any findings.

Yes, and that is how we build. One control set mapped to every framework you answer to, with evidence collected once and reused. Separate programs per framework is the expensive way.

Yes. Under Lead, a senior practitioner can serve as your named security owner or fractional CISO, keeping the program current between assessments.

Ready?

Bring us
the problem.

One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.