Case Studies

Real results from recent projects. All client names and identifying details have been anonymised to protect confidentiality.

Each engagement is unique, with specific challenges and tailored solutions. Browse the detailed case studies below to see how I've helped organizations achieve their technical and compliance goals.

Results Disclaimer: Case studies represent real client engagements with actual outcomes. Results vary significantly based on client starting state, implementation quality, organizational maturity, and follow-through. These results are not typical and should not be interpreted as guarantees of specific outcomes. Engagements are customized to each client's unique circumstances.

Cloud Governance

Multi-Account AWS Stabilization for a Global Professional Services Firm

Snapshot

2019 · 3-month engagement · 126 hours · AWS Organizations, Terraform, CodePipeline/CodeDeploy, GuardDuty, Config, Transit Gateway planning

Challenge

All workloads (production, staging, development, and shared services) lived inside a single AWS account with snowflake IAM keys and ad-hoc VPN access. Logging was fragmented, deployments were manual, and strategic migrations stalled because the team lacked a reliable blueprint.

Solution

  • Designed an AWS Organizations layout with dedicated Production, Staging, Shared Services, and Development accounts
  • Defined VPC boundaries, Transit Gateway strategy, and centralized ingress/egress with least-privilege IAM roles per account
  • Standardized Terraform modules and wired them into AWS CodePipeline & CodeDeploy for infrastructure and applications
  • Enabled organization-wide logging and monitoring (CloudTrail, Config, GuardDuty, Security Hub) with centralized storage
  • Documented “current vs. target” architecture, migration priorities, and runbooks so the internal team could continue independently

Results

  • This engagement delivered isolated environments that reduced blast radius and simplified compliance conversations
  • This engagement unified Terraform and CI/CD workflows to restore release confidence
  • Centralized logging and monitoring provided visibility into drift, threats, and cost drivers
  • Delivered diagrams and playbooks so the internal team could continue migrations and replatforming
Diagram of the legacy single-account AWS environment
Before: everything lived inside one AWS account with mixed workloads, static IAM keys, and manual deploys.
Diagram of the redesigned multi-account AWS organization
After: dedicated Production, Staging, Shared Services, and Development accounts with Terraform-driven guardrails.
Compliance

Audit-Ready Landing Zone for a Healthcare Staffing Platform

Snapshot

2025 · 7-week engagement · 92 hours · AWS Control Tower, IAM Identity Center, Terraform/Terragrunt, GuardDuty, Security Hub, Secrets Manager

Challenge

Years of organic AWS growth left the company with dozens of workloads in a single account, IAM/CLI keys shared between contractors, secrets hard-coded in config files, and no audit trail for access changes. With healthcare clients asking tougher compliance questions, leadership needed a governance model that would satisfy auditors and scale across client projects.

Solution

  • Implemented AWS Control Tower with dedicated Management, Security, Logging, and client project accounts for clear separation of duties
  • Designed IAM Identity Center roles (Developer, PowerUser, Contractor) with audit-friendly access logging and session tracking
  • Built a compliance baseline that auto-enables CloudTrail, Config, GuardDuty, and Security Hub in every new account
  • Codified Service Control Policies (SCPs) to enforce guardrails and prevent configuration drift
  • Eliminated hard-coded secrets with a dual-layer approach (SSM Parameter Store + Secrets Manager) for credential rotation

Results

  • This engagement delivered an audit-ready AWS environment with centralized logging and access controls
  • IAM access moved to Identity Center with session logging, removing reliance on long-lived keys
  • Repeatable account provisioning via Terraform/Terragrunt with compliance guardrails baked in
  • Leadership gained a clear, defensible response to auditor questions on access control and change management

Compliance Controls Implemented

  • CloudTrail logging across all accounts
  • AWS Config rules for drift detection
  • GuardDuty for threat detection
  • Security Hub for compliance scoring
  • IAM Identity Center with session logging
  • Service Control Policies (SCPs) for guardrails

This foundation positions the client for HIPAA, ISO 27001, or other compliance frameworks without major rework.

Cybersecurity

HIPAA Security Assessment for Healthcare WordPress Platform

Snapshot

2025 · 2-week engagement · 14 hours · Security audit, HIPAA gap analysis, disaster recovery assessment, remediation roadmap

Challenge

A managed services provider needed an independent security review of their healthcare client's AWS environment. The client was running WordPress on AWS specifically for HIPAA compliance, but had no documentation, no DR process, and no visibility into their actual security posture. Leadership wanted to understand where they stood and what it would take to achieve genuine compliance.

Solution

  • Conducted a full AWS infrastructure security audit covering IAM, network architecture, encryption, and monitoring
  • Identified 6 critical, 9 high, 9 medium, and 7 low-risk findings using a structured risk matrix
  • Identified multiple critical security findings including authentication weaknesses, access control gaps, and encryption vulnerabilities
  • Assessed HIPAA compliance gaps including missing Business Associate Addendum, AWS-managed encryption keys, and disabled audit logging
  • Delivered a 4-phase remediation roadmap with prioritized actions, cost estimates, and timeline (0-30 days through 6+ months)
  • Provided Well-Architected Framework scoring across all five pillars

