Wiz

Easy-to-understand layout: Users appreciate the easy-to-understand and approachable layout of findings in Wiz, even for those without extensive cloud configuration knowledge. They find the presentation of dashboards and graphs to be easy to interpret, providing in-depth visibility across all assets operating within their cloud environments.

Rich with detail and risk-rated findings: Many reviewers have praised Wiz for providing detailed findings that are appropriately risk-rated. The rich level of detail helps users quickly identify and prioritize security issues, allowing them to take prompt action.

Effective integration with ticketing/alert systems: Several users find Wiz's integration with ticketing/alert systems to be seamless and efficient. This feature allows them to easily delegate findings to other teams, streamlining the overall workflow and ensuring timely resolution of security issues.

Confusing User Interface: Some users have found the user interface of Wiz confusing and difficult to navigate, particularly when searching for specific information or generating reports. The GUI can be challenging to navigate and may not always present desired information clearly.

Difficulty in Finding Assets: Several users have mentioned difficulty in finding assets due to case-sensitive searches, especially when using FQDNs. This has made it tedious and time-consuming for users to track down responsible parties in the cloud environment based on AWS ARNs.

High Cost: The pricing of Wiz has been a concern for some users, with several mentioning that it is high and does not align with their deployment needs. There have been suggestions for a different pricing model to cater to the needs of different users.

Users commonly recommend the following actions when using the software:

1. Run a proof of concept (POC) to gain visibility, understand security posture, and save time and money. This recommendation allows users to assess the software's capabilities and its fit with their specific needs. By conducting a POC, users can make informed decisions before fully committing to the software.

2. Assess current needs and requirements before deciding to use the software. This suggestion emphasizes the importance of evaluating one's own security needs and objectives before implementing the software. Users should consider factors such as compliance needs and exposure concerns to ensure that the software effectively meets their expectations.

3. Utilize the software's fast and efficient capabilities in meeting compliance needs and addressing exposure concerns. Users appreciate how the software streamlines compliance processes, helping them meet regulatory requirements efficiently. Additionally, users find value in the software's ability to address potential security risks and vulnerabilities, minimizing exposure to threats.

Overall, users find the software valuable for gaining visibility into their security posture and saving time and money through a proof of concept. They also stress the importance of assessing current needs before adopting the software given its effectiveness in meeting compliance requirements and addressing exposure concerns.