Back to Labs Week 06

Digital Twin and Remediation Simulation Run Output and Evidence

This page is generated from the AWS Linux blind-trial run evidence. The terminal transcript below is the actual output rendered into the matching screencast MP4, so instructors can compare the Response HTML and video without guessing.

Screencast match: The section named Run Script Output Shown In Screencast is copied from docs/final/lab-material/screencasts/phase06-lab-screencast-20260517T154718Z.cast. Its SHA-256 is 5c80f97af39933886d1337c1b7a14a2e415a93854e329f457b425c0542b8d312. The public video is /downloads/labs/screencasts/phase06-lab-screencast.mp4.
Recorded Exit Code 0
MP4 Duration 18.000000 seconds
Transcript Bytes 536
Screencast Manifest Generated 2026-05-17T16:13:17Z

Run Script Output Shown In Screencast

This is the recorded terminal output for Week 06. It is intentionally verbatim so it can be checked against the MP4 screencast.

find "$HOME/seas8414-blind-trial/evidence/phase-json" -name 'phase*.status' -print | sort | while read f; do printf '%s ' "$(basename "$f")"; cat "$f"; done > "$HOME/seas8414-blind-trial/evidence/final-phase-status-summary.txt"


===== Phase 6: blast-radius and segmentation analytics =====
172.30.0.10
200
phase06-behavioral GET /v1/analytics/behavioral/fbc50d99-7b45-4568-afda-3d807bc8e3cd -> HTTP 200
[
  "data",
  "status"
]
200
phase06-segmentation GET /v1/analytics/segmentation/fbc50d99-7b45-4568-afda-3d807bc8e3cd -> HTTP 200
[
  "data",
  "status"
]
200
phase06-blast-radius GET /v1/analytics/blast-radius/fbc50d99-7b45-4568-afda-3d807bc8e3cd/172.30.0.10 -> HTTP 200
[
  "data",
  "status"
]
200
phase06-timeline GET /v1/analytics/timeline/fbc50d99-7b45-4568-afda-3d807bc8e3cd/172.30.0.10 -> HTTP 200
[
  "data",
  "status"
]
200
phase06-what-if POST /v1/analytics/what-if/fbc50d99-7b45-4568-afda-3d807bc8e3cd -> HTTP 200
[
  "data",
  "status"
]
200
phase06-optimal-plan GET /v1/analytics/what-if/fbc50d99-7b45-4568-afda-3d807bc8e3cd/optimal-plan -> HTTP 200
[
  "data",
  "status"
]

Endpoint Status Output

These status files came from the same remote evidence bundle. They are listed separately so students can see which API calls completed successfully without publishing raw credential examples.

Evidence Status FileHTTP Status
phase06-behavioral.status200
phase06-blast-radius.status200
phase06-optimal-plan.status200
phase06-segmentation.status200
phase06-timeline.status200
phase06-what-if.status200

Evidence Files Produced By The Run

The response page records the actual evidence inventory and file shapes from docs/final/lab-material/run-evidence/aws-8414-20260517T152520Z/remote-evidence/phase-json. JSON values that may contain credential examples are summarized rather than published raw.

FileBytesSHA-256 PrefixShape Or Safe Excerpt
phase06-behavioral.json75900c74f0f2d484ef95object keys: data, status
phase06-blast-radius.json33924aba6ae7a58197dobject keys: data, status
phase06-optimal-plan.json1343b916b035064a972cobject keys: data, status
phase06-protocol-findings.json53fa9203f41c565007object keys: data, status
phase06-rfc-conformance.json1471e1932ce42a9777fobject keys: data, status
phase06-segmentation.json8727732a0e2edfb0c5object keys: data, status
phase06-target-ip.txt1227ac145df4d0714e172.30.0.10
phase06-timeline.json512a7167ab3a8f0d403object keys: data, status
phase06-what-if.json1797165a46c49055a655object keys: data, status