Findings Topology
Visualize your findings as an interactive graph. See which resource types have issues, how they connect, and where to focus first.
What You See
┌──────────────────────────────────────────────────────────────┐ │ Findings Topology 6 types • 48 findings │ ├──────────────────────────────────────────────────────────────┤ │ │ │ [Lambda]──────[Secrets Manager] │ │ 46 2 │ │ 🟠 🟡 │ │ │ │ ╌╌╌╌╌╌╌╌ ╌╌╌╌╌╌╌╌ ╌╌╌╌╌╌╌╌ ╌╌╌╌╌╌╌╌ │ │ DynamoDB CloudFront API GW Route53 │ │ ✓ ✓ ✓ ✓ │ │ (clean) (clean) (clean) (clean) │ │ │ ├──────────────────────────────────────────────────────────────┤ │ 💥 Blast Radius: Lambda shares violations with 1 type │ │ 🏝️ Isolated: DynamoDB, CloudFront, API GW, Route53 — clean │ │ ✅ Coverage: 6/6 resource types scanned │ └──────────────────────────────────────────────────────────────┘
Understanding the Graph
Nodes (circles): Each node = one AWS resource type (e.g., aws.lambda). Size = number of findings.
Colors: 🔴 critical, 🟠 high, 🟡 medium, ⚪ low. Based on worst severity in that type.
Edges (lines): Connect resource types that share the same policy violation. Label shows the policy name.
Clean nodes (dashed): Resource types scanned without findings. Shows ✓ icon. Not clickable.
Glow effect: Nodes with findings have a subtle glow matching their severity color.
Interacting with the Graph
- Click a node: Opens sidebar with all findings for that resource type
- Sidebar features: Remediation commands, Ignore/Fixed buttons, Explain with AI
- Zoom/Pan: Scroll to zoom, drag to pan. Controls in bottom-right.
- MiniMap: Bottom-left shows overview of entire graph
- "View Timeline →" link takes you to /history for time-based view
Graph Insights
Below the graph, SOFE computes 4 automatic insights:
💥 Blast Radius: Which resource type shares violations with the most others (fix it → wide impact)
🏝️ Isolated (Clean): Types with no findings (scanned clean)
🔗 Critical Path: Longest chain of connected types (dependency depth)
⚠️ High Connectivity: Types connected to many others (single point of failure)
When Is the Topology Useful?
- Quickly see which resource types are "clean" vs have issues
- Identify the biggest offender (largest node = most findings)
- See cross-cutting issues (edges = same policy violated across types)
- Demo/reporting: screenshot the graph for stakeholders