Manager at a comms service provider with 10,001+ employees
Real User
Top 20
2023-11-10T09:17:00Z
Nov 10, 2023
I would rate Gurucul UEBA seven out of ten. It took us eight months to fully realize the benefits of Gurucul UEBA because we first needed to adapt the tool to our specific environment. This involved identifying and addressing various generic issues, developing relevant models, and establishing use cases aligned with our comprehensive policy framework. Only after completing these steps could we effectively utilize Gurucul UEBA to minimize false positives. Gurucul UEBA is deployed across multiple locations. We have around 40,000 users and a team of 70 that work on the tool. Gurucul UEBA requires ongoing maintenance, including software upgrades. If false positives arise, we may need to modify, simplify, or subtly refine the models. Additionally, periodic maintenance of use cases is essential. Therefore, Gurucul UEBA necessitates maintenance after a few years of operation. Organizations must have a clear understanding of their needs before purchasing Gurucul UEBA. This includes determining the number of user IDs they intend to use the tool for and the specific functionalities they require. These three factors are essential prerequisites for making an informed decision about tool acquisition. Purchasing a tool without thorough consideration of these factors can lead to challenges in effectively utilizing the tool and realizing its full potential. Therefore, it is crucial to clearly define the requirements, identify the specific needs, and determine the number of users to be supported to maximize the value derived from Gurucul UEBA.
User and Entity Behavior Analytics (UEBA) is a type of cybersecurity solution that uses machine learning to monitor and analyze the behavior of users and entities (such as devices, applications, servers, etc.) in a network. UEBA can detect anomalous or malicious activities in real time and alert security teams or take automated actions.
UEBA solutions work by analyzing activity from network users and other entities, such as hosts, applications, data repositories, and network traffic. They...
I would rate Gurucul UEBA seven out of ten. It took us eight months to fully realize the benefits of Gurucul UEBA because we first needed to adapt the tool to our specific environment. This involved identifying and addressing various generic issues, developing relevant models, and establishing use cases aligned with our comprehensive policy framework. Only after completing these steps could we effectively utilize Gurucul UEBA to minimize false positives. Gurucul UEBA is deployed across multiple locations. We have around 40,000 users and a team of 70 that work on the tool. Gurucul UEBA requires ongoing maintenance, including software upgrades. If false positives arise, we may need to modify, simplify, or subtly refine the models. Additionally, periodic maintenance of use cases is essential. Therefore, Gurucul UEBA necessitates maintenance after a few years of operation. Organizations must have a clear understanding of their needs before purchasing Gurucul UEBA. This includes determining the number of user IDs they intend to use the tool for and the specific functionalities they require. These three factors are essential prerequisites for making an informed decision about tool acquisition. Purchasing a tool without thorough consideration of these factors can lead to challenges in effectively utilizing the tool and realizing its full potential. Therefore, it is crucial to clearly define the requirements, identify the specific needs, and determine the number of users to be supported to maximize the value derived from Gurucul UEBA.
I rate Gurucul a six out of seven.
From my experience Gurucul, I would say that it is fairly good. On a scale from one to ten, I would give Gurucul a seven.