> For the complete documentation index, see [llms.txt](https://docs.alpha-security.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alpha-security.app/user-guide/findings.md).

# Findings

The findings board tracks vulnerabilities discovered during the engagement. It's where raw evidence becomes actionable output for the report.

## Creating findings

There are two ways to create findings:

1. **From a parser** - Some parsers (like Nuclei and Nikto) automatically create findings when they detect vulnerabilities. These appear on the board linked to the run that produced them.
2. **Manually** - Click **New Finding** to create one yourself. Link it to hosts, services, or runs to connect it to the evidence.

## Finding fields

Each finding has:

* **Title** - Short name of the vulnerability
* **Severity** - Critical, High, Medium, Low, or Informational
* **CVSS score** - Optional numeric score
* **Description** - What the vulnerability is
* **Impact** - What an attacker could do with it
* **Remediation** - How to fix it
* **Evidence** - Linked runs, entities, and screenshots that prove the finding

## Workflow

Findings have a status: Open, Confirmed, Accepted, or Resolved. Use these to track your progress through the assessment.

## Evidence linking

Every finding can link to:

* Runs (the raw output that shows the vulnerability)
* Entities (the affected hosts, services, or credentials)
* Screenshots (uploaded through the UI)

These links carry through into the report, so each finding in the final deliverable traces back to concrete evidence.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.alpha-security.app/user-guide/findings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.