Wiz can be improved by providing clearer remediation guidance, more actionable remediation recommendations, and better integration with existing security and ticketing tools. Simplifying dashboards and reducing false positives would help teams prioritize genuine threats more efficiently. Improved reporting and customization options would also make it easier to track security improvements over time. Better prioritization of security alerts, more accurate risk scoring, and clearer step-by-step remediation guidance would make Wiz even more effective. Enhanced automation for routine security tasks and more flexible reporting would also help teams save time and manage cloud security risk more efficiently. Wiz could further improve its automated remediation capabilities, provide more customizable security reports, and offer clearer explanations of risk scores. Better integration with existing workflows and fewer false-positive alerts would help teams resolve genuine security issues faster and manage cloud risks more efficiently.
Information Security Analyst at a manufacturing company with 10,001+ employees
Real User
Top 5
Sep 3, 2026
While Checkmarx may perform better in some deep code scanning aspects, Wiz is considerably easier to use, has a better user interface, and offers a more compelling argument for its use. It is more robust and stable, making these positive points quite clear. The only slight negative is its scanning capability compared to Checkmarx, but it is still very good. Additional comments regarding needed improvements around scanning capabilities or any other area where Wiz could catch up to Checkmarx are not necessary.
I believe a little more documentation could help users follow step by step. That is the extent of the improvements needed. I feel there is a bit of noise in the initial setup and quality cleaning that may take time in larger environments. Additionally, advanced features might require security expertise; hence, improvements in documentation would be beneficial. Otherwise, all aspects are very good and easy to use.
More customizable executive dashboards can be created, and better reporting for non-technical stakeholders can also be improved in Wiz platform. Overall, it is a mature platform and most enhancements I would like are around reporting automation and simplifying executive level reporting.
I haven't really explored the scalability of Wiz Code yet, but I'm looking to explore it on the production side for my DevSec project scheduled to start in about two weeks from now. The pricing of Wiz Code is a little bit higher for small enterprises that I run, but it's something that I can manage.
Security Architect/Staff Engineer at a consultancy with 10,001+ employees
Real User
Top 5
May 21, 2026
Every tool has some sort of improvement required. No tool can be said to be one hundred percent secure, so there's always a scope for improvement. When it comes to Wiz Code, how they are ingesting the metadata with respect to the integrated platform is something they can improve upon. In fact, they have already started working on this and are continuously improving those data ingestion parts with the integrated platform, whether GitHub, Bitbucket, or GitLab. Whatever information the platform is ingesting can be further used for automation as well. If I want to create some sort of policy by ingesting those data, I can do that. However, that requires visibility to the API that can support these integrations. In summary, there is a good scope for improvement for this platform. Metadata ingestion and probably the integration of Wiz Code platform is something which is missing. They are already working on that. With the advancement of GenAI and AI, most vendors are in the AI race, and they want to make sure they are supportable for other platforms that are currently used in vibe coding. This is something I think Wiz Code can work on, making those integrations accessible for vendors available in the market.
The areas that have room for improvement in Wiz Code are their IaC policies, which require a little more maturity. When discussing IaC policies, you want to ensure engineers cannot merge anything non-compliant to your environment, and they need to streamline these with different cloud service providers, as every cloud has its own policies, such as Azure's policies. They need to mature their IaC policies and provide more custom policies for better integration. Aside from the policies, that is the main area for improvement.
Security Manager at a consultancy with 10,001+ employees
Real User
Top 20
Jan 2, 2026
I have a big improvement in mind for Wiz Code, not a small improvement. When I look at tools such as vulnerability detection tools, I focus on how the reporting could help fast-track risk mitigations. I don't want folks to just look at the severity rating, whether it's critical, high, or medium. I would love to see how that presents a risk. Meaning that if a particular vulnerability is compromised, it could be a low severity, but if it's compromised, what business impact does it have? With capabilities we have in AI and other technologies, I think we could do much more than just sharing vulnerability ratings or severity ratings for folks to act on. That approach is outdated. Something that communicates the value would make sense and could help drive or change habits. That's what I'm thinking, and that's why I say it's a big one, not just something small.
There is nothing I wish worked better or features I would like to see for improving Wiz Code. There is nothing that comes to mind about needed improvements for Wiz Code.
Wiz enhances cloud security with features like CSPM, risk prioritization, and centralized visibility. Users benefit from agentless scanning and integration with CI/CD tools, improving threat detection and compliance management.Wiz offers a comprehensive security solution for cloud environments by providing functionalities like threat intelligence, detailed risk analysis, and automated compliance mapping. It supports vulnerability management and risk analysis, utilizing agentless deployment...
Wiz could use some more clarity on the limits and budgets in their license offerings. There could be more clarity in the licensing and costs of Wiz.
I think Wiz could improve its identity component.
Wiz can be improved by providing clearer remediation guidance, more actionable remediation recommendations, and better integration with existing security and ticketing tools. Simplifying dashboards and reducing false positives would help teams prioritize genuine threats more efficiently. Improved reporting and customization options would also make it easier to track security improvements over time. Better prioritization of security alerts, more accurate risk scoring, and clearer step-by-step remediation guidance would make Wiz even more effective. Enhanced automation for routine security tasks and more flexible reporting would also help teams save time and manage cloud security risk more efficiently. Wiz could further improve its automated remediation capabilities, provide more customizable security reports, and offer clearer explanations of risk scores. Better integration with existing workflows and fewer false-positive alerts would help teams resolve genuine security issues faster and manage cloud risks more efficiently.
While Checkmarx may perform better in some deep code scanning aspects, Wiz is considerably easier to use, has a better user interface, and offers a more compelling argument for its use. It is more robust and stable, making these positive points quite clear. The only slight negative is its scanning capability compared to Checkmarx, but it is still very good. Additional comments regarding needed improvements around scanning capabilities or any other area where Wiz could catch up to Checkmarx are not necessary.
I believe a little more documentation could help users follow step by step. That is the extent of the improvements needed. I feel there is a bit of noise in the initial setup and quality cleaning that may take time in larger environments. Additionally, advanced features might require security expertise; hence, improvements in documentation would be beneficial. Otherwise, all aspects are very good and easy to use.
More customizable executive dashboards can be created, and better reporting for non-technical stakeholders can also be improved in Wiz platform. Overall, it is a mature platform and most enhancements I would like are around reporting automation and simplifying executive level reporting.
I haven't really explored the scalability of Wiz Code yet, but I'm looking to explore it on the production side for my DevSec project scheduled to start in about two weeks from now. The pricing of Wiz Code is a little bit higher for small enterprises that I run, but it's something that I can manage.
Every tool has some sort of improvement required. No tool can be said to be one hundred percent secure, so there's always a scope for improvement. When it comes to Wiz Code, how they are ingesting the metadata with respect to the integrated platform is something they can improve upon. In fact, they have already started working on this and are continuously improving those data ingestion parts with the integrated platform, whether GitHub, Bitbucket, or GitLab. Whatever information the platform is ingesting can be further used for automation as well. If I want to create some sort of policy by ingesting those data, I can do that. However, that requires visibility to the API that can support these integrations. In summary, there is a good scope for improvement for this platform. Metadata ingestion and probably the integration of Wiz Code platform is something which is missing. They are already working on that. With the advancement of GenAI and AI, most vendors are in the AI race, and they want to make sure they are supportable for other platforms that are currently used in vibe coding. This is something I think Wiz Code can work on, making those integrations accessible for vendors available in the market.
The areas that have room for improvement in Wiz Code are their IaC policies, which require a little more maturity. When discussing IaC policies, you want to ensure engineers cannot merge anything non-compliant to your environment, and they need to streamline these with different cloud service providers, as every cloud has its own policies, such as Azure's policies. They need to mature their IaC policies and provide more custom policies for better integration. Aside from the policies, that is the main area for improvement.
I have a big improvement in mind for Wiz Code, not a small improvement. When I look at tools such as vulnerability detection tools, I focus on how the reporting could help fast-track risk mitigations. I don't want folks to just look at the severity rating, whether it's critical, high, or medium. I would love to see how that presents a risk. Meaning that if a particular vulnerability is compromised, it could be a low severity, but if it's compromised, what business impact does it have? With capabilities we have in AI and other technologies, I think we could do much more than just sharing vulnerability ratings or severity ratings for folks to act on. That approach is outdated. Something that communicates the value would make sense and could help drive or change habits. That's what I'm thinking, and that's why I say it's a big one, not just something small.
Integration with more scans would be great, though Wiz Code is currently pretty solid as it is.
There is nothing I wish worked better or features I would like to see for improving Wiz Code. There is nothing that comes to mind about needed improvements for Wiz Code.