We did a PoC, but we did not go ahead with SentinelOne Singularity Cloud Security. It is currently on a test cluster. It is not in production.

We were looking for a CSPM tool to monitor all of our AWS resources. We also wanted it to give us an alert in the case of a vulnerability. If, for example, a zero-day vulnerability is there, it should scan all of our tools.

We used agentless vulnerability scanning. It helped us to see all the vulnerabilities without deploying any third-party component in our system.

We used SentinelOne Singularity Cloud Security's Offensive Security Engine. It helped us to identify all the CVEs. We could see what kind of CVEs were there and what severity level they had, such as normal or critical. It helped visualize all the severities.

SentinelOne Singularity Cloud Security changed our security posture a lot. In one dashboard, we were able to see all the information. We could see which resources are vulnerable and which ones have critical bugs. It helped us with that.

SentinelOne Singularity Cloud Security did not reduce our mean time to detect and mean time to remediate.

SentinelOne Singularity Cloud Security helped with collaboration, but in my organization, developers are not directly involved with SentinelOne Singularity Cloud Security. There was mainly the infrastructure component where we deployed agents and based on our particular role or access, they were able to send all the data to the SentinelOne Singularity Cloud Security server. We were able to see all the reports and all the details in the UI.

We liked the search bar in SentinelOne Singularity Cloud Security. It is a global search. We were able to get some insights from there.

The reporting feature is good. It is able to generate reports.

Its UI is very good, and it is easy to adapt. Any new person will be able to navigate, and within a week, he or she will be able to understand SentinelOne Singularity Cloud Security.

We wanted it to provide us with something like Claroty Hub in AWS for lateral movement. For example, if an EC2 instance or a virtual machine is compromised in a public subnet based on a particular vulnerability, such as Log4j, we want it to not be able to reach some of our databases. This kind of feature is not supported in SentinelOne Singularity Cloud Security.

If there is any virtual machine running on your public subnet, it is accessible outside your network. It is accessible via the Internet. If it has any Log4j or remote accessibility vulnerability, the attacker would be able to access the machine. From the private machine, the attacker can do NS Lookup and reach our DBs. It creates a channel for vulnerabilities. Such a feature is not present in SentinelOne Singularity Cloud Security.

It is stable. We have not had any issues.

It is scalable.

They were helpful. They helped us with the configuration. They were available through the Zoom call. Initially, they also provided us with a demo of all the features. They showed us all the features that we could use.

The speed of their support was good. I would rate their support a 9 out of 10.

We are using Orca. We did a PoC with SentinelOne Singularity Cloud Security, and there were some cost benefits.

SentinelOne Singularity Cloud Security is a SaaS solution. I was involved in its initial deployment. It took around three months.

We used their support. Its implementation requires at least two people.

Its pricing was a little less than other providers.

I would advise doing a PoC with all the similar tools and then making a decision based on the capabilities, features, and price.

Overall, I would rate SentinelOne Singularity Cloud Security a 9 out of 10.

We use it to monitor Azure and AWS accounts. We also use it to monitor the GitHub account for any data leakage and misconfigurations and also to have proactive configuration checks.

We were looking for a CNAPP solution that could provide details about cloud misconfigurations, compliance, and any risks. SentinelOne Singularity Cloud Security provides that. The feature of offensive security has been very helpful for us.

We only use agentless scanning. We have not installed agents anywhere. It collects data and provides information.

We use SentinelOne Singularity Cloud Security's Offensive Security Engine. The analytics features of SentinelOne Singularity Cloud Security are something that other providers do not provide. They have scanning on the port base and simulation of attacks. It is a very helpful feature to proactively resolve issues. It handles verifying actual exploit paths and prioritizing breach potential very well.

The proactive approach and offensive security have helped us to fix things in advance before they can be exploited.

We were able to realize its benefits immediately. As soon as you configure it, it does its job. It takes a day to configure it and discover the assets. It is easily deployable, and it immediately starts providing inputs.

SentinelOne Singularity Cloud Security helped reduce the number of false positives. It also helps with our SOC monitoring. The alerts are reduced, and we are in compliance.

We get details about how much we are compliant with different frameworks. It helps us to evaluate the risk posture as well. We use the reports to evaluate our risk posture.

