Splunk Enterprise Security Reviews

Splunk Enterprise Security is mainly used for detecting and monitoring log analysis, threat detection, and incident investigation. It is primarily used for failed login detection where multiple login failed attempts occur from the same source IP. Brute force attacks are another common use case. Splunk Enterprise Security use cases can be extended through visualization on data dashboards, setting incident triage, and Windows event log analysis in SOC environments. I use it from a SIEM perspective in my organization.

The best features of Splunk Enterprise Security are that it is the leading platform in cybersecurity right now in SOC environments. Business resilience is very useful for real-time monitoring and investigation, which improves our business resilience.

The AI-driven detections have improved the accuracy of my investigations significantly. I have worked with two other SIEM tools: Wazuh and Azure Microsoft Sentinel. Compared to both, Splunk AI is very good. When we mark an alert as a false alert, Splunk Enterprise Security automatically detects it as a false positive. Whenever another similar alert comes through, it automatically takes action, so we will not get that alert on our dashboard again. It automatically handles false positive alerts, preventing clutter on our dashboard.

It has reduced my mean time to detection (MTTD) by about 30 percent and my mean time to resolution (MTTR) by about 40 percent. Our SLA has reduced from fifteen minutes to ten minutes, which is very helpful because we are raising alerts within ten minutes.

Risk-based alerting provides significant value. When we raise an alert, we provide the incident classification as either true positive or false positive in Splunk and also in the ticketing tool. If an alert is a false positive, Splunk's AI takes care of this and tells us whether we want this alert to show to the SOC team or not. The decision depends on AI analysis.

The assessment of the threat topology and the MITRE ATT&CK framework in Splunk shows that Splunk already maps MITRE ATT&CK with incidents. Whenever an alert comes, the AI configures it to that framework. For investigation purposes, I check the process tree to see how the alert originates and where the malware is going to end. This is very good for threat investigation.

Splunk Enterprise Security has become at least forty to fifty percent faster at detecting threats compared to Azure Sentinel. It is very fast for detecting alerts.

It has contributed to the reduction of analyst burnout and fatigue because it reduces our alerts. If we raise an alert on Splunk, it takes care of them through AI. False positive alerts will not show up, preventing mess for our team. Our threat hunting team and forensic team handle the true positive alerts, while false positives are automatically taken care of by AI.

When comparing Splunk with other vendors, I find that Splunk use cases have more power to detect alerts. Azure Microsoft Sentinel has inbuilt over two hundred use cases analytics for their team only, and we cannot create more customized use cases. In Splunk, we can create additional customized use cases, plus there is AI for detection. If we miss some use cases for any logs or events, AI takes care of it and creates its own use case, showing alerts for us. The dashboard is also very user-friendly compared to both.

Areas that have room for improvement in Splunk Enterprise Security include user access. When we give access to a new user, it becomes difficult for them to log in and understand the interface. It would be beneficial if there is a demo for L1 users. I also see improvement needed in integration. Currently, we have to manually integrate devices, but I would like AI to take care of it, similar to how SentinelOne operates. This would make the process smoother.

My experience using the solution has been two years.

Stability-wise, Splunk Enterprise Security is very good. I have not experienced any significant performance issue or downtime.

I rate the scalability of Splunk Enterprise Security as an eight. It depends on how stable and scalable you manage Splunk Enterprise Security for your organization.

I rate the technical support of Splunk Enterprise Security as a three. I find it not good because whenever I raise a ticket, they take a very long time. Even if I call the toll-free number, tickets are pending.

I have worked with two other SIEM tools: Wazuh and Azure Microsoft Sentinel. The AI-driven detections have improved the accuracy of my investigations significantly compared to these solutions.

It is very easy to deploy Splunk Enterprise Security compared to both other SIEM tools. Splunk connector is very easy to set up.

The time it takes to install depends on whether we are installing on a Windows or Linux machine or the size of the organization. For a moderate-level company, it usually takes around five days to install everywhere the connectors and endpoints.

When it comes to upgrading Splunk Enterprise Security to version eight point zero, I have a team that handles the upgrade, and it is basically easy to upgrade the version.

Combining SIEM, SOAR, and UEBA into a single interface has improved my operational efficiency significantly. Before we integrated SOAR, we usually took fifteen minutes to raise SLA alerts. For analysis, L1 would take ten to twelve minutes to decide if they wanted to raise an alert or not. With SOAR, we have predefined playbooks, so if any inbound connection happens from a malicious IP, it automatically blocks on the firewall. We handle most alerts through SOAR now, which allows us to focus on the more significant incidents like malicious attacks, effectively reducing our response time.

