Application control: ports don't tell you the app
▶ Start the interactive lesson
Burrow allows TCP 443 to the internet, "because that's web". Then IT discovers staff running a file-sharing app, a remote-desktop tool and a game, all over port 443. "Ports were never the app," Maya says. "Modern firewalls look at the traffic itself."
Key points
- Application control identifies the real application using signatures, protocol decoding and behaviour, regardless of port. It can also spot apps hiding inside other protocols.
- Apps are grouped by category, risk and behaviour (file transfer, evasive, tunnels other apps), so you can block "all remote-access tools except the approved one" in one rule.
- The firewall may need a few packets before it's sure which app it is, so the first packets are allowed while identification happens. A good practice is to allow the app only on its usual ports so nothing hides on odd ones.
- Start with monitor mode: see which apps are really in use, agree with the business what's allowed, then block. Blocking blind breaks things and gets the firewall blamed.
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →