SentinelOne Singularity Cloud Security Reviews

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.

Positive

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.

We utilize SentinelOne Singularity Cloud to safeguard our clients from viruses and to perform forensic analysis on threats.

We are a service integrator in the public sector in Italy, and we implemented SentinelOne Singularity Cloud because we lacked an antivirus solution.

The real-time detection and response capabilities of SentinelOne Singularity Cloud are excellent. We have implemented automated remediation on the Singularity platform. I have tested this on both our tenant and our customers' tenant, and we haven't encountered any issues with this method.

Singularity offers profound forensic visibility, which proves highly advantageous for in-depth analysis of events. Through a single console, we can observe comprehensive event details from start to finish.

The historical data record provided by Singularity after an attack is valuable. It allows us to identify any misconfigurations and has assisted us in rectifying errors during the deployment of group policies in Active Directory. This capability helps us manage group policies more effectively, particularly in terms of security policy deployment.

SentinelOne Singularity Cloud has been immensely helpful in mitigating issues for us. Our organization consists of approximately five hundred employees, including technicians and administrators, and Singularity has played a vital role in safeguarding our organization.

It has helped us reduce our MTTD. 

Singularity helps us reduce our MTTR.

We have saved time. The automatic remediation helped me a lot when an event occurred, as it analyzed and remediated the issue automatically. This saved a significant amount of time.

Singularity operates smoothly and does not cause our laptops to experience any performance degradation, which has been very beneficial.

Deploying SentinelOne Singularity Cloud is a simple process that requires only three clicks. 

The management console is highly intuitive to comprehend and operate.

The cost has the potential for improvement. I would appreciate it if the full edition could be made more affordable, allowing me to upgrade from the intermediate version.

I have been using SentinelOne Singularity Cloud for one and a half years.

SentinelOne Singularity Cloud is incredibly reliable. I have never come across a crash or experienced any downtime. I have never needed to initiate a support case.

The SentinelOne Singularity Cloud exhibits high scalability. We only need to incorporate licenses to facilitate scaling, eliminating concerns regarding servers or databases, as it functions as a cloud-based platform.

The initial setup is straightforward because the platform is cloud-based, allowing accessibility from anywhere, and deploying the agent is as easy as clicking three times.

Two people were involved in the deployment.

We are a system integrator and we implemented the solution in-house.

As a partner, we receive a discount on the licenses. Currently, we possess over 250 licenses, but there is potential for the licenses to become even more affordable.

We evaluated various products such as Trend Micro, Symantec, and Sophos. SentinelOne Singularity Cloud stood out among the solutions we evaluated as the easiest to manage and with the best performance.

I rate SentinelOne Singularity Cloud a nine out of ten.

SentinelOne is a novel form of endpoint detection and response that has assisted us in effectively managing our clients and servers. It provides us with substantial visibility and aids in safeguarding our infrastructure against emerging threats.

Regarding maintenance, I check the event logs every two weeks, in addition to reviewing emails, and I update the schedule to manage the agents.

The interoperability with third-party solutions is good. We don't have any compatibility issues.

SentinelOne Singularity Cloud is updated bi-weekly or monthly and the signature to the client is updated every two days.

Evaluating SentinelOne Singularity Cloud is made simple by installing the client and logging into the console.

I'm taking a look and digging into applications. I use it for general analysis. 

The visibility is very good. It allows me to go deeper into my investigations. It gives me the information I need. 

I do use the vulnerability scanning every day. It's excellent. I have no complaints. 

We do get false positives, however, it can be from downloading from dodgy sites or whatever the case may be. 

The mean time to detect is good. It's very fast.

It's good as is. From a beginner's perspective, while it's not necessarily complicated, it can be confusing. However, once you get the gist of it, it's pretty clear. For example, when you first go on it, you don't know what's going on. A few YouTube videos could be helpful. There isn't a lot of information out there to look at. 

I've been using the solution for roughly six to seven months. 

The stability of the solution is good. There is no lagging, crashing or downtime. This year we haven't had any downtime with the solution. 

The solution is very scalable. 

I've never contacted technical support. 

I did not previously use a different solution. 

