Prove the Block
Part of the Stopping the Spread section of Coddy's Cybersecurity journey. Lesson 16 of 20.
After containment, verify a later attempt instead of relying only on the current route. You want evidence that the protection held when the program tried again.
The practice computer is isolated. Watch the next interval:
seclab waitYou should see:
Watching the next interval.
demo-upload: practice-laptop -> parcel-cache:443 (isolated)Read the resulting connection record:
seclab inspect connections demo-uploadLook for these lines:
demo-upload:
Allowed: no
Reason: isolatedThe attempt was blocked by isolation. This confirms containment, but the process is still present and will need cleanup.
When several computers are involved, verify every affected route. One blocked connection does not prove that another source is contained.
Challenge
EasyTicket from Sam, IT lead
Both contained computers will retry within two intervals. Observe the retries from returns-pc and stock-relay, and verify that neither transfers new data. Keep both computers isolated, preserve their running processes for the cleanup investigation, and keep checkout working.
Try it yourself
All lessons in Stopping the Spread
1Trace the Connection
Follow a ConnectionTest a RouteFollow the Whole OrderInside the CompanyOrders Without Payment4Recover and Verify
Prove the BlockRecover in StagesReport the ImpactReview the BoundaryLumen Stays Open2Close the Unwanted Route
Destination RulesRule OrderOutbound RulesAllow the Needed WorkTwo Unwanted Routes3Contain More Than One Computer
Isolate a ComputerThe Exposed PasswordFollow the SpreadKeep Customers WorkingTwo Active Computers