We use SentinelOne Singularity Cloud Security for cloud security posture management. It's used for AWS use cases to prevent leaked credentials and unauthorized access to our S3 buckets.

Before SentinelOne Singularity Cloud Security, we couldn't identify all of the hidden vulnerabilities on the endpoints. A manual approach was insufficient because we weren't getting everything. We were catching about 40 percent of the issues, and now it's up to almost 99 percent.

SentinelOne Singularity Cloud Security provides email alerts and ranks issues based on severity, such as high, critical, etc., that help us prioritize issues. SentinelOne Singularity Cloud Security's vulnerability scanning works well.

The reporting works well, but sometimes the severity classifications are inaccurate. Sometimes, it flags an issue as high-impact, but it should be a lower severity. For example, it might highlight an exposed AWS encryption key, a critical compliance issue, but it isn't tagged as a high-risk problem. That only happens about 10 percent of the time. It shows a true positive 80-90 percent of the time.

I have used SentinelOne Singularity Cloud Security for six months.

We haven't had any problems with SentinelOne Singularity Cloud Security's stability.

SentinelOne Singularity Cloud Security is more scalable than Qualys.

I rate SentinelOne Singularity Cloud Security support eight out of 10. They are very knowledgeable and supportive.

We previously used Qualys but switched to SentinelOne Singularity Cloud Security because it's easier to use. It's also more scalable and flexible. We don't need to install an agent.

SentinelOne Singularity Cloud Security is a hybrid deployment. The initial setup was easy. We had a consultant.

SentinelOne Singularity Cloud Security is priced in the middle. It's better than Qualys.

I rate SentinelOne Singularity Cloud Security 10 out of 10.

We are using the solution to identify the security vulnerabilities in our AWS infrastructure. Whenever we create a new infrastructure in AWS, if there is a vulnerability, an issue is created in the SentinelOne Singularity Cloud Security console. There are different severities, such as critical, medium, and high. The product also provides solutions to resolve the issues. SentinelOne Singularity Cloud Security provides a solution document for AWS. It helps us resolve issues. We have seven to eight AWS accounts. It is all in SentinelOne Singularity Cloud Security. SentinelOne Singularity Cloud Security identifies the issues with all the accounts.

Our company has very strict compliance requirements for security. SentinelOne Singularity Cloud Security has helped us resolve vulnerabilities and issues using best practices. It helps us resolve the security vulnerabilities of the AWS cloud infrastructure. The compliance monitoring capabilities are helpful. The tool identifies issues quickly. It gives us the root cause of the security issues rapidly.

The evidence given by the product helps us resolve the issues. It provides a step-by-step guide to resolve issues. It helps us a lot. SentinelOne Singularity Cloud Security provides us with a lot of information. It provides us with a document of AWS. We use AWS CloudFormation. If there is an issue with AWS CloudFormation or if the code is rapidly changing, SentinelOne Singularity Cloud Security will identify the issue.

The number of false positives depends on the requirements of the clients. If the client needs something for their application and it shows as an issue in SentinelOne Singularity Cloud Security, we must contact SentinelOne Singularity Cloud Security and close the issue as an exception. The tool has reduced the false positives by 10%.

The solution helps us maintain our risk posture. We use a web firewall in AWS. If we do not have a firewall in any of the resources, the SentinelOne Singularity Cloud Security console will identify it as an issue. The tool has helped reduce the mean time to detect. We check the SentinelOne Singularity Cloud Security dashboard daily. We have a checklist. We can identify how many issues are open and how many issues are closed. It helps us reduce the time to identify the issues and open vulnerabilities. SentinelOne Singularity Cloud Security has helped us reduce our workload and time by 50% to 60%.

SentinelOne Singularity Cloud Security helps reduce our mean time to remediate by 70% to 80%. The product reduces workload and time. It is very important in every organization to reduce time and find vulnerabilities. SentinelOne Singularity Cloud Security also provides us with solutions to the issues. Every organization must have a tool like SentinelOne Singularity Cloud Security. I will recommend the product to others.