When I joined the company, it was already being used; I did not set up the solution.

It doesn't need ongoing maintenance, although there are occasional agent updates. 

I don't know about the pricing or licensing. 

I'm an end-user.

I've never used the evidence-based reporting or the offensive or infrastructure-as-code scanning yet. 

I'd rate the solution nine out of ten. 

We have one client, and we need a portal to manage security. We use Singularity to provide security information and identify vulnerabilities or malicious scripts that need to be fixed. It also provides recommendations about each of the vulnerabilities that are helpful.

We provide cloud services on our site using AWS. Singularity detects flaws that we must close for security reasons. We use Singularity to observe those findings and fix things based on the customer's requirements. Previously, we used to segregate issues and look after them. Singularity helped us secure our infrastructure. We've significantly reduced our potential security breaches to a minimum. 

It has improved how we operate on a larger scale. We set up the platform, onboarded the info, and then gradually moved further. Over time, it helped us slowly resolve those issues. We were using the cloud platforms' native security tools, but those were unhelpful. Now, we rely on this more than those services. 

Singularity reduced our false positive rate by about 60 percent. We've had even better results in terms of our risk posture. We can rely on this tool to improve our security conditions on a broader scale. If I gave our security posture a percent rating, I would give it 89 percent.

The solution saves time by giving us everything in one place. You don't need to manually check every account. It tells us a lot. Singularity reduces our detection time by about 60 percent. 

Singularity has improved collaboration among cloud security, application developers, and AppSec teams. Previously, it would take around a week for engineers to address issues. Now that we use this tool, we resolve issues in one or two days.

We're monitoring several cloud accounts with Singularity. It is convenient to identify issues or security failures in any account. It's nice to have all the details we need to solve these issues. Singularity is easy and convenient to use. It is extremely easy for a novice to understand what the dashboard is trying to say and the terminology's meanings.

Evidence-based reporting is excellent for auditing. It shows all the findings and severity: low, high, medium, or critical. We solve the low-level and medium issues. Next, we resolve high-level and critical problems. It's easy to fix the security breaches.

We repeatedly get alerts on the tool dashboard that we've already solved on our end, but they still appear. That is somewhat irritating. 

We have used Singularity Cloud Security for about six months.

I rate Singularity nine out of 10 for stability. 

I rate Singularity eight out of 10 for scalability. 

I rate SentinelOne support nine out of 10. 

Positive

Singularity took about a week to deploy. A team of 40 to 50 people was involved. 

I rate SentinelOne Singularity Cloud Security nine out of 10. I would recommend the tool to others. It's a convenient and cost-effective tool for identifying security breaches. You get everything in one place, saving you time and costs.

Our cloud security posture management is handled by PingSafe.

To prevent cloud misconfigurations and developer code errors, we implemented PingSafe as a safeguard.

PingSafe is deployed as a SaaS.

The UI is easy to navigate and user-friendly even for users with limited experience.

PingSafe is easy to use.

The evidence-based reporting is good for helping prioritize and solve important cloud security issues.

Agentless vulnerability scanning simplifies vulnerability discovery across our entire cloud infrastructure, even in multi-cloud environments. This means we can see all our scan results in a unified view.

PingSafe's proof of exploitability in evidence-based reporting is important because it helps us easily identify issues.

The offensive security engine is handy for verifying actual exploit paths and prioritizing breach potential. We can identify the issues easily and check with the developers to mitigate them.

The IaC scanning helps with identifying preproduction issues in templates and container configuration files.

PingSafe has improved our ability to see and understand our cloud environment. By adhering to compliance regulations, we were able to identify areas where we had blind spots.

PingSafe has helped reduce the number of false positives by 60 percent. We have a whitelisting option that makes it easy to avoid false positives.

PingSafe has strengthened our overall security posture by both enhancing our environment's security and proactively identifying misconfiguration.

PingSafe has reduced our mean time to detection by 90 percent.

PingSafe has reduced our mean time to remediation by 90 percent.

PingSafe has affected the collaboration among our cloud security, application developers, and AppSec teams.

The collaboration has saved engineering 80 percent of their time. 

