Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Snort is the long-established open-source intrusion detection and prevention engine whose rule language became the common format for describing malicious network traffic.

What Is Snort?
Snort inspects network traffic packet by packet, compares it against a set of rules, and raises an alert or drops the packet when something matches. Martin Roesch wrote it in 1998, Sourcefire grew up around it, and Cisco acquired that company in 2013. More than a quarter of a century later it is still in production everywhere, and its rule syntax has become the shared vocabulary for describing network attacks.
That influence is the point worth grasping. When a vendor advertises that their product accepts Snort rules, or when a threat report publishes a detection signature, the format on the page is almost always Snort’s.
Snort operates in distinct modes. As a sniffer it simply prints packets. As a packet logger it writes them to disk. As an intrusion detection system it sits on a span port or network tap, watches a copy of the traffic, and alerts. As an intrusion prevention system it runs inline, with traffic passing through it, so a matching rule can drop the packet before it reaches the destination.
Inline deployment buys prevention at the cost of risk: the sensor becomes a point of failure and a false positive becomes an outage. Most organisations start in detection mode, tune the rule set until alerts are trustworthy, and only then move selected rules to a drop action.
A rule has a header and a body. The header states the action, protocol, source and destination addresses, ports, and direction. The body contains the matching options and the metadata.
alert tcp $EXTERNAL_NET any -> $HOME_NET 445 (
msg:"Suspicious SMB request";
flow:to_server,established;
content:"|FF|SMB"; offset:4; depth:4;
sid:1000001; rev:1;
)
The useful parts for an analyst are content, which matches bytes with optional position constraints, flow, which restricts matching to one direction of an established session, pcre for regular expressions, and sid, the identifier that ties an alert back to the rule that produced it. Variables such as $HOME_NET are defined once in configuration, which is why a sensor configured with the wrong network definition produces either silence or noise.
| Source | Terms |
|---|---|
| Community ruleset | Free, published under GPL, lags the subscriber set |
| Registered ruleset | Free with registration; subscriber rules released after 30 days |
| Subscriber ruleset | Paid, from Cisco Talos, released as soon as rules are written |
| Emerging Threats | Community and commercial sets maintained separately, widely used alongside Talos |
Rule management is the real operational work. A default set generates alerts on traffic that is normal in your environment, and an unmanaged sensor trains analysts to ignore it within a fortnight. Thresholding, suppression for known-good sources, and disabling rules that do not apply to your estate are what turn a Snort deployment into something a SOC can use.
Snort 3 arrived in 2021 and changed the internals substantially. It is multi-threaded, which removes the single-core bottleneck that limited Snort 2 on high-bandwidth links. Configuration moved to Lua, preprocessors became inspectors with a cleaner plugin model, and the pattern matcher was improved. Rule syntax is largely compatible, with some options renamed. Many organisations still run Snort 2 because it is embedded in appliances and tooling, but new deployments should start on Snort 3.
These three names appear together constantly and do different jobs. Suricata is a signature engine like Snort, with native multi-threading from the start, structured JSON output, and file extraction built in; it accepts most Snort rules, which is how many teams migrate. Zeek is not a signature engine at all: it produces rich transaction logs that describe what happened rather than alerting on known-bad patterns. A mature network monitoring stack commonly runs a signature engine and Zeek side by side, feeding both into a SIEM.
Snort inspects what it can read, and most traffic is now encrypted. Without TLS interception, a sensor sees connection metadata, certificates, and timing rather than payloads, which narrows signature matching considerably. Signatures also describe what is already known, so novel techniques pass. And a sensor positioned only at the perimeter sees nothing of lateral movement inside the network.
None of that makes it obsolete. It catches commodity exploitation, scanning, known command-and-control infrastructure, and policy violations cheaply and at line rate. Our SOC Maturation Services help teams tune sensors of this kind so the alerts that reach an analyst are worth reading.
Yes, although its role has narrowed. Encrypted traffic limits payload inspection, and endpoint detection now catches much of what network signatures once found. Snort remains valuable for identifying scanning, commodity exploitation, known command-and-control destinations, and policy violations at line rate, and its rule format is still the common language for sharing network detections.
Both are signature-based network engines with largely compatible rule syntax. Suricata was multi-threaded from the start, outputs structured JSON that integrates easily with log platforms, and includes file extraction and TLS fingerprinting natively. Snort 3 closed much of the performance gap. The choice usually comes down to existing tooling, rule subscriptions, and vendor support.
Start on a tap or span port in detection mode. Inline operation lets rules drop traffic, but it puts the sensor in the data path, so a false positive becomes a service outage and a sensor failure becomes a network failure. Move to inline prevention only for rules that have been tuned and proven in detection mode first.
Not necessarily. The community and registered rule sets cover a great deal, and the Emerging Threats open set is widely used alongside them. The paid subscriber feed gives immediate access to new Talos rules rather than waiting thirty days, which matters when a vulnerability is being exploited at scale. Many organisations combine free and paid sources.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.