Regarding the pricing of Splunk Enterprise Security, I would say it is very expensive for our organization compared to the two others. Wazuh is open-source, and for SentinelOne, we are a partner with Microsoft, but Splunk has a high cost for setup, which is based on the EPS count and storage.

When comparing Splunk with other vendors, I find that Splunk use cases have more power to detect alerts. Azure Microsoft Sentinel has already inbuilt over two hundred use cases analytics for their team only, and we cannot create more customized use cases. In Splunk, we can create additional customized use cases, plus there is AI for detection. If we miss some use cases for any logs or events, AI takes care of it and creates its own use case, showing alerts for us. The dashboard is also very user-friendly compared to both.

9

On-premises

Amazon Web Services (AWS)

My main use case for Splunk Enterprise Security is visibility. I use Splunk Enterprise Security for visibility specifically for the IR team for cybersecurity incidents. Splunk Enterprise Security helps my incident response team detect and manage cybersecurity incidents by being the only tool they use for finding incidents.

Splunk Enterprise Security has positively impacted my organization by being able to respond faster and track down exactly what has happened.

With the correlation and the alerting in Splunk Enterprise Security, we are able to respond faster than we had before when we were unable to have dashboards that show us what was going on.

Splunk Enterprise Security has helped improve my organization's business resilience, and it helps the IR analysts do their jobs.

Splunk Enterprise Security has helped reduce my team's average mean time to resolve, MTTR metric, by 25%.

The best feature Splunk Enterprise Security offers is the correlation of logs. The correlation of logs stands out for my team because in incident triage, it is able to help us identify what had happened.

I cannot think of any improvements for Splunk Enterprise Security at the moment. I would like to add that I am not a fan of the new UI. I find the new UI challenging because it takes much more searching to find everything that you need; they introduced it all at once instead of gradually introducing it.

I have been using Splunk Enterprise Security for 5 years.

Splunk Enterprise Security is stable.

The scalability of Splunk Enterprise Security is fine.

Customer support has been quite poor until recently, but they have been improving. I would rate the customer support a five on a scale of 1 to 10.

We previously used a different solution; it was a managed solution and we wanted something that was ours.

Splunk Enterprise Security is deployed in my organization through Splunk Cloud.

I am not currently using RBA at the moment, so I cannot describe how Splunk Enterprise Security's risk-based alerting has impacted my alert volume and analyst productivity. I am not currently using the threat topology or MITRE ATT&CK framework features for helping discover the overall scope of an incident. The integration of threat intelligence directly into the TDIR workflow has not improved my ability to preemptively block threats. I am not a user of SOAR, so I cannot assess how the consolidation of SIEM, SOAR, and UEBA into a single interface has improved my team's operational efficiency.

I have saved time but have not seen true savings in investment.

I find the licensing and pricing a bit much being a cloud client.

Before choosing Splunk Enterprise Security, I did not evaluate other options.

I have no problems with Splunk Enterprise Security's AI capabilities regarding its governance and security; I think it is actually good. Regarding the accuracy and reliability of output, Splunk Enterprise Security seems to be right on. I am not using RBA at the moment, so I cannot describe how Splunk Enterprise Security's risk-based alerting has impacted my alert volume and analyst productivity. I give this review a rating of 7.

Public Cloud

Amazon Web Services (AWS)

I am still working with Splunk Enterprise Security. We are a reseller of Splunk Enterprise Security, providing it to our customers.

On a daily basis, we use Splunk Enterprise Security for advanced threat and ransomware detection, providing it to our customers for threat detection and ransomware detection, as well as for detecting insider threat anomalies and for continuous monitoring and log analysis.

We provide Splunk Enterprise Security both internally as we are an MSSP, managing our customers and our internal operations.

Splunk Enterprise Security Essentials has contributed to a reduction in analyst burnout or fatigue by addressing the issue of receiving thousands of alerts, with nearly half being false positives, which creates a psychological burden and desensitizes analysts to warnings.

The integration of threat intelligence directly into our TDIR workflow helps us identify false IOCs based on external data, normalizing and correlating it with our internal networks, with Splunk Enterprise Security operationalizing TI feeds through highly structured workflows that manage multiple threat feeds effectively.