The proactive approach and advanced fixes reduce the number of false positives, but it is difficult to know if SentinelOne Singularity Cloud Security has reduced our mean time to detect. SentinelOne Singularity Cloud Security has definitely reduced our mean time to remediate.

SentinelOne Singularity Cloud Security has not had an effect on the collaboration among various teams because, in our environment, everything is done by IT, but we have visibility across all the domains. We can work together if needed, but it is not yet applicable to our organization.

The offensive security where they do a fix is valuable. They go to a misconfiguration and provide detailed alerts on what could be there. They also provide a remediation feature where if we give the permission, they can also go and fix the issue.

They also support private clouds to a certain extent. It is pretty easy and customizable.

SentinelOne Singularity Cloud Security's interface is pretty easy and comfortable. They keep on improvising it. When you are configuring, it is pretty easy.

It is a very secluded solution. It works only as CNAPP. It does not bring much threat intel from the outside world. All it does is scan. If it can also correlate things, it will be better. It can discover the threats from the outside world. It can discover the threats or vulnerabilities happening across those assets. If it can bring that in and evaluate, it will be good.

We have been using SentinelOne Singularity Cloud Security for a year.

It is stable. We have not observed any issues.

We have not increased our assets, so it is difficult to say anything about the scalability part.

I never had to contact their support.

We were not using a similar solution previously.

It was pretty easy. It was very straightforward. They had many things available. We got the scripts on Azure, AWS, and GitHub, so the installation was pretty easy. It took a couple of hours.

It is a cloud solution. It does not require any maintenance.

We implemented it on our own. Only one person was required from our side.

Their support was not required. They offered to help. They assigned a customer success manager, but it was easy to deploy, so we did not require much help from their side.

Its pricing is okay. It is in line with what other providers were providing. It is not cheap. It is not expensive.

We evaluated 2 more products. One was Zscaler, and the other one was Wiz. Offensive security and support for the private cloud were the reasons for going for SentinelOne Singularity Cloud Security.

I would advise evaluating SentinelOne Singularity Cloud Security based on the use cases. You should know what is required and how SentinelOne Singularity Cloud Security can support that. If SentinelOne Singularity Cloud Security is able to fulfill your cases, it will be good. A thorough evaluation and mapping of the organization's objective should be done before buying SentinelOne Singularity Cloud Security.

I would rate SentinelOne Singularity Cloud Security an 8 out of 10. It is good.

We are a security-based company. We use SentinelOne Singularity Cloud Security to put our data planes on it. We have a cloud setup, and we have integrated SentinelOne Singularity Cloud Security into our environment. It checks for any audit or security-related issues.

By implementing SentinelOne Singularity Cloud Security, we wanted a centralized solution. We have many AWS accounts to manage, so we wanted a single dashboard with analytics. We wanted to be able to view and monitor everything at once. We also wanted to customize the rules on which we wanted the alerts to be set up. SentinelOne Singularity Cloud Security was a better option for our use case.

We have multiple rules set up on SentinelOne Singularity Cloud Security for things that we want to monitor. We have set up something for restricted access for SSH, and then we have access to the EC2 instances. If any of the rules are broken or if there is a bad actor, we get notified quickly. It also helps with the audit and keeping the infrastructure clean.

SentinelOne Singularity Cloud Security includes proof of exploitability in its evidence-based reporting. This is quite important for us because we are a security-based company. We want to tag each and every alert correctly. We also need to provide RCA to the customers. SentinelOne Singularity Cloud Security forms a very good basic layer for things that are happening in the infrastructure. The reports that it gives are also nice. It gives us information about the impact and other things. It helps us.

Its setup is good. It also depends on how finely you want to set it up. It depends on the rules you set, the thresholds you set, and how quickly you act on things. We did not want SentinelOne Singularity Cloud Security to act on things, so we went for a basic setup without any auto-remediation. We act on the issues. It provides us with a basic layer of security.

