Compliance Frameworks Decoded
Cut through the alphabet soup. Learn which frameworks actually apply to you (HIPAA, PCI DSS, GDPR, SOC 2, ISO 27001, NIST/CMMC), the ~65% of controls they all share, how to satisfy many at once with one control set, and how to build a compliance roadmap. The hub course — take the deep-dive spoke for each framework you pick. For founders, managers, compliance leads, and engineers.
"We need SOC 2 and GDPR, most of the work is shared, and here's our one-control-set roadmap to satisfy both"
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
Why companies have to prove they are secure
Compliance means writing down how you keep data safe so that others can check it. Two groups push for it: regulators, who can fine you, and customers, who will not buy without proof.
- 2
Find the frameworks that apply to you
You do not choose your frameworks from a menu. What data you handle and who you sell to decide them, and most companies end up with two or three.
- 3
The controls every framework asks for
Almost every framework asks for the same seven families of controls: access control, encryption, logging, incident response, vendor risk, staff training, and risk and governance. They just give them different names and numbers.
- 4
Do the work once and use it for many audits
Because the frameworks share so many controls, you do not do the work again for each one. You keep one list of your own controls, map each framework onto it, and collect the proof once.
- 5
Draw the line: what is in scope, and what each framework adds
A framework applies only to the part of your business that touches the regulated data. Draw that line on purpose, build the shared controls once, and add only the extras each framework needs.
- 6
Your compliance roadmap
Compliance is one program you can plan: pick what applies, build the shared controls once, map and add the extras, collect proof once, and keep it running. Then go deeper on each framework in its own course.
Skills you'll practise
Practice data included
- Framework picker (applies-when)
- Shared control families
- Cross-framework crosswalk example
- Overlays by framework
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, Why Compliance Exists: A clear-eyed view: trust written down, driven by regulators and customers.
- Module 2, Which Frameworks Apply to You: A shortlist of the frameworks your business actually triggers.
- Module 3, The Shared DNA: The ~65% of controls that every framework repeats under different names.
- Module 4, Do It Once, Satisfy Many: The crosswalk: one control set mapped across frameworks, evidence collected once.
- Module 5, Scope & the Overlays: A scoped boundary plus the framework-specific overlays you'll actually need.
- Module 6, Your Compliance Roadmap: A sequenced plan — pick, build the core, add overlays, evidence once, go continuous.
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 Compliance Frameworks Decoded?
First course free. $20 per course after that.