THE STARTING POINT
Three things to get right.
- Map necessary flows between users, workloads, and data stores.
- Restrict tool egress to approved destinations where practical.
- Keep enough network context to explain an unexpected connection.
TRY THIS IN THE LAB
A question worth testing.
Diagram a lab assistant’s network dependencies. Separate model calls, retrieval, administration, and telemetry, then review each allowed flow with its owner.
Browse the lab notesLeave a useful trail.
Write down your starting assumptions, scope, expected behavior, observed behavior, and evidence. A successful test should explain what happened and which question to investigate next.