One thing I think Sweet Security can definitely improve is that they have a lot of features, but the UI right now is not so well designed in my opinion. It's a bit difficult to navigate and get to the signal. There is a lot of signal there, but it's a bit difficult to get to the correct place and understand what I am seeing. It has a small learning curve that I don't think such a product should have. It should be very straightforward. Sweet Security has a mechanism where they initially show all the vulnerabilities that are in my infrastructure, which they show as a huge number, maybe around ten thousand, and they narrow it down to which of these could actually be exploited and are actually severe. It's nice that they are able to narrow it down to a few incidents. However, they don't really need to show this in the UI. Maybe they can just show the actual signal and not show that there is a lot of vulnerabilities, but indicate which are important. That's good that they can do it, but it's not so important to see it every time in the platform.
Director of Security Operations at a tech vendor with 501-1,000 employees
Real User
Top 10
Sep 30, 2025
Sweet Security has room for improvement in two areas. One is for robust integration with automations and playbooks. We have our internally developed platform that operates around security incident playbooks, so the connection between those two systems would be great. The option to run specific playbooks through the Sweet Security platform would help us a lot, but these must be fully customizable. We prefer not to block the business from progressing unless we are fully sure that it is an incident. Most of the actions I would take would revolve around containment or notification on a specific platform and not via email or similar communications. The second area is around the code perspective. I know it's just the start of a long journey that Sweet Security is going to go through to become a platform that also handles code, but I would expect options for a complete analysis and writing policies for infrastructure as code. The next great thing that Sweet Security can do is to turn toward IAC, how it is handled and enforced, to tackle potential breaches of policy before they really happen.
Cloud and compute team leader at a manufacturing company with 1,001-5,000 employees
Real User
Top 10
Sep 4, 2025
There is room for improvement. We have a very close relationship with Sweet Security and have a weekly meeting where we ask for new features, which they usually respond to very quickly, including the feature we requested for a Windows Server sensor, which they created and we are currently testing. One area for improvement could be the alerts, as we have an issue with the alert time, the time it takes for the system to send the alert, but besides that, there is nothing special.
Sweet Security offers advanced cybersecurity measures designed to protect enterprise-level networks from complex threats, providing efficient monitoring and robust protection capabilities.Focused on sophisticated threat detection and network security, Sweet Security provides an enterprise-grade solution for cybersecurity challenges. It integrates seamlessly with existing systems, offering real-time analytics and threat intelligence. Its comprehensive approach ensures high-level data...
One thing I think Sweet Security can definitely improve is that they have a lot of features, but the UI right now is not so well designed in my opinion. It's a bit difficult to navigate and get to the signal. There is a lot of signal there, but it's a bit difficult to get to the correct place and understand what I am seeing. It has a small learning curve that I don't think such a product should have. It should be very straightforward. Sweet Security has a mechanism where they initially show all the vulnerabilities that are in my infrastructure, which they show as a huge number, maybe around ten thousand, and they narrow it down to which of these could actually be exploited and are actually severe. It's nice that they are able to narrow it down to a few incidents. However, they don't really need to show this in the UI. Maybe they can just show the actual signal and not show that there is a lot of vulnerabilities, but indicate which are important. That's good that they can do it, but it's not so important to see it every time in the platform.
Sweet Security has room for improvement in two areas. One is for robust integration with automations and playbooks. We have our internally developed platform that operates around security incident playbooks, so the connection between those two systems would be great. The option to run specific playbooks through the Sweet Security platform would help us a lot, but these must be fully customizable. We prefer not to block the business from progressing unless we are fully sure that it is an incident. Most of the actions I would take would revolve around containment or notification on a specific platform and not via email or similar communications. The second area is around the code perspective. I know it's just the start of a long journey that Sweet Security is going to go through to become a platform that also handles code, but I would expect options for a complete analysis and writing policies for infrastructure as code. The next great thing that Sweet Security can do is to turn toward IAC, how it is handled and enforced, to tackle potential breaches of policy before they really happen.
There is room for improvement. We have a very close relationship with Sweet Security and have a weekly meeting where we ask for new features, which they usually respond to very quickly, including the feature we requested for a Windows Server sensor, which they created and we are currently testing. One area for improvement could be the alerts, as we have an issue with the alert time, the time it takes for the system to send the alert, but besides that, there is nothing special.