> For the complete documentation index, see [llms.txt](https://copilot-docs.bugbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://copilot-docs.bugbase.ai/enterprise/modules/statistics.md).

# Statistics

The **Statistics** page provides a high-level overview of vulnerabilities and findings for a given assessment scope. It can be viewed **per assessment** or **per root entity** (Domain, Subnet, or APK file) to help prioritize remediation efforts.

* **Views** – Separate dashboards are available for **External Assessments** and **Internal Assessments**, each tailored to the nature of the test.
* **Metrics shown:**
  * Total vulnerabilities and severity breakdown
  * Percentages of vulnerabilities by severity. External assessments follow the active severity display mode: CVSS uses Critical, High, Medium, Low, or Informational, while VRT uses Bugcrowd-style P1-P5 priorities when VRT data is available.
  * Most common CWE IDs and vulnerability types
  * Top vulnerabilities by CVSS score
  * Vulnerabilities grouped by affected asset or relation
  * Time-based trends of vulnerability discovery
  * For internal assessments: discovered subnets, hosts, services, ports/protocols, and secrets found

<figure><img src="/files/n5bnH6duRC4uSFQU1Oz9" alt=""><figcaption></figcaption></figure>

Set the external severity mode from **Settings -> External -> Severity Display**.

Choose **CVSS** for standards-aligned risk and compliance views. Choose **VRT** for bug bounty style prioritization using Bugcrowd's web and API taxonomy. See [Bugcrowd VRT](https://bugcrowd.com/vulnerability-rating-taxonomy).

This page acts as the **central reporting view** for assessment results, helping security teams understand exposure, identify recurring weaknesses, and track progress over time.


---

# 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://copilot-docs.bugbase.ai/enterprise/modules/statistics.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.