Trace One Command Path

Trace One Command Path

  1. Asset. Name the data, command, device function, or service being protected.
  2. Entry path. Describe how a request, packet, update, or user action reaches the asset.
  3. Trust boundary. Identify where traffic or authority crosses from one zone to another.
  4. Control placement. List the control operating at each boundary or layer.
  5. Failure behavior. State what remains true when one control fails.
  6. Evidence. Record the configuration, log, packet trace, access test, or recovery record that proves the layer works.

Back to the chapter