Security Onion: a Linux distribution for security monitoring
Security Onion packages Suricata, Zeek, the Elastic stack, host agents and investigation tools into one installable Linux platform, so a team can stand up a complete monitoring sensor and console in an afternoon.
Drafted with AI from official documentation. Scripts were run in a test environment and repository links verified. Awaiting a human check. Did it work for you? Last edited Outdated?
Security-Onion-Solutions/securityonion
- Stars
- 4.9k
- Forks
- 682
- Language
- Shell
- Licence
- NOASSERTION
- Last push
- 15 Oct 2026
On GitHub: Security Onion is a free and open platform for threat hunting, enterprise security monitoring, and log management. It includes our own interfaces for alerting, dashboards, hunting, PCAP, detections, and case management. It also includes other tools such as osquery, CyberChef, Elasticsearch, Logstash, Kibana, Suricata, and Zeek.
Open on GitHubSecurity Onion (about 4,900 stars on GitHub) is a free and open platform for threat hunting, network security monitoring and log management, delivered as a Linux distribution. It was started in 2008 by Doug Burks as a collection of scripts on top of Ubuntu and is now developed by Security Onion Solutions, the company he founded, which funds the work through training, support and hardware appliances. The current generation, Security Onion 2, is built on Oracle Linux and manages its components with Salt and containers.
What it bundles
Rather than a single tool, Security Onion is an integration of many of the projects described in this encyclopedia. Suricata provides signature based network detection, Zeek produces protocol logs, and Stenographer keeps full packet capture for a configurable window. On the host side, the Elastic Agent collects logs from Windows and Linux endpoints and Elastic’s public detection rules run against them. Everything lands in Elasticsearch, and the project’s own web console, Security Onion Console, provides alert triage, a hunting interface, case management and dashboards, with Kibana available alongside. Sigma rules can be imported, and the platform includes CyberChef, a file analysis sandbox and other utilities an analyst needs during an investigation.
Who it is for
- Small security teams and IT departments that want enterprise style monitoring without assembling and tuning each component themselves.
- Students and instructors, since it is the standard lab platform in many network security courses.
- Organisations that need distributed sensors at several sites reporting to one central manager.
- Incident responders who need to deploy a sensor quickly during an engagement.
How to install it
The project publishes an ISO image that installs the operating system and all components. For evaluation choose the import or standalone mode, which runs everything on one machine; the documentation recommends at least sixteen gigabytes of memory and two network interfaces, one for management and one for sniffing. Download the ISO, verify its checksum, boot it in a virtual machine and follow the text based setup:
sha256sum securityonion-*.iso
Production deployments split the roles across manager, search and sensor nodes. The documentation describes each architecture, hardware sizing and the upgrade process in detail.
Credit
Security Onion was created by Doug Burks and is developed by the Security Onion Solutions team with a long standing community. The platform is released under the GNU General Public License version 2, while the bundled components keep their own licences; the Elastic Agent and Elasticsearch are used under the Elastic License and the project ships only the free features.
Did this work for you?
No votes yet. Be the first.
If it did not work, the report form below tells the editors what went wrong.
See also
- 0193 Linux logs reference: journalctl, journald storage, logrotate and centralized logging Read and filter systemd journal logs, keep their disk use in check, rotate classic log files with logrotate, and understand when to… Intermediate · Cheat sheet · Linux Article Linux administration · Logs 15 Oct 2026
- 0291 What is a log? A log is a running record of what a program did and when, written to a file so you can look back… Beginner · Explains an idea · Any system Article Logs 15 Oct 2026
- 0323 Fix: Failed to start service, how to read systemctl status and journalctl Job for x.service failed tells you only that the service did not start. The real reason is in systemctl status and journalctl… Beginner · Fixes an error · Linux Article Logs · Services & systemd 15 Oct 2026
- 0371 Where are the logs? journalctl, /var/log and container logs A practical map of where Linux programs write their logs and the commands to read them: journalctl filters, the classic files under… Beginner · Step by step · Linux Article Logs 15 Oct 2026
- 0373 Loki: ship and search logs Run Loki, Grafana Alloy and Grafana with Docker Compose, collect the systemd journal and /var/log files with a short Alloy configuration, and… Intermediate · Step by step · Linux Article Logs 15 Oct 2026
- 0432 Try Sigma rules against your own logs Install the sigma-cli converter, take a rule from the public SigmaHQ library, convert it into a query for a log tool you… Intermediate · Step by step · Linux, macOS Article Logs · Security resources & detection 15 Oct 2026
History
Every saved edit is kept. The plot on the sleeve draws one line per edit. Open any edit to see exactly what changed.
- Dominik +2,775 chars