skills.rest
dreadnode
dreadnodeOFFICIAL
Explore all skills by this author →
Website𝕏@dreadnodeGitHub

vuln-assessment-methodology

Enforce rigorous vulnerability assessment workflows with source-to-sink tracing and disprove-first validation.

11|1|Updated May 4, 2026
Search Tags:#vulnerability assessment#security testing#severity scoring#exploitability validation#false positive prevention#CWE mapping#source-to-sink tracing
One-click install
npx skills add https://github.com/dreadnode/capabilities --skill vuln-assessment-methodology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vuln-assessment-methodology
Source: https://github.com/dreadnode/capabilities/tree/main/capabilities/vuln-assessment-methodology/skills/vuln-assessment-methodology
Command: npx skills add https://github.com/dreadnode/capabilities --skill vuln-assessment-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the pervasive problem of low-quality vulnerability assessments that produce false positives, inflated severity ratings, and incomplete analysis, leading to wasted remediation effort, missed critical risks, and reduced trust in security testing outputs.

Core Features & Use Cases

  • Full Source-to-Sink Tracing: Enforces complete data flow analysis from attacker-controlled input to dangerous sinks, eliminating sink-only false positives.
  • Disprove-First Validation: Requires active search for evidence of non-exploitability before reporting, ensuring only valid findings are escalated.
  • Threat-Model-Aware Severity Scoring: Assigns severity based on input source, access requirements, and deployment context rather than generic vulnerability class labels.
  • Confidence Classification & CWE Mapping: Requires explicit confidence levels for all findings and maps to specific leaf-level CWE IDs for accurate remediation guidance.
  • Use Case: When assessing a public-facing web application, this Skill prevents reporting an internal-only configuration parameter injection as a critical finding, and ensures you trace the full data flow to confirm if existing sanitization can be bypassed before escalating the issue.

Quick Start

Use the vuln-assessment-methodology skill to evaluate the reported SQL injection in the public user login endpoint, trace the complete data flow from the HTTP request parameter to the database query sink, validate any existing input sanitization for bypasses, assign severity based on unauthenticated internet-facing access, and include the specific CWE-89 mapping with a confirmed confidence level.

Frequently Asked Questions about vuln-assessment-methodology

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I eliminate false positives in vulnerability assessment and security testing?▼

To eliminate false positives in vulnerability assessment, enforce full source-to-sink data flow tracing and disprove-first exploitability validation, requiring active search for evidence of non-exploitability before escalating findings.

What is source-to-sink tracing in vulnerability assessment?▼

Source-to-sink tracing in vulnerability assessment is the complete data flow analysis from attacker-controlled input to dangerous sinks, which eliminates sink-only false positives by confirming if existing sanitization can be bypassed.

How do I assign threat-model-aware severity scoring for security findings?▼

Threat-model-aware severity scoring assigns vulnerability severity based on input source, access requirements, and deployment context rather than generic vulnerability class labels, preventing severity inflation.

Can I use this vulnerability assessment methodology for cloud infrastructure and AI system security testing?▼

Yes, this vulnerability assessment methodology applies to all vulnerability assessment domains including web application security, cloud infrastructure, internal tooling, and AI system security testing.

What is the best way to map CWE IDs during vulnerability assessment?▼

The best way to map CWE IDs during vulnerability assessment is to map findings to specific leaf-level CWE IDs while assigning explicit confidence classification levels for accurate remediation guidance.

Why does vulnerability severity inflation happen and how can attack chain analysis prevent it?▼

Vulnerability severity inflation happens when ratings ignore deployment context, and attack chain analysis prevents it by validating exploitability through complete data flow tracing and threat-model-aware scoring before reporting.

Related Skills

Explore More Software Engineering Skills→
salmanabdurrahmansalmanabdurrahman

vuln-dom-xss

Trace attacker-controlled JavaScript sources to dangerous execution sinks.

Community
Advanced
jinyimeng01jinyimeng01
54

report-agent

Generate HackerOne-format vulnerability reports from validated security findings.

Community
Advanced
SocketDevSocketDev
125

fleet-triaging-findings

Triage raw security-scanner output into prioritized findings with owners.

Official
Advanced
CENKSSSCENKSSS

pentest-validation

Validate SAST and DAST vulnerability exploitability through a 4-phase pipeline.

Community
Advanced