Install / Update / Upgrade¶
What’s the recommended procedure for installing Security Onion?¶
Please see the Installation section.
What languages are supported?¶
We only support the English language at this time.
Users / Passwords¶
Support / Help¶
Can Security Onion run in
No, Security Onion does not support blocking traffic. Most organizations have some sort of Next Generation Firewall (NGFW) with IPS features and that is the proper place for blocking to occur. Security Onion is designed to monitor the traffic that makes it through your firewall.
Security Onion internals¶
Where can I read more about the tools contained within Security Onion?¶
Please see the Tools section.
How is my data kept secure?¶
Standard network connections to or from Security Onion are encrypted. This includes SSH, HTTPS, Elasticsearch network queries, and Salt minion traffic. Endpoint agent traffic is encrypted where supported. This includes the Elastic Agent which supports encryption with additional configuration. SOC user account passwords are hashed via bcrypt in Kratos and you can read more about that at https://github.com/ory/kratos.
Why is Security Onion connecting to an IP address on the Internet over port 123?¶
Please see the NTP section.
Should I backup my Security Onion box?¶
Security Onion automatically backs up some important configuration as described in the Backup section. However, there is no automated data backup. Network Security Monitoring as a whole is considered “best effort”. It is not a “mission critical” resource like a file server or web server. Since we’re dealing with “big data” (potentially terabytes of full packet capture) of a transient nature, backing up the data would be prohibitively expensive. Most organizations don’t do any data backups and instead just rebuild boxes when necessary.
Can I connect Security Onion to Active Directory or LDAP?¶
We understand the appeal of integrating with directory services like Active Directory and LDAP, but we typically recommend against joining any security infrastructure (including Security Onion) to directory services. The reason is that when you get an adversary inside your network, one of their first goals is going to be gaining access to that directory. If they get access to the directory, then they get access to everything connected to the directory. For that reason, we recommend that all security infrastructure (including Security Onion) be totally separate from directory services.