fp-check

Solid

Systematic false positive verification for security findings. Provides structured methodology to confirm or dismiss scanner results, manual audit findings, and automated alerts. Adapted from Trail of Bits. Use when triaging security scan results or verifying audit findings.

AI & Automation 552 stars 45 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
91
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# False Positive Verification Not every finding is real. But dismissing a real finding as "false positive" is worse than investigating a false one. This skill provides a systematic approach to verify findings without bias. ## Verification Process ### Step 1: Reproduce the Claim Before dismissing anything, attempt to confirm: ``` FINDING: SQL injection in /api/users CLAIM: User input reaches database query unsanitized VERIFICATION: 1. Read the actual code at the reported location 2. Trace the data flow from input to sink 3. Check for sanitization/validation between input and sink 4. Check for framework-level protections (ORM, parameterized queries) 5. Attempt to construct an exploit payload ``` ### Step 2: Evidence-Based Triage | Verdict | Criteria | Evidence Required | |---------|----------|-------------------| | TRUE POSITIVE | Vulnerability exists and is exploitable | Code path + exploit scenario | | TRUE POSITIVE (mitigated) | Vulnerability exists but other controls prevent exploitation | Code path + mitigation proof | | FALSE POSITIVE (provable) | Finding is wrong due to tool limitation | Specific reason why tool was wrong | | FALSE POSITIVE (contextual) | Code is technically flagged but context makes it safe | Context documentation | | NEEDS INVESTIGATION | Cannot determine without more analysis | What additional info is needed | ### Step 3: Document the Decision ``` FINDING: [scanner/auditor finding description] SOURCE: [which tool/person reported it] LOCATION...

Details

Author
vibeeval
Repository
vibeeval/vibecosystem
Created
8 months ago
Last Updated
6 days ago
Language
C#
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Featured

fp-check

Systematically verifies suspected security bugs to eliminate false positives. Produces TRUE POSITIVE or FALSE POSITIVE verdicts with documented evidence for each bug.

8,273 Updated 6 days ago
trailofbits
AI & Automation Listed

ghost-validate

This skill should be used when the user asks to "validate a finding", "check if a vulnerability is real", "triage a security finding", "confirm a vulnerability", "determine if a finding is a true positive or false positive", or provides a security finding for review. It validates security vulnerability findings by tracing data flows, verifying exploit conditions, analyzing security controls, and optionally testing attack vectors against a live application.

446 Updated 1 months ago
ghostsecurity
Web & Frontend Listed

security-triage

Verifies, deduplicates, ranks and patches security findings for a web/SaaS product that the user owns or is authorized to test. Takes output of security-audit, pentester, saas-entitlements, server-armor, or any scanner (Semgrep, ZAP, Snyk, Trivy, npm audit, bug-bounty reports, an old backlog) and returns a short evidence-backed list: what is real, what is a false positive and why, severity derived from preconditions, owner, and optional candidate patches that are re-verified with a failing test and a fresh re-attack. Read-only by default. Triggers: "/security-triage", "triage findings", "verify scanner output", "false positives", "dedupe findings", "prioritize vulns", "fix the findings", "patch these vulns", "go through the findings", "filter out the noise", "which of these are real", "what should I fix first".

0 Updated today
arcticloud