Insights provides comprehensive data on pentest results, remediation progress, and overall performance.

Insights provides comprehensive data on pentest results, remediation progress, and overall performance.

## A Comprehensive View of Your Security Posture

The Insights page is designed to give you a comprehensive view of your security program and performance, organized into three distinct tabs:


1. [Findings](https://cobalt-io.brainfish.ai/en-us/articles/insights-r4Jw78EcgA#h-findings)
2. [Assets](https://cobalt-io.brainfish.ai/en-us/articles/insights-r4Jw78EcgA#h-assets)
3. [Benchmark](https://cobalt-io.brainfish.ai/en-us/articles/insights-r4Jw78EcgA#h-benchmark)

Use the filters to refine the displayed data, filters include:

* **Groups:** Groups are specific teams that you have assigned to assets
* **Asset**: Drill down into your security posture by selecting a single asset, multiple assets, or viewing data for all assets. Graphs on the Assets tab show a maximum of 10 assets.
* **Date Range:** Adjust the reporting period to see insights for the specific time range you need.

We categorize all findings by their assigned [OWASP-based severity level](https://cobalt-io.brainfish.ai/en-us/articles/severity-levels-QCUIhkAYey#h-owasp-risk-rating) (Critical, High, Medium, Low, Informational) and also by their [Finding State](https://cobalt-io.brainfish.ai/en-us/articles/finding-states-De6IE4W5Zw).

For easy sharing and offline review, you can also download a PDF version of the currently viewed tab by clicking the “Download” button.


---

## Findings

Detailed look at the state of your pentest findings.

At the top, you’ll find these key metrics:

* **Pentests Performed:** The total count of pentests you’ve completed (Live, Remediation or Closed).
* **Testing Hours:** The cumulative hours spent on your completed pentests.
* **Findings Reported:** The total number of findings identified in the following states: Pending Fix, Ready for Retest, Accepted Fisk, Fixed, Carried Over
* **Findings Open:** The total number of findings currently in a Pending Fix state
* **Findings Resolved:** The total number of findings that have reached a “Resolved” state of Fixed or Accepted Risk.

The Findings tab also includes the following charts to help you visualize your data:

### **Findings by Status and Severity** 

A breakdown of all findings categorized by their current status and the severity level (Critical, High, Medium, Low, Informational).


:::info
**How to use this data:** Use this to see how your teams are doing at remediating findings across different severity levels. It can help you pinpoint challenges in your remediation process and facilitate progress.

:::

### **Time to Fix by Severity** 

This metric displays the average time it takes for a Fixed finding to move from a Pending Fix state to Ready for Retest, broken down by severity. We use “Ready for Retest” as the end point to ensure the duration accurately reflects only the time spent on the fix itself.


:::info
**How to use this data:** Use this to track your teams’ progress in risk remediation within an asset or across all assets. It can also help you estimate the effort and time needed for future remediation, helping you minimize risks.

:::

### **Age by Severity**

The average age of your currently open findings, categorized by severity.


:::info
**How to use this data:** Use this chart to identify long-standing findings, especially those of high or critical severity that have been open for an extended period. It helps you understand the duration of your risk exposure and can pinpoint bottlenecks in your remediation process. By reviewing the average age, you can prioritize remediation efforts for the oldest and most critical findings, and inform discussions around resource allocation to accelerate their resolution.

:::

### **Severity Trend** 

This chart displays the total number of open pentest and engagement findings over time, broken down by their severity. For better readability and focus on critical issues, Low and Informational findings are not included in this visualization.


:::info
**How to use this data:** Identify trends in your open critical and high-severity findings. An upward trend signals a growing backlog, while spikes can highlight periods of rapid discovery outpacing resolution.

:::


---

## Assets

Focused view of your assets and the risk and findings associated with them. 

The Assets tab includes the following charts to help you visualize your data:

### **Risk Overview**

Aggregated Risk is calculated by summing the individual risks of all findings discovered during a pentest on a specific asset. This score is then compared against the Cobalt Average, which is the average Aggregated Risk derived from all pentests conducted across all Cobalt customers in a given year, providing a benchmark for your asset’s performance.


:::info
**How to use this data:** Compare your Aggregated Risk to the Cobalt Average to see how your security posture stands compared to others.

:::

### **All Findings by Type broken down by Asset**

This section categorizes findings by their specific vulnerability types for each asset. We define these types based on industry standards like the Common Vulnerabilities and Exposures (CVE) database. If an asset has more than 10 unique finding types, we’ll display the top 10 most frequent types and group the rest under “Remaining Types.”


:::info
**How to use this data:** Identify shortcomings in how your systems were developed and what the engineering team should focus on. Find patterns emerging across multiple asset types. Based on this data, you may want to arrange a training for your teams to fix the root cause of findings.

:::

### **Findings by Status and Severity** 

For each asset, this provides a breakdown of findings by their current status and severity levels. Pending Fix findings are displayed by severity. Fixed, Accepted Risk, and Carried Over findings are shown as actioned counts.


:::info
**How to use this data:** Analyze the number of findings that pentesters reported on each asset. Identify assets with Pending Fix Critical findings to start remediating them first.

:::


---

## Benchmark

Compare your organization’s performance against industry benchmarks, drawing insights from the State of Pentesting Report 2025. This comparison focuses exclusively on critical and high-severity pentest findings.

The Benchmark tab includes the following charts to help you visualize your data:

### **Resolution Rate of Critical and High Pentest Findings**

This metric shows the percentage of your Critical and High-severity pentest findings that are Resolved (Fixed or Accepted Risk).


:::info
**How to use this data:** Use this to understand how effectively your team is addressing the most severe findings compared to industry peers. A higher percentage indicates a more efficient remediation process.

:::

### **Percentage of Pentest Findings that are Critical & High** 

This is the proportion of all your reported findings that are classified as Critical or High-severity.


:::info
**How to use this data:** This helps you assess the overall severity of findings discovered in your assets compared to the industry. A lower percentage might suggest more robust security controls upfront or a different risk profile.

:::

### **Median Time to Remediate (MTTR) Critical & High Pentest Findings**

The median number of days from when a Critical or High-severity finding is reported until it’s Resolved (Fixed or Accepted Risk).


:::info
**How to use this data:** This metric is crucial for evaluating your team’s agility and response time to critical threats. A lower median time signifies faster remediation and reduced exposure windows.

:::

### **Median Age of Unresolved Critical & High Pentest Findings**

The median age (in days) of your open Critical and High-severity Pending Fix findings. This metric is compared against the half-life benchmark from the State of Pentesting Report.


:::info
**How to use this data:** Use this to understand the longevity of your most severe unaddressed risks. Comparing it to the half-life benchmark helps you see if your critical findings are lingering longer than industry averages, prompting you to prioritize and expedite resolution.

:::





Insights

How to get started with Cobalt

Getting Started

Risk Advisories

Assets are what we pentest

Asset Types

Create an Asset

Assets

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

Finding States

Severity Levels

Remediate Findings

Findings

Customize Your Report

Co-branded Reports

Contents of a Pentest Report

Reports

Engagements Overview

Digital Risk Assessment

Secure Code Review

Engagements

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

Insights

Share

Share

Insights

Share

Share