SentinelOne Singularity Cloud Security Reviews

The solution closes the gaps in cloud infrastructure. We can find any gaps that exist and what possible attack factors may be. Everything is gathered together and removed. So we primarily use it for cloud security assessment.  

The primary benefit for our company has been the reduction of false positives. It's saved us time and resources. 

I like that we get a map view of all the assets we have and how these assets are connected together. We can get a view of the entire structure and that gives us a good vantage point when assessing gaps. We can see which assets are public and which are private. It gives us good visibility.

It brings in good security.

It is fairly simple. Anybody can use it.

The evidence-based reporting capabilities are useful. It's good for everyday reporting. It makes it easy to identify actual false positives. Priority cases are assigned accordingly so we don't need to find a needle in a haystack. If something is critical, it's very easy to find and see it. 

The solution offers agentless vulnerability scanning, which helps us identify any open ports on the server or any vulnerable assets online in the cloud. 

While they do have an offensive security engine, we do not use that aspect. We use a different vendor for that. However, it's a very good initiative. It basically expands and searches and does more offensive security.

It's very easy to integrate.

The notifications are very good. We can get notified right on Slack. if we aren't checking out email regularly.

The benefits we witnessed were pretty immediate post-implementation. Once you've done your integrations, it starts showing you vulnerabilities that are being observed, and he lets us immediately identify and deal with infrastructure gaps. It even has allowed us to deal with several misconfigurations. 

It has helped us reduce false positives significantly. That's something I've been focused on. 

The solution has positively affected our risk posture. Thanks to the lower number of security vulnerabilities, it's helped us with several benchmarks and compliance-related issues. 

Our mean time to detection and mean time to remediation has been reduced. If there's an issues, it can be found and dealt with in a short amount of time. It also gives you remediation details as to where particular vulnerabilities exist. We're able to fix problems as soon as possible when we see issues pop up. The mean time to remediation depends on the severity of the issue and who is handling it. Remediation for an experienced user versus a new hire may vary.

After introducing PingSafe, we were able to bridge the gap between developers. Since PingSafe had details about that particular vulnerability and how to remediate it, we could just pass that on to the application developers, who could fix it. That has also reduced the number of vulnerabilities that are being discovered by the application security testing team.

There is a bit of a learning curve. However, you only need 2 to 3 days to identify options and get accustomed. 

They could separate or differentiate between different kinds of frameworks.

I've used the solution since I started working with my company - for about one year and three months. 

I don't recall any stability issues. 

The solution is scalable. The scalability is highly flexible. 

We do have regular meetings with support. They catch us up every month and provide us regular updates and solicit feedback. Support is excellent.

I have not used any alternatives.

I was not initially involved in the deployment process. 

There isn't really any maintenance needed. The only thing would be if you find a false positive. You can mark it so it doesn't happen again. Beyond that, you don't have to maintain anything. 

I'm not sure how the pricing for the solution works. 

I'm an end-user. 

I'd rate the solution 9 out of 10. 

It's pretty easy to use. Integration with cloud infrastructure may require a bit of help in the initial stages. However, once you are up and running, finding vulnerabilities is simple and reporting is good. 

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 company relies on Cloud Native Security to fortify the security of our cloud accounts spanning various environments, such as AWS, AZURE and Google Cloud. Cloud Native Security provides timely alerts upon identifying vulnerabilities within our cloud infrastructure services, such as security groups and data encryption, empowering us to prioritize and address them promptly.

Cloud Native Security helps us discover vulnerabilities in a cloud environment like open ports that allow people to attack our environment. If someone unintentionally opens a port, we are exposed. Cloud Native Security alerts us so we can remediate the problem. We can also automate it so that Cloud Native Security will fix it. 

Since implementing Cloud Native Security, our security team has engaged in robust discussions on enhancing compliance with key regulatory standards such as SOC, ISO, and other pertinent IT infrastructure-related guidelines. As a result of these proactive measures, our security posture has seen a remarkable improvement, reflecting our commitment to maintaining a secure and compliant environment.

Cloud Native Security plays a major role in compliance. IT companies must maintain our company's security level to achieve ISO-based certifications. We are so proud of the changes we have made using Cloud Native Security. We've implemented many of the controls Cloud Native Security recommended, helping us maintain a high security standard. Fintech companies must maintain security best practices overall in our infrastructure. 

