Day 1 of 5
0 of 5 complete
Task 1 of 5
Day 1: First-Day GRC Engineer Stress
Your new team thinks you are comfortable reading code. Read the scenario first, then work through five short tasks to turn an unfamiliar snippet into a useful GRC response.
First Morning
Your first morning as a GRC engineer is going pretty well until introductions.
Your supervisor tells the technical teams that you know your way around Python, JSON, automation, and “all that engineering stuff.” You may have been a little generous in the interview.
Before lunch, someone from DevSecOps drops a short snippet into chat: “Quick sanity check before we rely on this for access-review evidence?”
You have not written Python at work. Fortunately, nobody asked you to. Your job is to look at what they sent, figure out what you can, and ask the right questions.
Task 1 of 5
Cold Read
A cold read means looking at code before anyone tells you what language it is or how it works. The goal is not to understand everything. It is to see what you can figure out with no help.
Here’s what the DevSecOps team sent.
You have one minute for your first look.
See if you can spot an input, an action, an output, or a decision. Do not Google anything, and do not worry about being right.
Take a breath. Start the timer when you are ready.
🕒 One-Minute Cold Read
1:00
Start the timer when you are ready. The code will appear and you will have one minute for your first look.
What DevSecOps Sent You
Your first look. The language and syntax clues are intentionally hidden.
Take Notes
Capture anything you noticed during the cold read. A guess is fine.
Your notes stay in this browser.