In general, if something needs to be improved in the algorithm, it would be the dashboards. The dashboards with solutions such as Splunk are very neat and clean. I would also like to improve the use cases LogRhythm has. It does not have a very large use case library, so the content engineer needs to develop use cases rapidly alongside emerging threats.
The product should improve its dashboards. Splunk has neat dashboards. Additionally, we would like to enhance the use cases provided by LogRhythm as its use case library is not as extensive as other tools. Its machine-learning capabilities need to improve when compared to other solutions. It lacks risk quantification in a single, transparent view for individuals such as CSOs. Consequently, presenting this information to a CSO or senior manager often requires manual reporting rather than relying on the dashboard. I recall experiencing integration challenges with LogRhythm UEBA, particularly when connecting with products not listed in its predefined integrations. These issues often manifest as parsing errors, even when attempting to integrate with cloud logs.
Sr.Security Operations Engineer at a pharma/biotech company with 501-1,000 employees
Real User
Oct 20, 2023
LogRhythm UEBA's data aggregation needs to be improved. Open-source users do not have much documentation available. Documentation is available only for enterprise users.
Head Of Technical And Network Security at Connex Information Technologies
Real User
Top 20
Jan 6, 2023
What needs improvement in LogRhythm UEBA is the pricing. Here in Asia, for example, in Sri Lanka, pricing is the primary concern, and this is the only area for improvement I see in LogRhythm UEBA.
LogRhythm UEBA [EOL] offers advanced threat detection with an intuitive interface, utilizing correlation, behavior analysis, and machine learning to monitor server threats and privileged accounts effectively.LogRhythm UEBA [EOL] provides comprehensive user behavior analytics and threat hunting capabilities, making use of customizable dashboards, reporting tools, file and registry monitoring. CloudAI adds depth by identifying unknown activities, enhancing network visibility and cyber risk...
![LogRhythm UEBA [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_40/JhFXMVCYzfCrAS3M9VeNUMi6.png?_a=BACAGSGT){kind=small}
In general, if something needs to be improved in the algorithm, it would be the dashboards. The dashboards with solutions such as Splunk are very neat and clean. I would also like to improve the use cases LogRhythm has. It does not have a very large use case library, so the content engineer needs to develop use cases rapidly alongside emerging threats.
The product should improve its dashboards. Splunk has neat dashboards. Additionally, we would like to enhance the use cases provided by LogRhythm as its use case library is not as extensive as other tools. Its machine-learning capabilities need to improve when compared to other solutions. It lacks risk quantification in a single, transparent view for individuals such as CSOs. Consequently, presenting this information to a CSO or senior manager often requires manual reporting rather than relying on the dashboard. I recall experiencing integration challenges with LogRhythm UEBA, particularly when connecting with products not listed in its predefined integrations. These issues often manifest as parsing errors, even when attempting to integrate with cloud logs.
LogRhythm UEBA's data aggregation needs to be improved. Open-source users do not have much documentation available. Documentation is available only for enterprise users.
The product could be user-friendly for someone who doesn’t have any prior experience working with it.
The UI could be improved a little bit.
What needs improvement in LogRhythm UEBA is the pricing. Here in Asia, for example, in Sri Lanka, pricing is the primary concern, and this is the only area for improvement I see in LogRhythm UEBA.
We're now exploring the cloud version but unfortunately we've found that they are lagging in that space.