Goal: security and compliance
Reader: Security teams showing controls, boundaries, evidence and risk. Meta cluster: C — infrastructure & governance Scenarios: 8 · Examples: 8
Scenarios
| Scenario | Tier | Engines | Example files |
|---|---|---|---|
| audit trail | T2 | infographic | audit-trail-checkpoints.md |
| compliance audit | T2 | html-css | compliance-audit-card.md |
| compliance evidence | T2 | infographic | compliance-evidence-zigzag.md |
| hardening sprint | T2 | infographic | security-hardening-sprint.md |
| risk register | T2 | html-css | risk-register-card.md |
| security baseline | T2 | plantuml | security-baseline-aws.md |
| threat model | T2 | plantuml | threat-model-trust-boundaries.md |
| zero trust access | T2 | plantuml | zero-trust-access.md |
Reading order
Boundaries and layers first (zero trust, baseline), then the threat model, then evidence and audit trails.
Engines in this goal
- HTML/CSS — system architecture diagrams, cards and page-level layouts (no fence)
infographic— template-driven boards, sequences and comparisonsplantuml— diagrams with icon families and UML/ArchiMate/BPMN semantics
Details, limits and anti-patterns: ../engines/html-css.md · ../engines/infographic.md · ../engines/plantuml.md.
Palette
Every figure takes its colours from a theme. Pick one in
../styles/palette.md — the token contract, the theme index and the
per-engine blocks all start there.
Most figures in this set want Default. Depart from it for the medium, not the topic: Print when it may be photocopied, Contrast for low vision or large-print handouts, Vivid when it will be projected, Accessible when colour must not be the only cue, Editorial for long-form reading, Slate for technical reference, Pastel when the figure sits inside gentle prose, Nord for a cool Nordic register. Every theme is designed for a light ground — the set has no dark page.
Don't
- A trust boundary drawn without saying what crosses it
- Compliance evidence presented without the control it satisfies