SOC 2 Compliant Terraform Modules
Enforced Before terraform apply

Your SOC 2 audit needs encryption, logging, access controls, and versioning on every AWS resource. These modules enforce all of it before terraform apply.

If you sell software or cloud services to other businesses, your customers will ask for a SOC 2 report. Procurement teams at enterprise buyers treat it as a gate — no report, no signed contract.

130

Controls

13

Clauses

34

AWS Modules

No credit card or AWS account needed to start.

From the team behind terraform-aws-modules. 2B+ provisions worldwide.

IAM · S3 · RDS · VPC · CloudTrail · EC2SOC 2 Type II CertifiedAvailable on AWS Marketplace

Three Steps to SOC 2 Compliant Infrastructure

For terraform-aws-modules users, migration is a one-line change. Same workflow, same interface. Bringing your own modules? We can make those compliant too. Join the beta.

1

Change One Line

main.tf
module "s3" {
- source = "registry.terraform.io/..."
+ source = "soc2.compliance.tf/..."
 
  bucket = "awesome-docs"
}
2

Run Terraform Commands

terminal
$ terraform init
Initializing modules...
- module.s3 in soc2.compliance.tf/...
Terraform has been successfully initialized!
$ terraform apply
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
3

Compliance Enforced

CC6.1 · Versioning Enabled
CC6.1 · Default Encryption
CC6.1 · Public Access Blocked
CC6.1 · Object Lock Enabled
CC6.6 · SSL Requests Only
CC7.2 · Logging Enabled
CC7.2 · Event Notifications
CC7.2 · Lifecycle Policy

Every compliance requirement you define is enforced automatically. Nothing to scan, nothing to remediate.

Controls Enforced for SOC 2

130 controls across 13 clauses and AWS services

Enforced (4)Detected (1)
·

Additional Controls

125 additional controls enforced for SOC 2

Enforced (59)Detected (66)

SOC 2 Scope: What We Handle vs. What You Own

compliance.tf handles the infrastructure configuration layer for SOC 2. Here is what it covers and what stays with your team.

compliance.tf Enforces for SOC 2

  • Module-level infrastructure controls (encryption, logging, access, versioning)
  • Trust Services Criteria mapping (CC6.1, CC6.6, CC7.2, and more)
  • Deployment-time evidence generation via AWS-native tools
  • Upstream module updates (terraform-aws-modules kept in sync)
  • Exception management with audit trail
  • Control documentation and compliance mapping matrices

Your Team Still Handles for SOC 2

  • Organizational policies and procedures
  • Employee background checks and security training
  • Change management procedures and approval workflows
  • Vendor management and third-party risk assessments
  • Incident response and communication plans
  • Business continuity and disaster recovery testing
  • Resources outside compliance.tf module coverage

Infrastructure controls are typically 30-40% of SOC 2 audit findings. compliance.tf handles that portion so your team can focus on organizational controls.

SOC 2 Audit Evidence, Generated Automatically

Your auditor does not need to trust compliance.tf. Evidence comes from AWS-native tools they already accept.

Evidence your auditor already trusts

Every compliance.tf module enforces controls at deploy time. When AWS Config, Security Hub, or Audit Manager evaluates your resources, they report clean findings because the controls are built into the modules, not bolted on after the fact.

  • AWS Config rules validate resource configuration continuously
  • Security Hub aggregates findings across accounts and regions
  • Audit Manager generates assessment reports mapped to SOC 2
  • Downloadable control mapping matrices for your auditor
evidence.json
{
  "framework": "SOC 2",
  "clause": "CC6.1",
  "control": "s3_bucket_default_encryption_enabled",
  "status": "COMPLIANT",
  "source": "AWS Config",
  "resource": "arn:aws:s3:::awesome-docs",
  "evaluated": "2026-03-04T10:30:00Z"
}

Prevention vs. Detection for SOC 2

compliance.tf prevents non-compliant deployments. Scanning tools detect them after the fact. Most mature programs use both.

DimensionIaC Scanning
Checkov / Trivy / Prowler
compliance.tf
Prevents non-compliant configs before terraform applyNo (post-plan scan)Yes
Maps controls to framework clause IDsPartialYes
Produces auditor-accepted evidence (AWS-native)Scan reports onlyYes
Exception management with audit trailSuppression rulesYes
Same interface as terraform-aws-modulesN/AYes
Keeps pace with upstream module updatesN/AYes
Catches runtime drift / console changesYesNo
Covers non-Terraform resourcesYesNo
Internal engineering timeMediumLow

We recommend keeping scanning tools active alongside compliance.tf for defense in depth. The scanner validates what compliance.tf already enforces.

SOC 2 Compliance Questions

Which Trust Services Criteria does this cover?

compliance.tf enforces infrastructure controls mapped to CC6 (Logical and Physical Access Controls), CC7 (System Operations), and CC8 (Change Management). These are the criteria tied to AWS resource configuration: encryption at rest and in transit, access blocking, logging, versioning, and lifecycle policies. Criteria like CC1 (Control Environment) and CC2 (Communication) are organizational and remain your team's responsibility.

How is this different from Checkov, Trivy, or Prowler?

Those tools are detective controls. They scan infrastructure after you write it and report findings you fix manually. compliance.tf is a preventive control. The modules themselves cannot produce non-compliant resources. There is nothing to scan, nothing to remediate. Most teams keep their scanners running alongside compliance.tf for defense in depth.

Can I adopt this gradually, or is it all-or-nothing?

Fully incremental. Start with one module in one environment. Your existing modules continue working untouched. If you use Terragrunt or Terramate to orchestrate your runs, nothing changes — you’re only swapping the module source line. There is no global policy agent to deploy, no wrapper binary, no sidecar. Each module source line is independent.

Does compliance.tf replace our GRC platform (Vanta, Drata, Sprinto)?

No. We enforce controls inside Terraform modules. Your GRC platform tracks policies, collects evidence, and manages audit workflows. We feed evidence into your GRC platform, not the other way around.

Will my auditor accept this as evidence?

Your auditor does not need to trust compliance.tf directly. Evidence comes from AWS-native tools they already accept: AWS Config, Security Hub, and Audit Manager. We enforce controls at deploy time so those AWS tools always report clean findings.

What if I want to switch back or compliance.tf shuts down?

Our modules are standard Terraform. They work with Terraform, OpenTofu, Terragrunt, Terramate, and any tool that speaks the Terraform module protocol. Every module is a drop-in replacement for its upstream terraform-aws-modules equivalent with the same variables and outputs. Change your module source line back, run terraform init. Your infrastructure does not change. No lock-in, no proprietary state.

Start Deploying SOC 2-Compliant Infrastructure

$100/year for all 34 modules, all frameworks. 30-day free trial.

No credit card required. Switch back at any time.

Stay Informed About New Features

Join the mailing list for releases, new modules, and roadmap updates. No spam. Unsubscribe anytime.

Not convinced yet or dying for a feature we don't have? Send us an email — we really want to hear your feedback!