The SentinelOne Singularity Cloud Security team identifies issues when we create the infrastructure. Within two to three hours, they create an issue in the SentinelOne Singularity Cloud Security console. It helps us resolve the vulnerabilities during the creation of the infrastructure. SentinelOne Singularity Cloud Security provides us with documents on how to resolve issues with the infrastructure. It saves our time in identifying issues. Integration with our cloud environment was straightforward.

Based on our application requirements, we discussed some improvement points with the SentinelOne Singularity Cloud Security team. However, after the new updates, what we asked for was not implemented. The exceptions we requested from the SentinelOne Singularity Cloud Security team were not included in the console. When we request any changes, they must be reflected in the next update.

I have been using the solution for two years.

The product is stable. I rate the stability a ten out of ten.

We have 12 users, including internal users and clients. I rate the scalability a nine out of ten.

The solution is deployed on the cloud. The deployment takes a few days. Our cloud team and the SentinelOne Singularity Cloud Security team were involved in the deployment process. We need two to three people for the deployment. The tool does not require any maintenance.

I am satisfied with the technical support.

We save a lot of time identifying vulnerabilities. The product gives us the issue and the solution. It reduces our time and workload.

The tool is cost-effective.

The product is easy to use. My colleague provided me with a KT of the tool. I could learn to use it in two to three days. I understood how to check and resolve issues and segregate them into different severities. The ease of use is very helpful.

Overall, I rate the tool a ten out of ten.

I work for an insurance company whose infrastructure is on the cloud, so we use SentinelOne Singularity Cloud Security for security management and vulnerability detection.

SentinelOne Singularity Cloud Security is a valuable tool for managing infrastructure security. It offers advanced features like container security management, microservices security management, and Configuration Drift Remediation, which helps identify and address unauthorized configuration changes. These features are comprehensive and adaptable. Even for custom infrastructure modifications, such as XYZ, the SentinelOne Singularity Cloud Security team can be contacted for guidance and policy adjustments to ensure a smooth adoption process.

Infrastructure as Code is valuable because the code itself defines the infrastructure. This means any vulnerabilities or misconfigurations in the IaC code will be deployed to our infrastructure. However, IaC tools can scan the code and alert us to potential problems before deployment, allowing us to fix them proactively.

We saw the benefits of SentinelOne Singularity Cloud Security immediately.

It helped reduce the amount of false positives.

It has reduced our mean time to detection and remediation.

SentinelOne Singularity Cloud Security improved collaboration between our cloud security developers and the application security teams.

The collaboration helped us save time, which is one of the reasons we have continued to use SentinelOne Singularity Cloud Security.

The cloud misconfiguration is the most valuable feature. It highlights any misconfiguration that can make our infrastructure vulnerable.

I would like SentinelOne Singularity Cloud Security to add real-time detection of vulnerabilities and cloud misconfigurations.

I have been using SentinelOne Singularity Cloud Security for almost 2 years.

I would rate the stability of SentinelOne Singularity Cloud Security 10 out of 10.

I would rate the scalability of SentinelOne Singularity Cloud Security 10 out of 10.

The technical support is good. They are knowledgeable and prompt.

The deployment was straightforward. One person was required from our end.

The implementation process itself was very smooth. The SentinelOne Singularity Cloud Security team provided excellent assistance in integrating the solution with our existing infrastructure and account. This made the integration process hassle-free. We've also recently integrated a new CDR feature using SentinelOne Singularity Cloud Security.

I would rate SentinelOne Singularity Cloud Security 10 out of 10.

No maintenance is required for SentinelOne Singularity Cloud Security.

Once you've acquired SentinelOne Singularity Cloud Security, it's essential to review all your existing organizational policies. If these policies are compatible with your infrastructure, you can proceed without modifications. However, if there are any incompatibilities, you'll need to make adjustments to ensure your infrastructure triggers accurate alerts. Skipping this step can lead to a flood of false positives.

