Skip to content
Compliance for Technical Staff

Compliance for Technical Staff

How compliance actually works, and what it asks of the people who build software. Practical decisions, real consequences, and how six common frameworks connect to the code you write.

About 40 minutes · 9 lessons

Start the course

No account needed

Built by the team at

One model for every control

01 · policy · in practice

Access to production must match job responsibilities.

Evidence it leaves

The approved policy, with its owner and review date.

record access-control-policy.md · v4 · owner: security · next review 2027-01

Lessons

  1. 01What compliance actually isObligations, controls, and the four layers that turn a rule into something you can show working.5 min
  2. 02Know your scopeScope follows the data. Find every place it goes before deciding which rules apply.4 min
  3. 03Give access deliberatelyLeast privilege for people and pipelines, access that changes when roles change, and secrets handled as secrets.4 min
  4. 04Make changes you can explainReview, test, approve, and record, so every production change can be explained later.4 min
  5. 05Handle data through its lifecycleCollect less, use it only for its purpose, keep it only as long as needed, and make deletion reach every copy.4 min
  6. 06Prove it and keep it workingEvidence that holds up, owners who keep controls running, and remediation that actually closes.4 min
  7. 07Respond when something goes wrongEscalate early, contain carefully, preserve evidence, and learn from it.3 min
  8. 08Treat AI as a managed systemAn AI feature is a system with a life cycle. Govern it like one.4 min
  9. 09One practice, six frameworksSOC 2, ISO 27001, ISO 42001, HIPAA, GDPR, and CMMC: what they are, and what they ask of developers.6 min
  10. Wrap-upYour review topics, next steps, and the three-page cheat sheet.2 min