Review and remediate findings that our pentesters discover.

Review and remediate findings that our pentesters discover.


:::info
A finding is a vulnerability that a pentester reports during a pentest. Each finding includes a detailed description of the vulnerability and clear recommendations on how your team can remediate the issue.

:::

## Accessing Findings

Once your pentest goes [Live](https://docs.cobalt.io/en-us/articles/pentest-states-KfXxlt4Re2), pentesters begin testing your [asset](https://docs.cobalt.io/en-us/articles/assets-are-what-we-pentest-09RgsvQ7zv).

To access the detailed list of reported findings for a specific pentest, navigate to the pentest and select the Findings tab.

The Findings tab is organized into two distinct views to help you manage vulnerabilities across test cycles:

* **[Current Pentest Findings](https://docs.cobalt.io/en-us/articles/findings-6prkG67iav#h-current-pentest-findings)**: This view shows all vulnerabilities actively discovered and reported within the current pentest.
* **[Historical Findings](https://docs.cobalt.io/en-us/articles/findings-6prkG67iav#h-historical-findings)**: This is a reference view, listing all findings from the asset’s previous pentest(s) that were still in an Open or Accepted Risk state when the current test began.

## Current Pentest Findings

The Current Pentest Findings tab is your main remediation workspace, displaying all vulnerabilities identified in the active engagement.

### Finding Overview and Quick Filters

At the top of this tab, you will see a series of tiles that count the total number of findings within each state. You can quickly filter the list of findings below by clicking on any of these tiles.

### Filtering, Sorting, and Exporting

To manage your remediation workflow, you have the flexibility to tailor your view of the findings using:

* **Filter Findings**: Easily narrow the list by specific criteria:
  * [Severity](https://docs.cobalt.io/en-us/articles/severity-levels-QCUIhkAYey)
  * [State](https://docs.cobalt.io/en-us/articles/finding-states-De6IE4W5Zw)
  * Finding Type
  * Assignee
  * Label
* **Sort the List**: Organize your view by:
  * Created At
  * Severity
  * Latest Activity
  * Name
* **Search**: Use the Search bar to quickly locate specific findings by keyword.
* **Export**: Download a CSV file of all findings for offline analysis or external reporting.

## Historical Findings

This tab gives you full visibility into the triage and verification process performed by the pentesters on your previously open or accepted risk vulnerabilities.

Pentesters review every open or accepted risk historical finding to determine if the vulnerability is still reproducible in the current environment.

* **Vulnerability Still Exists**: If the vulnerability was not fixed (still reproducible), the previous finding is marked as Carried Over. A new corresponding finding is then created on the Current Pentest Findings tab for you to manage in the active test cycle.
* **Vulnerability Fixed**: If the vulnerability was successfully remediated, the finding is marked as Fixed and closed.
* **No Longer Applicable**: If the finding is irrelevant to the scope or state of the current test, it is simply not re-reported.

You can track the progress using the **Original State → Review Outcome** column and see which tester reviewed each previous finding and their final decision.

To manage the triage workflow, you can filter this list by the finding’s Original State (e.g., Pending Fix, Accepted Risk) and by the Reviewed Status (Reviewed or Unreviewed) to see which items still require attention.


:::info
#### Note

You can manage findings using the Cobalt API. Learn more in our [API documentation](https://docs.cobalt.io/articles/findings-D4kEiuzfAW).

:::




Findings

Pentests

Overview

Asset Details

Pentest Details

Scope & Test Period

Preparation

Create a Pentest

Pentest Process

Pentest States

Coverage Checklist

Pentest Expectations

Set Up an In-House Pentest

Complete an In-House Pentest (For Pentesters)

In House Pentests

Severity Levels

Finding States

Remediate Findings

Customize Your Report

Co-branded Reports

Contents of a Pentest Report

Reports

How to get started with Cobalt

Getting Started

Risk Advisories

Assets are what we pentest

Asset Types

Create an Asset

Assets

Engagements Overview

Digital Risk Assessment

Secure Code Review

Engagements

Insights

Planning

Cobalt Methodologies Overview

Web Methodologies

API Methodologies

External Network Methodologies

Internal Network Methodologies

Mobile Methodologies

Cloud Configuration Review Methodologies

Cloud Pentest Methodology

Desktop Methodologies

AI/LLM Methodologies

Digital Risk Assessment Methodology

Secure Code Review Methodologies

Methodologies

Attack Surface Monitoring (ASM)

Attack Surface

DAST Scanner Overview

Best Practices

Integrations

Partial Scans: Reduced Scope

Scans

Sequence recorder

Targets

Target Authentication

Extra Hosts

Blackout Period

DAST Scanner

Account Overview

Account Settings

Password Best Practices

Sign In to Cobalt

Troubleshoot Sign-in Issues

User Account

Collaboration Overview

Collaborate on Pentests

Groups

Manage Pentest Collaborators

Manage Notifications

User Roles and Permissions

Collaboration

Organization Overview

Manage Users

Your Cobalt Contract

Configure SAML SSO

How to Configure SAML 2.0 for Cobalt 

SAML Migration: Update Your Configuration

SCIM Provisioning Setup Guide

Configure Organization Settings

Organization

Track Your Credits

Cobalt Credits

Cobalt PtaaS Tiers

Credits

Cobalt Integrations Overview

Troubleshooting

Create Jira tickets for Findings

Send email notifications for Findings from Outlook

Create GitLab tickets for Findings

Create GitHub tickets for Findings

HTTP Connector

Import Assets from Google Sheets

Map Cobalt Pentest Finding Severity to Jira Issue Priority

Modify Jira Issue Summary to contain Pentest Title

Create Azure DevOps Work Item for Findings

Send MS Teams notifications for Findings

How to Guides

Connect your applications

Integration Builder

Synchronize Cobalt Severity Levels with Jira

Push Cobalt Findings to Jira

Jira Cloud Integration

Jira Data Center Integration

Troubleshoot Your Jira Integration

Switching to a New Jira Instance

Integrate Jira with Cobalt

Slack

Microsoft Teams

Webhooks

DefectDojo

Kenna Security

Vanta

Carried Over Findings

Create Test Finding

Cobalt API Overview

Create a Personal Cobalt API Token

Get an Organization Token

Revoke Your Personal Cobalt API Tokens

Create or Modify an Asset

Import Findings to Google Sheets

Cobalt API

Glossary

March 2026

February 2026

January 2026

November 2025 

August 2025

July 2025

June 2025

May 2025

April 2025

March 2025

January 2025

December 2024

November 2024

October 2024

September 2024

August 2024

July 2024

June 2024

May 2024

April 2024

March 2024

January 2024

What's New

Guide

Cobalt Product Documentation

Findings

Share

Remediate Findings

Finding States

Severity Levels

Share

Findings

Share

Remediate Findings

Finding States

Severity Levels

Share