> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/modules/analytics.md).

# Analytics

## Overview <a href="#overview" id="overview"></a>

Analytics helps you answer the tough questions about your security testing programme. It helps management and executives track the performance of their organisation, business units, suppliers, teams, platforms, technologies and compliance, so they can make better decisions based on hard data.

Analytics can be viewed globally, across all the projects, assets and vulnerabilities you have access to. You can compare different time periods, groups, or both, to narrow the results to a specific reporting period or requirement. Every analytic can be clicked to see the underlying data for further analysis.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FgcVFa0YmZyquz8OHHQNp%2Fanalytics-at-a-glance.svg?alt=media&amp;token=942af260-fae4-438c-8504-c104e5943527" alt=""><figcaption></figcaption></figure>

## Why it matters <a href="#why-it-matters" id="why-it-matters"></a>

* **Answers, not just counts.** The dashboard shows where things stand today. Analytics shows how they're changing, and where.
* **Evidence for decisions.** Budget, supplier and remediation decisions are easier to make and defend with real data from your testing.
* **One source of truth.** The analytics come from the same projects and vulnerabilities your teams work on, so there's no separate spreadsheet to maintain.
* **Every number can be checked.** Click any analytic to see exactly what's behind it.

## Who uses it <a href="#who-uses-it" id="who-uses-it"></a>

| Who                                 | To                                                                                        |
| ----------------------------------- | ----------------------------------------------------------------------------------------- |
| **Executives and management**       | Track the performance of the organisation and its business units, and report to the board |
| **Security and programme managers** | Compare teams, suppliers and periods, and find where risk is building                     |
| **Vendor and supplier managers**    | Compare the performance of testing vendors and suppliers                                  |
| **Risk and compliance teams**       | Track compliance and evidence progress over a reporting period                            |

Every application role can filter analytics on their own data. See [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access).

## Use Analytics <a href="#use-analytics" id="use-analytics"></a>

### Choose what to track <a href="#choose-what-to-track" id="choose-what-to-track"></a>

Analytics can track the performance of:

| Track                 | Example question                                                         |
| --------------------- | ------------------------------------------------------------------------ |
| **Your organisation** | Are we finding and fixing vulnerabilities faster than last year?         |
| **Business units**    | Which business unit has the most open Critical and High vulnerabilities? |
| **Suppliers**         | Which supplier's applications have the most findings per test?           |
| **Teams**             | Which remediation team is closing vulnerabilities within SLA?            |
| **Platforms**         | Are our cloud platforms improving over time?                             |
| **Technologies**      | Which technologies keep producing the same kinds of findings?            |
| **Compliance**        | How much of this year's required testing is complete?                    |

These questions are examples.

### Compare periods and groups <a href="#compare-periods-and-groups" id="compare-periods-and-groups"></a>

Compare different time periods, groups, or both, to narrow the results to a specific reporting period or requirement. For example, compare this quarter with last quarter, or compare two business units over the same financial year.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FGUV0LieapSz5GBMyKWgs%2FScreenshot%202026-11-06%20at%205.56.04%E2%80%AFpm.png?alt=media&amp;token=1caeb997-68a4-4e8a-90f6-d01e4d8c9353" alt=""><figcaption></figcaption></figure>

#### Drill down into the data <a href="#drill-down-into-the-data" id="drill-down-into-the-data"></a>

Click any analytic to see the underlying data. Use it to:

* check what's behind a number before you report it
* find the projects, assets or vulnerabilities driving a trend
* carry on your analysis from the data itself

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F1jPmxQ7L6HcoqMadUCpS%2FScreenshot%202026-11-06%20at%205.56.58%E2%80%AFpm.png?alt=media&amp;token=464f4d12-4b03-4399-850c-33b532708fb5" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FdeLurHkrQd1j765uHPmb%2FScreenshot%202026-11-06%20at%205.58.03%E2%80%AFpm.png?alt=media&amp;token=942f82f3-439b-4565-b43c-299679fa6cd6" alt=""><figcaption></figcaption></figure>

### Understand what you're seeing <a href="#understand-what-youre-seeing" id="understand-what-youre-seeing"></a>

Analytics only includes the projects, assets and vulnerabilities you have access to. Administrators can access all projects by default, so their analytics cover everything. Other users see analytics for the projects they've been given access to, directly or through a group. Two people can see different results, and both are correct.

If an analytic is missing data you expect, check the person's access first. See [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access).

## Tips <a href="#tips" id="tips"></a>

* **Start with the question.** Decide what you need to answer, then choose the period and groups that answer it.
* **Compare like with like.** Use periods of the same length, such as quarter against quarter.
* **Use groups to model your organisation.** Groups for business units, suppliers or teams make those comparisons possible.
* **Drill down before you report.** Check the data behind a number so you can answer the first follow-up question.
* **Remember access.** A colleague with different access will see different results.

## FAQ <a href="#faq" id="faq"></a>

**What data does Analytics use?** All the projects, assets and vulnerabilities you have access to.

**Who can use Analytics?** Every application role can filter analytics on their own data.

**Can I compare two periods?** Yes. You can compare different time periods, groups, or both.

**Can I see the data behind a chart?** Yes. Every analytic can be clicked to see the underlying data.

**How is Analytics different from the dashboard?** The [dashboard](https://support.attackforge.com/app/modules/dashboard) gives a summary of your projects and vulnerabilities when you log in. Analytics lets you track performance over time and compare periods and groups.

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Dashboard](https://support.attackforge.com/app/modules/dashboard)
* [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access)
* [Groups](https://support.attackforge.com/app/modules/groups)
* [Advanced filtering](https://support.attackforge.com/app/getting-started/advanced-filtering)
* [Vulnerability SLAs](https://support.attackforge.com/app/getting-started/vulnerability-slas)
* [Reporting](https://support.attackforge.com/app/getting-started/reporting)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.attackforge.com/app/modules/analytics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
