ISO 27001:2022 Cloud Controls Audit & Implementation

The Problem and Why It Mattered

I conducted an ISO 27001:2022 readiness assessment of a GCP environment — mapping infrastructure against all 93 Annex A controls, implementing missing controls, and producing the full evidence artefacts required for certification audit. 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 Cloud Asset Inventory, Security Command Center, BigQuery. 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 Cloud Asset Inventory, Security Command Center, BigQuery 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: Scope & Asset Inventory

Cloud Asset Inventory used to enumerate all in-scope resources. Asset register produced per ISO 27001 Clause 8.1, including asset owner, classification (Public, Internal, Confidential, Restricted), and applicable controls.

Implementation: Annex A Control Mapping — Key Controls

A.5.15 (Access Control): IAM least privilege, quarterly access reviews. A.8.5 (Secure Authentication): MFA via Cloud Identity; FIDO2 keys for privileged access. A.8.9 (Configuration Management): all infrastructure in Terraform. A.8.15 (Logging): 3-year minimum retention. A.8.24 (Cryptography): CMEK enforced.

Implementation: Vulnerability Management Programme (A.8.8)

Self-hosted Trivy scanning every 6 hours. CVSS thresholds mapped to remediation SLAs: Critical 24h, High 7 days, Medium 30 days. Vulnerability register in BigQuery with assigned owners.

Implementation: Statement of Applicability

I produced the Statement of Applicability — the master document required by ISO 27001 Clause 6.1.3(d) — listing all 93 Annex A controls, applicability or exclusion, justification, and implementation status.

Implementation: Internal Audit Programme

Structured review of 20 selected controls per quarter, producing non-conformity reports with root cause analysis and corrective action plans.

Implementation: Results

93 Annex A controls assessed. 18 non-conformities identified, all resolved before external audit. Organisation achieved ISO 27001:2022 certification in the subsequent external audit.

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. 93 Annex A controls assessed. 18 non-conformities identified, all resolved before external audit. Organisation achieved ISO 27001:2022 certification in the subsequent external audit. Claims are limited to the implementation details and outcomes documented in this case study.

Results and Evidence

93 Annex A controls assessed. 18 non-conformities identified, all resolved before external audit. Organisation achieved ISO 27001:2022 certification in the subsequent external audit.

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 Cloud Asset Inventory, Security Command Center, BigQuery. 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.