Our Outcomes from Using Splunk ES
Overall Satisfaction with Splunk Enterprise Security
We use it to monitor and correlate data across more than 20 client environments, each with different infrastructures and compliance needs. The main challenge it addresses is visibility. Previously, our SOC relied on separate SIEM tools for certain customers, which meant fragmented investigations and duplicated alerts. Now Splunk ES centralizes all that.
Pros
- Instead of reviewing thousands of low level alerts, I can prioritize risks based on the entity's risk score on the risk based alerts dashboard
- The adaptive response framework allows me to link alerts directly to our SOAR playbooks in phantom. This way I can automate triage steps that traditionally took hours.
Cons
- Creating complex custom correlation searches sometimes feels more complicated than it should. You need deep SPL experience to build anything beyond basic logic.
- By consolidating 3 legacy SIEM tools into Splunk ES, we reduced licensing and infrastructure costs by about 30 percent annually.
- We are able to have retention rates much higher than the industry average, since Splunk is ridiculously reliable
In our tests, Sentinel came really close. It was even easier to deploy for cloud native environments. However, once we started integrating OT logs and custom threat intel feeds, the performance and correlation didn't scale as efficiently.
Do you think Splunk Enterprise Security delivers good value for the price?
Yes
Are you happy with Splunk Enterprise Security's feature set?
Yes
Did Splunk Enterprise Security live up to sales and marketing promises?
Yes
Did implementation of Splunk Enterprise Security go as expected?
No
Would you buy Splunk Enterprise Security again?
Yes

Comments
Please log in to join the conversation