PlatformEngr® DevSecOps runtime course

Cheat notes · Module 00 · Re-entry

Re-enter the lab

A five-minute review for when you have done this module and want it back in your head. Open the full module for the steps and the lab, or the full text to print.

The idea

Resume with the register and notebook from the pipeline course. The same register and repo continue; S01 to S06 remain evidenced and S07 is ready to test.

Remember

  • Surface: surfaces:
  • Trust: A retest date shows when the proof was last run.
  • Evidence: An open row is a gap, not a failed course.
  • Owner: assign the control and retest to a named team.

Pitfalls

  • A single control can be lifted or misconfigured; test independent layers.
  • Preserve useful run evidence before disabling the path or rotating credentials.

Commands

./scripts/validate.shCheck evidence files without executing learner code.
git log --oneline -3Find the recent commits that changed the surface.

Test yourself

Answer in your head first, then open the answer.

What is the objective?

surfaces:

What do you test?

Check the shared repository, kind cluster and course A evidence before changing runtime policy.

What evidence proves the fix?

The same register and repo continue; S01 to S06 remain evidenced and S07 is ready to test.

Where module 00 leaves you: The same register and repo continue; S01 to S06 remain evidenced and S07 is ready to test.