I bridge the gap between federal security frameworks and modern software delivery, turning RMF, cATO, and Policy-as-Code from paperwork into pipeline-native automation. Then I build the tools and curriculum to help others do the same.
I'm a Senior Information Security Analyst embedded in an engineering team at 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.
My background spans GRC, Risk Management Framework, and federal compliance at Amazon, PepsiCo, and Sev1Tech, grounded by years of service as a Cyber Services Technician in the United States Air Force. That combination of military precision, enterprise scale, and modern software delivery is what shaped how I think about security programs today.
I'm also building the GRC Playground, a lab-based learning platform designed to turn compliance analysts into GRC engineers, because the skill gap in this field is real, and I've spent long enough watching it slow down good teams.
Architecting cATO programs inside real software delivery pipelines, not theoretical frameworks. RMF that moves at the speed of deployment.
Translating security controls into 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 compliance infrastructure the same way engineering teams build software: versioned, testable, repeatable, and connected to the things that actually get deployed.
Creating curriculum, platforms, and content that closes the gap between traditional GRC analysts and the automation-first skills federal security programs actually need.
Most compliance training teaches you what a control is. The GRC Playground teaches you what to do with it. Here's what the platform looks like and how a user actually moves through it.
Users choose between two skill paths depending on where they are in their career. Path 1 covers RMF from the ground up for analysts who need a solid foundation. Path 2 moves into GRC engineering territory, where compliance stops being a document and starts being code.
Each path contains multiple labs that build on each other. Progress is tracked individually per user, so the platform meets you where you are rather than forcing a linear sequence that doesn't match your background.
Labs are built around real-world scenarios, not textbook examples. The platform is built on Vercel with Supabase handling authentication, user data, and progress state.
Compliance has a perception problem. It gets treated as a tax on engineering, a thing that slows teams down, a checklist that someone else manages. I've spent years working to change that narrative, both inside the organizations I've worked with and publicly through my LinkedIn content.
My content strategy focuses on making RMF, cATO, and Policy-as-Code accessible to the practitioners who need it most, not just the executives who sign off on it. The goal is a field where GRC engineers are as well understood and well respected as software engineers.
I post twice a week, mixing technical explainers, framework breakdowns, and practitioner-focused perspective on where federal and enterprise compliance is actually heading.
I'm actively building toward a GRC Engineering Director role in federal and enterprise markets. If you're working on security programs that need to move at the speed of modern software delivery, let's talk.