---
title: "Read the Security report | Proofline Help"
description: "The Security report counts your organization's security findings by OWASP Top 10 (2021) category or CWE Top 25 rank, over the reviews created in the last 30 or 90 days. Below the counts, Coverage gaps lists what the window did not analyze, so you can see how far the counts reach."
url: https://proofline.sh/help/security-report/
---

[Help center](/help/)

# Read the Security report

The Security report counts your organization's security findings by OWASP Top 10 (2021) category or CWE Top 25 rank, over the reviews created in the last 30 or 90 days. Below the counts, **Coverage gaps** lists what the window did not analyze, so you can see how far the counts reach.

Open **Reviews → Security report**. Outside collaborators do not have the report. A member with access to only some repositories sees the reviews of those repositories.

[![Security report with findings by OWASP category, coverage gaps and rule packs.](/help-images/security-report-light.png)](/help-images/security-report-light.png)

Read the counts beside what the window did not analyze. Fictional demo workspace.

## Choose the taxonomy and window

Use **Taxonomy** to group findings by **OWASP Top 10 (2021)** or **CWE Top 25**, and **Window** to choose **Last 30 days** or **Last 90 days**. The window selects reviews by when they were created.

Beside the table's title, the report names the reviews and commits analyzed: the reviews in the window whose analyzer run finished, and the distinct commits those runs read.

## Read the counts

A finding counts when it cites a static application security scan result whose rule declares a CWE. Each row is one category or rank, one CWE and one severity. A CWE that the OWASP map does not place appears under **Unmapped CWE**, and one outside the CWE Top 25 under **Not in the CWE Top 25**.

A finding that recurs across reviews counts once in a row, under its current state:

-   **Open**: it still awaits a fix or a decision.
-   **Resolved**: someone marked it fixed, or a later push fixed it.
-   **Accepted risk** and **Dismissed**: someone recorded that decision. See [Read and act on a finding](/help/findings/).
-   **Covered**: another finding already tracks the same problem.
-   **No series**: Proofline does not track the finding across reviews, as with a deployment review's finding, so it has no state.

One CWE can belong to two OWASP categories, and one finding can cite two CWEs, so rows do not add up to a total. The report gives counts only, with no score or rating.

## Read the coverage gaps

**Coverage gaps** lists what the counts do not include. Every member sees it, so an exported or shared report never reads as a complete analysis. Each line gives a count:

-   **Reviews with no finished analyzer run**: reviews in the window that static analysis did not finish or never ran on.
-   A failed or cut-short analysis, such as **Secret scan was cut short: its output was too large.**, with how many runs it affected.
-   **Application security findings that cite no CWE**: findings the report cannot place in a category or rank.
-   **Incomplete assessments, by cause**: assessments in the window that ended incomplete, by why they stopped. Each cause the Reviews search supports opens the matching reviews.
-   Repositories with no finished analyzer run in the window, each linked to its repository page.

When static analysis is off for the organization, the report says so above the counts. New reviews then run no analyzers, and their findings cite no CWE. An administrator turns it on with **Open code review settings**. When the deployment offers no static analysis, the report says it has nothing to count.

## Export the report

Choose **CSV** or **JSON** to download the report for the selected taxonomy and window. The export ends at the moment you choose it, so it can include reviews created after the page loaded; the page then shows the same report. The file lists the counts, each coverage gap and the rule packs the counts came from. Proofline records each export in the [audit log](/help/audit-log/).

## Check the rule packs

**Rule packs** lists each analyzer pack the window's runs used, with its version, the digest of its pinned image and how many runs used it. Use it to tell which rules produced the counts when you compare two reports.

## Related guides

-   [Read and act on a finding](/help/findings/)
-   [Find a review or pull request](/help/find-reviews/)
-   [Inspect the audit log](/help/audit-log/)
