This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

What We're Working on for SEM (Updated Nov 18 2020)

Now that SEM 2020.4 is generally available, all major functionality has been migrated to HTML5 interface and we will be pivoting to bring new features to SEM. Here is what we're working on, in no particular order:

  • Microsoft 365 Events: Support for Microsoft 365 audit logs from sources including Azure Active Directory, Exchange, Sharepoint, OneDrive, Teams and more. Vote for this feature. 
  • New Reporting Engine: Provide a new reporting engine in the HTML5 GUI and drop the need for Crystal Reports. Vote for this feature
  • Additional Threat Feeds: Allow users to configure and use additional threat feeds. Vote for this feature.
  • IP Geolocation:  Map IP address to their geolocation and allow users to leverage location in filters, searches and rules. Vote for this feature

This list doesn't enumerate a lot of the features we're looking into for long term development and further releases, but we continually use Thwack as one of our biggest source of feedback

I hope you're happy with the direction SEM is going, but if there is something missing or a feature you're really keen on, be sure to vote for features in Security Event Manager Feature Requests forum. .

Available Beta and RC releases:

  • None

Releases:

Parents
  • I think the new items on the roadmap are great; however, the one thing that is right up there that is killing our ability to fully utilize this SIEM solution is the inability to create our own connectors.  I can't keep telling clients that we can't support their logs because they are not on the "supported list" for LEM.  I fear that at some point we are going to have to move to a new solution if this doesn't change.

Reply
  • I think the new items on the roadmap are great; however, the one thing that is right up there that is killing our ability to fully utilize this SIEM solution is the inability to create our own connectors.  I can't keep telling clients that we can't support their logs because they are not on the "supported list" for LEM.  I fear that at some point we are going to have to move to a new solution if this doesn't change.

Children
No Data