Over the course of using Splunk Enterprise Security, it has helped us grow our business and attract more clients due to its low mean time to respond and various analytic engines that help us address threats daily, resulting in positive customer feedback and satisfaction.

The most useful features of Splunk Enterprise Security are the data handling, schema flexibility, correlation rules, threat detection engines, and log search capability, which makes it easy to find logs among lots of data, as well as customizable dashboards and risk-based alerting, among other features.

These features are valuable because they help us daily find logs related to our customer requirements and provide reports based on that, making it easier to find data for devices such as networks and Windows.

The most benefits from using Splunk Enterprise Security are the drastic reduction in alert fatigue, rapid incident triage, the ability to find a particular log for specific devices, unified security workflows, data flexibility, instant mapping to security frameworks, and correlation rules, along with anomaly-based rule detection and threat hunting that help us on a daily basis.

These benefits are very important for my users, as they help us and our customers secure our infrastructure from unauthorized access and detect spoofing, phishing, and all types of attacks, allowing us to identify vulnerabilities and patch them before exploitation.

There is not much to improve in Splunk Enterprise Security, but points such as deep learning and writing complex queries can be time-consuming, and managing multiple correlation rules can become complex over time, especially with high volumes of log data that can affect performance.

I have been using Splunk Enterprise Security for almost three years.

Regarding stability, we have not faced significant challenges with Splunk Enterprise Security so far, though we have had some minor issues due to service failures, which were resolved without major threats. Its reliability is strong, especially after the visual redesign that helps prevent critical signals from getting lost.

I rate the scalability of Splunk Enterprise Security as nine out of ten based on my use cases and observations.

My experience communicating with technical support has been very good, as we quickly receive resolutions from them.

The AI-driven detections and assistance have improved the accuracy of my investigations.

Splunk Enterprise Security is very helpful in triaging and raising alerts before they reach SLA times, which helps us reduce the mean time to respond.

I estimate that we have reduced the mean time to resolve by around 40 to 70%.

Splunk Enterprise Security has helped reduce my team's average mean time to detect by around 50 to 70%, overall for threat detection and alert detection.

Regarding risk-based alerting, it helps us identify true positives and false positives, effectively eliminating alert fatigue; we rarely get false positive alerts, as RBA assigns a risk score to user devices and alerts analysts only when an asset accumulates enough risk score from different systems, exposing advanced persistent threats that traditional SIEM rules miss.

The threat topology or MITRE ATT&CK framework features help us easily identify unauthorized persons and attackers' tactics and techniques used to gain unauthorized access to our data center, making it easy to analyze active correlation rules and identify blind spots.

Splunk Enterprise Security helps us detect threats faster due to its advanced rule-based alerting and anomaly detection, allowing us to catch threats before they impact our services and servers.

I estimate that we can detect threats about 30 to 40% faster compared to traditional SIEM services.

I participated in the initial setup of Splunk Enterprise Security, working with numerous device installations in Wazuh and Splunk Enterprise Security, including network devices, servers, and cloud services.

To set up Splunk Enterprise Security, we need to install Splunk Enterprise Security on the server, share logs with the forwarder, and then receive logs from the forwarder.

I faced some challenges specifically with the AWS integration during the initial setup.

I did not participate in the decision-making process for Splunk Enterprise Security, but I highly suggested it for small businesses seeking a low-cost solution.

I did not have any other options besides Splunk Enterprise Security.

I consider Splunk Enterprise Security to be an affordable solution given the capabilities it offers; for organizations with predictable data environments wanting certainty in cost, it is a worthwhile investment. I rate this review as a nine out of ten overall.

Amazon Web Services (AWS)

I work with a couple of security solutions as well as devices. We have companies such as IBM, Splunk, QRadar, and many other SIEM solutions. I have worked with technologies such as DLP firewalls, proxies, file transfer solutions, and monitoring via security monitoring solutions. I am from a security analyst background.

Regarding Splunk Enterprise Security, we have both this product and Splunk as a SIEM solution with us.

Regarding Splunk's real-time capabilities, I have been using it from the monitoring perspective. We have been onboarding our customers over to the Splunk platform, gathering log details from the security monitoring perspective, and building alerts over the Splunk platform. It serves as a SIEM solution and SIEM provider by Splunk. Splunk is one of the most powerful SIEM platforms due to its flexibility, scalability, and advanced search capabilities as it uses the SPL language.

