Exploitability Validation Skill

Vulnerability validation involves a structured multi-stage pipeline that confirms findings are real, reachable, and exploitable. This skill gates your analysis through inventory checks, attack-tree exploration, sanity checks, and feasibility analysis to eliminate false positives before exploitation planning.

Run Stage A through Stage E sequentially: start with scanner output and initial findings, apply inventory and one-shot analysis gates, map attack trees, validate sanity checks, and generate final findings.json with attack-paths and attack-surface artifacts for exploitation workflows.

Yes. Attack-tree exploration is a core gate in this validation pipeline. It maps reachability and exploitability paths through your findings, generating attack-tree.json and hypotheses.json artifacts that support both ruling out false positives and planning real exploitation routes.

The pipeline generates findings.json, attack-tree.json, hypotheses.json, disproven.json, attack-paths.json, and attack-surface.json. These artifacts document validated vulnerabilities, explored attack trees, tested hypotheses, ruled-out findings, and confirmed exploitation routes for defense-focused security workflows.

Structured gate-driven validation prevents wasted effort on false positives by applying repeatable, documented checks—inventory, one-shot analysis, attack-tree exploration, and sanity checks—ensuring only real, reachable vulnerabilities advance to exploitation planning.