Try our new research platform with insights from 80,000+ expert users

FortiCNAPP vs Red Hat Advanced Cluster Security for Kubernetes comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Nov 18, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

FortiCNAPP
Ranking in Container Security
30th
Average Rating
8.4
Reviews Sentiment
6.9
Number of Reviews
11
Ranking in other categories
Vulnerability Management (41st), Cloud Workload Protection Platforms (CWPP) (18th), Cloud Security Posture Management (CSPM) (26th), Cloud-Native Application Protection Platforms (CNAPP) (16th), Compliance Management (10th)
Red Hat Advanced Cluster Se...
Ranking in Container Security
20th
Average Rating
8.2
Reviews Sentiment
7.5
Number of Reviews
12
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2026, in the Container Security category, the mindshare of FortiCNAPP is 2.7%, up from 1.7% compared to the previous year. The mindshare of Red Hat Advanced Cluster Security for Kubernetes is 2.1%, down from 2.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Security Market Share Distribution
ProductMarket Share (%)
Red Hat Advanced Cluster Security for Kubernetes2.1%
FortiCNAPP2.7%
Other95.2%
Container Security
 

Featured Reviews

SK
Software Engineer at a university with 5,001-10,000 employees
Improving security insights has been helpful but inconsistent vulnerability tracking needs attention
The vulnerability part is not systematically organized; it is all clumsy in the web UI, and it is not user-friendly. Regarding improvements, the vulnerability part, recent changes with user management, and Fortinet IM coming into place, which is not helpful at all because it cuts out the automation part, are the most important things. Lacework FortiCNAPP should have a new clean UI and ease of access for the users as that should be the main concern. There are limitations regarding the scalability of Lacework FortiCNAPP. There are also more limitations with integrations like GitHub or any other pipeline, CI/CD, or ISD. It is glitchy and works well only sometimes, and most of the time, the reports or other things are not properly calculated or circulated with the teams.
Daniel Stevens - PeerSpot reviewer
Software Engineer at Galley
Offers easy management and container connection with HTTPS, but the support needs to improve
I have experience with the solution's setup in Rio de Janeiro, Brazil and our company has assisted in the development of a cluster in a research department, but we didn't start from scratch because we have IT professionals who have installed Kubernetes across 12 nodes of a cluster and a new environment can be created for a new platform. I also had another setup experience of Red Hat Advanced Cluster Security for Kubernetes in Portugal where I had to implement the solution in a cluster of 22 computer servers, which was completed with assistance from the IT department of the company. The initial setup process of the solution can be considered as difficult. The setup process involves using the permissions, subnets and range of IPs, which makes it complex. Deploying Red Hat Advanced Cluster Security for Kubernetes takes around eight to ten hours for new clusters. The solution's deployment can be divided into three parts. The first part involves OpenStack, where the cluster's resources need to be identified. The second part involves virtualizing assets and identifying other physical assets, for which OpenStack, Kubernetes, or OpenShift are used. The third part of the deployment involves dividing the networks into subnetworks and implementing automation to deploy the microservices using Helm. The number of professionals required for the solution's deployment depends upon the presence of automated scripts. Ideally, two or three professionals are required to set up Red Hat Advanced Cluster Security for Kubernetes.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"For the most part, out-of-the-box, it tells you right away about the things you need to work on. I like the fact that it prioritizes alerts based on severity, so that you can focus your efforts on anything that would be critical/high first, moderate second, and work your way down, trying to continue to improve your security posture."
"The most valuable feature is Lacework's ability to distill all the security and audit logs. I recommend it to my customers. Normally, when I consult for other customers that are getting into the cloud, we use native security tools. It's more of a rule-based engine."
"Polygraph compliance is a valuable feature. In our perspective, it delivers significant benefits. The clarity it offers, along with the ability to identify and address misconfigurations, is invaluable. When such issues arise, we promptly acknowledge and take action, effectively collaborating with our teams and the responsible parties for those assets. This enables us to promptly manage problems as soon as they arise."
"Lacework is helping a lot in reducing the noise of the alerts. Usually, whenever you have a tool in place, you have a lot of noise in terms of alerts, but the time for an engineer to look into those alerts is limited. Lacework is helping us to consolidate the information that we are getting from the agents and other sources. We are able to focus only on the things that matter, which is the most valuable thing for us. It saves time, and for investigations, we have the right context to take action."
"I find the cloud configuration compliance scanning mature. It generates a lot of data and supports major frameworks like ISO 27001 or SOC 2, providing reports and datasets. Another feature I appreciate is setting custom alerts for specific events. Additionally, I value the agent-based monitoring and scanning for compute nodes. It gives us deeper insights into our workloads and helps identify vulnerabilities across our deployed assets."
"The best feature, in my opinion, is the ease of use."
"The most valuable aspects are identifying vulnerabilities—things that are out there that we aren't aware of—as well as finding what path of access attackers could use, and being able to see open SSL or S3 buckets and the like."
"The most valuable feature, from a compliance perspective, is the ability to use Lacework as a platform for multiple compliance standards. We have to meet multiple standards like PCI, SOC 2, CIS, and whatever else is out there. The ability to have reports generated, per security standard, is one of the best features for me."
"The benefit of working with the solution is the fact that it's very straightforward...It is a perfectly stable product since the details are very accurate."
"The technical support is good."
"Scalability-wise, I rate the solution a nine out of ten."
"The most beneficial security feature of the product revolves around the areas of vulnerability and configuration."
"Segmentation is the most powerful feature."
"I like virtualization and all those tools that come with OpenShift. I also like Advanced Cluster Management and the built-in security."
"I am impressed with the tool's visibility."
"The most valuable feature is the ability to share resources."
 

