About Skills Projects Contact
Available for new opportunities

Davin Reynolds

GRC Engineer (in training) | AWS Compliance Automation | Python & Terraform

San Diego, CA  ยท  Open to Remote

13+
AWS Projects Deployed
300+
Compliance Controls Enforced
85%
Compliance Automation

About Me

Aspiring GRC engineer with a focus on cloud security and compliance automation

My path into cloud security started with a hands-on question: how do you build infrastructure that stays compliant without grinding your engineering team to a halt? That question has driven everything I've pursued since, from learning AWS inside and out to building automated solutions that turn compliance into a built-in feature rather than an afterthought.

I'm working toward a career in GRC engineering, building hands-on experience with AWS, CloudFormation, and Infrastructure as Code while picking up Python to automate the compliance and governance tasks that usually get done manually. My focus is on how security controls can be embedded into cloud infrastructure from the start, not bolted on after the fact.

Right now I'm focused on earning my AWS credentials, deepening my automation toolkit, and building projects that show what practical GRC engineering looks like in a real cloud environment. I'm looking to join a team where I can contribute, keep learning, and grow into a strong GRC engineering role.

Focus Area

AWS Cloud Security, GRC Automation & Infrastructure as Code

Frameworks

NIST CSF, AWS Well-Architected, SOC 2, PCI DSS

Location

San Diego, CA ยท Open to remote opportunities

Currently

Pursuing AWS Cloud Practitioner certification & expanding GRC automation skills

Skills & Expertise

Technical proficiencies spanning cloud security, compliance frameworks, and automation

Cloud Platforms

  • AWS (Security Focus)
  • AWS CloudFormation
  • S3, CloudFront, Route 53
  • Certificate Manager
  • Infrastructure as Code (IaC)

Security & Compliance

  • NIST Cybersecurity Framework
  • AWS Well-Architected Framework
  • Cloud Security Best Practices
  • Infrastructure Security Controls
  • Data Protection Standards

Tools & Technologies

  • AWS CloudFormation
  • Route 53, CloudFront
  • Git / GitHub
  • VS Code, PowerShell
  • React, Vite, JavaScript

Programming / Scripting

  • Python
  • PowerShell
  • JavaScript / Node.js
  • Bash Scripting

GRC Frameworks

  • SOC 2
  • PCI DSS
  • NIST CSF
  • NIST 800-53

Other Skills

  • Risk Assessment
  • Compliance Reporting
  • Security Architecture Design
  • Process Automation
  • Technical Documentation

Certifications & Training

Professional credentials and specialized training

โ˜๏ธ

AWS Solutions Architect - Associate

Designing resilient, secure, high-performing, and cost-optimized AWS architectures

In Progress
๐Ÿ

Python for GRC Automation

Specialized training in compliance process automation using Python

Completed
๐Ÿ—๏ธ

Infrastructure as Code Specialist

Expert-level CloudFormation and secure infrastructure deployment

Completed
๐Ÿ›ก๏ธ

CGE-P (GRC Engineering Club)

Hands-on GRC engineering labs covering NIST 800-53, Terraform compliance modules, OPA/Rego policy-as-code, OSCAL documentation, and AWS security automation. Capstone: SOC 2 Type II GRC baseline with automated evidence pipeline.

Completed

Featured Projects

Real-world cloud security and GRC automation solutions

AWS GRC Compliance Infrastructure

Designed and implemented a comprehensive AWS infrastructure deployment solution for GRC compliance using Infrastructure as Code principles. Built automated compliance monitoring and reporting systems with CloudFormation templates, ensuring security-first architecture.

AWS CloudFormation Python Security Controls IaC

Key Achievements

โœ“ Reduced infrastructure deployment time by 90% (8 hours โ†’ 45 minutes)
โœ“ Automated 85% of compliance control validation
โœ“ Implemented security-first architecture with zero security incidents
โœ“ Built scalable architecture supporting global HTTPS delivery
โœ“ Saved $25K annually in manual deployment costs

Cloud Security Compliance Automation

Developed an automated compliance monitoring system for AWS environments using Infrastructure as Code principles. Built continuous security validation, automated reporting dashboards, and real-time compliance tracking for NIST CSF and AWS Well-Architected Framework requirements.

Python AWS CloudFormation Security Automation NIST CSF

Key Achievements

โœ“ Automated 75% of security control validation processes
โœ“ Reduced compliance audit preparation time by 60%
โœ“ Built real-time security posture dashboards
โœ“ Implemented continuous compliance monitoring
โœ“ Created reusable security control templates

Professional GRC Portfolio Platform

Designed and developed a professional portfolio website showcasing GRC expertise using modern web technologies and AWS cloud services. Implemented security best practices, automated deployment pipelines, responsive design, and performance optimization for global content delivery.

React AWS S3 CloudFront Vite

Key Achievements

โœ“ Built responsive portfolio website from scratch
โœ“ Achieved 95+ Google PageSpeed performance score
โœ“ Implemented modern web security best practices
โœ“ Deployed scalable application using AWS global infrastructure
โœ“ Automated CI/CD pipeline for continuous deployment