The most valuable features of PingSafe are cloud misconfiguration, Kubernetes, and IaC scanning.

A beneficial improvement for PingSafe would be integration with Jira, allowing for a more streamlined ticketing system.

I have been using PingSafe for two years.

I would rate the stability of PingSafe nine out of ten.

I would rate the scalability of PingSafe ten out of ten.

PingSafe's support is my favorite. They are easy to contact.

Positive

In the past, we relied on an open-source CSPM tool, but it lacked functionality beyond basic cloud misconfiguration detection. This necessitated using additional tools to address our broader security needs.

The deployment took two months and involved four people.

We have saved a lot of time and resources using PingSafe.

The cost for PingSafe is average when compared to other CSPM tools.

Having experience with both Prisma Cloud and PingSafe, I found PingSafe to be the superior solution.

I would rate PingSafe nine out of ten.

We have under 50 PingSafe users within our organization and it is deployed in one location.

No maintenance is required on our end.

I recommend PingSafe to others.

My company has around ten AWS accounts, and we use SentinelOne to monitor and see if any risks are there or not in any security groups for VPC endpoints or any other resources that come under severe risk or medium risk, so my company uses the product for calculations concerning the aforementioned area. The tool also creates tickets for our company, which helps us monitor the resources and change them according to the standards applicable to the organization.

The solution's most valuable features are its ability to detect vulnerabilities inside AWS resources and its ability to rescan after a specific duration set by the administrator. It creates a ticket automatically, so you get to know the things in the tool that you need to attend to immediately, making it a core feature of the solution.

I am unsure as to what kind of subscriptions my company has taken from PingSafe. I am not sure about what other things are there in the product that can help our company. Based on whatever subscriptions related to the product my company has taken, I can say that though one of the security groups is open to my company's premises, it still stays that it is open, which, for my company, makes it secure, but for PingSafe, it is not secure, so I am not pretty sure about how it can check and update it. I am not sure if a feature to deal with the aforementioned area already exists in the solution and if my company has not taken a subscription to use it.

Let us assume that there is a ticket that states that one port is vulnerable in the security groups from AWS since it is exposed to the public. When the tool states that it is exposed to the public, it means that it is exposed to the IPs in the company premises and not the public.

Let us assume that there is a database that is exposed to all the IPs in an office. If I have 10 to 12 sets of IPs, I can use them for 10 to 12 Wi-Fi or VPN connections, and it is exposed on the company premises, but the tool states that it is exposed to the public and that the company needs to shut it down. My organization needs to expose the database so that our development team can access it over our office IPs. If you do not expose the database to office IPs, the development team cannot access DBs to manipulate or check data. In general, the database is exposed to the office IPs, not to the public, but the tool states that it is exposed to the public since it cannot identify whether the IP is a public IP or office IP. I am not very sure if there is a setting in the product that allows the office to give its set of IPs to the tool, and scanning can be done through them so that the tool can identify if the resources are inside or outside of the IP range, according to which can state whether it is safe or not. In general, the tool should offer users the ability to mark IPs as public and private ones so that the product can identify them. It would be good if a customer could provide the tool with a set of ten IPs and state that it will be okay and secure if any of the resources are exposed to them since they are inside the office premises.

One of the issues with the product stems from the fact that it clubs different resources under one ticket. If I have 10 resources in 10 accounts, there might be a problem if, from those 10 accounts, 5 resources have the same issues and they get clubbed together under a single ticket, which makes it somehow a difficult process since I have to get inside the ticket to get the resources and the account details.

I have been using PingSafe for 6 months. My company is a customer of the solution.

I never found any stability issues in PingSafe.

In terms of scalability, I have not used the application to its full extent. Right now, I cannot comment on the scalability part of the product.

PingSafe helps identify the resources that are vulnerable to attacks, and if I can fix them up, then my application will be safe at that particular point in time. The tool's aforementioned area has no relation to the product's deployment since it is used to secure my company's resources, applications, and infrastructure.

Though the solution can be deployed with the help of my team, consisting of three people, I can handle it by myself. With PingSafe, the reports come to me, after which I can give or segregate them for different applications while having two different individuals working under me.