We have onboarded multiple accounts from our organization. We have onboarded Azure accounts, and we have also onboarded GCP accounts.

We are using the vulnerability management feature, and we are also using the offensive security feature. We are planning to use IaC in a couple of months.

We are a services company. We are working for multiple clients from the banking sector or the finance sector. They have to follow the rules and regulations of their country. Each country has multiple compliance requirements, and SentinelOne Singularity Cloud Security helps with the compliance standards that need to be followed. We get reports on the basis of that. We get to know our compliance level. It helps organizations to achieve a high level of compliance.

Its reporting is very good. We do not have to go to the portal and see things again and again. All the required reports go to the respective teams. We have created multiple reports on the basis of applications and cloud accounts. The reports directly go to the application team or the cloud team. They are working on the security posture.

Offensive security is my favorite feature. It gives a lot of things with evidence. It also provides the severity levels, such as critical, high, and medium.

SentinelOne Singularity Cloud Security has reduced false alerts. We are using SentinelOne Singularity Cloud Security every day, and we are able to see every configuration. If we find anything different, we work with SentinelOne Singularity Cloud Security's support team. We create a support ticket as a bug or as a false positive. We are able to close an issue on the basis of priority.

SentinelOne Singularity Cloud Security is protecting our overall infrastructure. It protects our configuration, network, and IM configuration-related things. We trust SentinelOne Singularity Cloud Security. We are getting good results, and we hope to keep getting good results in the future as well.

SentinelOne Singularity Cloud Security has reduced the mean time to detect. If needed, we can also run a scan, and the results are reflected in the SentinelOne Singularity Cloud Security portal.

SentinelOne Singularity Cloud Security has reduced our mean time to remediate. It also has auto-remediation capability, but we are not using that. As of now, we are following the information given for closing an alert. This information makes it quite easy. It is very helpful. We do not have to search on the web to find a way to fix the issue. The description it provides is good enough.

SentinelOne Singularity Cloud Security has affected the collaboration among our cloud security, application developers, and app sec teams. All the teams are on the same platform. They are able to communicate with each other.

The offensive security feature is valuable because it publicly detects the offensive and vulnerable things present in our domain or applications. It checks any applications with public access. Some of the applications give public access to certain files or are present over a particular domain. It detects and lets us know with evidence. That is quite good. It is protecting our infrastructure quite well.

Its UI is quite easy. The recommendation part is also quite easy to understand. Users can read the description, and they get to know which action to perform. It is quite easy to use it and onboard things. I would rate it a 9 out of 10 for the ease of use.

For vulnerabilities, they are showing CVE ID. The naming convention should be better so that it indicates the container where a vulnerability is present. Currently, they are only showing CVE ID, but the same CVE ID might be present in multiple containers. We would like to have the container name so that we can easily fix the issue. This is a feature request that we have. We are trying to get that done as soon as possible.

We have been using SentinelOne Singularity Cloud Security for the last year. We are implementing it for customers. We are also trying to be a partner of SentinelOne Singularity Cloud Security or SentinelOne.

It is stable. I would rate it a 10 out of 10 for stability. We have not faced any downtime. The platform is working well.

Its scalability is very good. We can onboard multiple accounts, Kubernetes clusters, or ECS services on a single platform.

I have contacted them. We also have a Customer Success Manager whom we can contact via email. Whenever required, we raise a support ticket with them. We get a call from them, and it gets resolved every time.

We also have biweekly calls with the SentinelOne Singularity Cloud Security team. We discuss any issue that we have with them. They let us know about the things they can do. They provide us with updates. This is how we are working with the SentinelOne team or the SentinelOne Singularity Cloud Security team.

SentinelOne Singularity Cloud Security is a SaaS solution. It is easy to deploy it for a customer. If we have all the permissions on the infrastructure, we can onboard any cloud within an hour. However, in an organization, some approvals might be required. In such a case, it can take a week.

It does not require any maintenance. Whatever they are doing is quite good, and the application is working fine. They let us know about their maintenance plans via email. We get to know that downtime is at a specific time. So far, we have not had any issues. It has been pretty good.

