DevOps

What SOC 2 actually wants from your infrastructure

SOC 2 infrastructure requirements explained: what auditors ask your infrastructure to prove, and which work is necessary versus over-building for the audit.

What SOC 2 actually wants from your infrastructure

A customer may require a SOC 2 report before signing a deal. Before agreeing to a delivery date, involve the people who operate the systems and will need to provide evidence.

Define the controls and evidence you need before buying a compliance platform or scanning tool. SOC 2 does not prescribe an instance type or a list of cloud services for your application.


The thing to understand first

Describe your controls and show how your team operates them.

The auditor checks the controls and supporting evidence. Document the practices your team performs and retain records across the assessment period.

What we'd do

Choose tools against the controls you need to operate and evidence. Buying a platform does not establish that your team performs those controls.

Keep dated evidence of access reviews, restores and change approvals. You need to show that your team performed the control during the period under review.


Prepare evidence for the infrastructure controls

Prepare to explain the following practices:

Who can reach production, and how do you know?

Access has to be granted deliberately, reviewed periodically, and — the part that catches people — removed when someone leaves. Offboarding evidence is where a lot of findings land.

How does a change get to production?

Reviewed, approved, traceable. If deploys happen from a laptop with credentials nobody can enumerate, there's no story to tell here.

Would you notice something going wrong?

Monitoring, alerting, and log retention — plus evidence that alerts reach a human who acts. Silent monitoring is a finding, not a control.

Can you recover, and have you checked?

Backups are the easy half. Restore testing is the half that's usually theoretical, and it's the half that gets asked about.

Are your systems consistently configured?

Not perfectly hardened — consistently. An auditor wants to know that what's true of one server is true of the fleet, and that you can show it.

Do you know what you have?

An asset inventory that's current. Hard to fake, hard to maintain by hand, and quietly the thing that makes every other control provable.

Explain how your team operates the controls on the stack you use.


Why it's hard anyway

Check that engineers follow the same procedures across the fleet and retain evidence. A practice performed on a few remembered servers will not establish what happened on the others.

Common trap

A Type II report covers an observation window, commonly 3–12 months. Agree that period with the auditor before promising a report date to a customer. You need evidence of operating the controls throughout the agreed window.


The order that works

Scope it down, aggressively

SOC 2 covers the systems in scope. A smaller, clearly bounded production environment is dramatically cheaper to certify than a sprawling one. Reducing scope is the highest-leverage hour you'll spend on this.

Make the fleet consistent before you make it compliant

Configuration automation first. If every server is built the same way from the same definition, a control demonstrated on one is demonstrated on all of them. Without this, every control is an audit of individual servers, forever.

Fix access and offboarding

Cheap, unglamorous, and the source of a disproportionate share of findings. Who has production access, why, and what happened when the last person left?

Put change control in the pipeline, not in a document

If the pipeline enforces review and records what shipped, your change-management evidence generates itself. If it's a policy people follow by hand, you'll be assembling evidence manually forever.

Test a restore, and keep the record

Not the backup — the restore. Do it once properly and you've answered a question that makes most teams uncomfortable.

Write down what you actually do

Last, not first. Policies written before the practice exists describe a fiction, and the gap between them is exactly what the auditor is employed to find.

The sequence matters. Steps 2 and 4 mean the evidence is a by-product of running the system properly. Skip them and every subsequent audit period is a manual evidence-gathering project.


What this looked like on a 70-server fleet

We implemented infrastructure supporting SOC 2 for a global cybersecurity enterprise with more than 70 servers across the UK, US and Australia.

The core of the work was baseline automation with Chef and Ubuntu Pro, producing CIS-compliant environments from a definition rather than from a runbook, plus a CI pipeline that streamlined releases for the engineering team.

The work also improved how the team ran the environment:

We used the same configuration and release procedures for daily operations and audit evidence. SOC 2 gave the business a reason to fund that work.

During the same review, we found that 20% of resource requirements were unnecessary and removed with no impact to uptime or SLAs. A consistent inventory helped us assess the resources and retain evidence for the controls.


What's real and what's panic

Real: configuration automation, access review and offboarding, change control in the pipeline, restore testing, an accurate inventory, alerting that reaches a human.

Panic: buying a compliance platform before you have controls for it to evidence; hardening beyond CIS baseline because it feels safer; re-architecting for the audit; a policy library that describes a company you aren't yet.

Establish the controls before choosing a platform to collect their evidence.


Frequently asked questions

SOC 2 does not prescribe a particular stack or provider. The auditor assesses controls against applicable trust services criteria. Prepare evidence for access control, change management, monitoring, backup and restore, configuration and inventory.

Allow for remediation and an agreed observation window. A Type II report commonly covers 3–12 months; confirm the scope and period with the auditor before committing to a customer deadline.

Missing evidence can prevent a team from demonstrating that it performed access reviews, restores or change approvals on a specific date. Keep the records as part of the operating procedure.

Eventually, and not first. These tools collect evidence for controls you already run; they can't create the controls. Buying one before the controls exist gives you a dashboard of things you aren't doing.

The work may also identify unnecessary resources. On a 70+ server fleet we supported, the review cut resource requirements 20% with no impact to uptime or SLAs.

ISO 27001 concerns certification of a management system; SOC 2 is an auditor's report on controls. Reuse relevant infrastructure work and evidence, but check the scope of each assessment.

Get SOC 2-ready without gold-plating

Infrastructure that passes the audit because it's well run, not because it was built for one.