> 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/vulnerabilities.md).

# Vulnerabilities

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

The Vulnerabilities module is where you can see all your vulnerabilities, across every project you have access to. Here you can filter and track your vulnerabilities, to make remediation and follow-ups faster and easier.

AttackForge supports extensive filters to help you get the information you need. You can combine filters to drill down the results, sort and group the data, and toggle different views of certain fields. You can also customise your table settings to see the data how you want it.

To learn how vulnerabilities are created and updated, see [Creating vulnerabilities](https://support.attackforge.com/app/getting-started/creating-vulnerabilities) and [Updating vulnerabilities](https://support.attackforge.com/app/getting-started/updating-vulnerabilities).

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FAoFpN49Pj4lOjH8pXgmm%2Fvulnerabilities-at-a-glance.svg?alt=media&amp;token=b0fee5f1-28e6-4398-b78f-4a6a0ce10fc1" alt=""><figcaption></figcaption></figure>

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

* **One list, not one per project.** Findings from every project you can access are in one place, so nothing is missed between projects.
* **Faster remediation.** Filters take you straight to the vulnerabilities that need action, such as open Critical findings or those close to their SLA.
* **Easier follow-ups.** Group by project, asset or owner to see who needs to act, and track progress until each vulnerability is closed.
* **Your view, your way.** Save time each day by setting up the table with the columns and order you use most.

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

| Who                                  | To                                                                         |
| ------------------------------------ | -------------------------------------------------------------------------- |
| **Security and programme managers**  | Track open vulnerabilities and remediation across every project            |
| **Remediation teams and developers** | Find the vulnerabilities they need to fix, and request retests             |
| **Testers**                          | Check findings across projects, such as recurring issues on the same asset |
| **Clients and stakeholders**         | See the vulnerabilities on their projects and follow up on fixes           |
| **Risk and compliance teams**        | Report on open risk, SLAs and remediation progress                         |

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

## Work with your vulnerabilities <a href="#work-with-your-vulnerabilities" id="work-with-your-vulnerabilities"></a>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FBsBG1QAeETnkaFIHzxTc%2FScreenshot%202026-11-06%20at%206.03.24%E2%80%AFpm.png?alt=media&amp;token=93681579-74d6-4c01-b2ec-ba2d490b8693" alt=""><figcaption></figcaption></figure>

### Filter your vulnerabilities <a href="#filter-your-vulnerabilities" id="filter-your-vulnerabilities"></a>

AttackForge supports extensive filters to help you get the information you need. Use them to find, for example:

* open Critical and High vulnerabilities
* vulnerabilities on a particular project or asset
* vulnerabilities that are close to, or past, their SLA
* vulnerabilities that are ready for retesting

These are examples.

For complex conditions, use advanced filtering. See [Advanced filtering](https://support.attackforge.com/app/getting-started/advanced-filtering).

### Combine filters to drill down <a href="#combine-filters-to-drill-down" id="combine-filters-to-drill-down"></a>

You can combine filters to drill down the results. Each filter you add narrows the list. For example, filter on Critical vulnerabilities, then on one business unit's projects, then on those still open.

### Sort and group the data <a href="#sort-and-group-the-data" id="sort-and-group-the-data"></a>

You can sort and group the data:

* **Sort** to put the most important vulnerabilities first, such as by priority or due date.
* **Group** to see vulnerabilities together, such as by project, asset or status, so you can follow up with each owner.

## Set up your custom views <a href="#set-up-your-tables" id="set-up-your-tables"></a>

**Views** save the way you've set up a table, so you can get back to it in one click instead of setting it up again each time.

Views belong to the table you create them on. You can name them, give them advanced filters, put them in the order you like, and duplicate them.

Set up a table, save it as a view, and open it again in one click. Personal and cross-table views are only visible to you. System views are shared by Administrators with the roles, groups and users who need them. See [Custom views](https://support.attackforge.com/app/getting-started/custom-views).

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

The module only shows vulnerabilities on projects you have access to.

| Who                                               | What they see                                                                                                      |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Administrators**                                | Vulnerabilities on every project, because Administrators can access all projects by default                        |
| **Everyone else**                                 | Vulnerabilities on the projects they've been given access to, directly or through a group                          |
| **Users with Upload or View access on a project** | That project's vulnerabilities, except those still pending. Pending vulnerabilities are hidden until they pass QA. |

If someone can't find a vulnerability, check their access to the project, and whether the vulnerability is still pending. See [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access).

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

* **Start broad, then narrow.** Add one filter at a time, so you can see what each one removes.
* **Group for follow-ups.** Grouping by project or asset shows who needs to act on what.
* **Set up your table once.** Customise the columns you use most, and they'll be there every time.
* **Use advanced filtering for complex questions** that simple filters can't answer.
* **Check access before assuming a finding is missing.** Pending vulnerabilities are hidden from Upload and View users.

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

**Which vulnerabilities appear in the module?** All the vulnerabilities on projects you have access to.

**Can I combine filters?** Yes. Combine filters to drill down the results.

**Can I change the columns in the table?** Yes. You can customise your table settings and crate custom views. See [Custom views](https://support.attackforge.com/app/getting-started/custom-views).

**Why can't a client see a vulnerability?** It may still be pending. Users with Upload or View access can't see pending vulnerabilities.

**Where do I create or update a vulnerability?** On the project. See [Creating vulnerabilities](https://support.attackforge.com/app/getting-started/creating-vulnerabilities) and [Updating vulnerabilities](https://support.attackforge.com/app/getting-started/updating-vulnerabilities).

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

* [Creating vulnerabilities](https://support.attackforge.com/app/getting-started/creating-vulnerabilities)
* [Updating vulnerabilities](https://support.attackforge.com/app/getting-started/updating-vulnerabilities)
* [Advanced filtering](https://support.attackforge.com/app/getting-started/advanced-filtering)
* [Manage user](https://support.attackforge.com/app/getting-started/manage-user)
* [Custom views](https://support.attackforge.com/app/getting-started/custom-views)
* [Vulnerability SLAs](https://support.attackforge.com/app/getting-started/vulnerability-slas)
* [Retesting](https://support.attackforge.com/app/getting-started/retesting)
* [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access)


---

# 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/vulnerabilities.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.
