A decade of federal and enterprise security experience, building risk-driven, scalable GRC programs that automate compliance and replace manual audit work. I translate regulatory requirements into engineering solutions like Policy-as-Code, Compliance-as-Code, and continuous controls embedded directly in the CI/CD pipeline.
I'm a senior GRC and compliance engineering leader with a decade of work across federal and enterprise security programs. Today I architect a modern GRC engineering function inside Rise8, a defense software company built around continuous Authorization to Operate. My work lives inside the CI/CD pipeline, where compliance has to be automated, auditable, and fast. Not a checklist someone prints before an audit.
That perspective wasn't theoretical. I've spent the last decade building it. I've worked on federal cATO programs at Rise8, third-party risk at Amazon, enterprise security exceptions at PepsiCo, classified RMF and ATO work in eMASS at Sev1Tech, and audit and recovery foundations at Bowhead, all grounded by my time in the United States Air Force. That blend of military discipline, enterprise scale, federal regulation, and modern delivery is what shaped how I think about security programs today.
Outside my day job, I founded GRC Playground, a hands-on lab platform that converts traditional compliance analysts into GRC engineers. I lead Career Operations for the GRC Engineering Club, and I write and speak about Compliance-as-Code, cATO, and the future of the discipline. I care about this field. I want it to grow up.
Architecting cATO programs inside real software delivery pipelines. RMF that moves at the speed of deployment, with real-time risk telemetry replacing point-in-time audits.
Translating security controls into versioned, machine-readable, pipeline-native checks. If a human has to manually validate it every time, it's not a compliance program. It's a liability.
Building reusable Policy Libraries, control-to-pipeline mappings, and automated evidence collection so that maturing governance does not slow delivery. It accelerates it.
Founder of GRC Playground. Head of Career Operations at the GRC Engineering Club. Mentor to analysts becoming engineers. The skill gap in this field is real, and I have spent long enough watching it slow down good teams.
Four operating principles I have arrived at through a decade of audits, exceptions, and ATO packages. They quietly drive every program I have built.
A control that does not enforce itself is a story we tell auditors. Real compliance is a system: versioned, testable, deployed, and observed. Treat it like the software it lives next to.
Manual evidence collection scales linearly with auditors and exponentially with risk. Pipeline-native enforcement and automated evidence make assurance a side effect of doing the work right, not a quarterly fire drill.
cATO works because Authorizing Officials get continuous, real-time signal, not 600-page point-in-time packages. The right answer to "are we secure?" is a live dashboard, not a stack of PDFs from last quarter.
Checkbox compliance fails twice: first when it costs more than the risk it mitigates, and again when it gives engineers reason to route around the security team. Risk-based scoping is the conversation that earns the program a seat at the table.
Federal contracting, hyperscale enterprise, Fortune 50 risk programs, and now defense software delivery. Each role rewrote how I think about controls.
Architecting and leading a modern GRC engineering program embedded inside a secure CI/CD release pipeline, replacing document-driven compliance with controls-as-code and automated evidence collection mapped to NIST 800-53 Rev. 5 and NIST SSDF. Driving cATO strategy across product and engineering teams and partnering directly with Authorizing Officials to establish trust through transparency, real-time risk telemetry, and ongoing assurance rather than point-in-time audits.
Owned end-to-end risk assessments of third-party vendors against ISO 27001 and Amazon's internal security standards at hyperscale. Authored risk analysis reports and remediation plans, partnered with vendors to design compensating controls where direct compliance was not feasible, and worked with internal stakeholders to make accept / mitigate / reject decisions on residual risk.
Owned daily review and adjudication of enterprise security exceptions across a global Fortune 50 environment, evaluating risk impact to network, data, and business operations. Partnered with requestors, control owners, and risk leadership to design mitigating controls, develop remediation paths, and right-size exception terms based on actual residual risk.
Served as GRC SME across classified and unclassified federal systems, implementing security controls and risk assessment frameworks aligned to NIST 800-53 and DoD RMF requirements with sustainable, audit-ready documentation. This is where I first integrated automated security assessments into CI/CD pipelines and used eMASS as a system of record for continuous compliance. An early precursor to the cATO program work I lead today.
The technical and operational foundation underneath everything that came later. Government contracting taught me audit discipline. Military service taught me how systems are actually used in mission environments, and how to build them so the people on the ground can trust them.
A hands-on, lab-based learning platform built to convert traditional compliance analysts into GRC engineers. Most GRC professionals are excellent at the what. Playground teaches the how.
Anchored around a 5-lab Policy-as-Code curriculum grounded in real-world misconfigurations and case studies, not synthetic exercises designed to look good in a course catalog. Every lab maps directly to continuous authorization and modern controls automation.
The origin is personal. Over years of RMF work, I kept seeing the same bottleneck: organizations with strong security intent but no infrastructure to enforce it at scale. Playground exists to close that gap, one practitioner at a time.
Publishing, building community, and influencing how peer organizations approach the next era of compliance.
Publishing on RMF, cATO, Compliance-as-Code, and the future of GRC engineering, reaching a growing audience of practitioners and leaders rethinking how compliance integrates with software delivery.
Leading career operations for an emerging professional community focused on advancing the GRC engineering discipline. Building programming and resources that help practitioners shift from documentation-heavy work into engineering-driven compliance.
Authored a Policy-as-Code lab series grounded in real misconfigurations and case studies, where each lab ties directly to continuous authorization and modern controls automation. Designed for engineers and analysts converting to engineering-first compliance.
Built and lead an internal mentorship and enablement track at Rise8 that transitions traditional GRC analysts into GRC engineers, with curriculum, training materials, and labs that make RMF, ATOs, and cATO operationally fluent rather than theoretical.
The next wave of GRC is not another dashboard. It is autonomous agents quietly handling evidence collection, control mapping, audit response, and continuous monitoring, so humans can focus on the judgment work that actually requires judgment. This is where I am pointing my work next, and where the discipline is heading.
Pipeline-resident agents that watch the build, gather artifacts at the moment they're created, and assemble Body of Evidence packages without a human ever opening a folder.
Translating regulatory language and audit questions directly into control implementations and queries against existing telemetry, so the long tail of "where is this requirement enforced?" gets answered in seconds, not weeks.
Agents that don't just detect drift but explain it, propose remediations, and open the right tickets in front of the right humans, closing the loop between detection and action.
Risk, frameworks, engineering, tooling, and leadership. The full breadth of what a senior GRC engineering leader actually has to operate across.
Enterprise risk management, controls design and assurance, audit readiness, third-party risk, security exception management, and risk-based scoping over checkbox compliance.
Deep federal and growing enterprise framework fluency, built on years of audit-ready documentation across classified and unclassified environments.
The engineering layer that turns frameworks into something a pipeline actually enforces and a system actually proves, every day, automatically.
The actual stack I work in day to day. Pipeline-native security tooling and federal compliance systems of record.
The work that turns a function into a program: partnership across product, engineering, legal, and the executive table; mentorship; thought leadership.
Translating regulatory complexity into product, engineering, and executive language, and back. The work that quietly determines whether a compliance program lands.
Industry-standard validation of foundational security operations and risk management.
The Product School. Bringing PM rigor to compliance program design.
Full Sail University. A design foundation that quietly shapes how I communicate compliance to engineers, leaders, and auditors.
Coursera · Feb 2026 to Jun 2026. Sharpening Python automation directly applied to GRC engineering and agentic workflows.
A+, Network+, CCENT, CEH, and CASP coursework (New Horizons). The stack of technical foundations underneath the GRC work.
Cleared for sensitive federal and DoD security work. Available immediately for cATO, RMF, and engineering-led compliance programs that require trusted access.
Presidential Volunteer Service Award · United States Air Force.
I'm building toward senior IC and GRC Engineering leadership roles across federal and modern tech. If you're working on security programs that need to move at the speed of software delivery, or if you want to talk about cATO, Policy-as-Code, agentic GRC, or Playground, reach out.