CGE-P Capstone: SOC 2 GRC Baseline

Built a SOC 2 Type II GRC baseline for a patient intake API on AWS. Closed 8 compliance gaps using Terraform, enforced controls with OPA/Rego policy-as-code, automated evidence collection via GitHub Actions with Cosign signing and S3 Object Lock vault, and documented the control implementation in OSCAL mapped to NIST 800-53 Rev 5.

Terraform OPA/Rego GitHub Actions OSCAL SOC 2 NIST 800-53

Key Achievements

โœ“ Closed all 8 compliance gaps with Terraform baseline module (KMS CMK, VPC, DLQ, CloudTrail, least-privilege IAM)
โœ“ Wrote 5 OPA/Rego policies with 13 unit tests enforcing SOC 2 TSC controls CC6.1, CC6.3, CC6.6, CC6.7, CC7.2
โœ“ Built GitHub Actions pipeline that blocks non-compliant PRs and uploads Cosign-signed evidence bundles to an Object Lock vault
โœ“ Authored OSCAL component definition mapping 7 NIST 800-53 Rev 5 controls to SOC 2 Trust Services Criteria
โœ“ Earned CGE-P certification upon successful capstone review

Lab 2.3: Compliant AWS S3 Infrastructure with NIST 800-53 Controls

Provisioned a NIST 800-53 compliant AWS S3 bucket using Terraform, directly encoding four controls into infrastructure code. Built a dedicated audit log bucket, applied provider-level compliance tags across all resources, and produced machine-readable plan.json and state.json evidence files that map directly to NIST control IDs โ€” no screenshots required.

Terraform AWS S3 NIST 800-53 IaC

Key Achievements

โœ“ Enforced SC-28 (AES-256 SSE), AC-3 (all four public access block flags), CM-6 (versioning + tags), and AU-3 (dedicated log bucket)
โœ“ Applied compliance tags at the provider level using default_tags for single-point CM-6 control
โœ“ Isolated audit logs in a separate bucket preventing compromise of primary data from destroying its audit trail
โœ“ Produced plan.json and state.json as machine-readable evidence consumed by Lab 3.3 policies

Lab 2.4: Reusable Terraform Compliance Module with KMS Encryption

Built a reusable Terraform module that encodes six NIST 800-53 controls into a compliance wrapper for AWS S3 and KMS. Consumers supply only business configuration โ€” the compliance floor is hardcoded inside the module and structurally cannot be disabled. Plan-time validation blocks reject non-compliant configurations before any AWS API call is made.

Terraform AWS KMS AWS S3 NIST 800-53 IaC Modules

Key Achievements

โœ“ Encoded SC-12, SC-13, SC-28, AC-3, CM-6, and AU-11 as non-overridable module internals
โœ“ Validation block rejects prod retention under 365 days at plan time before any AWS cost is incurred
โœ“ compliance_attestation JSON output enables downstream Rego policies to verify the module ran correctly
โœ“ Negative test confirmed plan-time enforcement with zero resource creation for invalid configs

Lab 2.5: Immutable Compliance Evidence Vault with S3 Object Lock

Built an S3 Object Lock evidence vault and evidence capture script that packages Terraform workspace output into a tamper-evident, immutable bundle. The script SHA-256 hashes each file, records a manifest, and uploads a locked bundle to S3 โ€” producing audit evidence with integrity, attribution, and reproducibility properties that no screenshot or PDF can match.

AWS S3 Object Lock Terraform Bash Chain of Custody

Key Achievements

โœ“ S3 Object Lock GOVERNANCE vault preventing deletion or modification during retention period
โœ“ SHA-256 manifest per file enabling single-byte tamper detection without re-running the capture script
โœ“ S3 VersionId receipt anchors evidence to exact bytes stored for independent auditor verification
โœ“ Destructive test confirmed AccessDenied on deletion attempts proving immutability
โœ“ Bucket policy denying s3:DeleteBucket adds second protection layer leaving CloudTrail trace on override attempts

Lab 3.3: Policy-as-Code Library with OPA/Rego for NIST 800-53

Built a policy-as-code library using OPA and Rego that enforces NIST 800-53 controls against Terraform plan JSON before any infrastructure is deployed. Policies are annotated with NIST METADATA blocks and ship with a three-test suite per policy covering compliant pass, wrong value fail, and missing config fail โ€” shifting compliance left to the earliest point in the pipeline.

OPA Rego Policy-as-Code NIST 800-53 Terraform

Key Achievements

โœ“ Three policies enforcing SC-28 (KMS encryption), AC-3 (public access block), and CM-6 (required tags)
โœ“ 9/9 unit tests passing with zero false positives on fully compliant resources
โœ“ Name-suffix correlation solving the AWS cross-resource plan-time matching problem
โœ“ NIST METADATA annotations on every policy enabling machine-readable control routing and severity classification

Lab 3.4: Conftest CI/CD Policy Gate for Terraform Compliance

