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

# Attack Chains

## Overview

Attack chains turn a list of findings into a story that shows business impact. An attack chain links the vulnerabilities an attacker would use, step by step, from their starting point to their goal.

In this example, three findings that each look moderate on their own:

1. A login page that reveals whether a username exists (Low)
2. No lockout after repeated failed logins (Medium)
3. An admin panel reachable from the internet (Medium)

Together, they let an attacker find valid usernames, guess a password, and take over the admin panel. Fixing any one of them, such as adding account lockout, breaks the chain.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FitDBEvvmfwD3m2IT2ubJ%2Fattack-chains-at-a-glance.svg?alt=media&amp;token=20ef9c9b-e7bb-4cbc-b137-93e98ead94ea" alt=""><figcaption></figcaption></figure>

The Attack Chains module shows every attack chain across all the projects you have access to.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2Fimm6uB1z7UJ4FzsEdYvg%2FScreenshot%202026-11-10%20at%2012.09.14%E2%80%AFpm.png?alt=media&amp;token=76e705a5-bfcc-4a50-a2cd-8f20cb691516" alt=""><figcaption></figcaption></figure>

## Why it matters

Attack chains show things a plain list of vulnerabilities can't:

| Benefit                                   | What it means                                                                                                                                                                                                                                                                                          | Who it helps most                       |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------- |
| **Show real impact**                      | A pile of "medium" issues is often dismissed. Linking them into one path, from anonymous access to compromise of your crown jewels, shows the same findings as a serious business risk. The chain answers the "so what?" that executives and risk owners care about.                                   | Executives and risk owners              |
| **Force realism**                         | CVSS and similar scores rate each flaw on its own, but attackers chain them. A demonstrated chain proves a path can actually be walked. Scary findings may lead nowhere, and minor ones may be the key link, so chains give a better signal for prioritisation than severity alone.                    | Security managers and remediation teams |
| **Break the chain, don't fix everything** | If an attack needs five findings, fixing any one link can stop it. That's usually cheaper and faster than fixing everything, and gives you a defensible interim position while permanent fixes are built.                                                                                              | Remediation teams and clients           |
| **Map to frameworks**                     | Chains map cleanly onto frameworks such as MITRE ATT\&CK and the Cyber Kill Chain, giving the blue team a shared language. Each stage is a detection point: was it caught, and if not, where else could the chain have been broken? This supports purple team work, SOC tuning and tabletop exercises. | Blue teams, SOCs and purple teams       |
| **Expose systemic weaknesses**            | Chains reveal root causes that single findings hide, such as over-permissioned service accounts, flat networks, missing egress controls and identity sprawl. These rarely show up as one CVE, but become clear when you trace an attacker's movement end to end.                                       | Security architects and leadership      |

## Who uses it

| Who                            | To                                                               |
| ------------------------------ | ---------------------------------------------------------------- |
| **Testers**                    | Build chains from their findings, to show how they were combined |
| **Executives and risk owners** | Understand the business impact of a test                         |
| **Remediation teams**          | Find the one fix that breaks the most chains                     |
| **Blue teams and SOCs**        | Check which stages were detected, and tune detection             |
| **Security managers**          | See chains across every project, and spot recurring weaknesses   |

## Use attack chains

### See chains across your projects

Open **Attack Chains** from the main menu to see every attack chain across all the projects you have access to. Every application role has full access to the module. You only see chains on projects you can access.

### Create and change chains

Attack chains are built on a project, from that project's vulnerabilities. See [Attack chains](https://support.attackforge.com/app/getting-started/attack-chains) for how to create one.

| Who                                                            | Can                                                                |
| -------------------------------------------------------------- | ------------------------------------------------------------------ |
| **Administrators**                                             | View, create, update, re-order, duplicate and delete attack chains |
| **Users with Edit access on the project**                      | View, create, update, re-order, duplicate and delete attack chains |
| **Project Coordinators, and users with Upload or View access** | View attack chains                                                 |

See [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access).

## Use chains in reports

Attack chains are part of a project's reporting data, so report templates can include them. Use them in executive summaries to explain business impact. See [Reporting](https://support.attackforge.com/app/getting-started/reporting).

## Use chains to plan remediation

Look for the findings that appear in the most chains. Fixing those first breaks the most attack paths, and gives you a defensible interim position while the remaining fixes are built.

## Tips

* **Start from the goal.** Decide what the attacker wants, such as customer data or domain admin, then work back through the findings that get them there.
* **Include the low and medium findings.** They're often the links that make a chain work.
* **Name each stage clearly**, so a non-technical reader can follow the path.
* **Map stages to MITRE ATT\&CK or the Cyber Kill Chain** when the report is for a blue team or SOC.
* **Point to the cheapest link to break.** It gives the client a quick win while longer fixes are planned.
* **Look across projects.** The same weakness appearing in many chains is usually a systemic issue.

## FAQ

**What does the Attack Chains module show?** Every attack chain across all the projects you have access to.

**Who can create an attack chain?** Administrators, and users with Edit access on the project.

**Can clients see attack chains?** Yes. Every project access level can view attack chains.

**Why use attack chains if findings already have severity scores?** Severity scores rate each flaw on its own. Attack chains show how flaws combine, which is how attackers actually work.

**Do I need to fix every finding in a chain?** No. Fixing any one link can stop the attack. Fix the rest as permanent remediation.

**Can attack chains be mapped to MITRE ATT\&CK?** Chains map cleanly onto frameworks such as MITRE ATT\&CK and the Cyber Kill Chain.

## Related pages

* [Attack chains (getting started)](https://support.attackforge.com/app/getting-started/attack-chains)
* [Vulnerabilities](https://support.attackforge.com/app/modules/vulnerabilities)
* [Projects](https://support.attackforge.com/app/modules/projects)
* [Reporting](https://support.attackforge.com/app/getting-started/reporting)
* [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/attack-chains.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.
