Outbound Rules
Part of the Stopping the Spread section of Coddy's Cybersecurity journey. Lesson 8 of 20.
You do not control an outside server’s firewall. You can still control which connections leave a company computer.
Egress means outbound traffic. Inspect the practice computer’s outbound policy:
seclab inspect egress practice-laptopYou should see:
practice-laptop:
[
{
"action": "allow",
"port": "any",
"to": "any"
}
]Its rollout rule allows all destinations. Block its web connections to the internet before that broad allow:
seclab egress practice-laptop deny 443 internet at 1You should see:
Outbound rules updated. First match wins; unmatched traffic is blocked.Test the outside connection:
seclab probe demo-uploadYou should see:
practice-laptop -> parcel-cache:443
Blocked: egress (rule 1)The result says egress: the source computer’s outbound rule blocked it. This rule targets the internet zone, so it can leave approved connections to the storage zone available.
Challenge
EasyTicket from Sam, IT lead
Dispatch-pc’s helper is about to retry its outside upload. Restrict that computer’s outbound route to the internet before any new customer data leaves. Keep its approved archive backup and checkout working. Leave the helper running so this ticket verifies the network protection itself.
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