diff --git a/salt/soc/files/soc/changes.json b/salt/soc/files/soc/changes.json
index 04f227ebf..e7caffafc 100644
--- a/salt/soc/files/soc/changes.json
+++ b/salt/soc/files/soc/changes.json
@@ -1,7 +1,6 @@
{
"title": "Security Onion 2.3.0 is here!",
"changes": [
- { "summary": "Known Issues - It is still possible to update your grid from any release candidate to 2.3. However, if you have a true production deployment, then we recommend a fresh image and install for best results.
- In 2.3.0 we made some changes to data types in the elastic index templates. This will cause some errors in Kibana around field conflicts. You can address this in 2 ways:
- Delete all the data on the ES nodes preserving all of your other settings suchs as BPFs by running sudo so-elastic-clear on all the search nodes
- Re-Index the data. This is not a quick process but you can find more information at https://docs.securityonion.net/en/2.3/elasticsearch.html#re-indexing
- Please be patient as we update our documentation. We have made a concerted effort to update as much as possible but some things still may be incorrect or ommited. If you have questions or feedback, please start a discussion at https://securityonion.net/discuss.
- Once you update your grid to 2.3.0, any new nodes that join the grid must be 2.3.0. For example, if you try to join a new RC1 node it will fail. For best results, use the latest ISO (or 2.3.0 installer from github) when joining to an 2.3.0 grid.
- Shipping Windows Eventlogs with Osquery will fail intermittently with utf8 errors logged in the Application log. This is scheduled to be fixed in Osquery 4.5.
- When running soup to upgrade from RC1/RC2/RC3 to 2.3.0, there is a Salt error that occurs during the final highstate. This error is related to the patch_os_schedule and can be ignored as it will not occur again in subsequent highstates.
- When Search Nodes are upgraded from RC1 to 2.3.0, there is a chance of a race condition where certificates are missing. This will show errors in the manager log to the remote node. To fix this run the following on the search node that is having the issue:
- Stop elasticsearch - sudo so-elasticsearch-stop
- Run the SSL state - sudo salt-call state.apply ssl
- Restart elasticsearch - sudo so-elasticsearch-restart
- If you are upgrading from RC1 you might see errors around registry:2 missing. This error does not break the actual upgrade. To fix, run the following on the manager:
- Stop the Docker registry - sudo docker stop so-dockerregistry
- Remove the container - sudo docker rm so-dockerregistry
- Run the registry state - sudo salt-call state.apply registry
" },
{ "summary": "We have a new Alerts interface for reviewing alerts and acknowledging or escalating them. Escalating creates a new case in TheHive. Please note that TheHive no longer receives alerts directly." },
{ "summary": "Kibana no longer presents the option to create alerts from events, but instead allows creation of cases from events." },
{ "summary": "Our Security Onion ISO now works for UEFI as well as Secure Boot." },
@@ -20,6 +19,7 @@
{ "summary": "The script so-user-add will now validate the password is acceptable before attempting to create the user." },
{ "summary": "Playbook and Grafana no longer use static passwords for their admin accounts." },
{ "summary": "Analyst VM now comes with NetworkMiner 2.6 installed." },
- { "summary": "Strelka YARA matches now generate alerts that can be viewed through the Alerts interface." }
+ { "summary": "Strelka YARA matches now generate alerts that can be viewed through the Alerts interface." },
+ { "summary": "Known Issues - It is still possible to update your grid from any release candidate to 2.3. However, if you have a true production deployment, then we recommend a fresh image and install for best results.
- In 2.3.0 we made some changes to data types in the elastic index templates. This will cause some errors in Kibana around field conflicts. You can address this in 2 ways:
- Delete all the data on the ES nodes preserving all of your other settings suchs as BPFs by running sudo so-elastic-clear on all the search nodes
- Re-Index the data. This is not a quick process but you can find more information at https://docs.securityonion.net/en/2.3/elasticsearch.html#re-indexing
- Please be patient as we update our documentation. We have made a concerted effort to update as much as possible but some things still may be incorrect or ommited. If you have questions or feedback, please start a discussion at https://securityonion.net/discuss.
- Once you update your grid to 2.3.0, any new nodes that join the grid must be 2.3.0. For example, if you try to join a new RC1 node it will fail. For best results, use the latest ISO (or 2.3.0 installer from github) when joining to an 2.3.0 grid.
- Shipping Windows Eventlogs with Osquery will fail intermittently with utf8 errors logged in the Application log. This is scheduled to be fixed in Osquery 4.5.
- When running soup to upgrade from RC1/RC2/RC3 to 2.3.0, there is a Salt error that occurs during the final highstate. This error is related to the patch_os_schedule and can be ignored as it will not occur again in subsequent highstates.
- When Search Nodes are upgraded from RC1 to 2.3.0, there is a chance of a race condition where certificates are missing. This will show errors in the manager log to the remote node. To fix this run the following on the search node that is having the issue:
- Stop elasticsearch - sudo so-elasticsearch-stop
- Run the SSL state - sudo salt-call state.apply ssl
- Restart elasticsearch - sudo so-elasticsearch-restart
- If you are upgrading from RC1 you might see errors around registry:2 missing. This error does not break the actual upgrade. To fix, run the following on the manager:
- Stop the Docker registry - sudo docker stop so-dockerregistry
- Remove the container - sudo docker rm so-dockerregistry
- Run the registry state - sudo salt-call state.apply registry
" }
]
}