SECURITY ATLAS / EVALUATION BRIEF Wiz Research reviewed: 2026-10-18 https://atlasofsecurity.com/landscape/vendors/wiz/ THE ATLAS TAKE Atlas judgment: Wiz is most interesting as a way to connect otherwise separate cloud risks into an explanation an owner can act on. Its graph and agentless posture story can help a distributed engineering organization reason about exposed resources, identity and vulnerable workloads together. That is different from proving runtime prevention: Wiz Defend and its sensor have their own scope, and the sensor is documented as an add-on. Evaluate the exact modules, permission footprint and remediation handoff; a compelling attack-path visualization is valuable only if its underlying relationships are correct and its proposed fix survives deployment. SCOPE This profile covers the Wiz platform and separately scoped Sensor capability. Agentless API or snapshot visibility is not runtime monitoring. Verify cloud, workload and module coverage rather than assuming the same capability exists for every connected account. WORTH A LOOK WHEN Multicloud engineering organizations that need shared risk context and can assign remediation to service owners. THINK TWICE WHEN The requirement is comprehensive runtime blocking from an agentless connection alone, or the team cannot grant and maintain required cloud access. IMPLEMENTATION 1. Onboard a bounded cloud estate Review connection permissions and regional data handling, then reconcile discovered resources with an independent account inventory. 2. Validate a complete risk path Follow one synthetic exposed workload through identity and data relationships, checking each edge before accepting the priority. 3. Connect remediation to engineering Route the issue to the owning team, repair its infrastructure source and verify the deployed state after the next collection cycle. OPERATING REALITY Cloud onboarding is the beginning of an ongoing inventory and ownership program. Atlas would track connector permissions, new-account coverage, stale assets and remediation routing, then treat runtime sensor deployment as a separate change with workload compatibility, telemetry volume and response authority of its own. COMMERCIAL CONSIDERATIONS The reviewed public pages describe modular capabilities and request a sales conversation rather than establishing a reproducible price for this estate. - Cloud resource scope and negotiated module coverage - Wiz Defend and optional runtime sensor entitlement - Integration, remediation and cloud-side collection effort EVALUATION PLAN / PROPOSED TESTS, NOT COMPLETED RESULTS 1. Verify the graph against known ground truth Acceptance evidence: Create a disposable public workload with a restricted synthetic dataset and trace the exact network, identity and data edges in the finding. Owner: __________ Pass criterion: __________ Observed result: __________ Evidence location: __________ 2. Separate posture from runtime evidence Acceptance evidence: Run an approved benign runtime fixture with and without the selected sensor coverage and preserve which observations and actions each path produces. Owner: __________ Pass criterion: __________ Observed result: __________ Evidence location: __________ 3. Close the loop in code Acceptance evidence: Keep the original issue, owner assignment, infrastructure change, redeployment and refreshed finding state to demonstrate a durable fix. Owner: __________ Pass criterion: __________ Observed result: __________ Evidence location: __________ QUESTIONS FOR THE VENDOR - What permissions and data access are required by each agentless scan? - Which runtime signal requires Wiz Sensor, and which operating systems or deployment patterns support it? - Can the team export evidence and ownership mappings without making the visual graph its only record? EVIDENCE GAPS - Reviewed evidence is vendor product information; detailed authenticated deployment documentation and independent measurements were not available in this research pass. - Confirm contractual modules, region coverage, sensor compatibility and scan freshness for the actual cloud estate. SOURCES Wiz cloud and AI security platform (Product information) https://www.wiz.io/platform Wiz Defend runtime scope and sensor add-on (Product information) https://www.wiz.io/platform/wiz-defend Wiz integrations (Product information) https://www.wiz.io/integrations Use synthetic fixtures in an authorized environment. Agree rollback and acceptance criteria before enforcement. Documentation research and Atlas analysis. Independent hands-on effectiveness, effort, and complete price remain unassessed.