Results

  • Delivered a comprehensive security report the client could understand and act on
  • Provided a clear HIPAA compliance gap analysis with prioritized remediation steps
  • Phased implementation roadmap with realistic cost projections for compliance
  • Documented DR requirements and backup strategy recommendations

Risk Assessment Summary

6
Critical
9
High
9
Medium
7
Low

Finding Categories Included:

  • • Authentication and credential management gaps
  • • Access control and MFA implementation needs
  • • Encryption and data protection requirements
  • • Compliance documentation and agreements
  • • Audit logging and monitoring capabilities
  • • Security service configuration improvements

Full 4-phase remediation roadmap delivered with cost projections for full HIPAA compliance.

Fractional CTO

CI/CD Architecture & Technical Leadership for SaaS Startup

Snapshot

2019-2020 · Multi-phase engagement · CI/CD architecture, AWS CodeDeploy, Node.js, technical mentorship

Challenge

A startup building a B2B SaaS application needed senior technical guidance to modernize their deployment process. The engineering team was manually deploying their Node.js application to AWS and lacked confidence in their testing and release workflow. Leadership wanted an expert to assess their current architecture, design an automated CI/CD pipeline, and help the team execute.

Solution

  • Conducted a 3-hour architecture review with the lead engineer, mapping current state and identifying gaps
  • Designed a CI/CD pipeline strategy tailored to their Node.js stack (Mocha/Jasmine testing, AWS hosting)
  • Partnered with the lead engineer to architect and implement a sustainable automation solution
  • Provided hands-on mentorship so the internal team could own and extend the system
  • Resolved a complex CodeDeploy pipeline error during staging cutover
  • Implemented centralized logging to improve future debugging visibility

Results

  • This engagement replaced manual deployments with an automated CI/CD pipeline
  • Lead engineer gained confidence to maintain and extend the system independently
  • Clean handover delivered with documentation and knowledge transfer

Engagement Model

Phase 1: Discovery

3-hour architecture review with lead engineer

Phase 2: Implementation

Pair programming to build CI/CD pipeline

Phase 3: Handover

Documentation and knowledge transfer

This engagement model shows how fractional CTO work can scale from initial consultation through delivery and handover for the internal team.

Defence Compliance

CPCSC Readiness Sprint for a Canadian Defence Subcontractor

Snapshot

2025 · 5-week engagement · 68 hours · CPCSC readiness, NIST 800-171 mapping, Terraform guardrails, evidence library build-out

Challenge

An Ontario-based subcontractor needed to deliver components for both Canadian and U.S. defence primes. Their AWS estate mixed ITAR workloads with general R&D, documentation lived in spreadsheets, and leadership had no clear line of sight on CPCSC readiness scores.

Solution

  • Performed a Level 2 CPCSC control gap analysis mapped to existing NIST 800-171 implementation work
  • Split workloads into dedicated AWS accounts with GuardDuty, Config, and Security Hub auto-enabled via Terraform
  • Documented processes, SSP sections, and POA&M entries inside a Notion-based evidence library shared with the OSC
  • Ran tabletop exercises to rehearse assessor interviews, including demo scripts for logging, IAM, and incident response

Results

  • This engagement delivered centralized evidence and automation outputs designed to streamline assessor prep and enable leadership to start formal interviews sooner
  • Eliminated mixed-tenancy risk by establishing CPCSC-only AWS accounts with enforced logging and encryption
  • Prime contractor readiness reviews moved faster with a clearer evidence package
  • Delivery teams retained their existing CI/CD workflows while satisfying CPCSC guardrails

Readiness Artifacts Delivered

  • CPCSC Level 2 control matrix with evidence references
  • Terraform baseline for logging, GuardDuty, Config, and Security Hub
  • Tabletop interview scripts + demo environment checklist
  • Crosswalk between CPCSC, CMMC, and internal policies for OSC leadership

Outcome: prime contractor accepted the readiness package and scheduled formal CPCSC assessment without additional blockers.

Case Study Disclosure: All case studies represent actual client engagements with documented outcomes. Written consent obtained from all clients for use of their project details in anonymized case studies. Client identities, company names, and sensitive business details have been anonymized to protect confidentiality. Case study descriptions have been edited for clarity and to remove identifying information. Individual results will vary based on client circumstances, implementation quality, organizational maturity, and follow-through. These outcomes reflect specific engagements and should not be considered typical or guaranteed.

Ready to Discuss Your Project?

Whether you need cloud architecture, security assessment, compliance guidance, or fractional CTO support, I can help.

Book Your No-Cost Discovery Call

No sales pressure. Just a straightforward conversation.

Book No-Cost Discovery Call