Do compliance the hard way
summary
Practical steps for building compliance programs rather than theory: a team forks and fixes the open source Comply renderer, uses markdown + pandoc + minimal LaTeX to output HTML/PDF policies, and ties documents to GitHub issues for evidence and remediation. The workshop shows a live demo, shares a repo of SOC2 templates and plans to add PCI, and argues an 80/20 policy split — 80% reusable templates, 20% business-specific controls — plus a Slack channel for ongoing contributions.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 3:46Compliance acronyms
- 5:50Compliance in startup mode
- 7:00Principles of compliance
- 8:23Alignment
- 10:14Stakeholder support
- 12:03Compliance outsourcing
- 14:16Policies and procedures
- 15:50Compliance theater
- 16:32Efficient policies
- 17:21Passwords
- 18:54Max
- 25:51Install comply
- 27:37Fork comply
- 29:56Markdown
- 31:46HTML page
- 33:55Policy templates
- 36:27Evidence gathering
- 39:06Automation
- 43:41Policies
- 45:56New Policy
- 48:30Information Security Policy
- 50:00Wrapping up
- 51:26Conclusion
- 52:56QA
related talks
31mOperationalizing Open Source Projects: When the Rubber Meets the Road
20mChanging human behavior for better code
26m(Professionally) Coding with Others
50mOpen Source Survival Guide
20mOpen up to Open Source
16mFree Your Mind, and Your Docs Will Follow
40mFrom resistance to adoption: navigating the challenges of docs-like-code
43mPutting the “tech” in technical writer