01Input — constraints
Constraints and design decisions
The scope was drawn against these constraints — they are the decisions that gave the system its shape.
- Turn log retention and review into a workflow, not archaeology
02Architecture — system flow
System flow
03Interface — what was built
What was built
M1
Central collection & storage
Security event records gathered in one place
M2
Search & review interface
Screens where records are found and read
04Scope — current status
Scope and current status
Capability matrix4 / 9
Current status & scope
Internal product infrastructure: log collection, storage and review modules run in working condition. Hardening and compliance work was deliberately kept out of this scope.