Most engineers think…
Most people lump it all together as 'the firewall scans for viruses'. In an interview that single sentence collapses three very different jobs into one and gets you caught immediately.
Sophos Firewall stops threats in three complementary layers that share one streaming inspection engine. IPS uses SophosLabs signatures to block inbound known exploits. Advanced Threat Protection (ATP) looks the other way — it catches a host that is already infected by spotting its outbound command-and-control traffic and naming that host. Zero-Day Protection (formerly Sandstorm) is a cloud sandbox plus deep learning that judges unknown files before delivery. Knowing which layer owns which direction — and that HTTPS files need TLS inspection to be scanned at all — is what separates a real answer from a hand-wave.
① Three layers, three jobs — and one streaming engine
The single most useful idea: Sophos Firewall protects you in three layers, each pointed at a different problem, and they all run inside one streaming Deep Packet Inspection (DPI) pass — not three separate scans.
IPS (Intrusion Prevention) blocks inbound known exploits — attacks against your servers and clients matched by SophosLabs signatures. Advanced Threat Protection (ATP) looks the opposite way: it catches a host that is already infected by spotting its outbound command-and-control (C2) chatter, and it names the infected internal host. Zero-Day Protection (formerly Sandstorm) handles the files nobody has a signature for yet — unknown downloads and attachments get detonated in a cloud sandbox and scored by deep learning before they reach the user.
The interview line: IPS = inbound exploits, ATP = outbound C2 from an already-owned host, Zero-Day = unknown files. Together they cover known-bad, already-bad, and never-seen-before. Security Heartbeat ties in — a detection can mark the endpoint red.
Which statement maps the three layers correctly?
② IPS policies — signatures attached to firewall rules
IPS on Sophos Firewall is signature-based. You don't toggle 'IPS on' globally and walk away — you build an IPS policy, which is a named, tunable set of signatures/rules, and you attach it to a firewall rule. Traffic matching that rule is then inspected. Default policies ship for common directions (for example LAN-to-WAN, or DMZ traffic) so you have a sane starting point.
Tune with smart filters
Inside a policy you tune with smart filters by category (e.g. web-server attacks, browser exploits), severity, and action — typically drop for confident, high-severity signatures and recommend/alert while you observe. The classic mistake is setting every signature to drop: that buries you in false positives. Scope each policy to its traffic direction, keep SophosLabs updates flowing, and promote signatures to block as you gain confidence.
SophosLabs signatures packaged into an IPS policy and attached to a firewall rule — blocks inbound known exploits, tuned by category, severity and action.
Catches a host that is already infected by spotting its outbound C2/botnet traffic in DNS/IP/HTTP requests — drops, alerts and names the infected host.
Sends unknown web/email files to a cloud sandbox, detonates and ML-scores them, and returns a clean/malicious verdict before delivery.
The endpoint-firewall health link in Synchronized Security — a detected threat can mark the endpoint red so policy reacts.
In an interview, anchor every answer to direction: IPS guards the way in (inbound exploits via signatures), ATP guards the way out (outbound C2 from an already-infected host), and Zero-Day Protection judges unknown files. Three directions, three jobs, one streaming DPI.
How is IPS actually applied to traffic on Sophos Firewall?
③ ATP — catching the host that is already infected
IPS watches attacks coming in. But what about a laptop that got infected off-network and is now sitting inside your LAN, quietly phoning home? That is Advanced Threat Protection's job. ATP inspects DNS, IP and HTTP requests and checks them against SophosLabs threat intelligence for command-and-control / botnet destinations.
When it finds C2 traffic, ATP can drop and alert — but the real value is that it identifies the infected internal host (the source IP and user), so you can isolate and clean the right machine instead of guessing. Pair that with Security Heartbeat marking the endpoint red and you get a fast, targeted response. Tune ATP with exceptions for known-good destinations that happen to look suspicious, so legitimate services aren't dropped.
IPS matches inbound exploit signatures — it is not designed to spot a host that is already owned and phoning home. That outbound C2/botnet traffic is ATP's job, and ATP is what names the infected internal host. Don't ask IPS to do ATP's work.
A laptop infected off-site is now on your LAN, quietly making C2 lookups. Which layer is built to catch it and name the host?
④ Zero-Day Protection — the cloud sandbox for unknown files
Signatures and reputation can only judge what they already know. Zero-Day Protection (formerly Sandstorm) handles the rest: unknown or suspicious files from web downloads and email are sent to a cloud sandbox (SophosLabs Intelix), detonated and analysed by deep-learning machine learning — and a clean/malicious verdict is returned before the file is delivered. Known-good and known-bad files short-circuit instantly; only the genuinely unknown ones make the round trip.
Scope it sanely — and mind the TLS gotcha
Don't hold and sandbox everything: scope by file type and size (executables, documents, archives up to a limit) so you don't add delay to ordinary browsing. The quiet killer is encryption — files delivered over HTTPS are only inspected when TLS inspection (Decrypt & Scan) is on. With it off, the firewall sees ciphertext, never extracts the file, and the sandbox never runs — the unknown file walks straight through.
Priya at Konnect Logistics in Kochi faces this
A finance user downloaded a 'new invoicing tool' over HTTPS; two days later her PC makes odd outbound DNS lookups and the endpoint goes red in Heartbeat — but Zero-Day Protection logs show the installer was never sent to the sandbox.
TLS inspection was OFF on that web rule, so the encrypted download was never decrypted and the unknown file was never extracted for sandboxing — only ATP caught the aftermath (the C2 chatter).
The web/firewall rule shows Decrypt & Scan / TLS inspection off; ATP logs show the C2 detection that named her host as the source.
Rules and policies ▸ the web/firewall rule ▸ Decrypt & Scan (TLS) + Active threat response / ATP logsEnable TLS inspection on that rule (with a sane bypass list for banking/privacy), confirm Zero-Day Protection is scanning web downloads with file types/size in scope, keep IPS attached, and clean the infected host.
Re-download an unknown test file over HTTPS and confirm it is held, sent to the cloud sandbox, scored, and a verdict returned before delivery — and that a fresh malicious sample no longer reaches the endpoint.
Never assume Zero-Day Protection is working. Pull the sandbox/Zero-Day report for the download: it shows whether the file was extracted, sent to the cloud, detonated and scored. If there is no record, the file was almost certainly delivered over HTTPS with TLS inspection off.
▶ Watch an unknown download get sandboxed and blocked
How one HTTPS file download is inspected end-to-end. Press Play for the healthy path, then Break it to see the classic failure.
An unknown installer downloaded over HTTPS was never sent to the sandbox. The most likely reason is…
🤖 Ask the AI Tutor
Tap any question — instant, scoped to this lesson. No login, no waiting.
Pre-curated from vendor docs + community Q&A, scoped to this lesson. For a live prod issue, paste your export into chat.techclick.in.
📝 Wrap-up assessment — six more
You've answered 4 inline. Six left. 70% (7 of 10) marks the lesson complete on your profile. Tap Submit all answers at the end.
🧠 In your own words
Type one line: which layer catches a PC that is already infected and phoning home, and why isn't that IPS? Then compare with the expert version.
🗣 Teach a friend
Best way to lock it in — explain it in one line to a teammate. Tap to generate a paste-ready summary.
📖 Glossary
- IPS (Intrusion Prevention System)
- Signature-based detection and blocking of inbound known exploits using SophosLabs signatures.
- IPS policy
- A named, tunable set of signatures/rules — filtered by category, severity and action — attached to a firewall rule.
- Advanced Threat Protection (ATP)
- Detection of already-infected hosts by their outbound C2/botnet traffic in DNS/IP/HTTP requests; drops, alerts and names the host.
- Command-and-Control (C2)
- The channel infected malware uses to phone home and receive instructions; ATP watches for it.
- Zero-Day Protection (Sandstorm)
- A cloud sandbox plus deep-learning analysis that judges unknown web/email files before delivery.
- Cloud sandbox
- An isolated cloud environment where an unknown file is detonated and observed to produce a verdict.
- SophosLabs Intelix
- The SophosLabs cloud threat-intelligence and file-analysis service behind these protections.
- Deep Packet Inspection (DPI)
- The single streaming engine that inspects traffic content so IPS, ATP and file extraction share one pass.
- TLS inspection (Decrypt & Scan)
- Decrypting HTTPS so its content and files can be scanned; required for sandboxing HTTPS downloads.
- Security Heartbeat
- The endpoint-firewall health link in Synchronized Security; a detection can mark an endpoint red.
📚 Sources
- Sophos Firewall — Intrusion Prevention (IPS) policies and SophosLabs signatures. docs.sophos.com
- Sophos Firewall — Advanced Threat Protection (ATP): detecting compromised hosts and C2 traffic. docs.sophos.com
- Sophos Firewall — Zero-Day Protection: cloud sandbox & deep learning (formerly Sandstorm). docs.sophos.com
- Sophos Firewall — TLS / SSL inspection (Decrypt & Scan) and HTTPS file scanning. docs.sophos.com
- Sophos — Security Heartbeat and Synchronized Security. sophos.com
- SophosLabs Intelix — cloud threat intelligence and file analysis. sophos.com
What's next?
Got threats covered? Next, go deep on web protection, application control and traffic shaping — how Sophos Firewall filters web categories, identifies and controls apps, and shapes bandwidth so the important traffic always wins.