Destination Rules
Part of the Stopping the Spread section of Coddy's Cybersecurity journey. Lesson 6 of 20.
A destination firewall decides which incoming connections a computer accepts. Use it to block access that the source does not need.
In this example, office computers should not reach demo-shop’s administration port. Add a deny rule at the beginning:
seclab firewall demo-shop deny 22 office at 1You should see:
Added rule 1 on demo-shop: deny 22 from office. Rules are checked top down.Inspect the rules:
seclab machine demo-shopLook for these lines:
firewall (first match wins, anything unmatched is blocked):
rule action port from note
1 deny 22 officeThe rule applies to port 22 from office. It leaves retail traffic to port 443 alone. The position matters because this firewall uses the first matching rule.
Choose the source and service supported by the incident evidence. Blocking every port from every zone would also block customers and payments.
Challenge
EasyTicket from Sam, IT lead
Sam has confirmed that office computers do not need webstore administration access. Block that incoming route before dispatch-pc’s next attempt to read server configuration. Keep retail orders, payments and the dispatch backup working. The unwanted process should remain running for this controlled route test.
Try it yourself
All lessons in Stopping the Spread
2Close 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