Splunk has interactive dashboards with cloud detection and cloud integration platform capabilities, having their own built dashboards which help to get all details with the VPC flows and AWS data, showing how much data has been thrown, what the detections and vulnerabilities are, and we can easily access that information.

From our security monitoring perspective, the most valuable features are the dashboards. Splunk has a wide variety of dashboards and widgets available so I can monitor ROI, MTTD, and MTTR, which are required to adhere to SLAs with respect to clients. Splunk Enterprise Security also has valuable features such as the Splunk Processing Language (SPL), enabling analysts to perform advanced threat hunting, incident investigation, and log analysis over massive data sets for longer durations in real time. It helps create custom detections and rapid investigation queries.

Splunk Phantom with automation setup helped us reduce MTTD and MTTR time significantly. The automation ensures that detections get automated and notified to customers quickly. We have been positively impacted with the Splunk setup regarding automation and detection.

Splunk detects threats in real-time using the Splunk Query Language and helps with reduced MTTD and provides higher efficiencies. AI facilitates generating investigation queries without manual crafting. Interactive dashboards assist with retention, allowing analysts to prioritize alerts and start investigations quickly. The SOAR helps automate alerts and manage ITSM incidents, reducing MTTD and MTTR. UBA adds visibility to abnormal behaviors of users, and we have detected impossible travel incidents in near real-time and contained unauthorized attempts.

Regarding Splunk Enterprise Security improvements, I think there should be licensing flexibility, including cost optimization for larger data volumes. Additionally, for new users, the SPL language can be difficult. Practical examples provided within the dashboards or the query sets of datasets should be presented.

Regarding the pricing aspect, more licensing flexibility is needed. Splunk provides licensing based on data volume. If data peaks are above average, extra charges can occur. This should be optimal based on averages.

I have been using Splunk Enterprise Security for three years.

Splunk Enterprise Security is stable. They have been pushing upgrades frequently, and this has remained stable as well.

Splunk has continuously helped in terms of any issues or outages, helping us troubleshoot and having troubleshooting calls on a priority basis. They act according to their severity tags.

We have been having positive ROI. Time spent on log analysis and threat detection is less, and centralized multiple security tools have improved analyst efficiency. We have reduced our MTTD by about fifty percent with real-time detections.

Splunk Enterprise Security has been helping us in terms of AI and detection quality. We have improved fine-tuning and reduced false positives. There have been no false positives in the environment, helping focus on true positives more.

Regarding risk-based volume, Splunk generates alerts based on risk and we focus on particular incidents. We have received positive feedback about RBAs helping with quick investigation and remediation. The Threat Topology helps with incident categorization and severity mapping. Minimal efforts bring content packs into production, requiring little fine-tuning.

I would rate this review a nine out of ten.

Public Cloud

Amazon Web Services (AWS)

My main use cases for Splunk Enterprise Security are detections and incident response.

An example of how these features have benefited my organization is that risk-based alerting has transformed our ability to reduce the number of detections that we have, streamline our observability into risks and threats in our environment, and really focus our analysts on actual real problems, helping to remove the noise and false positives to a large degree. It frees us up to do actual work.

The features of Splunk Enterprise Security that I prefer the most are risk-based alerting, the new Mission Control, and the integrations that are coming into place between Mission Control and Splunk SOAR.

Splunk Enterprise Security could be improved by having better role-based access controls. We need to be able to better control who can do what, which people can be allowed to take certain actions, run certain playbooks, or view specific items, and separate things between teams.

I have been using Splunk Enterprise Security for about 8 years.

I evaluate customer service and technical support as fantastic. Technical support is some of the best that I've worked with.

I work with a lot of different vendors, and Splunk support is very responsive and capable. They have very knowledgeable people who can deep dive into the details and understand the inner workings of the platform without having to engage developers or back-end people all the time; they can just deal with it because they know what they're doing.

Positive

I have also used Google Chronicle and the Google SecOps platform. The factors that led me to consider a change included the lack of maturity in the other product and the maturity of Splunk. Google SecOps doesn't have anywhere near the capabilities of the Splunk ecosystem.

The search capabilities in Splunk Enterprise Security, and Splunk in general, are far superior to the search capabilities in Google's products. Their automation platform was extraordinarily immature. It doesn't have many of the basic capabilities that you would expect in an enterprise-class platform, and Splunk does have that. The Splunk capabilities were just vastly superior.

