15 docs tagged with "findings"

Web UI architecture for SecurityV0 — page specifications for 9-type entity model, component architecture, data fetching patterns, evidence pack rendering, execution chain views, and export capabili...

What an access path is, how it is materialised from the entity graph, the flat API endpoints, and how the detail page surfaces risk, ownership, and remediation. Includes proposed identity-scoped grouping design (not yet shipped).

Decision to move all detection/finding logic to the platform evaluator and remove connector-side detectors

Separate two axes that the product had conflated: severity (how bad is this CLASS of problem if real — a stable taxonomy kept in the backend/API) and priority (how urgently a human must act on THIS instance — evidence-gated and displayed). Posture never escalates to Critical on its own; proof is observed, resource-scoped execution. Captures the decision behind sv0-platform PRs #1400/#1401 (issues #1397–#1399) and the #1395 UI swap.

REST API contract for SecurityV0 platform

Two-page onboarding overview for engineers new to SecurityV0, covering product purpose, operating flow, repository map, current implementation status, and practical first-week setup/workflow

Architecture of the rule-based drift detection system — how scope, ownership, and reachability drift evaluators work, how findings are produced, and how the remediation service maps findings to pri...

Formalizes the distinction between proven and inferred evidence across all finding types. Defines an EvidenceClassification enum, an EvidenceClaim type, a per-rule classification table, and an implementation plan.

The Risk Paths preset filters the Graph Explorer to show only entities with critical or high severity findings, plus their direct (1-hop) graph neighbors

Defines the batch processing pipeline from connector submission through findings and evidence packs

Business response and product-direction guidance prompted by the Microsoft and Jira use cases, with applicability across systems.

Revocation Rehearsal answers 'what breaks if you revoke this access?' before anyone revokes — a deterministic, read-only dry-run that masks a role grant and diffs the resulting access paths against observed execution evidence

Founder feedback on the March 29 Wiz UX pattern analysis, with explicit direction on remediation aggregation, finding-detail structure, and scope-drift presentation.

12 issues found by the visual QA agent run against localhost demo-tenant: one API bug, four degraded-experience items, seven UX/readability improvements

Competitive UX analysis of Wiz presentation patterns for findings, posture, and remediation — with side-by-side comparisons to SecurityV0's current UI.