Previously, we used to find issues from the AWS console and the AWS logs, but because we had multiple AWS accounts, finding out the issues was a bit of a pain point for us. We had to go inside 30 to 40 AWS accounts to find out the capabilities. We had to write our own automation scripts to find the full logs. We wanted a solution that gave us a centralized place to put all the issues that we were facing based on security concerns. With SentinelOne Singularity Cloud Security, we found a centralized solution. It was easy for us to get the data of 30 to 40 clusters in a single dashboard. It was pretty nice to have that. The UI seems a bit confusing initially, but once you start using it, it becomes more intuitive.

There is a team that is working on setting it up on ISE. So far, with just a vanilla setup, it is doing its job, and we are happy with it.

There are a few false positives, but we want them to be there. We do not want to miss out on something. We want everything to be monitored. It does not matter to us if it is a false positive. At the end of the day, the cost that we would pay by ignoring a true positive thinking it is a false positive would be much higher than going through false positives and marking them as false positives.

For every module and everything that we do on our AWS clusters, we evaluate the risk individually, and then SentinelOne Singularity Cloud Security forms an extra layer of security on top of the personal checks that we do. It is like a shield for us. It helps us a lot.

SentinelOne Singularity Cloud Security has reduced the mean time to detect issues by a lot. Earlier, it was a very manual process to detect errors. There was not a single place where we could look into all the alerts. They were all scattered. SentinelOne Singularity Cloud Security unified that. With SentinelOne Singularity Cloud Security, once the alert is detected, we can just look into it directly. We can go into a specific cluster, resolve the issues, and mark it as resolved. There is a 45% to 50% reduction in the mean time to detect.

Our mean time to remediate remains the same because we have manual remediation. There is no change in that. The main issue for us was to be able to detect issues, and SentinelOne Singularity Cloud Security solved that for us, but because remediation is taken care of by us manually, the mean time to remediate remains the same.

SentinelOne Singularity Cloud Security is continuously monitored by the customer success engineering team and the security team. These people contact the infrastructure team. The application team is not involved because we mostly monitor the infrastructure side. That is the AWS side. It helps us with better collaboration. When the time zones change, we do not have to give a lot of context or change information across different time zones to different people. They can go into the console, see the issue, and continue to work on it.

Earlier, if there was a security issue, it had to be handed over to people in different time zones. Because we are a global company, we have on-calls and other things. Earlier, it used to be a big process. We had to write down the whole documentation of what happened, where we were seeing the issue, and whether it was resolved or not. We had to provide the complete information on that single issue. Things are simpler now because people can just log into it and see what is in the pending state and which security vulnerabilities we are still facing. A person in a different time zone can just log into the SentinelOne Singularity Cloud Security console and start remediating the issue.

The multi-cloud support is valuable. They are expanding to different clouds. It is not restricted to only AWS. It allows us to have different clouds on one platform. The integration is quite easy. It took around 15 minutes for the whole stack to set up. It was very easy to set up. That was one of the best things.

The custom rules are also valuable. We can set up our own thresholds on the rules. We can have a granular setup for the rules. We can also scan for specific ports and specific AWS modules. The granularity of rules is good.

In terms of ease of use, initially, it is a bit confusing to navigate around, but once you get used to it, it becomes easier. Initially, I had problems finding a few things and creating the policies. It was a bit difficult for me, but after going through the documentation, it got easier.

I was checking the IaC checks that they have, and they can add something for auto-remediating IaC. They can integrate something that will help auto-remediate on IaC and make needed changes to the code. They can also integrate something like CoPilot.

Other than that, I do not have any input. They have covered quite a bit. They are doing a good job. The features are good for what we are using it for right now.

I have been using SentinelOne Singularity Cloud Security for 3 to 4 months.

Its stability is good. We do not have a high volume. It is doing well for the scale that we have. I would rate it a 9 out of 10 for stability.

Its scalability is good. I would rate it an 8 out of 10 for scalability. It meets our requirements. SentinelOne Singularity Cloud Security does the very basic job of collecting the CloudWatch logs, keeping them in a centralized place, and looking for errors. We have scaled it across all of our AWS accounts, and it is doing well. I do not see any issues coming in the future as well.

SentinelOne Singularity Cloud Security is being used by our infrastructure team. There are 15 to 20 people who keep a check.

Their support was good. I would rate them an 8 out of 10.

We did not have anything like SentinelOne Singularity Cloud Security before.