I would describe my experience with deploying Splunk Enterprise Security as fairly straightforward.  We have detection engineers who know what they're doing, and so learning the detection platform in Splunk Enterprise Security was quick for them to pick up. Even those who were not familiar with Splunk Enterprise Security to begin with were able to pick that up quickly.

I have seen a return on investment with Splunk Enterprise Security.

I would rate it an eight out of ten.

Hybrid Cloud

Amazon Web Services (AWS)

The main use of Splunk Enterprise Security in my organization is for threat hunting activities, digging through logs by doing statistical searches and, as a result, having the ability to get results fairly quickly so I can then chain together searches or cross-reference information.

For example, I get bulletins with indicators of compromise from a vendor or an entity, a public administration in France, and then I search for the IOCs and from there, step by step, starting from that information I find, I cross it with other information to know, typically, whether the IOC that was found means that the user was compromised. Did the user go all the way, and what is the root cause of the malicious activity?

I am in pre-sales, so it is mainly for demos.

Splunk Enterprise Security was a leading platform and so I was able to address many clients with it. Because it is at the top right of the Gartner quadrant, it is a platform that is recognized by a lot of people, both in the technical world and among high-level decision makers.

Overall, when I move from a solution that is not a leader at all and with which clients encounter problems, I can then show that Splunk Enterprise Security addresses these issues in different ways. Splunk Enterprise Security is a platform that justifies its status as a leader.

The best features that Splunk Enterprise Security offers are the ability to search quickly and to get results quickly when I run a search. The ability to deploy on-premise, cloud, IaaS overall, and a platform that is very open, where I can do pretty much whatever I want on the dashboard side, rule creation, or really other behaviors.

Overall, when I compare with other products like IBM QRadar, when you run a search, you have to wait one hour, two hours to get results. With Splunk Enterprise Security, I get a result in less than three minutes, so that allows me to be much more efficient in my work.

There are many modules in Splunk Enterprise Security that allow me to improve operational resilience. There is AI, which allows me to anticipate attacks with the Machine Learning Toolkit module, the approach with weak signals, risk-based analysis alerting. These are features that many other solutions do not have and that allow me to be much more efficient in the operational management of alerts.

There is a lot to say regarding how Splunk Enterprise Security could be improved. Overall, it would be to have detection content that is truly effective and operationalizable and not just content that is available in Enterprise Security Content Update or in Splunk Enterprise Security, but content that is really mature for certain use cases that are difficult to manage in a production environment.

I have been using Splunk Enterprise Security for seven years.

In my opinion, Splunk Enterprise Security is stable.

Regarding the scalability of Splunk Enterprise Security, I would rate it as very good because in a cloud environment, as for on-prem environments, I do not really have an opinion; I have not been confronted with that.

I was using IBM QRadar before Splunk Enterprise Security because there were many negative aspects to that solution and it is no longer supported today.

I am not at the stage yet of having measured everything related to ROI with Splunk Enterprise Security.

Regarding pricing, implementation cost, and license management for Splunk Enterprise Security, I find that the licenses are expensive. Compared to other competitors who do broadly the same type of management and are cheaper, it is also harder to be more competitive when selling Splunk Enterprise Security. That is one of the negative points, even if Splunk Enterprise Security is still recognized.

I evaluated other options before choosing Splunk Enterprise Security, but I cannot disclose them.

For others considering adopting Splunk Enterprise Security, I advise to build a lab, test it, play with it, and build up your skills on it; it is a very good solution. Splunk Enterprise Security is a very good solution, and I have no other thoughts or points to share about Splunk Enterprise Security before we finish. I would rate this product an eight overall.

Hybrid Cloud

Amazon Web Services (AWS)

My main use cases for Splunk Enterprise Security are event correlation and risk-based alerting.

The features I appreciate most about Splunk Enterprise Security are the different domains they have and the intelligence that comes along with each of those dashboards, being that single pane of glass for analysts to go in and look at. Splunk Enterprise Security has helped improve my organization's business resilience.

We use Cribl to pull data in and get it optimized before it hits Splunk Enterprise Security as far as collection. I have not done much customizing, developing, testing, deploying, and refining detections in Splunk Enterprise Security yet; we started off with just getting data in, and now we are at the point where we are starting to look at detections.

In Splunk Enterprise Security, I do not use risk-based alerting as much as we should. That goes back to the whole time issue, as we need to teach people what to do with it and how to tune them, and we do not have enough time in the day.

