Documentation

What the Academy is, how to sign in, and how to find your way around.

The lab catalogue, tracks and difficulty, and how a run works.

Investigating with timelines and evidence, and how chain of custody works.

How mean time to detect and respond are measured, and what they mean.

The command palette and keyboard shortcuts for moving around quickly.

How to start a lab, the three kinds of experience you will meet, how your detection and response times are measured, and where to find your results.

A plain-language guide for organisation admins on inviting teammates, choosing what each of them may do, and switching access on or off, with the safeguard that a team always keeps one admin.

How the Academy proves a lab came from a publisher you trust and has not been tampered with, and what the verified-publisher badge does and does not mean.

A high-level tour of Invictus Academy: a cloud-native cyber range built as a modular Go monolith with isolated run-modes, an honest-asymmetric trust model, and EU-sovereign forensics.

How Invictus Academy separates its differently privileged backend run-modes from the delivery modes a trainee experiences, and how the MTTD/MTTR KPI is measured and honestly framed.

How Invictus Academy stores its data, isolates each tenant, and splits identity from authorization so Keycloak proves who you are while the app owns what you can do.

How Invictus Academy isolates hostile range workloads into tiers, defends the control plane and trainees, and keeps an honest, named trust posture across its boundaries.

How publishers sign lab-content bundles with ed25519, how to generate keys and sign and verify a bundle, and how an operator configures the trust store and enforcement (ADR-057).

The academy-api HTTP endpoints, generated from the OpenAPI specification.

The full log of architecture decision records (ADRs), with their status.

Plain-language definitions of the terms and metrics used across the platform.