End-of-Life Announcement for Open-Source Snort2 and Strategic Security Updates for Snort3

Today we are announcing lifecycle updates regarding open-source Snort2, along with development updates and details on upcoming releases for open-source Snort3.

 

Open-Source Snort2 Lifecycle and Talos Engagement

All versions of the open-source Snort2 engine have now formally reached its end-of-life (EOL) and end-of-support (EOS). Consequently, active development, maintenance releases, and software package updates for the entire open-source Snort2 codebase (including Snort 2.9.20) have fully concluded.

In conjunction with the engine reaching EOL, Cisco Talos will no longer provide rule support or vulnerability detections for any open-source Snort2 version. Users operating legacy open-source Snort2 deployments should prioritize a migration plan immediately, as continuing to use the legacy engine leaves your environment exposed to emerging threats that are no longer addressed by security updates. Historical open-source Snort2 software packages and documentation will remain accessible on snort.org as reference archives.

 

Open-Source Snort3 Development and Upcoming Releases

Over the past several months, we have been focused on comprehensive security reviews and codebase hardening across open-source Snort3. This initiative included extensive static analysis, fuzz testing of protocol inspectors, and remediation of vulnerability reports identified through automated and LLM-assisted analysis tools to ensure robust engine stability and parser resilience.

The next major open-source release, Snort 3.12.4.0, is now available and bundles all recent security hardening improvements, defect fixes, and performance updates. See the corresponding Cisco PSIRT advisory for more details.

Although we had temporarily paused further release publication while completing this work, significant active development has continued, so keep an eye out for additional releases that will be posted in the coming weeks.

 

Resources for Open-Source Snort3

For teams and practitioners interested in evaluating Snort3 or exploring a transition from legacy configurations, comprehensive documentation and tools are readily available on snort.org. You can access the latest source and build guides or use the snort2lua utility to translate existing configuration files and rules directly into Snort3 syntax. Our community Discord, mailing lists, and GitHub repositories are always open for discussions and technical exchange.

End of Life Announcement for versions of Snort 2 AND Snort 3

Multiple versions of Snort 2 and Snort 3 have reached End of Life and we will no longer publish Snort Talos Rules for these versions as of today.

As of Today we will no longer be supporting the following versions of Snort Talos Rules

Snort 2

2.9.11.1

2.9.13.0

2.9.14.1

2.9.15.1

2.9.16.0

2.9.16.1

2.9.17.0
2.9.19.0

Snort 3

3.0.3.1

3.0.3.4

3.1.0.0

3.1.3.0

3.1.4.0

3.1.5.0

3.1.7.0

3.1.9.0

We encourage All Snort 3 users to use the Talos lightSPD rules package for downloading rules as this singular package contains configurations for every version of Snort 3 and Shared Object rules for all supported versions and architectures, in addition to the latest versions of all rules

Upgrade to the latest version of Snort 3 available here: https://snort.org/downloads 

For more information on the features and advantages of Snort 3 please visit:
https://snort.org/snort3 

For More information on using the Talos lightSPD package please visit:
https://blog.snort.org/2020/12/soft-release-lightspd-new-rules-package.html

For help downloading, installing and configuring Snort 3 please visit:
https://docs.snort.org/rules/

To take advantage of SnortML:
https://blog.snort.org/2024/08/watch-snortml-training-video.html 

To learn more about Snort 3 and Wide String Detection:
https://blog.snort.org/2025/04/in-snort-3.html 

For users who would like to continue to use Snort 2, we encourage you to update to Snort 2.9.20 as soon as possible, which can be found at https://snort.org/downloads . 

Snort 2.9.20 is the version of Snort that we will continue to support for the longest period of time. 

If you have any questions, please feel free to reach out to us at: snort-sub@cisco.com  or join our discord: https://discord.gg/DZpdZDJtSH

End of Life Announcement for Multiple Versions of Snort 2 and Snort 3

Multiple versions of Snort 2 and Snort 3 will be reaching End of Life this year.

As of 12/18/2025 the following versions of Snort 2 will have reached end of life and we will no longer publish Snort Talos Rules for these versions as a result, the following versions of Snort 2 will no longer be supported: 

2.9.11.1
2.9.13.0
2.9.14.1
2.9.15.1
2.9.16.0
2.9.16.1
2.9.17.0
2.9.18.1
2.9.19.0 

As of 12/18/2025, all versions of Snort 3 prior to and including Snort 3.1.9.0 will reach end of life and will no longer be supported.  

We encourage All Snort 3 users to use the Talos lightSPD rules package for downloading rules as this singular package contains configurations for every version of Snort 3 and Shared Object rules for all supported versions and architectures, in addition to the latest versions of all rules

