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.
External reviews
External reviews are not included in the AWS star rating for the product.
Helps save time, improves collaboration, and identifies misconfigurations
What is our primary use case?
How has it helped my organization?
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.
What is most valuable?
The cloud misconfiguration is the most valuable feature. It highlights any misconfiguration that can make our infrastructure vulnerable.
What needs improvement?
I would like SentinelOne Singularity Cloud Security to add real-time detection of vulnerabilities and cloud misconfigurations.
For how long have I used the solution?
I have been using SentinelOne Singularity Cloud Security for almost 2 years.
What do I think about the stability of the solution?
I would rate the stability of SentinelOne Singularity Cloud Security 10 out of 10.
What do I think about the scalability of the solution?
I would rate the scalability of SentinelOne Singularity Cloud Security 10 out of 10.
How are customer service and support?
The technical support is good. They are knowledgeable and prompt.
How would you rate customer service and support?
Positive
How was the initial setup?
The deployment was straightforward. One person was required from our end.
What about the implementation team?
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.
What other advice do I have?
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.
Provides evidence-based reporting and makes onboarding and remediation easy
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
Its scalability is very good. We can onboard multiple accounts, Kubernetes clusters, or ECS services on a single platform.
How are customer service and support?
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.
How would you rate customer service and support?
Positive
How was the initial setup?
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.
What other advice do I have?
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.
Nice UI and features with helpful support
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
There should be more documentation about the product. Sometimes we have to go to customer support to get clarification.
For how long have I used the solution?
I've been using the solution for 1.5 years.
What do I think about the stability of the solution?
The solution is stable. I have not seen any downtime.
What do I think about the scalability of the solution?
We have around 15 users leveraging SentinelOne Singularity Cloud Security. They are mainly admins and engineers.
How are customer service and support?
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
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
The pricing is reasonable.
What other advice do I have?
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.
Cloud misconfigurations are managed effectively and response times have improved significantly
What is our primary use case?
In its all-in-one aspect, we started with Cloud Security Posture Management at the beginning and then added the Offensive Security Engine, Vulnerability Management of CDR. We also use it for compliance.
By implementing this solution, we wanted an alerting mechanism and detection of any deviation from our current configuration. We also wanted visibility into Kubernetes and AWS cloud. We wanted something that continuously monitors and gives us updates so that we can take action.
How has it helped my organization?
We have an overview of our compliance status. We check on a weekly or monthly basis where we are with respect to various compliance standards.
Its dashboard is quite good. We can select any resource and go to any details we want. We have a visual representation of our assets and how they are connected.
I like the granularity of access. We can give read-only, admin, or other types of access to team members based on their roles.
It provides an option for auto-remediation, but we are not leveraging that. However, we are using the exploit information to check what they saw versus what we are seeing. It helps to be able to see their evidence.
It includes proof of exploitability in its evidence-based reporting. This is very important for us. We can validate if something is false positive or not only if we have any evidence from the findings. Having the evidence for every issue helps us prioritize the findings.
Offensive Security Engine has helped to clear a lot of vulnerabilities in the past. Through the dashboard, we could see all the metrics related to public exposure and misconfigurations. We have a lot of services in our cloud, and they were very hard to track. It solves that problem for us.
Our time to detect and respond has improved drastically. If a misconfiguration happens, we gain visibility quickly. Our mean time to detect and respond has reduced by about 50%.
It has enabled collaboration between multiple teams for implementing cloud detection and response and understanding vulnerabilities. It has saved 20% to 30% of our time.
It has been highly effective in risk mitigation. Slack and Jira integrations have been helpful for alerting and creating tickets. We also have Kubernetes integration for insights.
What is most valuable?
The cloud misconfiguration feature and Offensive Security Engine, as well as their alerting process, are valuable. I get to customize severities or rules. The flexibility to rate a finding or category of vulnerabilities is the most interesting.
The cloud misconfiguration feature gave us almost zero false positives. We are happy with this feature.
What needs improvement?
In version 2, a lot of rules have been deployed for Kubernetes security and CDR, which makes a lot of issues of critical severity, whereas they are not critical or of high severity. There is a mismatch of severities. They need to work on severity management.
Alert fatigue is an issue as well. We get many alerts because of severity mismanagement. In CDR, there is no option to rescan or recheck. In cloud security, if a resource is restarting multiple times and gets a new name, we get alerts each time, leading to alert fatigue. If restarted five times, we get five alerts, which is not favorable.
For how long have I used the solution?
I have used the solution for two years.
What do I think about the stability of the solution?
It is a stable product. I would rate it a ten out of ten for stability.
What do I think about the scalability of the solution?
It is scalable. I would rate it a ten out of ten for scalability.
We are using the Enterprise plan which is the maximum that one can leverage. We are paying for all the features, but we are currently not leveraging VCS. We want to increase the usage of that.
How are customer service and support?
Their technical support is top-notch. I made friends there.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Previously, there was no product. We relied on in-house, independent ad-hoc automations. We now have a comprehensive and all-in-one solution.
How was the initial setup?
Its deployment was easy. It was set up in less than a week.
What about the implementation team?
There were a couple of people from PingSafe and a couple of people from our side.
We are based out of Indonesia and India. The deployment was done on the cloud. We use AWS. The PingSafe team was from Bangalore, India.
Its maintenance is taken care of by the SentinelOne team. There is nothing required from us.
What was our ROI?
On the resource side, we do not have to invest much money or time into developing our own automation or tools. It has saved us more than 50% of our time.
What's my experience with pricing, setup cost, and licensing?
It is cost-effective compared to other solutions in the market.
What other advice do I have?
I recommend looking at the exact requirements and exploring options for CSPM and Offensive Security Engine. These two are a must-have. I would recommend reviewing the use case first and seeing if any other features are required.
I would recommend this solution to others. Overall, I would rate it a ten on ten for cloud security.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Covers all aspects of cloud security and costs less than other solutions
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
It has been around two years since we have been using this product.
What do I think about the stability of the solution?
It is a stable product. I would rate it a 10 out of 10 for stability.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What about the implementation team?
We had two people involved in its deployment.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Helps improve our cloud security monitoring processes, streamline compliance management, and reduce detection time
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
In addition to our telecom and Slack channels, it would be helpful to receive Cloud Native Security security notifications in Microsoft Teams.
For how long have I used the solution?
I have been using Cloud Native Security for six months.
What do I think about the stability of the solution?
Cloud Native Security is stable.
What do I think about the scalability of the solution?
The scalability of Cloud Native Security is good.
How are customer service and support?
The technical support is the best. They can integrate our suggestions for security control into Cloud Native Security within three days.
How would you rate customer service and support?
Positive
How was the initial setup?
The deployment took one week. The deployment was completed by one person from our team along with a tech team from Cloud Native Security.
What's my experience with pricing, setup cost, and licensing?
Cloud Native Security is priced reasonably for our workload.
What other advice do I have?
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.
PingSafe: Offering a Comprehensive view of Cloud & Container Security
"
Priortize risk effectively with PingSafe's Agentless Vulnerablity Scanner
Detect Configuration Drifts in Multi-Cloud Infrastructure with PingSafe
Pingsafe: A Guardian Angel for Cloud Security
Difficulty in integrating the tool seamlessly into existing systems
Cost:
High in Cost
False Positives:
False Positives rate is high