SOC 2 Type II Readiness for a Cloud-Native SaaS

The Problem and Why It Mattered

I led the SOC 2 Type II readiness programme for a cloud-native SaaS — mapping Trust Services Criteria to GCP technical controls, implementing missing controls, and building automated evidence collection for the 12-month observation window. The relevant technical and business risk is the cost of leaving this workflow, control, or product boundary unclear, manual, insecure, or difficult to operate. The case study focuses on the decisions used to make that risk manageable.

Objectives and Success Criteria

• Deliver the capability described in the project objective using a maintainable technical design.
• Make the main workflow, control boundary, and operational responsibilities explicit.
• Produce reviewable implementation evidence without publishing confidential values or customer data.

Requirements and Constraints

The implementation had to create technically useful controls and evidence without representing the product or environment itself as formally certified. Confidential organisational details are generalised.

My Role and Ownership

I owned the technical design and implementation described in this portfolio record, including the technology choices, core system boundaries, and the documentation of the resulting approach. Related organisational decisions, vendor operations, and formal certification decisions remain outside the scope of this technical case study unless stated explicitly.

Solution Overview

The solution is built around Security Command Center, Cloud Audit Logs, Cloud Build. Its implementation is organised as the components below so that the architecture, control points, and operating model can be evaluated separately rather than treated as a list of tools.

Architecture and System Design

The public architecture description follows the path from the initiating user, workload, or operator action through the relevant compliance components. Access boundaries, data or state handling, and operational controls are described at a safe level; secrets, private addresses, and client-sensitive implementation details are intentionally omitted.

Technology Decisions and Trade-Offs

I selected Security Command Center, Cloud Audit Logs, Cloud Build because they support the project objective and make the critical engineering boundaries explicit. The trade-off is operational and platform complexity: the design depends on documented configuration, controlled access, and ongoing review rather than assuming that a managed service or framework removes engineering responsibility.

Implementation Walkthrough

The following implementation notes describe the components that matter most to the project outcome. They are intentionally focused on technical decisions and operating behaviour instead of reproducing entire source files or sensitive configuration.

Implementation: Trust Services Criteria Mapping

Mapped all CC controls across the five SOC 2 Trust Services Categories. Identified 11 partially implemented controls and 6 entirely missing controls across CC6 (Logical Access), CC7 (System Operations), and CC8 (Change Management).

Implementation: CC6 — Logical & Physical Access Controls

CC6.1: IAM least privilege, quarterly access reviews documented. CC6.2: Cloud Identity provisioning/deprovisioning; automated deprovisioning Cloud Function on HR offboarding webhook. CC6.3: MFA enforced at the Organisation level. CC6.6: VPC firewall rules, Cloud Armor policies, private GKE cluster.

Implementation: CC7 — System Operations

CC7.1: Vulnerability management via self-hosted Trivy. CC7.2: Security monitoring via Chronicle SIEM. CC7.3: Incident response procedures tested via tabletop exercise recorded for audit evidence.

Implementation: CC8 — Change Management

All infrastructure changes through PR review with second-reviewer approval. Terraform plan retained as evidence. No direct production access — all changes via CI/CD pipeline.

Implementation: Automated Evidence Collection

Python script runs monthly, pulls evidence artefacts from GCP APIs, archives them to a locked Cloud Storage bucket: IAM policy export, active user accounts with last-login, Cloud Armor policy export, GKE security configuration, Trivy scan summary.

Implementation: Results

17 control gaps identified and remediated in 10 weeks. Automated evidence collection covering 22 of 31 required evidence types. Organisation entered the 12-month SOC 2 observation window on schedule.

Challenges, Failures and Corrections

This portfolio record does not invent deployment failures, client incidents, or corrective actions that are not supported by the published project evidence. Where operational details are confidential or were not captured for public release, the case study documents the design boundary and lesson instead of presenting an unsupported narrative.

Security, Compliance and Risk

The implementation is described with least privilege, traceability, controlled configuration, and evidence boundaries in mind. Where the project supports a regulated environment, these are technical safeguards and audit-readiness contributions, not a claim that an application or product is independently certified.

Testing, Validation and Evidence

The evidence published for this project is the documented implementation, its stated architecture and controls, and the portfolio record. 17 control gaps identified and remediated in 10 weeks. Automated evidence collection covering 22 of 31 required evidence types. Organisation entered the 12-month SOC 2 observation window on schedule. Claims are limited to the implementation details and outcomes documented in this case study.

Results and Evidence

17 control gaps identified and remediated in 10 weeks. Automated evidence collection covering 22 of 31 required evidence types. Organisation entered the 12-month SOC 2 observation window on schedule.

What I Learned

This project reinforced that compliance work is not a technology checklist. The durable value comes from making boundaries, trade-offs, ownership, and evidence clear enough for another engineer or stakeholder to review and operate the system responsibly.

What I Would Improve Next

• Expand automated validation around the most important workflow and control boundaries.
• Add or deepen operational evidence, such as dashboards, test artefacts, or an architecture diagram where it is safe to publish one.
• Review the design against the next expected scale, reliability, and governance requirement before extending the system.

Final Takeaway

This compliance and governance engineering case study addresses a defined technical problem through Security Command Center, Cloud Audit Logs, Cloud Build. It demonstrates my ability to turn requirements into an explainable design, implement the important controls, and document outcomes and limitations without overstating what the evidence proves.