Upgrade to the latest version of Snort 3 available here: https://snort.org/downloads 

For more information on the features and advantages of Snort 3 please visit:
https://snort.org/snort3 

For More information on using the Talos lightSPD package please visit:
https://blog.snort.org/2020/12/soft-release-lightspd-new-rules-package.html

For help downloading, installing and configuring Snort 3 please visit:
https://docs.snort.org/rules/

To take advantage of SnortML:
https://blog.snort.org/2024/08/watch-snortml-training-video.html 

To learn more about Snort 3 and Wide String Detection:
https://blog.snort.org/2025/04/in-snort-3.html 

For users who would like to continue to use Snort 2, we encourage you to update to Snort 2.9.20 as soon as possible, which can be found at https://snort.org/downloads . 

Snort 2.9.20 is the version of Snort that we will continue to support for the longest period of time. 

If you have any questions, please feel free to reach out to us at: snort-sub@cisco.com  or join our discord: https://discord.gg/DZpdZDJtSH

Adding Improved Wide String Detection to Snort 3

By Chris Morrison

In Snort 3.6.2.0, the team has added new modifiers for the "content” option to simplify detection against multi-byte character strings.

For content matches, “width” and “endian” options allow users to modify the content to match against simple wide character strings without manually adding null bytes into the patterns. This makes rule writing easier and more maintainable against targets that use multi-byte character strings, as is common in file metadata or modern string encodings.

Width allows a simple expansion of the content from 8-bit character width to a specified width of 8, 16, or 32 bits. Note that 8 bits is the default behavior and does not impact detected content. 

 

# Match "hello" encoded with 32 bits per character in big endian  

content:"|000000|h|000000|e|000000|l|000000|l|000000|o";  

content:"hello", width 32; 

 

Endian further modifies the width option’s expansion to control the endianness of the expanded character with “big” (as the default) and “little” options. Combining these two options, we can easily flex our detection patterns to match on a variety of string encodings. For example, content: “Talos”, width 32, endian little; would detect on “Talos” encoded as a UTF-32-LE string. 

 

# Match "Talos" encoded with 32 bits per character in little endian content:"T|000000|a|000000|l|000000|o|000000|s|000000|"; 

content:"Talos",width 32,endian little; 

 

To showcase how the width and endian modifiers can make rules more maintainable, consider the existing malware detection in Snort SID 55927. This rule detects several highly suspect strings within a target binary; however, these strings are UTF-16-LE encoded. Here is the simplified rule in old content syntax with null bytes manually added: 

 

alert file ( 

msg:"MALWARE-CNC Win.Dropper.LemonDuck variant script download attempt"; 

file_data; 

content:"|00|%|00|u|00|s|00|e|00|r|00|n|00|a|00|m|00|e|00|%|00||00|%|00|c|00|o|00|m|00|p|00|u|00|t|00|e|00|r|00|n|00|a|00|m|00|e|00|%|00|*|00|",fast_pattern,nocase; 

content:"W|00|S|00|c|00|r|00|i|00|p|00|t|00|.|00|S|00|h|00|e|00|l|00|l|00|",nocase; 

content:"D|00|o|00|w|00|n|00|L|00|o|00|a|00|d|00|S|00|t|00|r|00|i|00|n|00|g|00|",nocase; 

) 

 

 

Here is an example of the new syntax, which makes the rule much easier to follow: 

 

alert file ( 

msg:"MALWARE-CNC Win.Dropper.LemonDuck variant script download attempt"; 

file_data; 

content:"%username%%computername%*", fast_pattern, nocase, width 16, endian little; 

content:"WScript.Shell", nocase, width 16, endian little; 

content:"DownLoadString", nocase, width 16, endian little; 

) 

 

As we can see, if the new rule were to have hits in our environment, we would be able to understand what the rule is alerting to much faster than the original syntax. ClamAV and Yara users will likely be familiar with this usage because the combination of “endian little” and “width 16” is functionally identical to the languages’ wide modifiers. 

These new features are available in Snort 3.6.2.0 and later. More documentation on these options is available in the Snort 3 Rule Writing Guide. 

If you have any questions, feel free to reach out to us via: snort-users@lists.snort.org or join our Snort Discord.

Changes to the Snort Sample IP Block List

Effective today, we have made some changes to the Snort Sample IP Block List available on Snort.org

The Snort Sample IP Blocklist has been a steady component of our open-source Snort community since its launch. It was originally provided so the community could test the functionality of their Snort installation, and it was never intended to be users’ sole source of IP blocking.

Traditionally, this is list of suggested IPs to block based on other open-source IP block lists. But over the past several years, we have seen an increasing number of users relying on the Snort Sample IP Blocklist as their primary source of IP Blocking, which may lead to a false sense of protection from threats.   