The initial setup was straightforward. It only took about 15 minutes.

We initially had issues handling the setup. We were doing it slightly wrong. We ran it multiple times which messed up the setup. We got SentinelOne Singularity Cloud Security folks on the call. SentinelOne Singularity Cloud Security people assisted us with it, and it was very quick once they were on the call.

We are on the cloud. We have different AWS clusters, and we have onboarded AWS clusters to it. There is a single dashboard for us. We have not integrated it with anything else. SentinelOne Singularity Cloud Security is a separate system running, and we have not integrated it with anything. Being a security company, we are directly adding third-party solutions to our stack.

SentinelOne Singularity Cloud Security does not require any maintenance from our side. It was a one-time installation, and since then, we have not had any issues with it.

Based on the things that we have tested, it does a pretty good job of alerting and reporting. If you have a highly scaled environment with 50 to 60 AWS clusters and you are looking for a tool that simplifies getting security logs, SentinelOne Singularity Cloud Security is the perfect solution. It does the job. I would recommend SentinelOne Singularity Cloud Security to others.

SentinelOne Singularity Cloud Security has an auto-remediation feature, but we are not using that because we have to give a lot of access to SentinelOne Singularity Cloud Security for that. We are not willing to do so. That is why we do not use the auto-remediation offered by SentinelOne Singularity Cloud Security. We just get the alerts, and then we act on them. We also do not use agentless vulnerability scanning, IaC scanning, and SentinelOne Singularity Cloud Security's Offensive Security Engine.

Overall, I would rate SentinelOne Singularity Cloud Security an 8 out of 10.

We use the solution for monitoring the security of our infrastructure. It helps us identify all the vulnerabilities.

We had code and infrastructure, and we just weren't sure of all the vulnerabilities within them. This knowledge has helped protect us from security loopholes.

It's integrated with all of our cloud services on our accounts. It automatically fetches all the resources, scans through the code, and reports back on our vulnerabilities. It helps with all of our overall security standards as per the industry, and it can give us a rating. If I go to the compliance section, it gives me an idea of how I'm performing with respect to compliance metrics.

There's real-time threat detection. It can show threats and find issues based on their severity and helps us with real-time monitoring.

It's fairly easy to use. I'd rate the ease of use 7 out of 10. There is a learning curve around the initial issues. However, we can look at issue descriptions and what to do. It gives us a lot of details about an issue, so that helps.

Evidence-based reporting helps prioritize and solve our cloud security issues.

PingSafe includes proof of exploitability in evidence-based reporting. It's really important. If we did have any proof, it would be harder to pinpoint false positives. I like that it gives proof.

The code scanning is helpful. Whenever somebody commits a recent code, it helps identify that immediately and check vulnerabilities.

It has positively affected our exposure. Before we implemented it, we were having lots of issues, and now, with PingSafe, we're up to 87% compliance with respect to all security metrics. It's been a gradual process, however, we're getting better and better.

We've been able to reduce mean time to detect. It's gotten a bit faster. If you have a solution like this, you can take a more proactive approach. When a vulnerability happens, you can act immediately. Our mean time to detect has improved by about 80%.

It's also helped us with our mean time to remediate. It shows recommended actions and helps tell us what could possibly remediate the issue.

The product has positively affected collaboration among our cloud security, application developers, and AppSec teams. PingSafe, however, is more centered around our infrastructure security and doesn't impact developer productivity much.

The compliance monitoring capabilities are helpful. We're a venture product, so we need to be compliant with everything. When we get a report, we can see what we need to do for compliance, and it helps us identify issues and mitigate them effectively to increase compliance.

There is a bit of a learning curve for new users. The ease of use could be better.

We've had an issue where we muted a false positive, however, when we made some changes to a cloud configuration, it popped up again. So it hasn't really reduced false positives; you just need to manually ignore them.

I've used the solution for one year.

The solution has been stable throughout.

We have three to four users that are actively using PingSafe. They are admins and engineers.

So far, we haven't had any scalability issues.

They have great technical support.

We didn't use a different solution previously.

The initial deployment was pretty quick. When you integrate any of your cloud service providers, it doesn't take long. We had it implemented in a few days. One of our reps can just work with the team to get it ready.