As for improvements to Splunk Enterprise Security, we will see how ES 8.2 looks. It is hard to say. We just found out about a bunch of changes, so it is difficult to make specific recommendations at this point.

The most significant challenges I face when using Splunk Enterprise Security for advanced threat detection include not having enough time to be in it, the resources and people to also be in there, and trying to configure it and teach people how to use it. A lack of resources prevents us from giving it the attention it needs.

I have been using Splunk Enterprise Security for two years.

I would assess the stability and reliability of Splunk Enterprise Security as good, as I have not had any issues with it. I have experienced downtime, crashes, or performance issues with Splunk Enterprise Security only once or twice when we have had to restart our Splunk instance, and it has taken three minutes and come right back, so nothing major.

Splunk Enterprise Security has not hit the point yet where we need to scale; we are still at the initial ingestion phase. We are in the process of expanding usage for Splunk Enterprise Security; we have not actually done it yet, as we are still planning and trying to get other teams involved while meeting their use cases, so we are probably a month away from that.

I would evaluate customer service and technical support for Splunk Enterprise Security as far better than anything else, giving it an eight out of ten, thanks to the response times they meet. When going to our account representatives, if we need something, they are always responsive and we get whatever we need.

Positive

The deployment was easy since we're cloud-based. We didn't really didn't have to do anything.

I have seen ROI with Splunk Enterprise Security. Just getting data in and being able to use the data and making sure it is compliant and mapping it to data models is far more efficient than any other SIM I have had experience with.

My experience with pricing, setup costs, and licensing for Splunk Enterprise Security is straightforward and self-explanatory. We are ingest-based, so we are not compute-based, making it pretty simple to get everything in without worrying about pricing.

Factors that led me to consider the change include shifting to a cloud-based solution at an affordable price and moving to something that is going to help reduce time spent on alerts and maintaining the system, with maintaining the system being probably the biggest reason since shifting to the cloud.

For the future of Splunk Enterprise Security, I would want the Edge Processor to be able to send to multiple destinations rather than just Splunk, though that is more about Observability.

The advice I would give to other organizations considering Splunk Enterprise Security is that everybody wants to drive a Ferrari, so get the Ferrari of SIMs.

I rate Splunk Enterprise Security ten out of ten.

Public Cloud

Other

My main use case for Splunk Enterprise Security is utilizing the correlation searches in the SOC environment that I work in to triage events.

A quick specific example of how I use it to triage events is that recently it helped us in a lateral movement case where we set up the correlation searches to detect lateral movement using the different telemetry and logs that were available. We were able to determine if it was a false positive or not through that capability.

Splunk Enterprise Security has positively impacted my organization greatly; without it, I don't even know how we had a SOC previously.

Since using Splunk Enterprise Security, I have seen specific outcomes and improvements such as our mean time to detection and mean time to mitigation substantially decreasing, and it has helped a lot with the team as well. The SOC analysts who used to have alert fatigue don't experience that as much anymore.

Some of my favorite features that Splunk Enterprise Security offers are the dashboards that it has available. What I appreciate most about the dashboards is definitely both the visualizations and the way that we customize them. We are able to customize them for our environment and then for the individual customers that we support as well, and taking all that data and being able to view it on the screen and make sense of it is the best.

We set up the custom correlation searches ourselves, which has been really helpful because previously we didn't have any correlation searches—it was just out-of-box searches that were set up, and then we were able to build it out to our environment, specific to the data that we have visibility into.

Splunk Enterprise Security's Risk-Based Alerting has positively impacted my alert volume and analyst productivity, as the metrics that it uses for RBA have been very helpful for us in being able to prioritize alerts, resulting in a substantially smaller alert volume compared to what it used to be, allowing analysts to be very productive.

The native integration with Splunk SOAR in Splunk Enterprise Security 8.0 has been excellent; we have set up a lot of playbooks.

Splunk Enterprise Security's accuracy and reliability of output is very accurate; I haven't noticed any errors.

Splunk Enterprise Security's AI capabilities are great, and a lot of the AI capabilities that are automatically built into it are excellent.

Splunk Enterprise Security can be improved by providing more visualizations, and if we have workflow actions that can be set up with it to help with OSINT, that would be a lot better.

I have been using Splunk Enterprise Security for over eight years.

Splunk Enterprise Security is stable.

The scalability of Splunk Enterprise Security is great.

The customer support for Splunk Enterprise Security is excellent; they have been very helpful, and it's one of the things I love the most.