To ensure the intention and legal usage of this blocklist is clear to all our users, we will be enabling a “click-to-accept” terms and conditions box for users to access the Snort Sample IP Blocklist hosted on Snort.org. This change will outline the legal terms and conditions for use of the blocklist, which clearly documents the intended use of the data.  

We will continuously update the Snort Sample IP Blocklist on Snort.org regularly and provide it free to all users to ensure that Snort is functioning as intended. 

You can download the Snort Sample IP Block List here.

Thanks,

The Snort Team

Upcoming changes to the Snort.org Sample IP Blocklist

We will be making some changes to the Snort Sample IP Block List on Sept. 26, 2024. 

The Snort Sample IP Blocklist has been a steady component of our open-source Snort community since its launch. It was originally provided so the community could test the functionality of their Snort installation, and it was never intended to be users’ sole source of IP blocking. 

The Snort Sample IP Block List is a list of suggested IPs to block based on other open-source IP block lists. Over the last several years, we have seen an increasing number of users relying on the Snort Sample IP Blocklist as their primary source of IP Blocking, which may be leading to a false sense of protection from threats.    

To ensure the intention and legal usage of this blocklist is clear to all our users, we will be enabling a “click-to-accept” terms and conditions box for users to access the Snort Sample IP Blocklist hosted on Snort.org.   

This change will outline the legal terms and conditions for use of the blocklist, which clearly documents the intended use of the data.  

We will continue to update the Snort Sample IP Blocklist on Snort.org regularly and provide it free to all users, to ensure that Snort is functioning as intended.  After Sept. 26, 2024, access to the list will require users to click to accept the terms and conditions. 

 
If you have any questions, feel free to reach out to us via:snort-users@lists.snort.org 
 
Or join our Discord https://discord.gg/Pj3usE9CZ7

Watch: SnortML Training video

We recently launched SnortML – our new machine learning exploit detection engine designed to detect novel attacks fitting known vulnerability types.  

Now, we have released a SnortML training video featuring Cisco Talos security researcher (and SnortML developer) Brandon Stultz. This video covers how SnortML addresses the zero-day problem, the vulnerability classes it is currently trained on, and a dive into neural networks.  

The training concludes a model development lab where you will see Brandon create a new model to detect a SQL injection attack. 

We hope you enjoy this training and are able to develop a good understanding of SnortML’s capabilities. We look forward to hearing your use cases for the models you create based on SnortML. 

You can find the SnortML and LibML code on GitHub. You can also join the conversation on our Discord or on the Snort users mailing list if you have any questions or feedback.  

Talos launching new machine learning-based exploit detection engine

By Brandon Stultz.

Every day, new vulnerabilities are discovered in the software critical to the function of the modern world. Security analysts take apart these new vulnerabilities, isolate what is necessary to trigger them and write signatures to block any exploits targeting them.
For Snort, these signatures are called Snort rules — and they’re extremely versatile. They can access specific network service fields, locate a vulnerable parameter and scan that parameter for the presence of an exploit.
They can also leverage numerous rule options to traverse protocols and file formats. Written well, these rules can have high efficacy and performance with few or no false positives.
This approach to defense is very good at protecting networks from known threats, but what if the threat is unknown? What if a vulnerability is discovered, an exploit for it is written, and the security community has no knowledge of it? We need another approach to defense that doesn’t require prior knowledge of the attack to function.
Over the past year at Cisco, we have been prototyping and building this new approach into a new detection engine for Snort. Today, I am proud to announce we are open-sourcing this engine to the community in the latest Snort 3 release (version 3.1.82.0). This new detection engine is called “SnortML.”
SnortML is a machine learning-based detection engine for the Snort intrusion prevention system. At a high level, there are two components to this new detection engine. The first component is the snort_ml_engine itself, which loads pre-trained machine learning models, instantiates classifiers based on these models and then makes the classifiers available for detection. The second is the snort_ml inspector, which subscribes to data provided by Snort service inspectors, passes the data to classifiers, and then acts on the output of the classifiers.
Currently, the snort_ml_engine module only has one model type, namely the http_param_model, but we plan on building other models in the future.
This http_param_model is used for classifying HTTP parameters as malicious or normal. Once the snort_ml_engine loads the http_param_model, it can be used in the snort_ml inspector to detect exploits.
The inspector subscribes to the HTTP request data provided by the HTTP inspector through the publish/subscribe interface. It then passes this data (HTTP URI query and optionally HTTP POST body) to a binary classifier based on the http_param_model. This classifier then returns the probability that it saw an exploit. Based on this probability, SnortML can generate an alert, similar to a Snort rule alert, which can be configured to block malicious traffic. Now that you know how the machine learning engine works, let’s get into how the models work.
SnortML models are designed to be extremely flexible, much like their Snort rule counterparts. To that end, we based our models and our inference engine on TensorFlow. The TensorFlow project is a free and open-source library for machine learning and artificial intelligence.
Any TensorFlow model can be a SnortML binary classifier model so long as it satisfies three conditions, namely, the model must have a single input tensor and a single output tensor, the input and output tensor types must be 32-bit floating point, and finally, the output tensor must have only a single element. We plan on adding other model types in the future (including multiclass classifiers), but right now, this is the only model type currently supported. The SnortML engine uses TensorFlow through a support library we call LibML. The LibML library handles loading, configuring and running machine learning models for Snort. It also includes the XNNPACK accelerator needed to run CPU-bound models at line rate. The easiest way to build a SnortML model is to use the TensorFlow Keras API. If you are new to machine learning, don’t worry, Keras is a simple but powerful deep-learning framework that allows you to build neural networks and train them in a few lines of Python. To get started, import the following: We are going to train our example model on just two samples, but a real production model would use far more: The next thing we need to do is prepare our data. SnortML models expect input data to be zero-padded which is what we are going to do here: Now, we need to construct a neural network that can classify our data. This example uses a simple LSTM (Long Short-Term Memory) network, but other combinations of layers available in Keras work here as well. LSTM is a type of neural network that is keenly suited to identify patterns in sequences of data, such as the sequences of bytes in HTTP parameters. To translate the bytes on the wire to tensors that the LSTM can accept, we can place an embedding layer in front of it. Embedding layers are a kind of association layer, they can learn relationships between input data (bytes in our case) and output those relationships as tensors that the LSTM neurons can accept.