I take care of the installation part of the product by myself.

The solution is very user-friendly in terms of ease of use.

I do not use the product's reporting feature because another team in my company handles it. I know that my company uses the product's reporting feature to extract reports on a weekly, bi-weekly, and monthly basis, but I don't deal with it.

I don't use the product's agentless vulnerability scanning. I check the reports that come to me, as I need to further check the resource tests attached to them, especially whatever resources are affected as per the reports. In general, I just go with the report and complete the task.

I have not used Pingsafe's Offensive Security Engine.

Pingsafe's IaC Scanning is a great functionality that is built into the product. It is one of the major functionalities that my company's team uses. With Pingsafe's IaC Scanning, it is easy to monitor and observe areas in a good way.

Pingsafe's IaC Scanning role in identifying pre-production issues in IaC templates or container configuration files is helpful because when in my company, we configure IaC Scanning in our production environment, it gives a brief detail about what the resources and security groups or whatever resources are the most vulnerable, after which they get sorted into four categories, namely, low, medium, high and severe. The tool sorts out the resources into four categories before you go to the production phase, ensuring that they are good and secure.

The main benefit of the use of the product in our company stems from the fact that it provides a vulnerability scanning report, which helps us to maintain the resources mainly, an area for which my team and organization use it.

I experienced the benefits attached to the solution from the first day of using it, and before its use, I was not able to identify the issues in the resources. PingSafe gave me the value and the reports that helped me to identify the issues in resources.

PingSafe's use has helped reduce the false positive rate. In the initial stages, my company had more than 100 severe cases, but within a month, we were able to reduce that to below 10 percent.

With PingSafe, the mean time to detect has reduced because initially, for detection, I had to observe resources end to end. Now, the tool provides me with a regular report because of which I don't need to observe everything inside the resources. I just need to go to a particular resource and check what is stated in the ticket to see which ports are vulnerable, after which it can be changed, so I can directly go and check it, owing to which the tool definitely reduces the mean time to detect vulnerabilities.

With PingSafe, the mean time to remediate is a maximum of twenty-four hours. Initially, in my company, we had to identify the problem and then proceed with remediation, but now we can do it directly since the report is already available.

PingSafe has affected and helped me a bit to deal with the collaboration between cloud security application developers and AppSec teams because it helps me to keep my resources and tell the developers that we cannot expose them to the extent where the application will become vulnerable to attacks. In general, the tool is helpful since it reduces the time needed to connect DevOps and developers.

I found the product to be pretty useful. I directly onboarded the product and started to use it. I did not find any difficulties with the tool.

I rate the tool an 8 out of 10.

We use PingSafe as a Cloud Native Application Protection tool to identify anomalies or deviations from best practices in our cloud environment.

We chose PingSafe because it meets our compliance requirements.

We have integrated PingSafe with all of our AWS accounts. By default, when PingSafe identifies an issue, it automatically creates a Jira ticket. Our Security Operations Center team then investigates all these Jira tickets and takes appropriate action.

PingSafe is user-friendly.

PingSafe's evidence reporting is valuable for prioritizing and resolving the most critical cloud security issues. Any issue it identifies, whether it warrants a Jira ticket or not, can be directly accessed through a provided link. The PingSafe dashboard then displays all vulnerabilities, including how the issue was identified, the type of scan used, and the affected code location. This can include details from secret scanning, pinpointing the specific repository, file, and location where a secret was leaked within GitHub. This level of detail makes it very easy to verify and prioritize remediation efforts.

We leverage IaC scanning because our infrastructure is defined using Terraform. This allows our DevOps team to proactively identify potential security vulnerabilities. These vulnerabilities can include accidentally embedding secrets directly in the IaC code, such as committing them to the GitHub repository. By utilizing IaC scanning, we can detect such issues and promptly notify the responsible DevOps team member for remediation.

PingSafe helps identify issues in container configuration files early in the development process.

