Welcome to the January 2024 release of LogRhythm Axon! We are pleased to announce numerous exciting updates and changes for this quarter’s release that we hope you’ll enjoy. Brief explanations of the updates are grouped into the following sections:
Key highlights include:
Automatic Case Creation
In the October release of Axon, Case Management was introduced, allowing you to track and record evidence for issues discovered. These cases could be created manually in a variety of ways. In this release, we have added the ability to automatically create cases when rules created using Axon Rule Builder are triggered. With this feature, any time one of your rules that has been configured to create cases is fired, a new case is added to the Case List with the name, description, and owner of your choosing.
For more information, refer to the Automatically Create Cases with Rule Builder section of the Add a New Case documentation.
New LogRhythm-authored MITRE content has been added to out-of-the-box Analytics Rules, including:
T1189: Drive-By Compromise
T1083: File and Directory Discovery
T1566.001: Spearphishing Attachment
T1566.002: Spearphishing Link
T1114.003: Email Forwarding Rule
T1070.006: Timestomp: Update
Single Screen Case Investigation Workflow
Now you can view case evidence without the hassle of shifting between multiple tabs. When looking at case evidence, instead of being redirected to the search page, the new log list panel will display. By clicking a row in this panel, the log inspector will display all the information about this log. Now you can see the case detail panel, evidence list panel, and the log inspector panel side by side.
For more information, refer to the Case Search Panel section of the Manage Cases topic.
Bulk Case Management
From the Case List, a user can change the owner, status, and priority on multiple cases at once. This gives users a way to manage cases in case of duplicates or team changes. Check off cases in the case grid and select an action from the top menu.
See the Modify Multiple Cases section of the Case List documentation for more information.
Case Management API Documentation
Leverage the API documentation to manage cases through the Case Management API. This empowers users to integrate their workflow with third-party tools or scripting.
Assisted Search - List Integration
Searching using lists has become more user-friendly, eliminating the need to memorize IDs or syntax. When using the IN or NOT IN operators, you'll now receive prompts for list names containing values that correspond to the field you're searching. Upon choosing a list name, relevant columns matching the data type will be automatically suggested, completing the query for you.
For more information, refer to the Assisted Search Tips section of the Search documentation.
Axon Agent Diagnostic Bundles
To assist with supporting Axon Agents, we have introduced a way to collect diagnostic data on Windows and Linux platforms. These diagnostic scripts can be generated before you create a ticket with LogRhythm Customer Support, and then attached to the ticket to give our support representatives a better idea of what exactly the issue might be before helping you to resolve it.
O365 Management Activity Collector
The O365 Management Activity Collector is now available, allowing you to configure the collection of Microsoft Office 365 Management Activity logs in Axon.
New Log Processing Policies
Akamai SIEM CEF
Microsoft Defender Advanced Hunting
Microsoft DNS Server
Cisco Wireless Controller
F5 BIG IP TMM
F5-BIG IP System
The following issues have been resolved since the October 2023 release of Axon:
It is no longer possible for the customer to edit the Axon Agent File Collector to change the file collection entry. The field is now read-only and has a "OK" or "Cancel" button.
Configuration details for the Axon Agent Collector are visible with the OK button but are not editable.
Carbon Black Policy Enforcement is now working properly.
Axon Agent logging now filters out any log that does not start with a timestamp.
Azure Active Directory Authentication logs no longer show success and failure common events on the same log.
Analytics rules created with a list filter now work as expected.
An issue with heat map timeframes in the search visualization window has been resolved.
The Bar Chart widget now correctly generates saved search data as expected.
Saved search data is no longer still present in widgets after the saved search has been deleted.
Filters using arrayable CDO fields can now be used in analytics rules as expected.
Searches initiated from the saved search tab no longer fail in certain situations.
Azure logs now correctly parse “results” values other than 0.
Windows Security EVID 4932 and 4933 no longer show as unidentified when a policy to identify the logs is present.
Users authenticated for Okta parsing once no longer automatically receive authorization success for subsequent request to access resources.
Many missing Okta platform event types have now been added to the policy.
An upstream connect error that would appear when configuring Google Drive logs has been fixed.
CrowdStrike is now correctly sending logs to Axon.
All saved searches can now correctly be displayed and filtered in a widget's saved searches dropdown menu.
An issue with certain Cisco Umbrella logs being collected but not identified has been resolved.
The ability to filter saved searches has been removed.
An issue with Microsoft Powershell and Microsoft System logs being recorded as “unidentified” despite a policy existing for them has been resolved.
An issue with filters not working when used in an analytics rule has been resolved.
Parsing improvements have been made for Azure Event Hub and FortiGate logs.
Parsing improvements have been made for Okta logs so that new user created data can be retrieved.
Parsing improvements have been made for Azure logs so that the “add user” value is parsed as an activity, not an application.
Analysts now can see all enabled analytics rules listed in the Analytics Rules Notification grid.
Parsing improvements have been made for Windows Security Logs so that the Origin IP Address is correctly parsed.
The Graph API Collector no longer produces intermittent errors when logs are being collected as expected, and errors that are produced are more detailed.
Clicking on a case no longer displays the incorrect case data in certain situations.
An issue with custom rules seemingly ignoring common event filters in certain situations has been resolved.
Comments can now be made on cases that have a status of “waiting.”
An issue with the Cisco Firepower Threat Defense log source type’s policies not correctly being parsed has been resolved.