Improved
- Connecting Wazuh no longer asks which version you run. The setup commands in Connect Wazuh now work on Wazuh 4.8 to 4.14 and 5.0, and Jutsu reads your version when it tests the connection. The read-only indexer user they create keeps working after you upgrade from 4.x to 5.0. The commands also give the full password rule that both versions accept.
Fixed
- The employee portal always shows a way back to the console if you manage a workspace. If you signed in to the portal with an emailed code, Back to the console at the top of the portal, and Open the console in your account menu, now take you to the password sign-in with your email filled in, then on to the console. The emailed code only opens the portal, and before this nothing in the portal led back. If you are an employee in one workspace and an admin in another, the same button switches you to the workspace you manage.
- Sign in again on a portal page now reaches the password sign-in. When a portal page asked you to sign in again for a workspace you manage, it could land on the emailed-code sign-in instead.
- AWS CloudTrail detection rules run on schedule again. A release on November 16 made each CloudTrail rule read up to six hours of events on every run, so on busy AWS accounts some rules ran late or timed out. Each run now reads only the events that reached Jutsu since the rule's last run, and an event CloudTrail delivers late is still checked.
- A security fix in Connect Wazuh.