We previously were using Elastic, and now we're using Splunk.

I have seen a return on investment in that time has been saved for the analysts and their workload has gotten a lot lighter.

My advice to others looking into using Splunk Enterprise Security is to not wait; implement it as if it is necessary and you needed it yesterday.

I love using Splunk Enterprise Security; it's one of my favorite tools, and I think it's needed in every single SOC environment. I have been using it for years, and every time that I've switched jobs, I have been an advocate to try to get them to bring it on.

Splunk Enterprise Security has helped improve my organization's business resilience. Splunk Enterprise Security has helped reduce my team's average mean time to resolve metric, although I'm not certain by how much.

Hybrid Cloud

Amazon Web Services (AWS)

My main use case for Splunk Enterprise Security is log analysis and incident response.

I use Splunk Enterprise Security to review logs and see additional information about traffic at the firewall, which users are associated with which IP addresses, and what devices they used. Additionally, I use it for hunting through the analyst dashboard to review quarantined email and conduct foreign travel analysis.

The best features Splunk Enterprise Security offers include data visualization, accurate logs, and an excellent user experience.

The dashboards and how they are set up are very useful for analysts on the watch floor because we can pull a lot of data very quickly. The Analyst Dashboard is the best in my opinion, particularly for hunting activities where I conduct analysis of quarantined email and data breaches.

Splunk Enterprise Security impacts our organization positively because we can see traffic associated with incidents and triage alerts in real time very quickly, and everything is very organized. It is very user-friendly for our analysts to view the data instantly.

My team has reduced the number of missed alerts, especially when using different indexes to pull logs. We are able to see if there are any outages quickly and determine where to start remediation.

I am not sure how Splunk Enterprise Security can be improved right now. I believe it is doing us a lot of good and is really helpful, so I am not able to speak on how it can be improved at the moment. Nothing comes to my mind about areas where Splunk Enterprise Security could be improved.

I have been using Splunk Enterprise Security for two years.

I find Splunk Enterprise Security stable.

Splunk Enterprise Security's scalability is probably good, and it has a lot of potential, especially with a new SOC environment.

Customer support is great with no issues.

I would rate customer support a 10.

Splunk Enterprise Security has definitely helped us save time. It has helped us tremendously with preventing breaches of SLA on incidents and tickets as well as with ticket volume and log analysis. The main benefit is the SLA, which I have not breached in a very long time.

Splunk Enterprise Security has really tremendously helped with SLAs and reaching those without breaching them every month. We actually have not had any breach of SLAs in a very long time, and I believe that is due to a lot of the capabilities of the tool.

I would tell others looking into using Splunk Enterprise Security to stay open-minded, continue learning, and go to trainings because even if it seems very complicated at first, it does have the potential to really help with metrics, especially in terms of SLA and analysis. I would rate this review a 9.

On-premises

The typical use case for Splunk Enterprise Security is to meet regulations and requirements for critical infrastructure. It is used to audit changes and authentication logs. The second purpose is for security operation center management and security management.

The most valuable features of Splunk Enterprise Security are the main component, which is the correlation engine that can specify detailed conditions such as how many events there need to be, what notification I will get, and if I get it per event or one per batch. 

There is also throttling; in basic Splunk, there is no throttling at all. In Splunk Enterprise Security, there is an additional layer of control of these alerts. I appreciate the correlations and the alerts in that product.

The asset management is particularly useful. We can enable asset lookups to show in every event. We define one, and it will translate to all events, allowing asset management to be easy. 

Splunk Enterprise Security helps to reduce alert volume because the language is similar to SQL with Google-style functionality above it. We can use these terms to specify what is in the allow list. We can specify what's in lookups, what should be there, and what's not. It definitely helps to reduce the numbers of full score.

Splunk Enterprise Security helps to speed up security investigations. When the finding is created, there are many correlations. You can quickly see what asset it is, what identity is involved, and you see the historical progress of what happened. Right from the findings, you can call VirusTotal and other resources, which is definitely helping.

I assess Splunk Enterprise Security's insider threat detection capabilities for helping to find unknown threats and anomalous user behavior as great. It regularly checks new events through the correlation search and compares them with threat intelligence. The threat intelligence is refreshed regularly, downloading new threat information. Splunk has a special research team for security content and intelligence, which distributes its own threat list to Splunk Enterprise Security.

It's great for finding anonymous threats. It checks new events and also works with the latest threat intelligence. At least once a day, it develops new threat information. In Splunk, there is a special research team. They are also distributing their own threat lists. The solution is capable of very good threat detection.