It's not integrated with any other security tools, however, it is integrated within our infrastructure.

No maintenance is required.

I don't have any visibility on the pricing of PingSafe.

We have not evaluated other solutions.

I'd recommend the solution to other users. Overall, I'd rate the product 8 out of 10.

We mainly use SentinelOne Singularity Cloud Security.

We like that it is cloud-native security. It gives us an overview of all cloud structures. For example, if I'm integrating with AWS or Azure and I'm not sure of all of the instances, it will scan the whole cloud and show us issues related to instances. It can help us uncover vulnerabilities.

Of all the features we use, the cloud configuration and the offensive security engine are the most used. There is a secret scanning feature that I really like. It scans the public repositories, private repositories, and developer repositories. That way, we can see if any secret is added to the search engine or anywhere over the Internet. It detects this and then lets us know to which repository it was added. We can get it removed if we need to from repositories like GitHub.

The solution is good for verifying actual exploit paths. It helps us detect whether all the instances that are publicly available can be made private. We can see if anything is suspicious or harmful to us in the future or if any technical exploit has a specific port or something like that. If there is any vulnerability, such as if our Microsoft version is publicly exposed or if it is an older version, we can disable it, or we can upgrade to get the latest version of iOS to avoid exploitation.

The solution is easy to use. The interface is nice. Anyone can spend a day or two with the solution and they'll be able to understand the whole structure of the application, its features, and how to use it.

The integration with other solutions is very good. We integrate it with Jira and it runs smoothly. There are also default integrations for various clouds, like Google and Azure. We can also get alerts in various ways, like through Jira or email.

The evidence-based reporting is useful. It provides evidence according to the issue. We get a proper overview of the issue. I can check the evidence panel to see if the issue is genuine or a false positive by looking at the evidence.

We noted immediate benefits from using the solution. Within about a month, we had it integrated with Jira, and connected to all accounts and were able to easily find issues.

With SentinelOne Singularity Cloud Security, we are 96% to 97% compliant. It helps us judge and, as necessary, mitigate risks.

We've noticed a drop in false positives. I haven't noticed any false positives in SentinelOne Singularity Cloud Security, to be frank. Unless it's a glitch in the system, everything coming in is a positive.

Our mean time to detect has been reduced.

It's helped us collaborate effectively between cloud security application developers and AppSec teams. Having a vulnerability management module gives good visibility to vulnerabilities that are highly exploitable. We can see exactly what's vulnerable or affected in order to troubleshoot.

We'd like the integration with Jira to be stronger in some areas. For example, we'd like to be able to create multiple tickets for multiple instances. Right now, we can only create one ticket and cannot be specific enough. There's no way to create multiple tickets. It's very difficult to assign multiple teams the same Jira ticket.

Scanning capabilities should be added for the dark web.

I've used the solution for the last two years.

The stability is good. There's no lagging or crashing. There may be a downtime once a quarter.

We haven't had any issues with scaling.

Technical support is very good. We do have a monthly call with SentinelOne Singularity Cloud Security whereby we run through and resolve any issues. They typically answer our queries within 24 hours. The team is good. They seem technical.

This is the first cloud security tool we've used.

The initial deployment was easy. The SentinelOne Singularity Cloud Security team was very helpful. If we needed any help they were there to guide us. There's even a step-by-step guide.

We had a member of the DevOps team provide us with all of the credentials and give permissions and another security team member to communicate to the SentinelOne Singularity Cloud Security team in order to arrange all of the integrations.

The tool is very efficient. There is no maintenance needed.

We did not need any assistance from a reseller or consultant.

While my understanding is there will be a price increase, so far, the pricing has been okay.

We evaluated Prisma Cloud and Crowd Strike. We used Crowd Strike for a while; however, now we are only using SentinelOne Singularity Cloud Security. SentinelOne Singularity Cloud Security is very good. It offers multiple modules, and no other tool provides vulnerability scanning, secret scanning, and container cloud security in one dashboard.

We are a SentinelOne Singularity Cloud Security customer.

I'd rate the solution 9 out of 10. Overall, the tool is good.

