Engineering for security compliance: How to prepare before the audit
summary
Encore Healthcare describes converting a Drupal-backed product Nexus to audit-ready SOC 2 and HITRUST compliance in about 16 months by integrating evidence into engineering: Terraform/SST IaC, DataDog for non-PHI telemetry and AWS OpenSearch for PHI logs, Monolog for app logging, TailScale for SSH auditing, and a Thorpass consultant for the 54-control readiness then 348 evidence requests. Documentation, automated logs with account/trace context, annual pentests, 6-year retention and time-stamped screenshots prove controls.
AI-written summary · about
chapters (17)
- 0:00Introduction and speaker intro
- 3:58What we're securing at Encore
- 6:26In-scope vs out-of-scope systems
- 8:13Compliance process timeline
- 11:05Document everything principle
- 15:00Policies and procedures setup
- 16:04Logging and log retention
- 21:23User onboarding and offboarding
- 26:18Access control best practices
- 32:39Software development lifecycle
- 39:19Infrastructure as code
- 43:15Backups and disaster recovery
- 47:15Incident response planning
- 48:39Inheriting cloud provider controls
- 49:01Penetration testing
- 50:04Drupal security considerations
- 53:21Closing takeaways and Q&A
