A course for the developer or platform engineer who owns the service template in a company with one security engineer across a hundred or more developers, or none at all. It argues that the scaffold is where a small team gets the most leverage per hour, works that claim as arithmetic on a clearly labelled hypothetical estate, and then stays on the scaffold rather than widening out to the paved road. Module one sets out the eight slots worth defaulting, namely authentication wiring, an authorisation checkpoint that denies by default, logging with an allow list based redactor, dependency pinning, a base image pinned by digest, pipeline checks, the secret access pattern and separated health and readiness endpoints, and the seven values that must never be hard coded, with a single review question that catches them by asking what happens if a literal ends up in two hundred services. Module two builds the asymmetry a default needs, hard to remove by accident and easy to override deliberately, through four mechanisms, an inline comment written for a reader eighteen months later who inherited the code, and a fail closed rule with the three cases where failing closed is the wrong call. Module three handles the template that ages: generation is a copy rather than a link, four kinds of decay needing four different responses, what a template version must promise, how to stamp generated output, and the version distribution worked through on a hypothetical estate of 140 services where a fix landing in version 4.0 leaves 92 services carrying the old behaviour. Module four is propagation, the problem every team discovers late, comparing regeneration, automated change across repositories, relocating the property to a layer that has an update mechanism, and detection only, then sequencing a campaign that needs no freeze and closing one that will never reach a hundred percent. Module five covers testing the template itself, which almost nobody does, with a slot by slot assertion list that separates behaviour from presence, and a quarterly ownership routine sized for a few hours a month. Every figure is arithmetic on a clearly labelled hypothetical dataset.
Nothing. Every course, exam, and certificate on the catalog is free — including retakes. All you need is a free Safeguard account.
None. The flagship course, Safeguard Certified Practitioner, is a beginner-level course — basic familiarity with how software is built helps, but every exam question is answerable from the lessons themselves.
You can retake it after a 24-hour cooldown, as many times as you need. Retakes are free, and each attempt draws a fresh random set of questions.
The Safeguard Certified Practitioner credential is valid for 24 months from issue. The expiry date is printed on the certificate and shown live on its public verification page. Renewing means passing the current exam again.
