
WIZ Cloud Infrastructure Security Platform
Cloud risk posture has improved and runtime defenses prioritize and block real threats
What is our primary use case?
Our primary use case is managing Wiz as SecOps as a Service for several of our clients. We have it deployed for them, and we issue tickets, perform investigations, and follow up on the remediation path. We have Wiz deployed for several customers, and we use the CSPM model, Wiz Defend, and Wiz Log ingestion.
Our customers use Wiz Code in their operations.
Our customers utilize Wiz Defend in their security strategy, and they have some subscriptions to it.
How has it helped my organization?
Wiz has helped our customers achieve zero critical issues every now and then. I am talking about some criticals. Wiz at least gives the risk assessment and prioritizes issues. Because we don’t have everything hidden, we have several endpoints that are exposed. Every now and then, zero-days happen, and we can’t estimate them.
First of all, Wiz provides us with the threat newsletter, which is updated constantly, nearly in real time. So we can see the particular CVE that has exploits, for example, and it is correlated with a particular endpoint we have exposed. So we have the whole attack path chain.
Wiz provides this as a primary risk, marked as critical, so we proceed with fixing. Either we remove it from the surface, hiding the particular endpoint under a VPN if we can, or we patch the particular issue to the newest version so the exploit is gone.
Wiz has reduced alert fatigue in our customers’ organizations. I would say it is not very noisy at all, but if you go wider through the modules, it can be noisier. If you just need risk assessment for things that need to be prioritized, it is very good.
What is most valuable?
In terms of threat prevention, Wiz uses an eBPF agent that has been deployed on the endpoints. First of all, we use crafted policies to block some predefined processes. We also use it in combination with the Admission Controller to make sure that nothing more is deployed except what we need. We use their signals, which give us more investigation capabilities and more observability on the hosts themselves, in real time. We also have several policies applied, so we have them for hardening as well.
Compared to previous tools, the Wiz Runtime Sensor has helped us identify active threats more effectively. First of all, if you compare it with Palo Alto, Palo Alto uses a Defender that is not so lightweight. I don’t know whether it has the latest version and maybe it has already been re-architected to be an eBPF sensor, but at that time, the version we used previously for Palo Alto also required us to deploy sensors. They were pretty heavy on resources, and too many processes were redirected to one particular pod that should be deployed on each. So with Wiz, it is more comfortable to use in this way.
We also have experience with Upwind, with Orca, and with other vendors. As I said, configuration is where Wiz excels. In comparison with GuardDuty, because we are an AWS partner, we have a lot of experience with it. However, Wiz can do not just runtime security monitoring that gives you a particular event, for example, a reverse shell that has already been executed; it can also block, and you can tell it the particular process to be stopped, not others, but this one. You can have exclusions. The same goes for DNS queries, where you can use allow lists and block lists. So it is pretty configurable.
What needs improvement?
Wiz can be improved in a few areas. First of all, it has pretty deterministic controls that are already set, which is obviously a good thing. However, one feature I missed is CIEM. As for the features Wiz does have, Wiz can tell you, for example, whether a user has some admin permissions. I am talking about the identity access findings in Wiz. Wiz gives you observability into who has admin roles, for example, EKS admin, organizational admin, et cetera.
But IAM Access Analyzer, the service from AWS, is capable of showing particular roles, not just endpoints, that give external access. It can also do an assessment for least privileges. IAM Access Analyzer can provide you insights into what particular role can be hardened and how, because a list of permissions was given to it that is redundant. That particular role has not used them for, I don’t know, 30 days. So you have this insight, and you can harden it. I don’t see these capabilities in Wiz.
As I mentioned, Wiz has some deterministic approaches to verify some things. I believe that for now, we also require more AI features, and these features were released with the Red Agent, Blue Agent, and Green Agent, but all of them have particular purposes. I mean not only the particular findings but also threats, et cetera. I believe this might be a feature with the insights. Maybe you need some additions to the library of issues you have, for example, some particular threats, et cetera. Maybe it should be based on threat modeling for AWS or others, or MITRE. I don’t know, but I would like to see more AI-based insights on what you have right now. Maybe there is no particular detector on the Wiz side, but you might enhance it by hardening something, because our AI thinks it would be reasonable for you.
So you see that it is a kind of non-deterministic approach, but it must be done not strictly, but in the insights. Nonetheless, I believe it is valuable.
In the future, I would like to see additional AI capabilities. But the products that are released for AWS, such as AWS Security Agent, give you the ability to do code from spec-driven development, this new trend where you create the features in the AI assistant, give it all the context, and next, build the code. So, first of all, you have spec-driven development, and this new AI Agent gives you the ability to do this. I believe this is the new way people would like to work.
I believe it must be something that goes from spec-driven development to static code analysis, to software composition analysis, and next to dynamic code analysis, and does it all at once in one particular place. I don’t think my previous experience with Wiz Code shows that it is capable of doing this right now, but who knows, because the Red Agent was released recently. I don’t have much experience with it, but it is the pen-test tool that can do some dynamic code analysis on your application. Maybe several things combined can provide it. Overall, I would say this is the main thing: for code, it should be done from A to Z based on AI enrichment, et cetera, and so on.
For how long have I used the solution?
I have been dealing with Wiz for more than two years.
What's my experience with pricing, setup cost, and licensing?
Wiz is actually the most expensive product we have at all. I believe it is more about having it properly licensed, maybe. For several clients, we had usage overlap. For example, we estimated particular billing units, and after onboarding, our usage was more than we expected. However, I didn’t see Wiz charge us for this. Instead, I see that they give us some windows, et cetera. They are not strict about it, which is good. But the overall pricing is pretty huge.
What other advice do I have?
Unfortunately, we don’t have many resources for Wiz to collect them. We don’t even have a huge AI inventory.
I would rate Wiz as a product at nine out of 10, which is definitely high.
Cloud security has improved as we triage faster and maintain zero critical issues
What is our primary use case?
My main use case for Wiz is that it helps me triage the issues that are most important to fix, keeps me alerted to upcoming and developing threats, and helps me understand exactly what our security posture is.
Wiz helps me decide which issues to fix first by scoring findings by severity: Critical or High, Medium, and Low. It uses the context it has about our environment to help determine what is actually important to fix.
AI security posture management is something we are just starting to address in our cloud security strategy. We are trying to understand exactly what our posture is today, so it is difficult to answer questions about it.
How has it helped my organization?
Wiz has impacted our organization positively. We definitely respond to findings and alerts a lot quicker than we used to. We have a better understanding of the things that we have within, for example, GitHub, where there are or were many orphaned repos that were no longer used. We therefore have a better understanding of the things that are actually important to us.
Compared with before Wiz, it is hard for me to quantify or qualify how much faster we are responding to findings or alerts now. What I can say is that the longer we have had the product and the more features we have enabled, the quicker we have been able to respond to alerts, threats, and findings. Certainly there was an element of manual work done previously that has now been removed, which frees up some of my time. The time it takes to triage has certainly reduced.
Wiz makes cloud security more accessible across our teams. The dashboards we have created per team allow each team to take responsibility for the things that they are building. They are ultimately accountable for making sure that they keep on top of remediating issues. It basically makes a central security person's or team's life a lot easier because everyone has visibility of the current status.
Wiz has allowed us to consolidate tools. Specifically, over the last six months, we have decided to end our bug bounty program, and we now rely solely on Wiz.
Relying on Wiz instead of the bug bounty program has affected our ability to prioritize Critical cloud risks. We are definitely seeing fewer false positives than we did with the bug bounty program. Many of the bug bounty submissions over the last 12 months seem to have been generated by AI tools, which meant that we were inundated with submissions that were not actually relevant and lacked an awful lot of context.
Wiz does a good job overall of reducing alert fatigue in our organization. However, in the last 24 hours, there have been an awful lot of alerts around new threats. While Wiz does a good job pretty much overall of reducing alert fatigue, the last 24 to 48 hours have been quite challenging because of everything that has been happening outside.
Wiz has helped our organization achieve Zero Criticals in its issue queues. We have been at Zero Criticals for quite a while now, and each time a new Critical pops up, we tend to remediate it within a few hours.
What is most valuable?
The best features Wiz offers are a clear, easy-to-understand dashboard, clear remediation steps, and clear information that I can provide to different members of the organization, from our exec team through to our engineering team. This helps them understand our security posture, what needs to be fixed, what threats we currently face, what our attack surface is, and how we compare against security frameworks.
The dashboards and remediation guidance change my conversations with engineering and leadership. From an engineering point of view, they help us determine what the priorities are that we need to fix internally. Most of our resources are not external facing. However, for those that are external facing, there is more context about what Wiz can see from using a mixture of the Red Agent as well as understanding our infrastructure, so we can have sensible conversations about whether the findings are something we need to act on or not. From a leadership perspective, they help us understand our security posture and what our risk is from a threat perspective. They are also very useful for understanding exactly what sort of progress we are making.
The AI capabilities I have used are both the Red Agent and the Green Agent. I am very happy with both of them.
The accuracy and reliability of Wiz's AI output is pretty good, actually. We still double check everything that it provides, just to make sure that we are in agreement.
My impression of the cloud security democratization aspect of Wiz is that each team has its own dashboard.
We use Wiz Code in our operations. It is early days. Currently, we are warning engineers when issues are detected in their pull requests.
We utilize Wiz Defend in our security strategy. It is also early days. I have not noticed anything from Wiz Defend that has given us anything over and above what we had previously, but I am happy that we have it in place and that it will let us know when there is something that we need to worry about.
The Wiz Runtime Sensor has not yet helped us identify active threats compared with previous solutions. So far, we have not had anything identified.
What needs improvement?
I am pretty satisfied with what we have in place right now.
The one thing that could still be improved is the reporting. I am not 100% sure that I am happy with the reporting the way it is. I think it could be improved upon, although I am not quite sure how you would do that. It would be quite cool if Mika AI could be used to have a conversation so that it would be able to create tailored reports or tailored dashboards in a way that would satisfy the organizations using the product.
The reason I rate Wiz an eight is that, at times, the pricing structure is a bit confusing for people coming into it to understand. In terms of how easy it is to configure, it might be slightly better. Overall, though, it is a strong eight.
For how long have I used the solution?
I have been using Wiz for about seven years.
What do I think about the stability of the solution?
As far as I can tell, Wiz is stable.
What do I think about the scalability of the solution?
I have no complaints about Wiz's scalability. It seems to do exactly what we need it to do. It seems to scale well, but we are a small organization.
How are customer service and support?
I use Wiz's post-sale support services. I use both the Slack community and speak to our technical account manager and account manager at Wiz.
The customer support has been very helpful. So far, I have had no complaints. They have been super helpful. We have also used the "I'm Under Attack" button, and the response from that was really good as well.
On a scale of one to 10, I would give the customer support a 10.
Which solution did I use previously and why did I switch?
We did not previously use a different solution. We have been using Wiz for quite a while now.
What was our ROI?
I think we have seen a return on investment. We definitely see time saved in terms of response to threats and issues. In terms of fewer people needed, it is just myself running our security function, so Wiz helps me hugely, and we have not needed to recruit additional people. We have possibly not saved money.
What's my experience with pricing, setup cost, and licensing?
We purchased Wiz through the AWS Marketplace.
Pricing is an interesting topic because Wiz has a slightly different way of licensing and pricing. I found it slightly confusing to start with. Pricing-wise, it is a bit of a tough sell internally because it is probably one of the more expensive tools that we have. Overall, I think the rest of it is fine.
Which other solutions did I evaluate?
Before choosing Wiz, I did not evaluate other options. At my previous employer, we had tried different solutions, and they did not necessarily fit the bill, so we were keen to use Wiz here simply because of the ease of use and the ease of setup.
What other advice do I have?
On a scale of one to 10, I would rate Wiz overall as an eight.
My advice for others looking into using Wiz is definitely to do a proof of concept. Try to get a proof of concept that lasts more than two weeks because there are various moving parts. If you are in a situation similar to ours, where different teams are responsible for different services and capabilities internally, the licensing needs to be understood a little. Do not assume that you are getting coverage of everything from day one, because you will have to buy some licenses for monitoring your cloud estate, some for monitoring your Kubernetes estate, and some for monitoring your code estate.