Cloud Native Security offers suggestions about best practices for security, and we've implemented them all. It's helpful for companies hosting their applications in the cloud configuration. This tool enables us to record unauthorized actors or security failures. Everything is reported in Cloud Native Security, allowing us to rectify mistakes and misconfigurations.

When security threats occur, Cloud Native Security immediately alerts us through various communication channels. It has several modules, including cloud misconfigurations, container security, Kubernetes, vulnerability management, infrastructure code scanning, and cloud detection and response. It also tells us when unauthorized API calls are occurring. Everything is recorded in Cloud Native Security, and it alerts us about what is happening in the account. The detection time for critical alerts is almost instant. We'll see it in under two minutes. 

The solution saves the company a lot of time. Responding to alerts can take up a lot of our team's bandwidth. But there is a feature of their remediate that helps the bandwidth of our engineering team to fix the issues when we used Cloud Native Security as a team member. They helped us fix the issues and saved a lot of bandwidth for our team.

My top preferences revolve around infrastructure-as-code scanning and Kubernetes security. With infrastructure-as-code scanning, we catch errors or inadvertent inclusion of sensitive data in our code prior to deploying infrastructure via Terraform. As we continue to leverage Terraform for infrastructure deployment, alongside embracing new technologies to stay aligned with industry advancements, these features play a pivotal role in maintaining our security standards and workflow efficiency.

Cloud Native Security helps us detect vulnerabilities when deploying infrastructure.  We use Cloud Native Security to monitor all our cloud infrastructure and accounts. It continuously scans whether or not we have the agent installed. It's something like a role. You can configure an IAM role that provides access to Cloud Native Security to scan. It enables seamless connectivity with any cloud environment.

The Offensive Security Engine has helped us to discover some breaches.
You can see across the cloud domain in Cloud Native Security. For example, the dot com map can cover multiple servers internally. Cloud Native Security flags all URLs exposed to the public and other vulnerabilities. When we get alerts from the Offensive Security Engine, it has some internal debugging tools the developers can use. 

The Kubernetes scanning on the Oracle Cloud needs to be improved. It's on the roadmap. AWS has this capability, but it's unavailable for Oracle Cloud. 

I have used Cloud Native Security for three years.

Cloud Native Security is highly stable. 

Cloud Native Security is scalable. 

I rate Cloud Native Security support nine out of ten. They solve issues within the agreed-upon period. They're impressive. 

Positive

We previously used the native AWS tools like Inspector. Cloud Native Security is impressive compared to those. 

It's easy to integrate Cloud Native Security and onboard all our cloud accounts. Before implementing, we tried to have all the security best practices in place. If you do that, it's easier to fix the vulnerabilities when Cloud Native Security detects them. Deployment took about five or six minutes. 

We opted for Business Plan at an affordable rate, providing excellent value for your investment. While I'm not entirely certain, I believe the monthly cost is around 180,000 rupees.

We looked at Trend Micro and some other options.

I rate Cloud Native Security nine out of ten. Use this tool if you want to keep your cloud applications secure.

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.

Positive

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.

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 primarily use SentinelOne Singularity Cloud Security for compliance purposes because we work with banks and the fintech industry, so we must follow some standards like PCI DSS.

We use SentinelOne Singularity Cloud Security for compliance and security purposes, and it has helped a lot. We face many audits, and during each audit, we must conduct a vulnerability assessment. SentinelOne Singularity Cloud Security gives us a list of vulnerabilities that we remediate to raise our compliance score. It's our only tool for vulnerability assessments. The benefits are mostly immediate. SentinelOne Singularity Cloud Security helped reduce the number of false positives, which has been difficult.

We like SentinelOne Singularity Cloud Security's vulnerability assessment and management features, and its vulnerability databases. The interface isn't too complex. It's quite easy to use. The agentless vulnerability scan is the feature we use the most.

The categorization of the results from the vulnerability assessment could be improved. 

We have used SentinelOne Singularity Cloud Security for 2 years. 

I have never faced any downtime.

SentinelOne Singularity Cloud Security's scalability is quite good. We have multiple projects, and scalability isn't an issue. 

I rate SentinelOne Singularity Cloud Security 8 out of 10 based on the features I have used. I haven't used all the features, but I give the vulnerability and compliance features 8 out of 10. I can recommend SentinelOne Singularity Cloud Security for vulnerability scanning and compliance. There are many competitors, but I find SentinelOne Singularity Cloud Security quite good, which is why we haven't switched to something else for the past 2 years. 

I consider it a cloud security posture management tool. It is being used for the overall posture of the environment. 

