My main use case for Security Onion is network analysis. I use Security Onion for network security monitoring, threat detection, and investigating suspicious activities. I use it to monitor traffic between Windows and Linux systems, analyze alerts, and identify potential security threats. For example, I have used Suricata to detect suspicious network activity, Zeek to examine connection logs, and Elastic Hunt to investigate alerts further. I have also used it to investigate port scans and failed login attempts. What I like most is that Security Onion brings these tools together in one platform, making it easier to investigate security events and understand what's happening across the network. I remember one situation that stands out when I was testing network security in my virtual environment. I used Kali Linux to perform a network scan against another system, and Security Onion detected the suspicious activity. I went into Security Onion, reviewed the Suricata alert, and used Zeek logs to examine the source and destination IP address, ports, and connection patterns. I also checked the packet capture to better understand what was happening. What I found was that the alerts were triggered by the scan I had performed rather than an actual attack. Security Onion helped me to connect the different pieces of evidence and understand why the activity was flagged. That experience really helped me to improve my investigation skills and learn how to distinguish suspicious activity from legitimate testing.
BCGEU Faculty, Computer Information Systems Administration at a educational organization with 1,001-5,000 employees
Real User
Top 5
Oct 18, 2026
I use Security Onion to view logs when students are working with different threats, as it has a dashboard that monitors logs, network traffic, and suspicious activities, which is the primary usage we employ. The scenario I use for Security Onion in one of my classes is when we have a DDoS attack, and we start to monitor the DDoS attack under Security Onion to see if the network traffic related to the DDoS is coming to Security Onion and showing an alert or not. One of the tools we regularly use through Security Onion is to show threats and suspicious activity by conducting port scanning and monitoring unusual connections, which allows students to identify red flags on Security Onion.
My main use case for Security Onion is monitoring components, including Zeek and Suricata, for training, as my environment runs on Proxmox and I use OpenSense as my firewall. I have also configured port mirroring on my Cisco switch to send network traffic for my lab VLANs to Security Onion for analysis. Currently, I am taking my master's degree and have set up some victim VMs that I use for testing in my lab with Security Onion, and I am using it towards my thesis paper.
Security Onion is primarily used for network security monitoring, threat detection, log management, and centralized visibility across our infrastructure, serving as the primary means for our organization. Security Onion is used in our organization by continuously leveraging the Linux platform, Linux system, and network-based architecture to monitor threat detections and log management systems, which has proven very helpful for our organization in terms of network security monitoring.
Scientist at a educational organization with 10,001+ employees
Real User
Jan 15, 2024
The solution is used to learn how the tools work. It enables us to do consulting and demonstrate solutions. We develop attacks, detect them, and demonstrate how it works. The customers are interested in seeing how and what these tools can do.
Security Onion is an open-source Linux distribution for intrusion detection, network security monitoring, and log management. It offers comprehensive solutions for enterprises seeking to enhance their cybersecurity infrastructure.
Security Onion provides a full suite of tools to detect and respond to cybersecurity threats efficiently. As a robust and versatile distribution, it includes capabilities for real-time analysis, network visibility, and threat detection, making it indispensable for...
My main use case for Security Onion is network analysis. I use Security Onion for network security monitoring, threat detection, and investigating suspicious activities. I use it to monitor traffic between Windows and Linux systems, analyze alerts, and identify potential security threats. For example, I have used Suricata to detect suspicious network activity, Zeek to examine connection logs, and Elastic Hunt to investigate alerts further. I have also used it to investigate port scans and failed login attempts. What I like most is that Security Onion brings these tools together in one platform, making it easier to investigate security events and understand what's happening across the network. I remember one situation that stands out when I was testing network security in my virtual environment. I used Kali Linux to perform a network scan against another system, and Security Onion detected the suspicious activity. I went into Security Onion, reviewed the Suricata alert, and used Zeek logs to examine the source and destination IP address, ports, and connection patterns. I also checked the packet capture to better understand what was happening. What I found was that the alerts were triggered by the scan I had performed rather than an actual attack. Security Onion helped me to connect the different pieces of evidence and understand why the activity was flagged. That experience really helped me to improve my investigation skills and learn how to distinguish suspicious activity from legitimate testing.
I use Security Onion to view logs when students are working with different threats, as it has a dashboard that monitors logs, network traffic, and suspicious activities, which is the primary usage we employ. The scenario I use for Security Onion in one of my classes is when we have a DDoS attack, and we start to monitor the DDoS attack under Security Onion to see if the network traffic related to the DDoS is coming to Security Onion and showing an alert or not. One of the tools we regularly use through Security Onion is to show threats and suspicious activity by conducting port scanning and monitoring unusual connections, which allows students to identify red flags on Security Onion.
My main use case for Security Onion is monitoring components, including Zeek and Suricata, for training, as my environment runs on Proxmox and I use OpenSense as my firewall. I have also configured port mirroring on my Cisco switch to send network traffic for my lab VLANs to Security Onion for analysis. Currently, I am taking my master's degree and have set up some victim VMs that I use for testing in my lab with Security Onion, and I am using it towards my thesis paper.
Security Onion is primarily used for network security monitoring, threat detection, log management, and centralized visibility across our infrastructure, serving as the primary means for our organization. Security Onion is used in our organization by continuously leveraging the Linux platform, Linux system, and network-based architecture to monitor threat detections and log management systems, which has proven very helpful for our organization in terms of network security monitoring.
My main use case for Security Onion is its integration with multiple platforms and its function as a centralized system to visualize logs and events.
The solution is used to learn how the tools work. It enables us to do consulting and demonstrate solutions. We develop attacks, detect them, and demonstrate how it works. The customers are interested in seeing how and what these tools can do.