Every case is source-reviewed before it anchors course content. Every framework reference is checked at clause or article level in the approved specification. This page shows the method, the current review status and what is not yet in place.
Approved course specifications will name the source material, the system or failure path examined, and the criteria used to review practical work.
State what a public case, publication or standard actually documents, and nothing beyond it.
Trace the relevant workflow and name its trust boundaries.
Publish scenario, inputs, task, output and review criteria before enrolment.
A working map of public cases to planned courses. Each connection needs source review before it appears in a published course specification.
Each case is source-reviewed before it anchors course content. Control requirements are stated, with their source and interpretation, in each approved course specification.
Draft course descriptions identify these frameworks as possible teaching references. Clause and article mappings require review in each approved course specification.
Referencing a framework does not mean its publisher has approved or endorsed a course.
Four criteria proposed for every course before launch. They are under review and are not yet adopted policy.
Identify the incident, research record or standard behind every teaching claim, and separate documented fact from inference.
Examine how a system can fail before selecting or evaluating a defensive control.
Teach the difference between required, recommended and optional control language.
Review courses against new findings and record every substantive change.
Practitioners appointed against a written standard for each domain. Named instructors are published once appointed.