Start with either path
Traditional GRC is the judgment work, practiced in the browser. GRC Engineering is the same work done with real tools, in your own Codespace and cloud account, and you keep everything you build. Both are free and both start at beginner.
Which path should I start with?
| Path 01Traditional GRC | Path 02GRC Engineering | |
|---|---|---|
| Start here if | You're new to GRC, or you want the judgment side: what to tell a customer, an assessor or the official who signs. | You want to build the controls yourself and finish with a repo you can show. |
| Where it runs | In the browser. Nothing to install. | Your own GitHub Codespace, and your own AWS account for the last two builds. |
| How long | Five scenarios, about four to five hours in all. | Five builds and one scenario, about 13 to 18 hours in all. |
| What you keep | Two written records and the calls you made in each scenario. | A public repo with the code, the evidence and a README for each build. |
| Cost | Free. | Free, except AWS detective controls, which costs under a dollar if you tear it down the same day. |
Nothing is locked, so you can start either one and move between them. Open Traditional GRC Open GRC Engineering
Traditional GRC
The judgment calls, practiced in the browser.
Categorize a system, answer a vendor review against the clock, inherit a program nobody documented, and put an authorization package in front of the official who signs it. Nothing to install. Every mission is a scenario with a deadline, real artifacts and a call you have to make.
What you'll practice
- Drawing a system boundary and categorizing it
- Reading evidence and spotting what it does not prove
- Answering an outside reviewer honestly, on a deadline
- Building an authorization package an AO can sign
- Build your first RMF systemWalk one system through all seven RMF steps and support an authorization decision.Scenario, beginner, 60–90 min, in the browser, leaves civictrack-rmf-package.mdStart this scenario
- FIPS 199 categorizationCategorize three federal systems using FIPS 199 impact levels and the high-water mark rule.Scenario, beginner, 45–60 min, in the browser, leaves fips-199-categorization.mdStart this scenario
- The Vendor Review RoomA customer's vendor review lands at 10:47. Find the logging gap and send an honest answer by 5 PM.Scenario, beginner, 45–60 min, in the browserStart this scenario
- The Diagnostic RoomDay one. The last GRC lead left six weeks ago and FedRAMP is thirteen weeks out. Find what drifted.Scenario, intermediate, about 45 min, in the browserStart this scenario
- The Authorization RoomNinety days to an honest ATO on Summit, then ninety more to make the case for ongoing authorization.Scenario, advanced, about 50 min, in the browserStart this scenario
GRC Engineering
Build the controls for real, and keep what you build.
Real tools, in your own GitHub Codespace and your own AWS account, with every click and command written out. Each build ends as a folder in your own public repo, with the code, the evidence and a README, so when you finish you have a portfolio you can walk an interviewer through.
What you'll practice
- Writing controls as code and proving they work
- Capturing evidence an assessor would accept
- Scanning, gating and blocking before anything ships
- Least privilege and detection in a live cloud account
- Set up your workbenchYour portfolio repo and a Codespace with every tool pinned, so every build runs on the same bench.Build, beginner, 1–1.5 hours, GitHub, freeStart this build
- Scan images and gate the pipelineScan images and Terraform, produce an SBOM, and build a pipeline gate that blocks critical CVEs.Build, beginner, 2–3 hours, Codespace, freeStart this build
- Kubernetes admission policyWrite two policies in Rego and prove risky pods are refused at the door and old ones are caught by audit.Build, intermediate, 2–3 hours, Codespace, freeStart this build
- The Pipeline RoomYou have built a gate. Now review five of them against a spec nobody wrote, 48 hours before the assessor arrives.Scenario, advanced, about 90 min, in the browserStart this scenario
- IAM least privilegeSet up your AWS account safely, then build a narrow, time-boxed, read-only role for an assessor.Build, intermediate, 3–4 hours, AWS, freeStart this build
- AWS detective controlsCloudTrail, Config, alarms and GuardDuty in Terraform. Set each one off on purpose and keep the proof.Build, advanced, 3–4 hours, AWS, under $1Start this build