We recently released Security Onion 2.3.140:
https://blog.securityonion.net/2022/07/security-onion-23140-now-available.html
Today, we are releasing a hotfix that addresses a few issues in the update process:
https://docs.securityonion.net/en/2.3/release-notes.html#hotfix-20220719-changes
New Installations
If you want to perform a new installation, please review the documentation and then you can find instructions here:
https://docs.securityonion.net/en/2.3/download.html
Existing 2.3 Installations
If you already updated to Security Onion 2.3.140 successfully, then you don't need to install this hotfix.
If you tried to update 2.3.140 and it failed, please see our support options:
https://docs.securityonion.net/en/2.3/support.html
If you haven't yet attempted to update to 2.3.140, then you should review all links at the top of this page so that you are aware of all recent changes.
https://docs.securityonion.net/en/2.3/soup.html#elastic-8
Please be aware that custom settings in Kibana may be overwritten during upgrade. We recommend that you test the upgrade process on a test deployment before deploying to production. If you have a distributed deployment, then we recommend monitoring SOC Grid while your update is running to verify that all nodes update properly. If there are issues, you can review logs, services, and containers for any additional clues. If you need help, please see our support information below.
If you have custom Elasticsearch templates, please see:
https://docs.securityonion.net/en/2.3/elasticsearch.html#custom-templates
For more information about the update process, please see:
https://docs.securityonion.net/en/2.3/soup.html
Security Onion 16.04
If you are still running Security Onion 16.04, please note that it is past End Of Life. Please take this opportunity to upgrade to Security Onion 2:
https://docs.securityonion.net/en/2.3/appendix.html
Questions or Problems
If you have questions or problems, please see our support options:
https://docs.securityonion.net/en/2.3/support.html
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.