$ ./start --path grc-engineering

Learn GRC engineering zero to hero

Compliance is becoming a software problem. Work through hands-on rooms that take you from control fundamentals to policy-as-code, evidence pipelines and AI governance, scored, ranked and built for practitioners.

No card, no trial timer. Room one is readable without an account.

8
learning tracks
82
rooms mapped
166
hands-on labs
-
challenges cleared

What a room actually looks like

An unedited slice of room one. Read the brief, then prove it against a deliberately messy scenario.

From the brief

The failure mode you are replacing

Traditional GRC fails in three predictable ways. First, evidence is point-in-time: a control can be broken for eleven months and still pass an audit sampled in month twelve. Second, effort scales linearly with scope: every new framework multiplies the same manual work. Third, the data is trapped in documents, so nobody can answer 'which controls are failing right now?' without a two-week fire drill.

Each failure has an engineering answer: continuous monitoring instead of sampling, shared control definitions instead of per-framework duplication, and structured data instead of prose.

The task you get

The eleven-month gap

INCIDENT 04-11: Your SOC 2 report was issued clean in December. In February the platform team discovers that the nightly backup-integrity job silently stopped restoring test data on 14 January of the previous year: eleven months before the auditor looked at it.

The control owner is adamant nothing was missed: "We had full logging the whole time, and the auditor pulled three restores from November and they all passed. The control was tested. This is a monitoring gap on the platform side, not a compliance issue."

Open the full room

Who this is for

GRC analyst going technical

You run the control program by hand today. Start with control modelling, then automate a whole family.

Start with GRC Fundamentals

Auditor who wants the data

Stop sampling three of three hundred. Learn evidence pipelines, coverage and population testing.

Go to Data & Evidence

Security engineer inheriting compliance

You already write code. Learn how controls, policy as code and guardrails fit your pipelines.

Go to Automation & Code

How the rooms work

A room is one self-contained lesson: read the material, then prove it. Finish every task to bank the XP and unlock the next room in the track.

Answer challenges

Work through real control artifacts and submit answers that are graded instantly.

Code & policy labs

Author YAML controls, evidence queries and Rego policy in the browser, then review and triage real artefacts: all graded by hidden server-side checks.

Scenario sims

Triage an audit request list or map controls inside a simulated GRC tool.

XP, ranks & streaks

Every room earns points toward Recruit, Analyst, Engineer and Architect ranks.

Finish a track, get a verifiable certificate

Every track ends in a gated capstone. Clear it and your certificate is entered on a public register: anyone can check the code, and you get a share link for LinkedIn. Yours could be the first.

See what each track certifies

Tell me when new rooms land

New rooms ship regularly across every track. Leave an address and we'll tell you when one opens.

New rooms only. No drip sequence, no sharing your address, unsubscribe any time.

Ready for room one?

"What Is GRC Engineering?" takes 25 minutes and is free to read right now.

Enter the room