finding-triage

Triage security findings into defensible dispositions with mitigation plans or false-positive justifications.

345|47|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/briiirussell/cybersecurity-skills --skill finding-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finding-triage
Source: https://github.com/briiirussell/cybersecurity-skills/tree/main/skills/finding-triage
Command: npx skills add https://github.com/briiirussell/cybersecurity-skills --skill finding-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finding-triage helps you determine whether a single security finding is real and, if so, document an auditable disposition (Fixed, Deferred, Accepted Risk, or False Positive) with a mitigation plan or justification that fits your environment.

Core Features & Use Cases

  • Single-Finding Disposition Writeup: Produces a ticket-ready record using the appropriate template (Fixed, Defer, Accept Risk, or False Positive).
  • Evidence-Based False-Positive Evaluation: Checks reachability, preconditions, environment mismatch, existing controls, and scanner artifacts so you can justify suppression or re-evaluation.
  • Contextual Severity Adjustment: Refines scanner-provided severity using factors like exploitability, exposure, data sensitivity, and compensating controls.

Quick Start

Use the finding-triage skill to triage the security finding you paste in by generating an actionable disposition and mitigation or justification document.

Frequently Asked Questions about finding-triage

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

FAQPage Schema
How do I triage a security finding from a SAST or DAST scanner into a defensible disposition?

Security finding triage evaluates scanner output to determine a defensible disposition by assessing contextual severity, exploitability, and existing controls, then generates a ticket-ready writeup for Fixed, Deferred, Accepted Risk, or False Positive outcomes.

What is the best way to document a false positive from a dependency advisory for an audit?

False positive justification for dependency advisories checks reachability, environment mismatch, and scanner artifacts to produce auditor-grade documentation that justifies suppression or re-evaluation of the flagged vulnerability.

How do I adjust contextual severity for a vulnerability found during a manual audit?

Contextual severity adjustment refines scanner-provided severity by evaluating exploitability, exposure, data sensitivity, and compensating controls to ensure the risk acceptance or mitigation planning reflects your actual environment.

Can I use this security triage process for findings from pentest reports and vendor disclosures?

Security triage applies to findings from pentest reports, vendor disclosures, threat-hunt hits, and manual audits, requiring contextual severity evaluation and selection among Fixed, Deferred, Accepted Risk, or False Positive dispositions.

How to generate audit-ready documentation for risk acceptance on a single vulnerability?

Audit-ready documentation for risk acceptance is generated by evaluating contextual severity and compensating controls, producing a ticket-ready record that justifies the defensible disposition for the single security finding.

When should I not use a standard mitigation plan for a security finding?

Standard mitigation planning is bypassed when false positive evaluation confirms environment mismatch or existing controls negate scanner artifacts, allowing you to select a False Positive disposition with auditor-grade justification instead.