Cons

"Lacework lacks remediation features, but I believe they're working on that. They're focused on the reporting aspect, but other features need to improve. They're also adding some compliance features, so it's not worth saying they need to get better at it."
"A feature that I have requested from them is the ability to sort alerts and policies based on a security framework. Right now, when you go into alerts, you have hundreds and hundreds of them that you have to manually pick. It would be useful to have categories for CIS Benchmark or SOC 2 and be able to display all the alerts and policies for one security framework."
"The configuration and setup of alerts should be easier. They should make it easier to integrate with systems like Slack and Datadog. I didn't spend too much time on it, but to me, it wasn't as simple as the alerting that I've seen on other systems."
"The biggest thing I would like to see improved is for them to pursue and obtain a FedRAMP moderate authorization... I don't believe they have any immediate plans to get FedRAMP moderate authorized, which is a bit of a challenge for us because we can only use Lacework in our commercial environment."
"Lacework has not reduced the number of alerts we get. We've actually had to add resources as a result of using it because the application requires a lot of people to understand it to get the value out of it properly."
"The solution lacks a cohesive data model, making extracting the necessary data from the platform challenging. It uses its own LQL query language, and each database across different layers and modules is structured differently, complicating correlation efforts. Consequently, I had to create extensive custom reports outside Lacework because their default dashboards didn't communicate risk metrics. They're addressing these issues by redesigning their tools, including introducing the dashboard, which is a step closer to actionable insights but still needs refinement."
"The vulnerability part is not systematically organized; it is all clumsy in the web UI, and it is not user-friendly."
"I would like to see a remote access assistance feature. And the threat-hunting platform could be better."
"The tool's command line and configuration are hard for us to understand and make deployment complex. It should also include zero trust, access control features and database connectivity."
"Red Hat is somewhat expensive."
"The testing process could be improved."
"The initial setup is pretty complex. There's a learning curve, and its cost varies across different environments. It's difficult."
"They're trying to convert it to the platform as a source. They are moving in the direction of Cloud Foundry so it can be easier for a developer to deploy it."
"I do see that some features associated with the IAST part are not included in the tool, making it an area where improvements are required."
"The solution lacks features when compared to some of the competitors such as Prisma Cloud by Palo Alto Networks and has room for improvement."
"The deprecation of APIs is a concern since the deprecation of APIs will cause issues for us every time we upgrade."
 

Pricing and Cost Advice

"My smaller deployments cost around 200,000 a year, which is probably not as expensive as Wiz."
"The pricing has gotten better. That scenario was somewhat unstable. They have a rather interesting licensing structure. I believe you get 200 resources per "Lacework unit." It was difficult, in the beginning, to figure out exactly what a "resource" was... That was a problem until about a year or so ago. They have improved it and it has stabilized quite a bit."
"It is slightly expensive. It depends on how big your environment is, but it is expensive. Right now, we are spending a lot of money. We have covered all of the cloud providers and most of our colocation facilities as well, so we cannot complain, but it is slightly expensive. It is not super expensive."
"The licensing fee was approximately $80,000 USD, per year."
"The pricing model is moderate, meaning it is not very expensive."
"Red Hat offers two pricing options for their solution: a separate price, and a bundled price under the OpenShift Platform Plus."
"We purchase a yearly basis license for the solution."
"It's a costly solution"
"The price of Red Hat Advanced Cluster Security for Kubernetes is better than Palo Alto Prisma."
report
Use our free recommendation engine to learn which Container Security solutions are best for your needs.
881,757 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
12%
Manufacturing Company
7%
University
6%
Financial Services Firm
27%
Computer Software Company
9%
Government
8%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise4
Large Enterprise4
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise2
Large Enterprise4
 

Questions from the Community

What is your experience regarding pricing and costs for Lacework?
My smaller deployments cost around 200,000 a year, which is probably not as expensive as Wiz.
What needs improvement with Lacework?
The vulnerability part is not systematically organized; it is all clumsy in the web UI, and it is not user-friendly. Regarding improvements, the vulnerability part, recent changes with user managem...
What is your primary use case for Lacework?
The major use case for Lacework FortiCNAPP is for security. I'm using it for security internally for my company.
What needs improvement with Red Hat Advanced Cluster Security for Kubernetes?
From an improvement perspective, I would like to create new policies in the tool, especially if it is deployed for the prevention part, but currently, we need to do it manually. I hear that Palo Al...
What is your primary use case for Red Hat Advanced Cluster Security for Kubernetes?
I use the solution in my company for vulnerability management, configuration management, compliance, safety handling, and everything else.
What advice do you have for others considering Red Hat Advanced Cluster Security for Kubernetes?
The tool's policy management supports our company's compliance efforts since any corporate entity or enterprise must follow specific regulations, which include periodic analysis and configuration r...
 

Also Known As

Polygraph, FortiCNP, Lacework
StackRox
 

Overview

 

Sample Customers

J.Crew, AdRoll, Snowflake, VMWare, Iterable, Pure Storage, TrueCar, NerdWallet, and more.
City National Bank, U.S. Department of Homeland Security
Find out what your peers are saying about FortiCNAPP vs. Red Hat Advanced Cluster Security for Kubernetes and other solutions. Updated: December 2025.
881,757 professionals have used our research since 2012.