Compliance

Phase 1, Phase 2, then keep it running

A fixed-price gap analysis, remediation through to your audit, and upkeep after it. All in a workspace you keep.

All compliance →
Security

Testing, review and leadership

Led by a published security researcher with five CVEs. One standard report, letters for your buyers, and retests of your fixes.

All security →
Who we help

Prove you are secure

To the people you sell to, raise from or answer to.

All industries →
Resources

Learn the space

Original research, free tools, and plain-language guides on security and compliance, from a published security researcher.

Read the blog →
Security & Compliance Glossary

PCI DSS

PCI DSS, the Payment Card Industry Data Security Standard, is a set of security requirements for any organization that stores, processes, or transmits payment card data. It is mandated by the major card brands and enforced through contracts with payment processors and banks. Compliance is validated annually, with requirements scaled to transaction volume.

In practice

The single most effective PCI move is to shrink scope: by routing card data through a compliant payment processor and never touching it directly, most companies sharply reduce what they have to secure and document.

Validation ranges from a Self-Assessment Questionnaire for smaller merchants to an audit by a Qualified Security Assessor for the largest. PCI DSS explicitly requires both regular vulnerability scanning and annual penetration testing.

// how traztech helps

traztech delivers PCI DSS scoping and readiness for startups and growth-stage companies, led by a published security researcher.

Book a call

For a broader look at getting audit-ready, see our SOC 2 readiness work, or talk to a fractional CISO about building a program around it.

Free PDFs, no card

Get the checklists that go with this

SOC 2 readiness, ISO 27001 gaps, incident response and vendor security, as PDFs you can print or forward. Free, no card.

From Jacob Masse, principal of traztech: the files by email, then a few short notes over the next month. No spam, unsubscribe in one click.

Where it comes up

PCI DSS work almost always starts in the wrong place. Teams begin with controls before establishing their SAQ type, when the SAQ type determines how much of the standard applies at all.

Scope reduction saves more than any control implementation. Moving card data out of your environment, through a hosted page or an iframe, changes which questions you have to answer rather than how well you answer them.

PCI DSS: common questions

Does using Stripe mean we are PCI compliant?

It reduces your scope substantially but does not remove the obligation. You still complete and attest to a Self-Assessment Questionnaire, and if anything on your side ever touches a card number the picture changes.

Which version applies now?

PCI DSS v4.0.1, and several requirements that were future-dated have since come into force, so an assessment from a couple of years ago will be out of date.