We have not used SentinelOne Singularity Cloud Security's agentless vulnerability scanning. We are trying to onboard all the features and enable them in our tenant. Currently, there are a few features that we have not enabled because we have onboarded some of the accounts as a single account. We are trying to onboard all the accounts at the org level, but we are facing some issues. We are communicating with the SentinelOne team. We are trying to get it done as soon as possible.

We have done a PoC of IaC for some of the projects. In a couple of months, we will start with this feature. It is quite a good feature because we get to the issues in our code before deploying it. It is very good for developers and the Infra team. They do not have to worry after the deployment of the application.

Overall, I would rate SentinelOne Singularity Cloud Security a 10 out of 10. It is helpful. It is easy to use and easy to understand. It makes it easy to explain things to the customers.

We have multiple AWS accounts and we use it for our products and deployments, et cetera, and they are being monitored by SentinelOne Singularity Cloud Security for best practices and good security. In the past, we've had code exposed to the internet, and SentinelOne Singularity Cloud Security has been able to catch such instances. Basically, it is for security and monitoring purposes.

We've been able to integrate SentinelOne Singularity Cloud Security with out AWS and deployed their agents to Kubernetes. For production and compliance purposes, it allows us to monitor actively for issues from one place.

The solution reduces notifications.

We mainly use it for monitoring and security guidelines only. It's been really useful for us in terms of the developer accounts. If any have been exposed, we get notified and we can take care of issues before anything happens.

We haven't seen any server downtime. It's always been available when we've needed it.

The UI is very nice, and feature-wise, it's very good.

It has very good documentation.

Support has been very helpful and provides regular feedback and help whenever needed. They've been very useful.

The solution is very easy to use. We have not had to spend much time customizing or integrating items. We were able to integrate all four AWS accounts in order to centrally monitor everything.

There is evidence-based reporting which can help prioritize and solve cloud security issues. We haven't actively used it or set it up.

We use the infrastructure as code scanning feature. It's good for identifying pre-production issues.

About six months ago, there was a major upgrade. We can see the containers running and which vulnerabilities appear, et cetera.

We haven't seen any increase in false positives since using the solution.

It's helped us improve our risk posture. We're more confident now that things aren't happening and getting missed. We're on the right track to adapting proper security rules.

More than saving engineering time, this solution has helped promote confidence is the security of our cloud accounts. We're more sure of our configurations and security posture. Since we don't have a cloud expertise team that might identify issues, it has helped us gain confidence in SQL deployments.

There should be more documentation about the product. Sometimes we have to go to customer support to get clarification.

I've been using the solution for 1.5 years.

The solution is stable. I have not seen any downtime.

We have around 15 users leveraging SentinelOne Singularity Cloud Security. They are mainly admins and engineers.

Technical support is very helpful. However, the documentation needs to be better.

They tend to resolve issues within an hour or so. With most issues, they are very helpful

We have a different pipeline product working in parallel to this solution that is also helping us reduce vulnerabilities. Something else, for example, monitors compliance for us. SentinelOne Singularity Cloud Security is more of an additional tool than our main solution. We have been using open-source tools for scanning.

The development was just one configuration, and we were able to implement SentinelOne Singularity Cloud Security in about an hour.

The solution does not require any maintenance.

We have noted an ROI based on the amount of confidence we've gained having visibility into our vulnerabilities. I do not have specific metrics on hand to illustrate that, however.

The pricing is reasonable.

We're a customer and end-user. I'm a DevOps engineer.

I'd recommend the solution to others. I would rate it 10 out of 10 as it currently meets all of our requirements. I can't speak to other companies that may have different requirements.

We are using Cloud Native Security for cloud posture management and cloud workload protection. Apart from this, it also provides alerts from infrastructure as code. If the tool finds any misconfiguration, it triggers that as an alert, and that gets collected in Jira.