Finally, we will converge the output of our LSTM neurons to a single output neuron with a Dense layer. This will serve as the output of the neural network.
Now for the fun part — let’s train this neural network: Training output:

As you can see above, the accuracy of our network increased, and the loss dropped. These metrics show that the neural network learned to differentiate attack from normal in our example dataset.
Now, let’s save this model to a file so we can load it in Snort: Now that we have a model file, we can run it against PCAPs with Snort 3: If you have Snort 3 built with debug messages enabled, you can even trace the ML engine input and output.

Notice that even with variations in the SQL injection attack above, we still detected it. For years, we had dreamed about tackling the zero-day problem, providing coverage for attacks that were like those we had seen before, but targeting different applications or parameters. Now, with SnortML, this dream is becoming a reality. You can find the SnortML and LibML code here. Feel free to join the conversation on our Discord or on the Snort users mailing list if you have any questions or feedback. 

Snort 2.9.8.3 and Snort 2.9.13.0 End of Life

We are announcing the end of life for Talos rules in the following versions of Snort 2:

• Snort 2.9.8.3
• Snort 2.9.13.0
• Snort 2.9.8.3 Rules: This rule set is no longer available.
• Snort 2.9.13.0 Rules: We will no longer produce Talos rules for these versions of Snort on or around July 1, 2024.

We encourage our open-source users to upgrade to the latest version of Snort 3 available here: Snort.org/downloads.

For users who would like to continue to use Snort 2, we recommend updating to Snort 2.9.20 as soon as possible, which can be found at Snort.org/downloads.

If you have any questions please feel free to reach out to us at: snort-sub@cisco.com or join our discord: Snort Discord Invite.

ICS protocol coverage using Snort 3 service inspectors

By Jared Rittle.

With more devices on operational technology (OT) networks now getting connected to wide-reaching IT networks, it is more important than ever to have effective detection capabilities for ICS protocols.

However, there are a few issues that usually arise when creating detection for ICS protocol traffic.

Oftentimes, the protocols connecting these devices on modern networks originate in older serial protocols. This transition resulted in protocols that use techniques like bitfields to reduce message size and multiple levels of encapsulation to avoid changes to the original protocol. These protocols often support combining multiple requests into one packet (pipelining) or splitting up a single request across multiple packets (fragmenting). Snort is fully capable of detecting traffic using any of these approaches, however, it requires a deeper understanding of the underlying protocol and more complicated plaintext rules, which is not always feasible.

The solution to these problems lies in the use of a Snort 3 service inspector for protocols requiring increased detection capabilities. Service inspectors are an evolution of Snort 2's preprocessors, providing access to additional built-in rules that look for protocol-level abnormalities, normalize pipelined and fragmented messages, and provide additional verification that the traffic being inspected is the expected protocol. Through the use of rule options exposed by existing service inspectors, plaintext rule writers can focus on the coverage of interest and let Snort handle protocol decoding and normalization.

Read the rest of this post over on the Talos blog.