Most engineering teams approach SOC 2 as a documentation exercise. They write policies, assign owners, and hope their existing systems produce enough evidence to satisfy an auditor. A useful engineering approach is to produce evidence continuously rather than reconstruct it retrospectively. For an example, see our continuous controls monitoring case study. An independent auditor assesses the applicable controls, period and evidence; no engineering checklist guarantees an audit result.

This guide covers what auditors actually request from your CI/CD pipeline, access management, and logging infrastructure — and how to ensure those systems produce clean, complete evidence by default.

The key takeaway

SOC 2 Type II auditors sample dates across the audit period and ask for evidence that changes were reviewed and approved, access was appropriate, monitoring was active and infrastructure matched your baseline. Design CI/CD, access management and logging to produce that evidence continuously, so collection becomes a reporting task rather than a project.

What Auditors Are Testing

A SOC 2 Type II audit tests whether your controls operated consistently across the audit period. For engineering systems, this means the auditor will sample specific dates and request evidence that proves:

  • Only authorised individuals could deploy to production
  • Changes were reviewed and approved before deployment
  • Access to production systems and sensitive data was appropriate at all times
  • Anomalous access or changes triggered detection and response
  • Infrastructure was configured to your stated security baseline throughout the period

CI/CD Pipeline Evidence Requirements

Your deployment pipeline is one of the most scrutinised areas in a security audit. Auditors look for:

  • Approval records: Who approved every production deployment and when. Pull request merge records with required reviewer counts satisfy this if your branch protection rules are properly configured.
  • Separation of duties: Evidence that the engineer who wrote the code did not also approve their own deployment to production. This requires enforcing required reviewers in GitHub/GitLab branch protection rules — and the audit log proving those rules were active throughout the period.
  • Automated test gates: Evidence that security scanning, unit tests, and dependency checks ran before every production deployment. CI run logs with timestamps and pass/fail status serve as evidence.
  • Change records: A linkable trail from ticket → pull request → CI run → deployment. Even a lightweight linear flow (Jira → GitHub → GitHub Actions → deployment log) satisfies this if the IDs are consistently referenced.
  • Rollback capability: Documentation or demonstration that rollback procedures exist and have been tested.

Action: Export your branch protection configuration and store it alongside audit evidence. If you change it, capture before/after snapshots with timestamps. For the release side of this, see how to set up a CI/CD pipeline.

Access Management Evidence

Access control evidence failures are the most common reason SOC 2 audits require remediation. Auditors will test:

  • Provisioning and deprovisioning: Sampled joiners and leavers over the audit period. Can you show that access was granted based on an approved request and revoked within your stated SLA after offboarding?
  • Access reviews: Quarterly or semi-annual records showing that someone with authority reviewed who had access to production systems and attested that access was appropriate
  • Privileged access: Evidence that elevated permissions (production database access, cloud console admin, break-glass accounts) were used only when justified and logged with reason codes
  • MFA enforcement: Configuration evidence and authentication logs showing MFA was required — not just available — for production system access throughout the period
  • Terminated user access: Sampled departures showing access removed within 24-48 hours across your identity provider, cloud consoles, and SaaS tools

Action: Run quarterly access reviews as a formal, documented process — not an informal team check. Export the review record, who conducted it, what was reviewed, and any remediation actions taken.

Logging and Monitoring Evidence

Auditors verify that you can detect security events — and that your monitoring was active throughout the period, not just at audit time.

  • Log retention: Evidence that audit logs were retained for your stated period (commonly 12 months minimum). Retention and immutability settings must match the agreed control and be tested; selecting a storage feature alone does not establish sufficient evidence.
  • Alert configuration records: Snapshots or version-controlled definitions of your alert rules — showing they were in place throughout the audit period, not only configured after the audit started
  • Incident and alert response records: A log of every security alert that fired, who triaged it, what the determination was, and whether escalation occurred. Even a simple spreadsheet or Jira project satisfies this if consistently maintained
  • Vulnerability management: Evidence that dependency and container scanning ran on a defined schedule, findings were tracked, and high/critical issues were remediated within your stated SLA

Infrastructure Configuration Evidence

Configuration drift between audit samples is a common failure mode. Use infrastructure-as-code to make your baseline auditable by default:

  • Store all infrastructure configuration in version-controlled IaC (Terraform, CDK, Pulumi). The git history is your configuration change log. For release guardrails on top of this, see GitOps with Terraform.
  • Run continuous compliance checks (AWS Config rules, GCP Security Command Centre, Checkov in CI) and export compliance posture snapshots monthly
  • Document your security baseline as code — encryption requirements, public access blocks, logging enablement — and alert on drift from that baseline
  • Enable cloud provider audit logs (CloudTrail, Cloud Audit Logs) across all accounts and all regions from day one of your audit period

How do you make SOC 2 evidence collection continuous?

Teams that pass Type II audits smoothly have one thing in common: they treat evidence as a continuous output, not a quarterly scramble. Auditable ESG reporting pipelines apply the same principle to sustainability data. Practically, this means:

  1. Every access review produces a timestamped record immediately — not reconstructed later
  2. Every incident or alert response is logged in a system auditors can query, even if it is a simple project management tool
  3. Deployment pipeline logs are retained for the full audit period with immutability controls
  4. Infrastructure configuration is version-controlled, so the history is already the audit trail

SOC 2 readiness is largely an engineering problem. If your CI/CD, access management, and logging systems are well-designed, evidence collection becomes a reporting task rather than a project. We help compliance-focused engineering teams build this infrastructure as part of our Cloud and DevOps service. If you are preparing for a first audit, talk to our team — a short architecture review often surfaces the largest gaps early.

Questions and answers

What is the difference between SOC 2 Type I and Type II?

Type I assesses whether controls are suitably designed at a single point in time. Type II assesses whether those controls operated effectively over a period — typically 6 to 12 months. Type II is what enterprise buyers, investors, and regulated customers ask for, because it proves consistency, not just design.

How long does it take to prepare for a SOC 2 Type II audit?

Most engineering teams need 3-6 months to build and operate the required controls before an audit period can begin. The audit period itself is typically 6-12 months. Teams with good CI/CD hygiene, centralised logging, and access review processes can reduce prep time significantly.

Which SOC 2 trust service criteria apply to most SaaS companies?

Security (CC) criteria apply to all SOC 2 reports. Availability, Confidentiality, Processing Integrity, and Privacy are optional and selected based on customer commitments. Most SaaS companies include Security and Availability as a baseline, with Confidentiality added if they handle sensitive data.

All insightsDiscuss your project