Previously, we were using AWS services, but we were not getting the alerts in Jira. When Cloud Native Security was introduced to us, we wanted it to automatically create Jira tickets, and we wanted custom alerts. These were the two areas that we shared with them, and they stood out in these aspects. We decided to take it ahead, and we have been using it for the last two years. I feel a lot of difference in the security posture development. When we share the tickets with the developers, they work on that, and we have tracking of them in Jira. We wanted to track alerts in Jira. We no longer have situations where we flag an issue and it does not get resolved on time.

We use agentless vulnerability scanning. The process that Cloud Native Security follows is that you have to deploy the cloud permission template in your account, and then it creates a role that tracks or scans all the resources and finds if there is any misconfiguration. We have integrated Cloud Native Security with Jira. It triggers alerts on Jira. A person is assigned to an alert, and the concerned person is notified. As a security team, we collect those tickets and forward them to the respective team.

Previously, we were not able to track those tickets, whereas now, we are getting automated Jira tickets. It has solved our biggest problem. We are expecting the same from Cloud Native Security in the future. We expect that it will capture the triggers or alerts. If any new security vulnerability is found, it will also flag that to us.

It provides an overview of our security posture. If a metrics endpoint is public for any domain, that gets triggered. We get reports for different domains, such as Kubernetes security and vulnerabilities management, IaC scanning, or cloud detection and response. Cloud Native Security covers all of these. There is also a graphics tool where we can get all the details in a graph. All the Kubernetes microservices get scanned in the workload protection. The Cloud Workload Protection module detects all the cluster misconfigurations and other things. It also gives you alerts on the containers. We were looking for such a tool with all the cloud security modules.

We can also create our own custom policy. For example, if we do not want to enable the recommended Cloud Native Security policies for our company, we can create our own policies. This feature is very helpful.

We use Infrastructure as Code (IaC) scanning. It follows all the features for shift-left. We get all the alerts for IaC scanning. For example, if TerraForm is not performing any security checks in the template, that gets triggered. We also get information about any vulnerabilities related to IaC.

We have not got any false positives with Cloud Native Security so far.

Cloud Native Security has affected our risk posture. It shows us our risk areas. As an organization, we look for cloud security tools that can manage all the areas, and Cloud Native Security is doing a good job in managing all the things.

Cloud Native Security has reduced our mean time to detect. The detection time of Cloud Native Security is quite good. It takes half an hour for critical alerts and one hour for high alerts. These are the SLAs that we have. The detection time is quite good.

Cloud Native Security has also reduced our mean time to remediate. We have defined our SLAs as well. In our organization, we define the SLAs and share them with the developers or the DevOps team so that they can follow them. They work on the assigned issue, and if there is any issue, they come back to us.

I like CSPM the most. It captures a lot of alerts within a short period of time. When an alert gets triggered on the cloud, it throws an alert within half an hour, which is very reasonable. It is a plus point for us.

Apart from the posture management, I like the UI. It gives a holistic view of all the alerts and the accounts from where they are triggered.

Cloud Native Security is quite easy to use. It is user-friendly. As compared to other tools, it is more user-friendly, and its cost is also less than the other tools. It provides the same visibility that the other tools are providing in the market.

They can add additional modules to see scanning alerts. Adding additional modules will give us a better view.

They can work on policies based on different compliance standards.

They can add more modules to the current subscription that we have. If they can merge some of the two modules, it would be great. For example, if they can merge Kubernetes Security with other modules related to Kubernetes, that would help us to get more modules in the current subscription.

It has been around two years since we have been using this product.

It is a stable product. I would rate it a 10 out of 10 for stability.

It is scalable. I would rate it a 10 out of 10 for scalability.

Our security team uses this solution. We have five to six people on the security team. Overall, we have 600 people.

Previously, we were using AWS services, but there was no dashboard. That was where we had an issue. We wanted a cloud security tool that matches our requirements and provides the same thing in a holistic view and a better manner. That is why we went for Cloud Native Security. It has now been acquired by SentinelOne. We are getting the same product even after the acquisition.

