Test a Route
Part of the Stopping the Spread section of Coddy's Cybersecurity journey. Lesson 2 of 20.
A failed connection does not always mean a firewall blocked it. The destination program might simply be stopped.
Use probe to check the current route for a known connection:
seclab probe demo-orderYou should see:
till-north -> demo-shop:443
Blocked: service_stoppedThe result says service_stopped. The destination service is not running, so changing a firewall rule would not fix this problem.
In this practice case, the maintenance note confirms that demo-checkout should be running. Start it:
seclab process demo-checkout startYou should see:
demo-checkout: running.Probe again:
seclab probe demo-orderYou should see:
till-north -> demo-shop:443
Allowed: allowed (rule 1)The route is now allowed. Probe checks the route without sending a customer file or advancing the clock. Read its reason before choosing a repair.
Challenge
EasyTicket from Sam, IT lead
Checkout stopped working after maintenance. Trace the place-order connection and find why it fails. Restore the approved service so customers can order again. Keep dispatch-pc’s approved backup working and leave the earlier account protections in place.
Try it yourself
All lessons in Stopping the Spread
1Trace the Connection
Follow a ConnectionTest a RouteFollow the Whole OrderInside the CompanyOrders Without Payment2Close 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