Wired the Lab 3.3 Rego policy library into Conftest, integrating compliance enforcement directly into the CI/CD pipeline. A policy-gate.sh wrapper evaluates all namespaces, captures JSON evidence on both pass and fail runs, and returns exit codes that block non-compliant PR merges. Includes AWS-specific policy variants using Terraform dependency graph reference matching.

Conftest OPA Rego CI/CD NIST 800-53

Key Achievements

โœ“ policy-gate.sh wrapper evaluates all namespaces even on partial failure, capturing complete violation evidence in one run
โœ“ Reference-based resource matching using Terraform dependency graph instead of name-suffix correlation
โœ“ JSON output evidence files produced for both compliant pass and violation fail scenarios
โœ“ Gate exit code 1 on violation blocking PR merge with exact resource address and remediation step

Lab 4.3: Automated GRC Evidence Pipeline with GitHub Actions and OIDC

Built a fully automated compliance gate running on every pull request via GitHub Actions. The pipeline authenticates to AWS using OIDC (no stored credentials), generates a Terraform plan, evaluates it against three NIST 800-53 Rego policies, runs a tfsec static security scan, and uploads a timestamped evidence artifact โ€” all before a single resource touches AWS.

GitHub Actions AWS OIDC OPA/Rego tfsec Terraform

Key Achievements

โœ“ OIDC trust eliminates stored AWS credentials โ€” IAM role scoped to this specific repository only
โœ“ Policy gate evaluates SC-28, AC-3, and CM-6 against every PR before any infrastructure reaches AWS
โœ“ if:always() on evidence upload ensures failure evidence is captured and not discarded on gate block
โœ“ Demonstrated green PR pass and red PR SC-28 violation block in 28 seconds end-to-end

Lab 4.4: Cryptographic Evidence Chain of Custody with Cosign and Object Lock

Extended the Lab 4.3 GRC pipeline with cryptographic evidence signing and immutable vault storage. Every pipeline run bundles evidence files, signs them with Cosign keyless signing using GitHub's OIDC token, and uploads the signed bundle to an S3 Object Lock vault. The chain of custody holds for both pass and fail runs, answering an auditor's hardest question with mathematical proof.

Cosign Sigstore GitHub Actions S3 Object Lock NIST 800-53

Key Achievements

โœ“ Keyless Cosign signing using GitHub OIDC โ€” no signing keys to rotate, store, or leak
โœ“ Evidence bundles logged in Sigstore Rekor transparency log (public, append-only, outside AWS and GitHub)
โœ“ Signed bundles uploaded to Object Lock vault even on gate failure โ€” failure evidence is preserved and verifiable
โœ“ Tamper test confirmed SHA mismatch detection on single-byte file modification
โœ“ IAM inline policy scoped to exactly 5 S3 actions on one bucket ARN โ€” least-privilege vault access

Lab 5.2: AWS Security Services Baseline with CloudTrail, Security Hub, and Config

Deployed the AWS-native detective control layer using Terraform. Stood up multi-region CloudTrail with log-file validation, enabled Security Hub subscribed to NIST 800-53 Rev 5 and AWS Foundational Security Best Practices, and deployed AWS Config for continuous resource configuration recording โ€” creating a continuously running detection layer that produces audit evidence without manual effort.

CloudTrail Security Hub AWS Config NIST 800-53 Terraform

Key Achievements

โœ“ Multi-region CloudTrail with log-file validation satisfying AU-2, AU-10, and AU-12 โ€” tamper detection via hourly SHA-256 digest files
โœ“ Security Hub subscribed to NIST 800-53 Rev 5 continuously evaluating ~300 controls across the account
โœ“ aws:SourceArn condition on CloudTrail bucket policy preventing confused deputy cross-account log injection
โœ“ Captured 525KB security-hub-findings.json as machine-readable continuous monitoring evidence for FedRAMP/SOC 2 auditors

Lab 6.1: OSCAL Component Definition and Machine-Readable Compliance Documentation

Authored OSCAL Component Definition and Profile documents using the NIST standard for machine-readable security documentation. The component definition links four NIST 800-53 Rev 5 controls to specific Terraform resources with evidence URIs pointing to signed bundles in the Object Lock vault, completing a cryptographically verifiable chain from control requirement to implementation to audit proof.

OSCAL NIST 800-53 Trestle Python Compliance Documentation

Key Achievements

โœ“ OSCAL Component Definition linking SC-28, AC-3, AU-3, and CM-6 to exact Terraform resource names with implementation-status props
โœ“ OSCAL Profile selecting controls from the published NIST 800-53 Rev 5 catalog with trestle validate passing all registered tests
โœ“ Resolved catalog produced by trestle โ€” full 10MB NIST catalog resolved to 68KB focused baseline
โœ“ Evidence URIs in component definition point to Cosign-signed bundles in Object Lock vault for automated auditor verification
โœ“ Demonstrated end-to-end traversal from OSCAL control claim to cryptographic chain intact verification

Get In Touch

Interested in discussing GRC opportunities, consulting projects, or collaboration? I'd love to hear from you.

Ready to collaborate?

Whether you're looking to strengthen your cloud security posture, automate compliance workflows, or discuss GRC strategy โ€” let's connect and make it happen.