Nodes & dependencies
Model the services, places and systems your operation relies on.
Nodes describe what an organisation cannot afford to lose. Dependencies describe how those things rely on each other, so exposure can be reasoned about rather than guessed.
What this helps you do
Without a node model, a signal can only be relevant to a region. With one, it is relevant to named functions, and the path from signal to function is inspectable. Dependencies are directional and can be reviewed and corrected as the operation changes.
The model reflects what an organisation has declared. SKALV does not discover dependencies on its own, and an out-of-date model produces out-of-date exposure.
What you can do after sign-in
- Create nodes for sites, services, systems and functions
- Declare directional dependencies between them
- Inspect the dependency path behind a stated consequence
- Export the model for review outside SKALV
- Keep an audit trail of every change to the model