In the past, we relied on multiple tools for latency scanning and Kubernetes security scanning. This meant using separate portals and logging tickets manually in Jira. Now, with PingSafe, we have a centralized solution. It provides a single point of access for everything, from security issues to the latest threat intelligence reports. This makes it user-friendly and saves our team significant time. We can investigate issues more efficiently and even create Jira tickets directly within PingSafe, eliminating the need for manual logging. Overall, PingSafe offers both time savings and improved accuracy.

The real-time detection offered by PingSafe is crucial because we manage all our data using Kubernetes. This makes it critical to identify any vulnerabilities within the running dependencies.

We rely on PingSafe's comprehensive compliance monitoring to maintain regulatory compliance. We utilize all its features to maximize its effectiveness.

PingSafe has a user-friendly interface. It provides a visual flow diagram that makes it easy to navigate between different AWS accounts and services. When we receive an alert, we can quickly see which account and service it's related to. Overall, it's a well-designed tool.

PingSafe has removed 80 percent of our false positives.

PingSafe has improved our mean time to detection by 100 percent.

PingSafe has reduced our mean time to remediation by 70 percent. This is because we can now quickly obtain a list of all issue tickets logged in Jira, allowing our SoC team to take action on them promptly.

PingSafe improved the collaboration between the cloud developers and AppSec teams.

Having a system that can identify and alert us to misconfigurations in our 3 data storage buckets is helpful for our organization's penetration testers. Since all our company data resides on cloud platforms, PingSafe allows the AppSec team to automatically detect vulnerabilities before manual penetration testing begins. While this automation might seem to reduce the AppSec team's workload for cloud security specifically, it would ultimately benefit both teams. The security operations team would be relieved of the burden of manually logging and ticketing every issue identified within AWS services.

PingSafe has helped save 90 percent of the engineering team's time.

We have successfully integrated PingSafe with AWS and have also integrated the GitHub organization. These integrations were implemented to identify potential issues on our cloud platform. PingSafe is also used for IaC and secret scanning within our organization. Fortunately, these integrations have been running smoothly and haven't caused any problems.

PingSafe's graph explorer is a valuable tool that lets us visualize all connected services. For instance, we can see all running Kubernetes clusters, including their components and nodes. If there are any problems with cluster components or nodes, the graph explorer will highlight them, allowing us to easily address the issues.

The threat intelligence section also focuses on identifying new vulnerabilities emerging in the market. PingSafe scans our existing infrastructure to pinpoint all affected resources. This allows us to easily identify any at-risk resources with a single click.

PingSafe can improve by eliminating 100 percent of the false positives.

Another area of improvement is for PingSafe to auto-remediate the alerts. 

I have been using PingSafe for 6 months.

I would rate the stability of PingSafe 10 out of 10.

I would rate the scalability of PingSafe 10 out of 10.

We connect with the PingSafe technical support on Slack and they are always helpful and knowledgable. They can help with any of our questions and issues.

Positive

In the past, we relied on open-source tools like Terraform scanning and Gitleaks to scan our infrastructure as code and identify secrets. However, this approach demanded significant manpower and time investment, and we were inundated with false positives. To address these challenges, we transitioned to PingSafe.

I would rate PingSafe 9 out of 10.

For our organization, PingSafe must include evidence of exploitability in its evidence-based reporting and it does.

We have 6 people in our organization that utilize PingSafe.

PingSafe does not require maintenance from our end.

I recommend PingSafe to others because it offers several advantages. One key benefit is that it saves a significant amount of manpower. This frees up our security engineers to focus on other assigned tasks. PingSafe is a valuable tool for automating tasks.

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

PingSafe 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 PingSafe 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 PingSafe immediately.

It helped reduce the amount of false positives.

It has reduced our mean time to detection and remediation.

PingSafe 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 PingSafe.

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

I would like PingSafe to add real-time detection of vulnerabilities and cloud misconfigurations.

I have been using PingSafe for almost 2 years.

I would rate the stability of PingSafe 10 out of 10.

I would rate the scalability of PingSafe 10 out of 10.

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

Positive

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

The implementation process itself was very smooth. The PingSafe 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 PingSafe.

I would rate PingSafe 10 out of 10.

No maintenance is required for PingSafe.

Once you've acquired PingSafe, 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.