SOC 2 readiness for SaaS on AWS + GitHub

SOC 2, fixed as code.

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.

  • 3phases, fixed fee each
  • 0standing admin access
  • 1:1with the engineer doing the work
PR / 01 Enable tamper-evident audit logging

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 }
CC7.2 · Monitoring Failing → Passing

01 / The problem

Sound familiar?

Three places where SOC 2 projects at small SaaS teams tend to stall.

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.

02

You bought a compliance platform. Now what?

The integrations are connected and the dashboard is full of failing tests. Nobody owns fixing them.

03

Policy templates are the easy part.

The hard part is changing access, logging and deploy pipelines without breaking production.

02 / How it works

Find. Fix. Prove.

Three phases, each with a fixed fee agreed before work starts. Stop after any phase.

  1. 01 Find

    Technical health check

    I review your AWS accounts, GitHub organization and identity setup against the SOC 2 Trust Services Criteria, using read-only access.

    • A gap list ranked by audit risk and effort
    • Each gap mapped to a SOC 2 criterion, with the fix I recommend
    • A realistic plan and timeline to your Type 1 audit

    About 1 week · read-only access

  2. 02 Fix

    Hands-on remediation

    I fix the gaps in your infrastructure, as code wherever possible, and set up the policies and processes the audit expects.

    • Pull requests in your repositories (Terraform or CloudFormation), reviewed and merged by your team
    • Runbooks for anything that can’t be code
    • A policy set tailored from templates I’ve taken through a real audit
    • Coordination with your auditor through the Type 1 report

    Typically 3–8 weeks · quoted from the health check

  3. 03 Prove

    Audit and observation support

    A SOC 2 Type 2 report covers an observation window of 3 to 12 months. Controls must keep running and evidence must keep accumulating.

    • A monthly evidence calendar, so nothing is gathered the week before fieldwork
    • Quarterly access reviews and vulnerability follow-ups
    • Answers to auditor requests: samples, screenshots, population lists

    From USD 1,200/month · through the Type 2 report

03 / Scope

What I fix.

The controls that compliance platforms flag most and startup teams rarely have time to change.

01

Identity and access

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

Logging and monitoring

Organization-wide CloudTrail with log file validation and retention, GuardDuty, and alerts that reach a channel someone watches.

CC7.2CC7.3

03

Vulnerability management

Amazon Inspector or equivalent scanning, Dependabot updates in GitHub, and a patching timeline you can meet.

CC7.1

04

Change management

Branch protection, required pull-request reviews, CI checks before merge, and infrastructure changes through code.

CC8.1

05

Network and encryption

Security groups and outbound (egress) limits, encryption at rest for S3, RDS and EBS, and TLS in transit.

CC6.1CC6.6CC6.7

06

Backup and recovery

Automated backups and a restore test, written up as evidence.

A1.2A1.3if Availability is in scope

04 / Principles

What I won’t do.

Rules I keep on every engagement.

Audit you.

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.

Stage evidence.

A control isn’t done until it runs in your environment and produces evidence your auditor can test. No screenshots staged for audit week.

Keep standing admin access.

Changes go through your pull-request review. Any console access is scoped to the engagement and removed when we finish.

05 / About

Hi, I’m Howard.

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.

Howard LeeCloud security engineer
  • CertificationAWS Certified Solutions Architect – Associate
  • Time zoneTaiwan, UTC+8. Two to three hours behind Sydney, so most of the Australian business day overlaps.
  • LanguagesEnglish and Mandarin (提供中文服務)

06 / FAQ

Questions.

Do you issue the SOC 2 report?

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.

Do we need Vanta, Drata or another compliance platform?

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.

What access do you need?

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.

Do you work with Google Cloud or Azure?

AWS and GitHub are my core. I take Google Cloud and Azure projects case by case, so tell me what you run.

What about ISO 27001?

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.

How does pricing work?

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

Find out where you stand.

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 call

or write to hello@complipass.org