Nguyễn Đình ThuyênAn open notebook
EN
Change colour theme
← Security & recovery
03 / Foundations · 3 min

Know what depends on what

An asset list becomes useful when it records function, ownership and dependencies, not just serial numbers.

In 30 seconds

  1. Record the system’s purpose, location, owner and supported software version.
  2. Map connections and shared dependencies such as power, GNSS time, authentication and backups.
  3. Start with approved documentation and passive observations; active scans can disturb sensitive OT.
Make it concrete

Two bridge displays share one position source. Draw that dependency: two screens do not necessarily mean two independent measurements.

  1. 01Asset
  2. 02Dependency
  3. 03Consequence
Concept diagram · simplified for learning
Check your understanding

Can two systems fail together because they share a dependency?

Learning paths →

Go to the source

Sources reviewed: 13.09.2026