Finding report
A finding's evidence references, verification_status and
verification_rationale constrain its supported conclusions. The selected
workflow owns authorship, canonical paths, completion and handoff.
Verdict handling
| Verdict |
Treatment |
verified |
Describe what was reproduced. For result_kind: vulnerability, score only with a justified cvss_score call and record its base_score. A verified negative result remains coverage, not a vulnerability. |
unverified |
Explain the constraint and the next discriminating test. Do not assert the claimed impact as fact. |
false_positive |
Preserve the rebuttal for coverage accounting. Do not assign a vulnerability score or remediation priority. |
For result_kind: negative_result or observation, report what was tested or
seen and what it does not prove. Do not turn it into a vulnerability.
Canonical document
Preserve all existing frontmatter, including id, objective_id, target,
evidence_pointer, evidence_manifest, result_kind, verdict and rationale.
Complete supported fields such as severity_rationale, cvss_vector,
cvss_score, cvss_version, cwe, mitre, remediation_priority, and
report_status. Unknown values may remain absent. Use sections for Summary,
Verification, Steps to Reproduce, Proof of Concept, Attack Scenario, Impact,
Controls and Limitations, CVSS, Remediation, and References. Cite exact paths.
The final engagement report links to the canonical finding rather than creating
a second record with an independently mutable verdict.
1---2name: finding-report3description: "Interpret finding verdicts, preserve evidence fields and present justified severity and remediation."4allowed-tools: Read Write5metadata:6 source: https://skillmd.com/skills/purpleailab/finding-report7 subdomain: reporting8 when_to_use: "report one finding, CVSS, verification verdict, remediation, FIND-"9 tags: finding, reporting, verification, cvss, evidence10 upstream_ref: "Canonical Decepticon finding verification and reporting workflow"11 skillogy:12 version: 113 requires: [finding-protocol]14---1516# Finding report1718A finding's evidence references, `verification_status` and19`verification_rationale` constrain its supported conclusions. The selected20workflow owns authorship, canonical paths, completion and handoff.2122## Verdict handling2324| Verdict | Treatment |25| --- | --- |26| `verified` | Describe what was reproduced. For `result_kind: vulnerability`, score only with a justified `cvss_score` call and record its `base_score`. A verified negative result remains coverage, not a vulnerability. |27| `unverified` | Explain the constraint and the next discriminating test. Do not assert the claimed impact as fact. |28| `false_positive` | Preserve the rebuttal for coverage accounting. Do not assign a vulnerability score or remediation priority. |2930For `result_kind: negative_result` or `observation`, report what was tested or31seen and what it does **not** prove. Do not turn it into a vulnerability.3233## Canonical document3435Preserve all existing frontmatter, including `id`, `objective_id`, target,36`evidence_pointer`, `evidence_manifest`, `result_kind`, verdict and rationale.37Complete supported fields such as `severity_rationale`, `cvss_vector`,38`cvss_score`, `cvss_version`, `cwe`, `mitre`, `remediation_priority`, and39`report_status`. Unknown values may remain absent. Use sections for Summary,40Verification, Steps to Reproduce, Proof of Concept, Attack Scenario, Impact,41Controls and Limitations, CVSS, Remediation, and References. Cite exact paths.42The final engagement report links to the canonical finding rather than creating43a second record with an independently mutable verdict.