Skip to content
Wasim Rashid

PCI DSS from the engineer's side of the table

What quarterly reviews look like when you are the one walking the assessor through the system.

WRBy Wasim Rashid··4 min read

01Compliance arrives as a list. Engineering needs tickets.

For a live card gateway, PCI DSS is not an annual event. I owned compliance for a gateway handling thousands of transactions a day and was the focal point for our QSA in quarterly one-to-one reviews, alongside quarterly ASV scans and the remediation that followed.

The job in the middle is translation. A requirement is written for assessors. An engineer needs to know which service, which change and how it will be evidenced.

02Scope is the biggest lever

The fewer systems that touch card data, the smaller the problem. A hosted payment page keeps card entry out of the merchant's environment. Tokenisation keeps card numbers out of most of your own. Sensitive authentication data is never stored after authorisation, in any table, log or debug trace.

Logs deserve their own review. Card numbers leak into logs through error messages and request dumps far more often than through the database.

03What an assessor actually asks

Show me how card data flows. Show me who can reach it. Show me how a change gets to production and who approved it. Show me the scan results and what happened to each finding.

Walkthroughs go well when the answers already exist as artefacts: a current data-flow diagram, access lists, change records, and a findings log where every item has an owner and a closing date.

04Build it into the release process

Controls that depend on someone remembering will fail. Code review, branching rules and a final check of each implementation against its security requirement before QA make compliance a property of how the team ships.

I am not an auditor and do not replace one. What I bring is the engineering half: making sure the assessor's questions have answers in the system and not only in a document.

Next article

Acceptance rate has three definitions. Most reports use one.

Open to consulting engagements

Have a payment problem that needs tracing?

Tell me which providers are involved and what is going wrong, or what needs to go live. I will tell you plainly whether I can help.

Tell me
Which providers and markets are involved
Show me
What is failing, or what needs to go live
You get
A plain answer on whether I can help