By implementing Cloud Native Security, we wanted to monitor end-to-end misconfigurations. That is why we started with it. We are now also using one other module for detection and response, but mainly, we are using it to monitor misconfiguration and benchmark compliance.

It is pretty good. It has good coverage and a good reporting system.

There has been tremendous improvement since implementing Cloud Native Security. Cloud Native Security reports any misconfiguration that is there in the infrastructure. We do not have to go and check each service individually. It has helped a lot.

For compliance management, we can find the benchmark compliance status in Cloud Native Security directly. We do not have to do anything. Many benchmarks that we are supposed to follow are added by default. It is pretty easy for us to showcase compliance to anyone.

Misconfiguration detection has been the most effective for threat detection in our cloud environment. We are mainly focusing on the misconfiguration. I can see any configuration-related issues in all the modules.

Because it covers all the modules, every single aspect of the compliance has improved. We were able to find out the critical issues related to cloud infrastructure. It is a real-time monitoring system, so, at any time, we can check and confirm.

Cloud Native Security provides information about the exact affected area. We can easily locate a resource in a particular account or service. It is very clear from the Cloud Native Security report where to look for a particular misconfiguration. They have also added a graphical representation.

The reports tell us what is the impact, how critical it is, and how to locate the issue. That helps to prioritize things and fix a critical issue on an urgent basis. It is easy to analyze things from our side.

After implementing Cloud Native Security, we were able to implement so many best practices. Initially, we were getting different types of issues. We learned from those issues, and we are now implementing best practices based on that. We are also able to do real-time monitoring.

It has helped reduce the number of false positives we deal with. We are hardly getting any false positives. Previously, if we had four false positives, we now have only one false positive.

Cloud Native Security's ease of use and precision in detection have improved our risk posture a lot.

Cloud Native Security has saved our mean time to detect. It has saved a lot of our time. It has saved almost 95% of the time because we cannot go and check all the services in AWS. It is very vast. Cloud Native Security gives us specific information. There is no manual effort.

Cloud Native Security has not helped reduce our mean time to remediate because remediation depends on so many factors. It has nothing to do with Cloud Native Security. We are getting the issues, and the team is responding to them. After fixing them, there is a lot of improvement in the number of issues.

It is pretty easy to integrate with this platform. When properly integrated, it monitors end-to-end. The other thing is the coverage. As far as I know, it has pretty good coverage. 

It is very easy to use. I would rate it a nine out of ten for ease of use. 

We are getting reports only in a predefined form. I would like to have customized reports so that I can see how many issues are open or closed today or in two weeks. 

I have been using Cloud Native Security for around ten months.

It is stable. I would rate it a nine out of ten for stability.

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

Overall, we have seven users of this solution, but at a time, we only have two active users. It is being used in a single location.

Their support is good. Whenever we have doubts, we get proper support. We connect with them and resolve the issue. I would rate them a nine out of ten.

Positive

We did not use any other solution. This is the first one.

It is on the cloud. The implementation phase varies. It can take a few months.

It does not require any maintenance.

I am not involved in the pricing, but it is cost-effective.

I would recommend Cloud Native Security to others. Overall, I would rate Cloud Native Security a nine out of ten.

It's a cloud-based SaaS tool. It's a cloud security partnership management tool. It gives you an overview of misconfigurations, Kubernetes security, Docker security, vulnerability scanning, and secret scanning.

Atlas security graph is pretty cool. It maps out relationships between components on AWS, like load balancers and servers. This helps visualize potential attack paths and even suggests attack paths a malicious actor might take.

Maybe container runtime security could be improved. But with the acquisition by a bigger company, things might roll out faster, potentially including this feature.

I have been using it for six months. 

It's been stable in my experience. 

Since it's a managed service, Cloud Native Security handles scalability. There are around 15 end users in my company using it.

We could just contact the CEO directly with any questions. It was a small team back then, but I don't think that's the case anymore since they've been acquired.

Previously, it was just a 50-person team, and the CEO would hop on the call to solve the problem. 

The initial setup is super easy! It's a SaaS portal, so no deployment is needed. Just configuration that takes about half an hour.

It was reasonable pricing for me. The costing model might have changed now since they have been acquired. 

I would advise integrating your Kubernetes clusters for extra features.

Overall, I would rate the solution a nine out of ten because I'm happy with Cloud Native Security overall.

The number of features Cloud Native Security offered with just a small team was phenomenal. Give them another six months to a year, and it could be one of the best tools out there.