New users should be ready for a lot of issues that will come onto their dashboard. They'll need a team of three to four at the outset to analyze the dashboard and work through reported vulnerabilities.

I am working with AWS. I'm a junior cloud engineer and on the client side, we use this software for security. We use this just for scanning all across the AWS environment for any bug, vulnerability, or high risk security issues, and we have to resolve these issues. The solution offers us low to critical alerts and our work depends on these alerts. If it is a critical alert, we have to resolve things as soon as possible.

The scanning is very good. We have an AWS environment and we can scan our whole account very quickly. Once the alerts get analyzed, we can automatically start removing issues.

It's easy to use. It comes with preconfigured settings. I haven't had to really change anything for months.

We have used evidence-based reporting. We're able to give reports on AWS, for example, how many data centers are used, et cetera. We can collect all of the information from SentinelOne Singularity Cloud Security and share all kinds of data which we can share with the database team for analysis.

The IaC scanning has been good. It's very interesting.

When I create a stack for any services in AWS, I can scan everything in a robust environment. This enables me to understand the level of protection.

SentinelOne Singularity Cloud Security can also scan code and provide alerts of there are vulnerabilities.

It's helped us reduce the number of false positives. I've been on the project for 6 months, and it was only until 3 or 4 months in that I received a false alert. Out of 20 alerts coming in, maybe only one or two are wrong.

The mean time to detect has been reduced. We check SentinelOne Singularity Cloud Security every day for a project happening 24/7. We check it frequently to ensure issues are being addressed quickly. We try to be consistent, however, the alerts don't come in at a certain time. They come in at varying times; we just work to keep on top of them.

We've had a glitch in SentinelOne Singularity Cloud Security where it has fed us false positives in the past.

Sometimes, it takes a few hours to detect a misconfiguration. It would be ideal if that happened faster. Detections should happen in minutes, not hours.

I've been using the solution for 6 months.

I have not noticed any lagging or crashing. The stability seems to be good.

We have dealt with support in the past. They were helpful.

We did not previously use a different product.

We had senior members of the team manage the installation since they had expertise. I'm not sure how long the process itself took.

I don't have any visibility on the pricing.

I'd rate the solution 8 out of 10.

There are a lot of options. It's a good idea to have a team member arrange on at least a quarterly basis, a review so that new team members can get up to speed on the product and everyone stays on the same page. This will help new team members understand the product.

We have AWS for most of our infrastructure, however, we don't have a dedicated security team. There are a lot of potential vulnerabilities which we are concerned about. We use SentinelOne Singularity Cloud Security for security. For example, if there are open ports or incorrect configurations, we would get alerted and could fix them.

They have dedicated cloud-based configurations, which are quite helpful.

The product works well with AWS. It can help us manage AWS security. If there are any groups or details that are incorrect or unsafe, or even misconfigured, it helps protect us.

The product offers ISE scanning, which basically scans all activities for issues.

We can pick up on pre-production issues. It's very helpful. They've helped us by providing a lot of CI/CD tools. Everything gets scanned so that we can get a sign-off before a deployment.

The ease of use is very good. I'd rate the ease of use 8 out of 10. They have nice UI and templates and the docmentation is very helpful. It's very thorough.

They also have a good support system for users. If something is not working, they have a good SLA, and within a day or so, they will reach out and help you with whatever you need.

The agentless vulnerability scanning is great.

If a protocol is not being properly followed, we'll be alerted. This helps us react faster to any production issues.

We do use the offensive security engine. It's good for verifying exploit paths and prioritizing items. We have recently started using this. It allows us to see which endpoints, for example, are publically accessible, or what code repositories have vulnerabilities in terms of libraries we are using that may be outdated. For example, if we've noted our NGINX server is very publically exposed we can change things.

The benefits of the product were felt almost immediately as it allowed us to handle issues in the pre-production phase. We didn't have to make anything live before finding issues. Within an hour, we'd begin to see issues, and within 4 to 6 hours, we'd have a full survey of security vulnerabilities. We also get regular notifications when the system sees something is off. Based on the information we receive, we're able to react and fix things very quickly.

We're able to see both high and low-priority issues so that we can accurately prioritize what to do first. That helps us manage bandwidth in terms of resources.

