PCI DSS Compliance
Go deep on PCI DSS: what the card-brand standard actually requires, how to shrink your cardholder data environment (the biggest cost lever), the 12 requirements, how you validate (SAQ, ASV scans, ROC), running a gap assessment, and staying compliant continuously. The payments deep-dive spoke — take it after the Compliance Frameworks hub. Educational, not legal/QSA advice.
"We use a processor so our CDE is tiny, we've mapped the 12 requirements, and here's our SAQ-ready gap-closed plan"
6 Interactive Sessions
Short, interactive sessions: watch it work, try it, then build it yourself. You can go deeper at any time in the written chapters.
- 1
What PCI DSS is and who sets the rules
PCI DSS is a security standard written by the card brands to protect card data. Your bank makes it part of your contract, and it applies as soon as you store, process or send card data.
- 2
Keep card data in a small corner
PCI DSS covers the systems that handle card data and the systems connected to them, called the cardholder data environment (CDE). The smaller you keep that area, the less work PCI DSS is.
- 3
The 12 requirements in six groups
The 12 requirements of PCI DSS fall into 6 goals, and most of them are security basics you may already run: access control, encryption, logging, patching and a written policy, made specific for card data.
- 4
Prove it with real evidence
Being PCI DSS compliant is something you prove. You use the right method, a questionnaire or an assessor's report, and back it with dated records that show your controls really run.
- 5
Find your gaps before you validate
A gap assessment is an honest self-check against the 12 requirements before you validate. You rate each one in place, partial or missing. Shrink your scope first, because a requirement that no longer applies to a system is a gap you never have to close.
- 6
Stay compliant all year
PCI DSS is a program that runs all year. Scope, controls, scans and validation each come round on a schedule, so the yearly check describes what is already true.
Skills you'll practise
Practice data included
- CDE scope examples (in/out)
- The 12 requirements (6 goals)
- Validation paths (SAQ/ROC/ASV/AOC)
- Gap checklist (12 items)
How this certificate is scored
Your certificate shows how many of your written answers met the rubric below, checked by an AI grader. Anyone who checks your certificate sees it.
- You answer 6 short questions, one for each module, in your own words (at least 40 words each).
- An AI grader checks each answer against what its module asks for: it must answer the question, use the course's practice case specifically, and be correct.
- To pass, at least 5 of the 6 answers must meet that bar. The certificate says the answers were graded by AI.
The rubric
- Module 1, What PCI DSS Actually Is: A correct model: a card-brand standard enforced contractually, not a law or a certificate.
- Module 2, The Cardholder Data Environment & Scope Reduction: A scoped CDE, shrunk with segmentation, tokenization, or a processor.
- Module 3, The 12 Requirements: The 12 requirements mapped to the 6 goals and your systems.
- Module 4, Validation & Evidence: The right validation path (SAQ/ROC) backed by scans, tests, and real artifacts.
- Module 5, The Gap Assessment: A self-assessment rating each requirement and a scope-first remediation roadmap.
- Module 6, Staying Compliant: A continuous PCI program: annual validation, quarterly scans, no scope drift.
What you walk away with
Shareable portfolio
A public URL showing your module timeline, patterns mastered, and completion status.
Everything you build
Download all your work as a ZIP file. It is yours to keep.
Module walkthrough
Each module documented with deliverables and the production pattern you implemented.
Ready to start PCI DSS Compliance?
First course free. $20 per course after that.