Our primary use case for using Sweet Security is to have more eyes and visibility to be able to catch things at runtime and not in a static way. I believe this offers more effective control.
Real-time insights have reduced false positives and improved cross-team collaboration
What is our primary use case?
What is most valuable?
I find the UX/UI to be comfortable. The insights that it brings us are related to the business logic of our company, which is important. If something is flagged as a critical alert, this indicates that it must be observed closely.
We have used the real-time monitoring feature of Sweet Security, and this specific solution has given us real detection that helps us find what is actually important against what is not important. It saves us a lot of investigation time that isn't required anymore. It's a very good product, I'm happy we have it. We looked into the CPU consumption and it's the lowest against the benchmark.
The time savings from Sweet Security have varied, but the impact has been significant. It has reduced the need for back-and-forth discussions between teams such as Security, DevOps, and R&D. It only flags the important and critical risks. It saves developers time from looking into fixes for false positives. We use the customizable dashboards in Sweet Security. These dashboards have helped in managing our security posture by presenting all the relevant information that the security team needs to see. The correlation between the information is very efficient. They made a lot of improvements to this over the last year. It's a lot better now than it was a year ago. The insights are good.
The reporting is very good because we can customize it to what we actually want to see.
The value of having real-time visibility in our cloud environment with Sweet Security changes everything because it differentiates between identifying and reacting to something that is not really a risk and something that is truly a risk that needs to be treated.
Sweet Security has had a big impact on mitigating risks and aiding development.
What needs improvement?
The main areas for improvement are related to how Sweet Security needs to be customized
We have weekly meetings with them to discuss any improvements. We asked for tailored company OKRs. a one-page report. This needs to be improved but it's not critical; it's a preference.
For how long have I used the solution?
We’re now in our second year of using Sweet Security.
What do I think about the stability of the solution?
I would rate the stability of Sweet Security a ten out of ten, though there was something a year ago that caused a production issue in my company, but they fixed it within an hour.
What do I think about the scalability of the solution?
I would rate the scalability of Sweet Security a ten because it is very scalable.
How are customer service and support?
I would rate the technical support that Sweet Security provides a ten out of ten. Their team is awesome.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Sweet Security was part of my strategy to go with a runtime solution for all the advantages and effectiveness it offers.
How was the initial setup?
The deployment of Sweet Security was easy with no challenges. It was very quick.
The team that uses it is around 3-5 people.
What was our ROI?
Sweet Security has saved time, though I cannot estimate the percentage as it's very difficult to measure.
What's my experience with pricing, setup cost, and licensing?
I would describe the pricing of Sweet Security as fair, as it depends on the company they're working with. They're not cheap, but they're not as expensive compared to other companies. I also look at the ROI I save by removing other tools.
Which other solutions did I evaluate?
In comparing Sweet Security with other products or vendors in the market, Sweet Security is among the top two.
What other advice do I have?
The Sweet Security solution requires maintenance from our end, and we would prefer it to require less maintenance if possible.
I would recommend Sweet Security to other users based on all my previous responses, and because they succeeded in getting the biggest results during my POC.
On a scale of one to ten, I rate Sweet Security a nine.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Security updates and management become an effortless routine
What is our primary use case?
We use Sweet Security primarily for vulnerability management on all of our cloud assets, mainly AWS, but we also use it for SOC, with the SOC integration getting the events and responding to them.
What is most valuable?
The best feature of Sweet Security is that the events come in the form of stories, which are very informative, making it very clear what's going on.
The good sensor that can be installed on the servers themselves is an excellent feature.
The value we see from having real-time visibility into our cloud environment is significant. We actually came from a different tool that does almost the same, but it did not have some of the features that Sweet Security has, with the main uses being the SOC integration and addressing misconfigurations from the IT team.
The real-time monitoring feature is essential; it's a security tool that points out vulnerabilities, and once they point out the vulnerability, we address and fix it.
Sweet Security's reporting tools enhance our insights into potential vulnerabilities and threats as they serve as our eyes and ears inside AWS, telling us what we are doing wrong so we can fix it.
Sweet Security's threat detection capabilities influence our decision-making processes by providing alerts and allowing us to look at the dashboards and respond accordingly, even as a very small team consisting of just two people.
What needs improvement?
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.
For how long have I used the solution?
I have been using Sweet Security for about a year, as we signed a contract about a year ago.
What do I think about the stability of the solution?
I would rate the stability at 10, at least for the last year.
What do I think about the scalability of the solution?
Sweet Security's scalability depends on what is considered scalability. For us, we don't need to scale it since it's all SaaS, but I can say it is very easily deployable.
How are customer service and support?
I would rate the vendor support an eight, as we have a very close relationship, allowing me to contact my account manager at Sweet Security anytime, and she gets the right people involved during our weekly meetings and ad hoc meetings, making the support very good.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Previously, we used Ermetic, and we moved away from it due to their price increase.
How was the initial setup?
The migration from our previous tool to Sweet Security was not seamless but it was not that difficult.
What about the implementation team?
Sweet Security does not require any maintenance, as it is a completely SaaS solution where everything, including updates and dashboards, is done on their side, and the agents are also updated automatically.
What was our ROI?
Regarding return on investment, I cannot say how much time or resources Sweet Security has saved since we are a very small team, but I am guessing it saves some time because it's a good tool.
What's my experience with pricing, setup cost, and licensing?
I am not aware of the pricing details; that is a different department.
Which other solutions did I evaluate?
We evaluated other solutions before choosing Sweet Security, including big names like Wiz and Orca, but Sweet Security stood out for their amazing pricing and because they were much cheaper than Ermetic while providing approximately the same capabilities.
What other advice do I have?
I haven't used the customizable dashboards feature yet.
I cannot assess the effectiveness of the machine learning algorithms in reducing threat response time; I don't remember using a feature like that in Sweet Security.
Regarding how Sweet Security has helped me prioritize risks and threats more effectively, I don't know how to say if it helped or not, but it is definitely needed, as the tool is our eyes and ears with everything cloud-related.
We purchased Sweet Security through a direct purchase.
We are not a small company; we have 7,500 users, but our IT team is indeed very small with just two users of this product.
I would recommend Sweet Security to other users for the price and functionality.
I rate Sweet Security eight out of ten.