Managing Finding Status - apviso [APVISO](/)Product

Resources

Developers

Company

[Pricing](/#pricing)[Partners](/partners)[Enterprise](/enterprise)

[Login](/login)[Start free pentest](/register?intent=free-local-pentest)

[Login](/login)[Start free](/register?intent=free-local-pentest)

[Home](/)[Knowledge Base](/docs)Managing Finding StatusFindings & ReportsManaging Finding Status
=======================

Track remediation progress using the finding status workflow — from open through to fixed, accepted risk, or false positive.

Finding Status Workflow
-----------------------

Every finding starts with a status of `open`. As your team triages and remediates vulnerabilities, you can move findings through the following workflow:

### `open`

The finding has been identified but no action has been taken yet. This is the default status for all new findings.

### `in_progress`

Your team is actively working on a fix. Set this status to signal that the vulnerability has been assigned and is being addressed.

### `fixed`

The vulnerability has been remediated and verified. You can set this manually, or it is set automatically when a retest confirms the fix.

### `accepted_risk`

Your team has reviewed the finding and decided to accept the risk rather than fix it. This is appropriate for low-severity issues where the cost of remediation outweighs the risk, or where compensating controls are in place. Adding a note explaining the risk acceptance decision is recommended.

### `false_positive`

The finding is not a real vulnerability. This can happen when the AI agents misinterpret application behavior. Marking a finding as a false positive removes it from active metrics and helps APVISO improve its detection accuracy.

Changing Status
---------------

1. Open the finding detail page.
2. Click the current status badge.
3. Select the new status from the dropdown.
4. Optionally add a note explaining the change.
5. Click **Save**.

Status changes are logged with the timestamp and the user who made the change.

Filtering and Sorting by Status
-------------------------------

The Findings list supports filtering by status. Use this to:

- View only `open` findings to see your current vulnerability backlog.
- Filter by `in_progress` to check on active remediation work.
- Show `fixed` findings to review what has been resolved.

Status in Reports
-----------------

When you generate a pentest report, finding statuses are included. This means reports reflect the current remediation state, making them useful for compliance audits and stakeholder updates.

Bulk Status Updates
-------------------

Select multiple findings using the checkboxes and use the **Bulk Actions** menu to change their status at once. This is useful when closing out a batch of related findings after a deployment.

### Related Articles

[Understanding Findings

What severity levels mean, how findings are structured, and how to interpret CWE/CVE references and compliance mappings.](/docs/understanding-findings)[Retesting Findings

How to verify that vulnerabilities have been fixed by running targeted retests against specific findings.](/docs/retesting-findings)[Pentest Reports

How reports are generated, what they contain, and how to download them as Markdown or PDF.](/docs/scan-reports)

[Back to Knowledge Base](/docs)

[APVISO](/)Autonomous AI-powered penetration testing for modern web applications.

Subscribe

[](https://github.com/apviso)[](https://x.com/Apviso_com)[](https://www.linkedin.com/company/apviso/)

[![Featured on Good AI Tools](https://goodaitools.com/assets/images/badge.png)](https://goodaitools.com/ai/apviso)

Product

- [Features](/#features)
- [Pricing](/pricing)
- [Integrations](/integrations)
- [Benchmarks](/#compare)
- [Affiliate Program](/affiliate)
- [Partners](/partners)
- [Enterprise](/enterprise)

Resources

- [Blog](/blog)
- [Use Cases](/use-cases)
- [Glossary](/glossary)
- [Comparisons](/comparisons)
- [Alternatives](/alternatives)
- [Compliance](/compliance)
- [Vulnerabilities](/vulnerabilities)
- [Industries](/industries)
- [OWASP APTS](/trust/apts)

Developers

- [Knowledge Base](/docs)
- [API Reference](/docs/api)
- [MCP Server](/docs/mcp)

Company

- [About](/about)
- [Contact](/contact)
- [Status](https://status.apviso.com)
- [Privacy Policy](/legal/privacy)
- [Terms of Service](/legal/terms)

© 2026 APVISO. All rights reserved.