It is deployed on the cloud. It took us about a week to implement all the features. It was very easy. They were very user-friendly.

In terms of maintenance, they do inform us when the maintenance will be going on.

We had two people involved in its deployment.

It is not that expensive. There are some tools that are double the cost of Cloud Native Security. It is good on the pricing side.

We started doing POC with Cloud Native Security, and we liked it. We did not think of any other product. It also had better pricing than any other product.

I would recommend Cloud Native Security as a cloud security solution. They are doing an excellent job of providing the features that we require for cloud security posture management.

I would rate Cloud Native Security a 10 out of 10.

Our Cloud Native Security use cases depend on the type of SQL server we use. Currently, we need to check all cloud-based configurations directly. Cloud Native Security helps us identify SQL configurations on our local PCs.

Cloud Native Security has improved our cloud security monitoring processes. We can now capture all issues and misconfigurations in real-time, allowing us to respond quickly.

It streamlined compliance management for our organization. They schedule a meeting with us every month to discuss any requirements on our end, such as updating the Cloud Native Security version. For example, one time they informed us that we needed to update to Cloud Native Security version four. We inquired with their customer support team, who were very approachable and requested them to implement the cloud version of Cloud Native Security version four into our Cloud Native Security dashboard. They implemented it within five to six days. We were happy to adopt the enhanced security controls of Cloud Native Security version four. The customer success team and the customer-facing teams were very helpful and provided us with the best solution. This is why we chose Cloud Native Security. They are a well-established CSPM company in India with a proven track record of assisting businesses with compliance requirements. By onboarding Cloud Native Security, we gained a cloud-based configuration management system for our workloads.

It's easy to use.

Our cloud security issues are already automated using a common subscription ticketing tool to capture them. Reports are then sent to both the internal DevOps team to identify potential false positives and the business team to assess if resolving the issue aligns with business requirements.

Cloud Native Security's event-based evidence reporting should include proof of exploitability. This would allow users to easily identify misconfigured areas in the graph and click on a provided link to conveniently be redirected to the cloud service provider management console page for more details.

Cloud Native Security's offensive security engine proved valuable recently. When an endpoint was mistakenly exposed, it automatically captured the unauthorized request in the cloud and sent an alert to our email address. This notification allowed us to take swift action and restrict access to the URL on our network.

The AI helps us handle the hundreds of audits each year helping to enhance our security posture.

Cloud Native Security's access to the IIM role in the cloud formation template significantly reduces false positives, thereby maximizing the number of true positives.

Cloud Native Security helps us improve our risk posture, failover capabilities, and compliance levels.

Cloud Native Security reduces our MTTD. We are alerted within seconds on the dashboard and email of the detection.

To assess our MTTR, we need to consult with the DevOps team and conduct an impact analysis. If the impact analysis reveals no disruption to the production application within the AWS network architecture, we can proceed with remediation immediately. However, if the analysis identifies a potential impact, obtaining management approval will add to the resolution timeframe.

Cloud Native Security improves collaboration between our cloud security application developers and AppSec teams. It's particularly helpful for AppSec because we can leverage cloud security controls directly from Cloud Native Security. This also allows us to mitigate cloud misconfigurations.

Cloud Native Security's most valuable features include cloud misconfiguration detection and remediation, compliance monitoring, a robust authentication security engine, and cloud threat detection and response capabilities.

In addition to our telecom and Slack channels, it would be helpful to receive Cloud Native Security security notifications in Microsoft Teams.

I have been using Cloud Native Security for six months.

Cloud Native Security is stable.

The scalability of Cloud Native Security is good.

The technical support is the best. They can integrate our suggestions for security control into Cloud Native Security within three days.

The deployment took one week. The deployment was completed by one person from our team along with a tech team from Cloud Native Security.

Cloud Native Security is priced reasonably for our workload.

I would rate Cloud Native Security ten out of ten.

We have a large number of users of Cloud Native Security in our organization.

I recommend Cloud Native Security to others.