SentinelOne Singularity Cloud Security has helped us reduce the amount of false positives we see. We've reduced false positives by around one-third.

Our mean time to detect has been reduced, as well as our mean time to respond. We used to rely on a third-party provider to find issues, and now we can do it in-house. This means we no longer have to sync our AWS information on a daily basis. Now, we have a direct integration with SentinelOne Singularity Cloud Security. We used to have a delay of 36 to 48 hours before we would recognize if there were any vulnerabilities. On top of that, there was a reaction time delay of 4 to 6 hours, meaning issues wouldn't be dealt with until maybe 50 or so hours after the vulnerability was detected. We've reduced all of this down to maybe 8 to 10 hours.

The collaboration between cloud security, application developers, and AppSec teams has been better. It's mostly been positive for us.

They could improve on their UI. Sometimes it's not clear where to look when seeking information. Support often can direct us by giving us the correct link to what we are looking for.

I'd like to see better onboarding documentation. If we want to be able to integrate something new, such as new assets, it can be difficult.

I've used the solution for more than 2 years now. We started using it around December 2021 or January 2022.

I haven't faced any lagging or crashing.

For our use case, it has been scalable.

The support they provide is good. They give you very detailed information and documentation which they have created internally. They are very informative. They've even shared their own internal documentation in terms of AWS issues or questions.

They are quick to respond, You can rely on them.

We did use a different solution, however, it didn't offer direct AWS integration. Due to this, we had to wait up to 48 hours for information on vulnerability issues. We were already having security issues in that timeframe, so we needed something that could help us detect faster.

The initial deployment was easy. However, having more initial onboarding documentation would have been better. However, we've created some internal docs that have helped us with our use case. How long it takes to deploy depends on the use case, however, we were able to have it up in 12 to 14 hours. We had 2 people working on the deployment.

SentinelOne Singularity Cloud Security did offer some assistance with the setup.

I'm not sure of the exact pricing. However, my understanding is that it is very economical.

We did explore Crowd Strike at some point. Crowd Strike was a very big platform and we were not sure how much support we'd get. We wanted to make sure we had priority support.

I'd rate the solution 9 out of 10. The usability is very good. Both their new and mature products are good in terms of their overall usability.

We use SentinelOne Singularity Cloud Security as a cloud security posture management tool. SentinelOne Singularity Cloud Security is integrated with our GCP, Azure, and AWS accounts. It will identify all the misconfigurations and security issues on all these cloud platforms and alert us. In addition to the CSPM capabilities, SentinelOne Singularity Cloud Security has several other features like vulnerability management, container security, Kubernetes security posture management, and secret scanning

All of these features are bundled inside SentinelOne Singularity Cloud Security. It combines all the telemetry from the cloud, containers, and the Kubernetes platform. The vulnerability scanners are connected to the registries and give us a holistic picture of what else is vulnerable versus all the dummy data others would give.

Before SentinelOne Singularity Cloud Security, we didn't have visibility into the security aspects of our cloud environment. SentinelOne Singularity Cloud Security allows us to see all the misconfigurations and security vulnerabilities. Certain native tools from AWS are quite expensive and not as reliable, but SentinelOne Singularity Cloud Security fixes that issue. Also, for highly regulated companies, having a cloud security posture management tool is a hard requirement.

Regarding risk posture, there are two kinds of risk: perceived and actual. SentinelOne Singularity Cloud Security has helped us reduce the actual risk. Our compliance score went up from 70 percent to more than 95 percent now.

We realized SentinelOne Singularity Cloud Security's benefits maybe 1 or 2 months after the deployment. We integrated the regional module, and the extra features were there. About 6 months in, we really scaled it up.

SentinelOne Singularity Cloud Security has helped reduce the number of false positives we deal with. They've been highly proactive. We have a Slack channel with their support team. We tell them the false positive you're seeing, and they get on a call with you in 30 minutes to solve that issue.

The detection time is immediate. It finds vulnerabilities almost instantly, so the detection time has decreased considerably. In terms of remediation, it depends on how we are doing it. The remediation time has gone down, but not to the extent that we need it to.

SentinelOne Singularity Cloud Security has improved cooperation between the DevOps and security teams by helping identify critical issues that must be prioritized instead of just going through and fixing each one.

