We performed a comparison between Azure Kubernetes Service (AKS) and Singularity Cloud Security by SentinelOne based on real PeerSpot user reviews.
Find out in this report how the two Container Security solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."AKS as a service is very good when you need to leverage applications or functions with much variability in their usage because you're trying to be as efficient as you can with resources."
"Integration and automation are the best features of the solution."
"The most valuable feature of the solution is the diagnostic service."
"The setup was straightforward and it took one hour to deploy."
"The product’s most valuable features are ease of use and automation."
"I found the Helm deployment feature of the solution valuable."
"Has a good management feature monitored by the cloud service provider."
"The product has built-in functionality that checks whether the service is available or not. In case the service is down, the tool will create a new instance by default. Hence, the web API will be always up irrespective of the server or the situation."
"Cloud Native Security offers attack path analysis."
"PingSafe can integrate all your cloud accounts and resources you create in the AWS account, We have set it up to scan the AWS transfer services, EC2, security groups, and GitHub."
"It used to guide me about an alert. There is something called an alert guide. I used to click on the alert guide, and I could read everything. I could read about the alert and how to resolve it. I used to love that feature."
"The visibility is the best part of the solution."
"The UI is responsive and user-friendly."
"Support has been very helpful and provides regular feedback and help whenever needed. They've been very useful."
"We liked the search bar in PingSafe. It is a global search. We were able to get some insights from there."
"All the features we use are equal and get the job done."
"AKS has the potential to enhance pricing by enabling us to explore ways to increase cost transparency. However, it's important to note that this refers to computation costs rather than client costs. Our objective is to optimize efficiency and minimize unnecessary expenses. Therefore, we aim to identify which services within the platform can benefit from improved consumption patterns. This is the focus of our ongoing research, with the goal of maximizing computational power within the cluster. We aim to avoid situations where resources are reserved but not utilized effectively. Additionally, our strong emphasis on security ensures that we adhere to all relevant compliance standards, bolstering our overall trustworthiness."
"One area that could be improved is the Azure CLI. It would be beneficial if they could abstract some of the complexities related to deployment scripts and make them a part of Azure CLI."
"This is a fairly expensive solution, which can make it prohibitive for smaller organizations."
"The solution's logs have room for improvement."
"Sometimes, it fails to provide specific metrics."
"We would like to see the addition of a service report from the server for this solution, so that we can monitor the health of server operations."
"The product needs to support a UI dashboard. I have to execute every single command to check the status of services which takes time."
"Its integration functions could be enhanced."
"There's an array of upcoming versions with numerous features to be incorporated into the roadmap. Customers particularly appreciate the service's emphasis on intensive security, especially the secret scanning aspect. During the proof of concept (POC) phase, the system is required to gather logs from the customer's environment. This process entails obtaining specific permissions, especially in terms of gateway access. While most permissions for POC are manageable, the need for various permissions may need improvement, especially in the context of security."
"We are experiencing problems with Cloud Native Security reporting."
"It took us a while to configure the software to work well in this type of environment, as the support documents were not always clear."
"Maybe container runtime security could be improved."
"We've found a lot of false positives."
"We had a glitch in PingSafe where it fed us false positives in the past."
"Scanning capabilities should be added for the dark web."
"When you find a vulnerability and resolve it, the same issue will not occur again. I want PingSafe to block the same vulnerability from appearing again. I want something like a playbook where the steps that we take to resolve an issue are repeated when that issue happens again."
More Azure Kubernetes Service (AKS) Pricing and Cost Advice →
More Singularity Cloud Security by SentinelOne Pricing and Cost Advice →
Azure Kubernetes Service (AKS) is ranked 13th in Container Security with 32 reviews while Singularity Cloud Security by SentinelOne is ranked 6th in Container Security with 67 reviews. Azure Kubernetes Service (AKS) is rated 8.2, while Singularity Cloud Security by SentinelOne is rated 8.6. The top reviewer of Azure Kubernetes Service (AKS) writes "Decreases administrative burdens and costs, has good diagnostic tools, and is easy to deploy". On the other hand, the top reviewer of Singularity Cloud Security by SentinelOne writes "Provides excellent workload telemetry, hunting capabilities, and deep visibility ". Azure Kubernetes Service (AKS) is most compared with OpenShift, CrowdStrike Falcon Cloud Security, SUSE Rancher and Qualys VMDR, whereas Singularity Cloud Security by SentinelOne is most compared with Prisma Cloud by Palo Alto Networks, Wiz, Orca Security and AWS GuardDuty. See our Azure Kubernetes Service (AKS) vs. Singularity Cloud Security by SentinelOne report.
See our list of best Container Security vendors.
We monitor all Container Security reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
