What is our primary use case?
My main use case for Splunk Enterprise Security is for detections.
A specific example of how I use Splunk Enterprise Security for detections involves VPN use cases, where we deal with clients who have numerous third-party vendors supported on VPN, leading to scenarios where users might share their VPN credentials, allowing access from disparate geographical locations. Splunk Enterprise Security is particularly effective at detecting these logins from different locations over a short period and alerting on these events, indicating users who are sharing their credentials.
There are quite many use cases, and some are user-customizable; for instance, we might have someone wanting to know which users got SSH access to servers over working hours or who is accessing RDP outside of working hours. We usually cover traditional brute force attacks and network intrusions within the rules that we enable.
What is most valuable?
The best features that Splunk Enterprise Security offers include easy customization of the rules and a pool of out-of-the-box rules, where creating customizable rules is quite user-friendly and easily achievable without a lot of complexity and required technical knowledge.
The easy customization of rules has helped my team and clients significantly, such as when customers migrate from older SIEMs and request that their previous rules and shortcomings be translated into Splunk Enterprise Security. We are able to create correlation searches within a few hours to achieve the necessary thresholds and supplement what was missing in their previous deployments. Basically, whatever a user can think of, we can translate it into a detection rule, allowing the customer to gain value.
The richness of those rules significantly benefits us when dealing with customers, as it is not a one-size-fits-all model. We have different customizations for different technology layers, so if there are detections tailored to AWS, we do not enable those for customers who are not using AWS, which makes the environment quite efficient.
Splunk Enterprise Security positively impacts our organization and clients mainly through early detections in the security landscape, allowing us to detect vulnerabilities and intrusions much earlier than previously undetected issues. Clients can comply with regulations, act on the detections within their environment, and gain actionable insights. Additionally, there is a minimization of alert load through the risk-based alerting system, which significantly reduces the alert noise for analysts, enhancing their overall work efficiency.
What needs improvement?
I believe the areas of improvement for Splunk Enterprise Security would focus on resource utilization. For smaller environments lacking adequate CPU and memory resources, the system tends to be laggy, so reducing resource consumption would greatly improve experiences in most customer environments.
The usability of the solution is well built, and the interface is intuitive, so there are few improvements to suggest apart from implementing multi-tenancy, which is a frequent request we receive, especially from regional banks managing different branches under varying administrative controls.
For how long have I used the solution?
I have been using Splunk Enterprise Security for coming up to five years now.
What do I think about the stability of the solution?
Splunk Enterprise Security is stable.
What do I think about the scalability of the solution?
Its scalability is impressive, especially when utilizing a multi-site search head cluster; we encounter no challenges scaling the solution.
How are customer service and support?
Customer support is excellent, with same-day responses to our opened tickets and a quick turnaround for out-of-the-box support queries.
Which solution did I use previously and why did I switch?
Previously, we used ArcSight, but we switched to Splunk Enterprise Security mainly due to the limitations of the ArcSight solution in adapting to the changing security landscape.
What was our ROI?
We have observed a return on investment in terms of turnaround time for incident investigations and a reduction in the number of engineers required to manage the system; where three agents were once necessary, tasks are now comfortably handled by two, though we typically maintain two for high availability.
What's my experience with pricing, setup cost, and licensing?
The most significant impact we see relates to license costs. While implementation and setup costs are manageable since we provide those services, the license expense is the primary cost concern.
Which other solutions did I evaluate?
Before choosing Splunk Enterprise Security, we evaluated other options, including FortiNet FortiSIEM and IBM QRadar.
What other advice do I have?
My advice for others considering Splunk Enterprise Security is to try it out, prepare definitive data sources, narrow down on the use cases they want to address, and focus on ensuring data availability to support those use cases.
I want to appreciate the effectiveness of Splunk Enterprise Security, how well it is designed, and its capability to meet customer objectives. I would rate this product a 9 out of 10.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other