In basic SPL, with the Splunk query language, we can detect brute force without threats. It scans every event, and if it finds patterns, IOCs, it can trigger notable events, which are now called findings. The new version includes an internal Git repository, so when the SOC team makes improvements to the correlation search and makes changes, it automatically keeps a history of that correlation search, what was changed, when, by whom, and you can revert if it breaks.

The value that Splunk Enterprise Security offers in resilience is vital. It helps customers distributing gas across the Slovak Republic, ensuring that critical infrastructure, such as operational pipelines, are running. If there were an outage that delayed recovery, the economic impact could be significant. 

It's good for analyzing malicious activities and detecting breaches. The interface sometimes can be very essential.  

Splunk has helped us reduce alert volume. We can use terms to specify what is whitelisted and we can search like we would on Google. 

We've been able to speed up security investigations. We a finding is created, there are many correlations. You can quickly see the asset, the identity involved, the history, et cetera. 

Splunk Enterprise Security can be improved mainly from the user interface regarding the visualizations. They are working on it, yet there are only five to ten very basic visualizations. When you have your data all set and the customer wants some new dashboards that would help them, it is pretty complicated to build them from the built-in visualizations. 

This is one of the blocking points in Splunk, however, they're working on a new layer called Dashboard Studio. It is still limited. An older version of Splunk allowed implementation of JavaScript to capture events when a user clicked by mouse, which enabled great features. In the improved Dashboard Studio, this is not possible. They have improved one part and have made the other part worse, so it still lacks a premium feeling. Cisco will improve it, however, it seems they are focusing on what the big companies want. They will implement it if it's usable for these big players that pay, but for small companies, it's too pricey to use this solution.

I've been working with this solution for seven years.

The stability of Splunk Enterprise Security is very impressive; it is a very stable product. They handle these things perfectly and conduct internal testing thoroughly. 

They test it very thoroughly before release, and our customers have Splunk running for months without issues. 

When I observe how customers work with Splunk in the cloud, it is also very good. They manage maintenance windows and inform customers, resulting in little to no interruptions to workflow. In terms of stability, I would give it a full score.

We work with medium to large organizations. Our typical environment has 500 servers. In volume, we're looking at 100GB in storage. From Splunk's view, we're doing rather small volumes. It's big in a Central European context, and small from a Splunk North American context. It can be pricey for small companies. 

I would rate technical support from Splunk Enterprise Security as a six out of ten. 

It's average, considering it's a very big product, and they handle several hundred tickets a day. I have opened 20 to 30 cases, and they helped me with only three to five of them. They try to close issues as soon as possible, often just offering documentation links. 

Even when I provide them with the core problem, they do not help much. The customer often has to rely on workarounds, custom scripts, and solutions which are somewhat lacking.

Neutral

Before Splunk Enterprise Security, I didn't use a different solution; this was my first job, and I started working full-time with Splunk about eight years ago. 

In the beginning, when they were testing, I was shown the OP5 and Nagios operating monitoring; we used tried them out, however, they were not really security-related.

You can quickly set up Splunk by downloading the package, unpacking it, and starting to work. It's straightforward to get a quick view of your data, and you do not have to worry about connections to databases; it will start parsing the data as soon as you hand it over. For bigger environments with several hundred servers, Splunk Enterprise Security is the best solution.

Customers see the value in investing in this solution, particularly when it helps resolve issues quickly, turning a potential 20-hour response into one hour.

It's still pretty pricey. It's an expensive solution for smaller companies. 

That said, if someone evaluating SIEM solutions wants to go with the cheapest solution, Splunk Enterprise Security is a very good option. It has difficulties in administration and setup, however, in comparison with other products, it's still a great platform.

My relationship with Splunk is that we are a partner and reseller partner. My organization does not monitor multiple cloud environments; we primarily monitor M365 and Azure environments from cloud products. We use the Microsoft Add-on for Splunk to read Exchange and Microsoft audit logs from the cloud. However, we still prefer on-premise solutions in our country.

We use the Mission Control feature. It's replaced another component. I don't use it too much myself. It's like a connector for SOAR. We're investigating its capabilities and have not implemented it fully.

Overall, I would rate Splunk Enterprise Security a nine out of ten. If you want to see your data quickly and in full view, it's very good - specifically for bigger environments.

On-premises

Microsoft Azure