Start an investigation
Every path leads to the same workspace — dependency map, blast radius, identity reach, telemetry, and a recommendation bundle with rollback and validation. Pick whichever entry matches what you have in hand.
Search existing findings
Browse scanner findings (Wiz, Defender, IaC drift) already ingested into the platform. Filter by severity, framework, source, or resource.
Post an issue manually
Describe what you're seeing. Paste a CLI/portal screenshot, a Terraform snippet, a resource ID, or just type it. We resolve the resource and run the same enrichment as a scanner finding.
Import from Wiz
If Wiz isn't connected yet, connect it. Existing Wiz findings are auto-ingested and become first-class issues here.
Search a resource directly
Start from a resource (VM, bucket, NSG, role, etc.) and ask 'what does this look like right now?'. Useful for change-window planning.
Engineer-first. The workspace surfaces what a real remediation needs: hidden dependencies, observed traffic on the affected path, change history, identity reach, blast radius, and per-cloud remediation in Portal / CLI / PowerShell / Terraform / CloudFormation / gcloud styles where evidence exists. Where it doesn't, we show the gap honestly rather than fabricating coverage.