The main use case for Sumo Logic Security is as a SIEM platform where our customers prefer it to gather logs from multiple places and have good detections, especially Sumo Logic insights, which is helping us a great deal to detect and correlate logs from different platforms and consolidate them into one insight. It helps for investigation and analysis. The major part is threat detection and threat analysis.
Logs for Security (AWS Built-In)
Sumo Logic Inc.External reviews
External reviews are not included in the AWS star rating for the product.
Automated threat insights have reduced detection time and improved SOC investigation efficiency
What is our primary use case?
What is most valuable?
The best features of Sumo Logic Security are automated log and event correlation, which may come from a firewall event, and User Entity Behavior Analytics (UEBA) for detecting impossible travel and unusual access times. Threat intelligence enrichments are good, and the MITRE ATT&CK framework is beneficial. The centralized log search for investigation is better compared to multiple SIEM solutions, where I can query everything in one place. The SEC records feature, something that returns index=sec_records, provides all the logs from different places. Pre-built dashboards and analytics, especially threat trends and the anomalies that return compliance patterns, are valuable. The workflow, including playbooks and workflows, can be triggered when we need to quarantine an endpoint, revoke credentials, or block IPs. Most importantly, it is cloud-native and has elastic scale. As a cloud-native SIEM, it scales up very well automatically, and real-time threat detection is available.
One of the most important things is MTTD, which is faster threat detection that reduced our MTTD, and we were able to detect alerts with multiple detections that used to take hours. Now the correlated alerts surface the real threat very quickly. Detection time has dropped significantly. We used to have MTTD of three to four hours, but now it is under 30 minutes. Automatically, our mean time to response has also increased substantially. Analysts are able to quickly pivot items and make faster decisions, especially without switching between tools. We have all our EDR tools and firewalls integrated to the same platform and viewing everything there. As a SOC, which faces major problems, it reduced the alert fatigue by over 100 days of low volume alerts, which have been made into insights, and this has greatly improved our alert efficiency and decision quality, the way we are able to enrich information. Operation stability has also improved very much. It has significantly impacted our organization, and our KPIs have improved substantially with respect to this.
What needs improvement?
If I want to mention anything related to Sumo Logic Security, I would say that with the current AI situation, AI enrichments should be very well integrated. I saw something in insights that it is doing something around 14 days of correlation, but I would prefer something around seven days would be better. Sometimes we see alerts coming from a different time frame. In some places, correlation could be much better in Sumo Logic. There is a scenario where we see five to six employees from the company log in from the same IP address, which is a shared IP address. Maybe one employee has login failures, perhaps because they forgot their password. In this situation, Sumo Logic gives us an alert saying that a brute-force alert was detected or a credential compromise was detected, stating that five people have successful logins and one user has a bad password. This is not practically correct detection. They should be doing some kind of better analysis, such as a historical analysis of this IP, to make it clear that this IP is a shared IP, so the logins that happened for all other users are normal. Sumo Logic has the capability as a modern SOC to include behavior correlation or attack chain visibility, which would be a great addition to reduce false positives. Good dashboards with AI capabilities would also be more helpful.
Since our product is also AI-based, something where they can focus more on AI with the possibility of detection engineering, writing custom correlation rules, and tuning detections to make more valid true positives would be beneficial. I have experienced some situations where false positives occurred. There can be more improvement in MITRE ATT&CK mapping, especially, as it helps us measure coverage gaps and where we are positioned. Beyond that, SOAR capabilities with automation focus should include more enrichments into the detection part and provide higher levels of true positives overall. When I compare Sumo Logic Security with other solutions like Splunk, Azure Sentinel, or Sentinel One, these are improvements I would expect to see.
Automation should be improved further. As we move to AI SOC, there is talk of automated multi-step response workflows where playbooks should be enriched for logs of different activities based on IP, user, user agent, or other fields. More advanced playbook-based correlation should be coming up with a set of rules that can help detect real true positives. Rich incident response playbooks and better integrations with ticketing tools would be beneficial so that we can take quick actions if a breach has been identified. Advanced attack path visualizations would be helpful. Creating a good attack graph showing when something has been detected, how quickly it has been investigated, what the timeline of all these activities was, and including entities such as user, host, network, cloud, or indicators of compromise would be valuable. Built-in threat group playbooks would be very helpful, whether for ransomware, account compromise, or data exfiltration. AI-driven threat insights at the automated flow of investigation would be more helpful. Sumo Logic Security is very good at role-based access controls, and we were able to manage that very well without any issues. Advanced attack path visualizations and built-in threat group playbooks for ransomware, account compromise, or data exfiltration scenarios would enhance the platform significantly.
For how long have I used the solution?
I have been using Sumo Logic Security for the past four years in my previous two organizations.
What do I think about the stability of the solution?
Sumo Logic Security is stable. It operates very well as a cloud-native SaaS platform with high availability, and there is no downtime that I have experienced. Sometimes we had API integration issues, but the platform scales up automatically without any performance degradation, especially with large volumes of logs without any failures in ingestion. This is something that I have seen be difficult in other places. It does not require any hardware and patch management, which is another good thing for being stable. These are some of the reasons why I would say it is stable.
What do I think about the scalability of the solution?
Sumo Logic Security scales up automatically because it is a cloud-native SIEM, and I do not need to worry about hardware clusters or capacity planning. The platform grows as security data grows. Real-world ingestion limits, cold versus hot data performance, and retention implications on the cost and query performance under high load are all handled very well. It supports business growth, as when the company grows, security analytics also grows with more servers, more users, and more applications, but without infrastructure headaches. Onboarding is something that I need to mention as well. I can ingest identity logs, endpoint detections, or any type of logs without worrying about underlying capacity. I was able to ingest all types of logs with Sumo Logic Security. In other platforms, we faced some challenges with complexities, especially in terms of handling the hardware part as well.
How are customer service and support?
Support for Sumo Logic Security is good. We have had a couple of issues, especially with the technical support team troubleshooting problems, particularly around API integration issues, but they had a faster response time. I would score them around 9 out of 10. Direct support includes documentations, tutorials, and training access along with community forums, which helps us resolve many questions independently without reaching out to them. Where we have faced some challenges, I would say it may be because of region-specific support in India or Europe, as some support times were slower. Some tickets even took two weeks when we were finding issues with email-related matters. Everything else is good because their documentation is very helpful and querying is also very good. They have a limited direct call option for support, but the response is good, and technically they will explain everything we need to do. Premium support is also available. The customer support is very good with them, and the documentation is helping us to fix issues today.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We used Devo and Splunk before Sumo Logic Security. Due to our organization's budget platforms and other factors, we switched to Sumo Logic to have our SIEM. We used to face challenges before, such as storage clusters and scaling issues, and the detection part was very much worse in other SIEMs. I may not give specific details, but Sumo Logic insights are playing a major role today in our investigation and reporting parts. I have used Splunk, Devo, and even ArcSight.
What was our ROI?
As I mentioned, we have 100% return on investment very well. I have experienced that we used to have over 100 alerts where we needed eight analysts, but now we are able to operate with five analysts because the time drop in investigation has been from 20 to 40 minutes. We have saved 64 hours of our time overall. Before we used to have eight analysts, now we have at least five analysts and we are able to do the work completely. We have a good return on investment in terms of even the log retention part as well.
Which other solutions did I evaluate?
We have not typically evaluated other solutions as alternatives. As I mentioned, we used Splunk, Azure Sentinel, and Devo. We directly switched to Sumo Logic Security as per our organization's needs. We had used different SIEM platforms as well.
What other advice do I have?
I would say to define especially what problems they have, particularly the threat detection part, incident response part, reporting part, cloud security monitoring, or insider threat analytics. They need to plan their log strategy about how much quality versus quantity they require and send only meaningful logs while filtering out debug and low-level information that makes noise. Categorizing the logs by priority is one of the most important things. Using something with very much tiered retention periods is helpful because Sumo Logic Security provides pre-built dashboards, correlation rules, analytics, and threat intelligence feeds. That is going to be helping. I would recommend investing in training, as good training helps the team write more effective queries, build custom correlation rules, alert tuning, and perform threat hunting. These are things to focus on, which especially help the organization. Measure metrics as well, such as MTTD, MTTR, false positive rate, analyst hours worked, and threat signals escalated, as these are outstanding for Sumo Logic Security.
Regarding additional thoughts about Sumo Logic Security before wrapping up, I would mention improvement in the detection part with AI integration regarding log summarization and advanced analytics, which should be part of the roadmap. Also, how Sumo Logic Security is going to handle scalability, such as onboarding different data sources or tuning alerts. The major direction I am interested in seeing is how Sumo Logic Security will move forward with AI-based SOC capabilities, as that is the next era of SIEM tools. I would give Sumo Logic Security an overall rating of 8 out of 10.
Flexible Record Analysis with Clean, Shareable Dashboards
Great Log Search, Overall Solid Experience
Modern security platform has reduced alert fatigue and supports a small SOC across multi-cloud
What is our primary use case?
Sumo Logic Security encompasses all three areas: SIEM, SOAR, and log management.
What is most valuable?
Sumo Logic Security offers excellent features including ease of use. I came from a competing product, Splunk, and I was able to recycle a lot of the knowledge from that tool into Sumo because the logic was very similar.
Beyond the ease of use, the consumption model of Sumo Logic Security is also easy to understand, which was helpful. The build-out with Sumo was very good, as they spent a lot of time ensuring that we were sized correctly for the product, and the follow-ups were good. Sumo Logic Security has really good customer support.
The capabilities of Sumo Logic Security in providing security visibility across multi-cloud and hybrid environments are very good, particularly because Mambu is still a multi-cloud vendor, and the product worked extremely well in that scenario.
Regarding the automated TDRI workflows in Sumo Logic Security, they are excellent. I would put them at the top because they are truly useful and actually work as advertised.
My experience with Sumo Logic Security has been good. My SOC analysts were crushed under Splunk, but Sumo has actually eased the workload and made it tolerable for three people.
The improvements or benefits I have seen from Sumo Logic Security relate to alerts. We were buried under alerts and Sumo actually helped us clean that up. The number one value is being able to action things in a proper time frame.
What needs improvement?
A more transparent roadmap as to what Sumo Logic Security is trying to achieve would be beneficial. Sumo often gives information in three-month cycles, which makes it hard for planning purposes.
For how long have I used the solution?
I have been using Sumo Logic Security for about a year and a half.
What do I think about the stability of the solution?
In terms of stability, Sumo Logic Security rates a ten; it has been up.
What do I think about the scalability of the solution?
Regarding scalability, I give Sumo Logic Security a nine. I have yet to run into an issue with scalability, but we really have not tested it.
How are customer service and support?
The build-out with Sumo was very good, as they spent a lot of time ensuring that we were sized correctly for the product, and the follow-ups were good. Sumo Logic Security has really good customer support.
The interactions have been extremely good, and the account team is great, so I never feel as though they just forgot us.
I rate the technical support for Sumo Logic Security a nine.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I came from a competing product, Splunk, and I was able to recycle a lot of the knowledge from that tool into Sumo because the logic was very similar.
When comparing Sumo Logic Security to Splunk or other vendors, the models are vastly different. Sumo's consumption model is easier to understand, while Splunk's is much more complex. Additionally, the Splunk service was not really fit for the size of our organization, which was about 1,000 people as it was a much more robust solution for something larger.
How was the initial setup?
The initial deployment of Sumo Logic Security was complex, but working with Sumo made it very easy.
It took three months to deploy Sumo Logic Security.
What about the implementation team?
I do use the SOC analyst agent for alert triage. I have three SOC analysts.
What was our ROI?
The return on investment I have seen with Sumo Logic Security in the past year and a half is tough to quantify, but I would estimate it has hit the milestones we set internally for return on investment, as we have not looked at the product and said it is not paying for itself.
What's my experience with pricing, setup cost, and licensing?
When it comes to pricing, I would say Sumo Logic Security is in the upper middle-class tier. It is not expensive, but it is not inexpensive, sitting between those two.
From one to ten, where one is cheap and ten is expensive, I would put Sumo Logic Security at a seven.
What other advice do I have?
Regarding the effectiveness of AI-driven analytics in reducing the workload and response times, it is too early to tell, as it is something that recently came out and we have not consumed it yet.
My impressions on the built-in threat intelligence feature are not bad. I would give them four out of five stars. They tend to be very good, but very specific to certain situations.
The impact of Sumo Logic Security in prioritizing alerts has been hard to quantify at this stage, as we are still trying to determine the value of that.
I could not tell you if the knowledge agent has helped improve onboarding efficiency because we do not utilize that function.
When it comes to how much time Sumo Logic Security saves, I would not say it is a time saver. It is an FTE saver. It did not really make my analysts work less in a day. They still have to work, but it avoided the need to procure more analysts to do the work.
Sumo Logic Security has probably saved us three FTEs.
Approximately 15 users utilize Sumo Logic Security.
Sumo Logic Security does not require any maintenance as it is a SaaS-based solution. We do not have to patch it, maintain it, or host it.
Sumo Logic Security was purchased through an engagement that was done pre-Marketplace, but it was purchased through Marketplace.
My advice for others looking to implement Sumo Logic Security would be three things: first, do a proof of concept because these solutions are very expensive. Second, definitely keep involved with Sumo through the entire process, making them a partner throughout the process. Third, and this is the most critical one, definitely take time to size your environments correctly because once you sign those contracts, that is the size.
I rate this review an overall eight.
Visually Powerful KPIs and Time-Saving LogReduce/LogCompare
Hands-Off Security: Instant Threat Detection and Automatic Updates
Flexible Log Management with Speedy Search
With SumoLogic you will gain total observability and visibility in your environment!
Security insights have enabled faster incident response and streamlined cross-team collaboration
What is our primary use case?
My main use case for Sumo Logic Security is relying on it for security insights when it comes to security alerts. This is heavily used by people who are on a weekly on-call rotation to ensure that security incidents from Sumo insights are actioned on and remediated.
A specific example of a security incident where Sumo Logic Security played a key role is when, about a couple of weeks ago, we had an incident where a user was a victim of a click-fix attack. Sumo Logic Security was able to determine that this user had performed some risky activity and also correlated the fact that the URL was associated with that incident. We were able to determine the involved entities, which included the user's device, and we were able to quickly action on it and perform a reset of the user's account in order to begin the remediation process.
In addition to the previous points, I use Sumo Logic Security for a lot of the enrichments when it comes to insights as well. An example of this is when we receive insights regarding a user entity, we are able to use Sumo enrichment automation to get user details including their manager. This is definitely beneficial in an example such as the one I provided earlier where a user was compromised, where we can at least know who the proper chain of command is if that needed to be used in that specific incident.
What is most valuable?
The best features Sumo Logic Security offers, in my opinion, are the ones that allow you to use dashboards as enrichments. For example, we had a situation where there was a suspected compromise on a specific server, a database server to be exact, and so we linked an enrichment action in the CSE component to then point us to a Qualys dashboard. In this specific case, the suspected server was suspected as being compromised, and we were able to check any available vulnerabilities from the Qualys dashboard itself by using it as an action in Sumo Logic Security.
We are actually using both out-of-the-box and custom rules from Cloud SIEM Enterprise, and it has been really great because we have a variety of ways to create rules based on our needs, such as match rules. What I really do appreciate are the first-seen rules that we can use in a fashion to determine a baseline of normal versus unexpected behavior depending on the entity, and I really do enjoy these.
In terms of threat intelligence, I was able to integrate, as an example, AlienVault, and using their actions, automated integrated actions into playbooks to enrich certain entities such as IPs, domains, URLs, and hashes. It has been very paramount to how we operate due to the fact we can all stay in the same single platform of Sumo Logic Security without having to reach out to different third-party sources, opening up different browsers, essentially saving time on trying to respond to an incident or review an incident. It has been really good in terms of integrating and using the threat intelligence features.
I find Sumo Logic Security's AI-driven analytics effective in reducing analyst workload and response times, and I have seen a difference since using those features. For example, we are using the anomaly-based AI detections in Sumo monitors, and I would say that it has been good, but the reason I say it could be better is the fact that we are seeing a bit of some false positives when it comes to understanding what is typical normal behavior and relying on AI to understand what normal behavior is versus what is unexpected. I found that when using this type of monitor, I do have to do quite a bit of tuning, which I would hope the AI would be a little bit more robust and essentially leave me hands-off when it comes to this.
We also use the dashboard enrichment feature in Sumo Logic Security when alerts pertain to specific entities, and we use it a lot. For example, we will get insights for server entities, and it is easy for us to pivot over to a dashboard when it comes to an enrichment perspective to determine if there are any actual vulnerabilities related to it. Another example is if we have an AWS related entity, we can pivot over using an enrichment action to navigate to one of the AWS dashboards to get some quick information pertaining to the specific entity involved in the insight.
Sumo Logic Security has positively impacted my organization by increasing engagement with different teams. For example, we have the database team being onboarded to Sumo Logic Security regarding their database logs, where they use it to monitor their database when it comes to informational all the way up to critical types of events, and they use it for alerting as well. This is due to the fact that they were not able to find any solution that can provide this type of functionality for them, and they have pivoted to Sumo Logic Security for their needs.
From this increased engagement, we are able to respond faster to incidents. For example, if they are seeing a type of activity that involves a user or an admin that is not supposed to be logging in at a specific time, they do get alerts on that. In addition to that, we are able to save time on fewer alerts because we are able to perform tuning on the logs to be able to only get relevant security-related incidents.
What needs improvement?
To improve Sumo Logic Security, I would appreciate the tool being easier to use from a search perspective. For example, we have a few teams that want to use the tool itself, but they are not as savvy when it comes to creating searches from the core platform. I understand that Mobot has come out and is in the works, and it really does assist non-savvy users when it comes to querying the platform. As far as that is concerned, I wish that could be improved a bit more, but I do know that that is in the works.
I would add that I wish for improved documentation. For example, we are using Sumo Playbooks and automation integrations along with that, but I have found that there has been a lack of documentation, very little to none at all when it comes to that. With regards to automation integrations as well, there are very few details included in them. I would also appreciate the AWS automation integrations to be more secure because currently, they are using access keys, which involves a user rather than roles, which is the security best practice recommended by AWS.
I chose eight out of ten because to make it a nine or ten, I would lean heavily on the documentation. A lot of the times when we get around to configuring things such as playbooks or trying to understand playbooks, what I found was that documentation sometimes is not up to date or documentation is lacking. There are instances also where some security best practices are not being followed. So, if we are able to set up an integration that is not only secure, following security best practices, and has complete documentation, I believe it would alleviate the issue of having to go back and forth with support to check the documentation and things of that nature.
My impression of the built-in threat intelligence feature in Sumo Logic Security is that it is comprehensive, but I would say that it could do a little bit better. For example, we have the TAXI feeds, which is STIX and TAXI integrated into the core platform, but the issue I am running into is that I am able to use that feed into a CSE alert; however, I am not able to see the contents of that feed. If I integrate CISA, which we do have integrated, I cannot see what IOCs are in that feed in the core platform, and I hope that is the case because, in order for us to better tune our alerts, we need to be able to see what is in the contents of that threat intelligence feed.
For how long have I used the solution?
I have been using Sumo Logic Security for three years.
What other advice do I have?
My advice to others looking into using Sumo Logic Security is to look at the customer service side of things. The product can be great, but if the customer service side of things fails, I think pretty much the rest follows. I would also advise them to look at the automation features, for which Sumo Logic Security has been pretty great in expanding that realm. I think those are going to be the two main things as we are moving a lot more towards being hands-off with automation and also being able to utilize support and getting timely answers. Those would be the two key factors of looking at or giving advice when it comes to Sumo Logic Security.
I have additional thoughts about Sumo Logic Security in that I do appreciate the product. It can be as vague as you want to or as detailed as you want to when it comes to getting telemetry information from the product itself. That is what I appreciate about Sumo Logic Security. Overall, I am happy with the product, just a few hiccups here and there. I provided a rating of eight out of ten for this review.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Sumo Logic for Better Alering ad Logging
Strong log ingestion, real-time analysis, and deep querying capabilities that help with troubleshooting and operations.
Built-in integrations with cloud services (AWS, Kubernetes, Jira, etc.) and dashboard customization
It handles large volumes of log data well and works effectively in cloud-native setups
Expensive
Can provide more flexible visualizations and if vconfigureation can be made easy