01
A deal is waiting on your SOC 2 report.
An enterprise customer sent a security questionnaire, and “SOC 2 in progress” isn’t closing it.
SOC 2 readiness for SaaS on AWS + GitHub
Your compliance dashboard is red and your engineers are busy shipping product. I find the gaps in your AWS and GitHub setup, fix them as pull requests in your infrastructure, and keep the evidence ready for your auditor.
terraform/cloudtrail.tf
resource "aws_cloudtrail" "main" { name = "org-trail"- is_multi_region_trail = false+ is_multi_region_trail = true+ is_organization_trail = true+ enable_log_file_validation = true+ kms_key_id = aws_kms_key.logs.arn }
01 / The problem
Three places where SOC 2 projects at small SaaS teams tend to stall.
01
An enterprise customer sent a security questionnaire, and “SOC 2 in progress” isn’t closing it.
02
The integrations are connected and the dashboard is full of failing tests. Nobody owns fixing them.
03
The hard part is changing access, logging and deploy pipelines without breaking production.
02 / How it works
Three phases, each with a fixed fee agreed before work starts. Stop after any phase.
01 Find
I review your AWS accounts, GitHub organization and identity setup against the SOC 2 Trust Services Criteria, using read-only access.
02 Fix
I fix the gaps in your infrastructure, as code wherever possible, and set up the policies and processes the audit expects.
03 Prove
A SOC 2 Type 2 report covers an observation window of 3 to 12 months. Controls must keep running and evidence must keep accumulating.
03 / Scope
The controls that compliance platforms flag most and startup teams rarely have time to change.
01
Single sign-on (SSO) and multi-factor authentication (MFA) everywhere, no long-lived access keys, least-privilege roles, and an offboarding checklist that actually removes access.
CC6.1CC6.2CC6.3
02
Organization-wide CloudTrail with log file validation and retention, GuardDuty, and alerts that reach a channel someone watches.
CC7.2CC7.3
03
Amazon Inspector or equivalent scanning, Dependabot updates in GitHub, and a patching timeline you can meet.
CC7.1
04
Branch protection, required pull-request reviews, CI checks before merge, and infrastructure changes through code.
CC8.1
05
Security groups and outbound (egress) limits, encryption at rest for S3, RDS and EBS, and TLS in transit.
CC6.1CC6.6CC6.7
06
Automated backups and a restore test, written up as evidence.
A1.2A1.3if Availability is in scope
04 / Principles
Rules I keep on every engagement.
A SOC 2 report must come from an independent, licensed CPA (certified public accountant) firm, and whoever implements your controls can’t audit them. I prepare you; your auditor tests and attests.
A control isn’t done until it runs in your environment and produces evidence your auditor can test. No screenshots staged for audit week.
Changes go through your pull-request review. Any console access is scoped to the engagement and removed when we finish.
05 / About
I’m a cloud infrastructure and security engineer. I run the SOC 2 and HIPAA (Health Insurance Portability and Accountability Act) program at a healthcare-adjacent AI SaaS company. I took it through a SOC 2 Type 1 audit with a US CPA firm and now run its Type 2 evidence cycle. I wrote the policies, built the security awareness training and fixed the infrastructure controls myself.
Before that I spent two and a half years as a cloud engineer at a cloud consultancy, building Terraform modules, Kubernetes platforms and CI/CD (continuous integration and delivery) pipelines.
I take a small number of clients at a time, so you work directly with the engineer doing the work. No account managers, no handoffs.
06 / FAQ
No. Only a licensed CPA firm can issue a SOC 2 report, and auditor independence rules mean the person who implements your controls can’t audit them. I get you ready and support you during the audit.
No. If you already have one, I work inside it and fix what its tests flag. If you don’t, we can run SOC 2 from a shared evidence folder and your own repositories, and decide on a platform later.
For the health check, read-only: an AWS role with the SecurityAudit and ViewOnlyAccess managed policies, plus read access to your GitHub organization. For fixes, I open pull requests your engineers review. Anything that needs console access uses a scoped role that is removed when we finish.
AWS and GitHub are my core. I take Google Cloud and Azure projects case by case, so tell me what you run.
My core is SOC 2. Most of the technical fixes also map to ISO 27001 Annex A controls, so the work still counts if you add ISO 27001 later.
Ongoing Type 2 support starts at USD 1,200 a month. The health check and remediation are fixed fees, quoted after a free call and agreed in writing before work starts, so you know the full cost before you commit.
Get started
Book a free 30-minute call. Tell me what your customers are asking for and what you run. I’ll tell you honestly whether you need me.
Email to book a callor write to hello@complipass.org