SentinelOne Singularity Cloud Security released a new security graph tool that helps us identify the root issue. Other tools give you a pass/fail type of profile on all misconfigurations, and those will run into the thousands. SentinelOne Singularity Cloud Security's graphing algorithm connects various components together and tries to identify what is severe and what is not. It can correlate various vulnerabilities and datasets to test them on the back end to pinpoint the real issue.

For example, let's say you have a vulnerability in a public instance of AWS EC2, and there's a relationship between that instance and the Kubernetes platform. From there, Kubernetes is connected to a container with a misconfiguration or vulnerability. That attack path is the root cause of the issue in your environment. It doesn't simply tell you whether something is public. That is a feature AWS provides natively. Native AWS tools provide us binary results about whether the instance is open, but SentinelOne Singularity Cloud Security can break down the data to identify the core issues.

SentinelOne Singularity Cloud Security is one of the easiest platforms to use. It's super intuitive. I have used CSPM tools in the past like CrowdStrike. This is much easier. With one click, you can deploy it in an hour. It automatically picks up a lot of the telemetry on its own. You don't need extra configuration steps because the scripts are all there. We can launch the cloud automation templates, and SentinelOne Singularity Cloud Security just directly deploys.

Agentless scanning is convenient for us. It will automatically copy the registry details from AWS, Azure, or GCP without any additional configuration before. If you have registries saved outside of your cloud environment, you can input the client key and secret file, and SentinelOne Singularity Cloud Security will integrate and scan it automatically. You don't need to deploy the agent because it does it on the back end. The best part is that they take this element and bring the cloud security posture management along with it. It will integrate the vulnerability scan into the containers, Kubernetes platform, and the entire cloud platform.

The offensive security engine isn't SentinelOne Singularity Cloud Security's standout feature, but it's an add-on that gives you insight into vulnerabilities in your cloud environment and how attackers can exploit them.

We have integrated SentinelOne Singularity Cloud Security's infrastructure-as-code features into our GitHub platform, enabling us to scan all the TerraForm and Kubernetes YAML code for vulnerabilities. That is a nice feature that allows you to detect issues in your code before it is deployed. It's inside the pipeline. It will scan the code and block the deployment if it doesn't meet preset criteria.

I want SentinelOne Singularity Cloud Security to integrate additional third-party resources. For example, SentinelOne Singularity Cloud Security is compatible with Azure and AWS, but Azure AD isn't integrated with AWS. If SentinelOne Singularity Cloud Security had that ability, it would enrich the data because how users interact with our AWS environment is crucial. All the identity-related features require improvement.

I have used SentinelOne Singularity Cloud Security for a year.

I have not experienced any instability, yet. SentinelOne Singularity Cloud Security is pretty solid.

SentinelOne Singularity Cloud Security is scalable if you have the licenses.

I rate SentinelOne Singularity Cloud Security support 8 out of 10. From the deployment until December of last year, SentinelOne Singularity Cloud Security's support was stellar and proactive. The support hasn't been as good since SentinelOne Singularity Cloud Security was acquired by another company. It's similar to what I've seen with other acquisitions. When it was a startup, you got more personalized support. You could even get the CTO to get on the call with you, which was nice. They have room to improve, but maybe they are undergoing a transition period after the acquisition.

We used a different solution, but the correlation wasn't as good, and it was expensive.

Deploying SentinelOne Singularity Cloud Security is effortless because it's a cloud-based platform. It's pretty intuitive, and we had lots of support from SentinelOne Singularity Cloud Security. If we had issues, we just got them on a call, and they fixed them. SentinelOne Singularity Cloud Security requires no maintenance on our end after deployment.

SentinelOne Singularity Cloud Security is cost-effective for the amount of infrastructure we have. It's reasonable for what they offer compared to our previous solution. It's at least 25 percent to 30 percent less.

I rate SentinelOne Singularity Cloud Security 9 out of 10. I recommend that new users onboard as many features as possible. Don't just stick to the cloud security part. Integrate the cloud security with your containers and GitHub or Bitbucket repositories. Perform all the integrations whether you need them or not, and it will take care of everything on the back end for you.