Vulnerability details
Every finding carries a set of actions for moving it through your workflow — from triage to remediation or documented acceptance. Use them to keep the findings list an honest picture of real, open risk. For the detail view itself — severity, evidence, logs — and for re-scanning an endpoint to verify a fix, see Viewing and understanding vulnerabilities.
Actions on a finding
- Accept the risk — record a deliberate decision not to fix, when remediation is not feasible or the impact is minimal. The finding stays documented instead of lingering as open noise.
- Mark as false positive — clear findings that don't represent a real issue, so remediation effort goes only to valid threats.
- Create a ticket — log the finding in Jira or Azure DevOps directly from the vulnerability page, and track remediation where your developers already work.
- Export as cURL — generate the exact request that triggered the finding, so a developer can reproduce and validate it.
- Export logs — download the finding's request/response evidence for deeper analysis, audits, or compliance records.
📖 Accept Vulnerability Risk
Visit Application
📖 Marking False Positive
Visit Application
📖 Create Ticket
Visit Application
📖 Export as Curl
---
📖 Export Logs
Visit Application