What is our primary use case?
My main use case for LogRhythm UEBA [EOL] is detecting insider threats and anomalous user behavior, and I rely on it most often to identify deviations from normal access patterns, such as unusual login times, privilege misuse, or abnormal data access, so the SOC team could investigate potential security incidents early and reduce the response time.
What is most valuable?
The best features LogRhythm UEBA [EOL] offers are its behavioral balancing, baselining, risk scoring, and correlation with SIEM events, and what stands out most is risk scoring, which gives clear visibility into which user behaviors are genuinely risky and helps our team to focus on the highest priority threats without drowning in noise.
Risk scoring helps us to quickly identify which users' activity needs immediate attention by clearly ranking threats based on impact and likelihood; it changes our day-to-day operations by reducing time spent on low-risk alerts and allowing the team to prioritize investigations and response actions more effectively and consistently.
LogRhythm UEBA [EOL] has positively impacted our organization by improving our ability to detect insider threats and compromised accounts earlier, resulting in better security visibility, reduced false positives, and faster investigations and response times, which helped the team operate more effectively with greater confidence.
I observed a noticeable reduction in false positive alert volume, which shortened the investigation time per incident, improving the mean time to detect and respond, and helping identify high-risk user activities earlier, which prevented potential security incidents from escalating.
What needs improvement?
LogRhythm UEBA [EOL] could be improved with more flexible tuning options and clearer model transparency to better understand why certain behaviors are flagged; enhanced integrations with additional data sources and more intuitive dashboards would also help improve usability and investigation efficiency.
More automation around alert triage and response would make daily work smoother, along with simpler tuning to reduce manual effort; better reporting and easier customization of risk thresholds would also help align the tool more closely with our operational workflows.
For how long have I used the solution?
I have been using LogRhythm UEBA [EOL] for the last three years.
What do I think about the stability of the solution?
In my experience, LogRhythm UEBA [EOL] is very stable.
What do I think about the scalability of the solution?
LogRhythm UEBA [EOL] has scaled reliably for our needs, as it has been able to handle increased user activity and log volumes as the organization grew, although scaling typically requires some planning and tuning to maintain performance and accuracy.
How are customer service and support?
My experience with LogRhythm UEBA [EOL] support team has been positive overall; the support team has been responsive and helpful when we needed assistance with tuning or troubleshooting, which helped keep our deployments running smoothly.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We previously relied on basic SIEM correlation rules without a dedicated UEBA solution; we switched to LogRhythm UEBA [EOL] to gain deeper behavior analytics, reduce false positives, and improve detection of insider threats and compromised accounts.
How was the initial setup?
I would advise others looking into using LogRhythm UEBA [EOL] to carefully plan their deployment and integrate UEBA with existing SIEM workflows from the start; they should focus on tuning risk scores and behavioral baselines to reduce false positives and take advantage of platform analytics to productively detect insider threats and account compromises.
What about the implementation team?
Our company relationship with LogRhythm is strictly as a customer; we do not have any partnership or reseller agreement.
Which other solutions did I evaluate?
Before choosing LogRhythm UEBA [EOL], we evaluated a few other UEBA options, including Splunk UEBA and Exabeam; LogRhythm UEBA [EOL] was chosen because it integrated more smoothly with our existing LogRhythm SIEM environment and offered a better balance of functionality and operational complexity for our team.
What other advice do I have?
LogRhythm UEBA [EOL] helped me detect an unusual after-hours login and abnormal data access from a user account that normally followed standard business hours, allowing the SOC team to investigate quickly and confirm the compromised account before any major impact occurred.
Risk behavior and better context around the user activity helped our team make faster decisions, quicker commitments, and improved confidence in handling potential insider or account compromise incidents.
LogRhythm UEBA [EOL] has been a valuable addition to our security operations, especially for detecting insider threats and anomalous user behavior; continued improvements in automation, usability, and integration would make it even more effective, but it already significantly enhances our visibility and response capabilities. I would rate this product an 8 out of 10.
Which deployment model are you using for this solution?
On-premises