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

# Training

## Overview

Learn AttackForge at your own pace with free, self-guided training courses. Each course is a downloadable slide deck you work through on your own, with hands-on labs in your own AttackForge tenant, quick knowledge checks, and links back to the Support site for every topic.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F08jwPvIpAsDY0mvnpnXu%2FAttackForge_Training_Overview.png?alt=media&amp;token=2ae79d4c-b9e8-48cd-a69c-ac68af9b9ef3" alt=""><figcaption></figcaption></figure>

There are three courses, one for each way people use AttackForge:

| Course                                  | Who it's for                                                                              | Length                       |
| --------------------------------------- | ----------------------------------------------------------------------------------------- | ---------------------------- |
| **AttackForge for Penetration Testers** | Pentesters, consultants, red and purple teamers, testing leads                            | About 8 hours, in 3 parts    |
| **AttackForge for Administrators**      | Tenant administrators, platform owners, security programme managers, Project Coordinators | About 12.5 hours, in 3 parts |
| **AttackForge for Clients**             | Engineers, developers, technology teams, asset owners, stakeholders                       | About 3 hours                |

## Why we built these courses

AttackForge brings security, engineering and business teams together on one platform. That only works when everyone knows their part: testers recording consistent findings, administrators setting up access and workflows the right way, and engineering teams fixing issues and proving the fixes work.

The courses teach more than where to click. They explain **why** each feature exists and **who** it helps, so you can make good decisions in your own tenant.

## How the courses work

Every module follows the same four steps:

1. **Learn.** Concept slides explain what a feature does and why it exists.
2. **Try it.** A hands-on lab with numbered steps and the result you should expect.
3. **Check.** A few questions to confirm the key points, with answers on the next slide.
4. **Go deeper.** Learn More links to the matching Support site pages.

Each course ends with a **capstone lab**: a realistic scenario you complete without step-by-step help, plus a self-assessment checklist. Aim for at least 80% before you call the course complete.

## Before you start

You'll get the most out of the courses with:

* **An AttackForge account.** Any deployment works: SaaS, self-hosted or air-gapped.
* **A safe place to practise.** Use a practice project with no client data, or a non-production tenant. **Never use a live client engagement for labs.**
* **The right access for your course.** Each course's first slides list exactly what you need.

{% hint style="info" %}
**Don't have access yet?** Deploy a **free 24-hour trial environment** on demand at [try.attackforge.io](https://try.attackforge.io) and do the labs there.
{% endhint %}

{% hint style="info" %}
**Tip:** keep AttackForge open in another window and switch between the course and the app as you go.
{% endhint %}

## AttackForge for Penetration Testers

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F3vrnZ5UMnAMDkYYam9Sm%2FAttackForge_Training_Penetration_Testers.png?alt=media&amp;token=085961c0-aad1-4254-98fa-21edffed1536" alt=""><figcaption></figcaption></figure>

Run a security assessment from start to finish in AttackForge: prepare, test, record, review, report and retest.

**You'll learn to:**

* Check entry criteria and keep credentials and files secure in the project workspace
* Work through test cases with evidence, so your coverage can be measured
* Create and import consistent findings from the writeup library
* Get findings through peer review and QA before the client sees them
* Build attack chains and generate client reports from live data
* Run retest rounds and close the loop with engineering teams

**You'll need:** Consultant access with **Edit** rights on a practice project that has a few in-scope assets and a test suite. Part 2 also needs a sample scan file from a lab target you're allowed to test.

<table data-header-hidden><thead><tr><th width="92.53125"></th><th width="251.640625"></th><th width="166.953125"></th><th></th></tr></thead><tbody><tr><td>Part</td><td>Modules</td><td>Time</td><td>Download</td></tr><tr><td><strong>Part 1</strong></td><td>0 Orientation and access · 1 The engagement lifecycle · 2 Workspace and pages · 3 Test cases</td><td>About 2.5 hours</td><td><div data-gb-custom-block data-tag="file" data-src="/files/HEfwX0MGZ0K1SkX2mvfk"></div></td></tr><tr><td><strong>Part 2</strong></td><td>4 Recording vulnerabilities · 5 Importing tool output · 6 Writeups and libraries · 7 Peer review and QA</td><td>About 2.5 hours</td><td><div data-gb-custom-block data-tag="file" data-src="/files/pCzffRfH7XoemdgAU4eC"></div></td></tr><tr><td><strong>Part 3</strong></td><td>8 Attack chains · 9 Reporting · 10 Retesting and remediation · 11 Views, Actions and AI · Capstone</td><td>About 3 hours</td><td><div data-gb-custom-block data-tag="file" data-src="/files/sxD5uTnRy5uluoXlZzCs"></div></td></tr></tbody></table>

**Capstone:** run a mini engagement end to end, from workspace preparation to a completed retest round.

## AttackForge for Administrators

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FRnoeQjeIrkIDFwpGAyog%2FAttackForge_Training_Administrators.png?alt=media&amp;token=83339ea2-69c1-4a5a-b1ec-868649e75386" alt=""><figcaption></figcaption></figure>

Configure, secure, govern, automate and operate an AttackForge tenant.

**You'll learn to:**

* Design least-privilege access with roles, access levels, groups and SSO
* Manage the user lifecycle, from joiners to leavers, and onboard external testing vendors safely
* Build and govern writeup libraries, test suites and asset libraries
* Shape forms with custom fields, and set up scoring, SLAs and QA
* Automate reminders, reports and workflows with custom emails, Flows and Actions
* Grant API, service account and AI MCP access safely
* Run the tenant reliably, including self-hosted and air-gapped updates

**You'll need:** an **Administrator** account on a non-production tenant, plus a **Consultant** and a **Client** test account so you can check what other users see after each change.

<table data-header-hidden><thead><tr><th width="86.73046875"></th><th width="256.046875"></th><th width="166.859375"></th><th></th></tr></thead><tbody><tr><td>Part</td><td>Modules</td><td>Time</td><td>Download</td></tr><tr><td><strong>Part 1</strong></td><td>A0 Administration and licensing · A1 The access model · A2 User lifecycle · A3 Single sign-on · A4 Groups and delegation</td><td>About 3.5 hours</td><td><div data-gb-custom-block data-tag="file" data-src="/files/ifnjf0HeeJHpE0RFphGD"></div></td></tr><tr><td><strong>Part 2</strong></td><td>A5 Libraries and content · A6 Requests, projects and portfolios · A7 Custom fields and forms · A8 Scoring, SLAs and QA · A9 Notifications and emails</td><td>About 4 hours</td><td><div data-gb-custom-block data-tag="file" data-src="/files/AVjHIPbOHRYYDAgZqjKY"></div></td></tr><tr><td><strong>Part 3</strong></td><td>A10 Report templates · A11 Flows and Actions · A12 Integrations · A13 APIs, service accounts and AI MCP · A14 Operating the tenant · Capstone</td><td>About 5 hours</td><td><div data-gb-custom-block data-tag="file" data-src="/files/dc3SSGtNs6D2eVCzSCBw"></div></td></tr></tbody></table>

**Capstone:** set up a tenant for a new business unit and an external vendor, then prove your access model works with test accounts.

Some features covered in Part 3, such as Flows, SSO and AI MCP, depend on your plan or add-ons. See [Add-ons](https://support.attackforge.com/core/add-ons).

## AttackForge for Clients

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FKDbmtq3tcTKwJ7bABjCq%2FAttackForge_Training_Clients.png?alt=media&amp;token=f4b9cced-cc16-4825-b546-ebd2082524ba" alt=""><figcaption></figcaption></figure>

For the engineers, technology teams and asset owners who request testing and fix what it finds.

**You'll learn to:**

* Request testing with a complete, well-scoped request
* Share builds and documents securely, and know when testing is happening
* Read a finding and understand how urgent it is and what to fix
* Commit to remediation dates and keep everyone updated
* Mark fixes ready, request retests and see findings closed
* Download reports and evidence, and track your security posture

**You'll need:** access to a practice project with **View** or **Upload** rights and a few sample findings. Ask your security team to set this up.

<table data-header-hidden><thead><tr><th width="351.50390625"></th><th width="156.58203125"></th><th></th></tr></thead><tbody><tr><td>Modules</td><td>Time</td><td>Download</td></tr><tr><td>C0 Orientation and access · C1 Requesting testing · C2 Supporting a live test · C3 Understanding findings · C4 Remediation and retesting · C5 Reports and insights · Capstone</td><td>About 3 hours</td><td><div data-gb-custom-block data-tag="file" data-src="/files/bM7nsDmQQT60rEituyl0"></div></td></tr></tbody></table>

**Capstone:** take a finding from the first alert to closed.

## Suggested learning paths

Not sure where to start? Pick the path that matches your role.

| Your role                              | Suggested path                                                                            |
| -------------------------------------- | ----------------------------------------------------------------------------------------- |
| Penetration tester or consultant       | Penetration Testers, Parts 1–3                                                            |
| Testing lead or Project Coordinator    | Penetration Testers, Parts 1–3, then Administrators Part 2 (A5–A6)                        |
| Tenant administrator or platform owner | Administrators, Parts 1–3. Penetration Testers Part 1 first, if you're new to AttackForge |
| Automation or integration builder      | Administrators Part 3 (A10–A13)                                                           |
| Security leader                        | Clients C0 and C5, then Administrators A6 and A8                                          |
| Engineer, developer or asset owner     | Clients                                                                                   |

## Rolling out training to your team

If you're onboarding a team, a vendor or your own clients:

* **Set up practice projects first.** Give each learner a practice project with the right access level, so labs never touch live engagements.
* **Match courses to roles.** Send testers, administrators and engineering teams to their own course.
* **Onboard vendors with the Penetration Testers course.** External testers learn your workflow before they start on your projects.
* **Share the Clients course with remediation teams.** Engineers who know how to update findings and request retests close issues faster.
* **Revisit after releases.** Check [What's new](https://support.attackforge.com/release-notes/2026) for features added since the courses were published.

## FAQ

**Are the courses free?** Yes. All courses are free to download from this page.

**Do I need my own AttackForge tenant?** You need somewhere safe to do the labs. Use a practice project or a non-production tenant, or deploy a free 24-hour trial at [try.attackforge.io](https://try.attackforge.io). You can read the Learn and Check slides without access.

**How long does each course take?** About 8 hours for Penetration Testers, 12.5 hours for Administrators and 3 hours for Clients. Each part can be done on its own, and each module takes 20–90 minutes.

**Will my screens look exactly like the course?** Your administrator may have added custom fields, forms, Actions and workflows, so some screens will differ. The concepts and core workflows are the same on every tenant.

**Some features in the course aren't available to me. Why?** That usually comes down to your access level, your role, or your plan. Ask your administrator, or see [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access).

**Is there a certificate?** The courses end with a self-assessment checklist rather than a formal exam.

**I found something out of date. What should I do?** Let us know through [Contact](https://support.attackforge.com/other/contact) or by [raising a support ticket](https://support.attackforge.com/enterprise/raising-support-tickets).

## Related pages

* [How AttackForge works](https://support.attackforge.com/app/getting-started)
* [Key concepts and access](https://support.attackforge.com/app/getting-started/concepts-and-access)
* [Modules](https://support.attackforge.com/app/modules)
* [Automations and integrations](https://support.attackforge.com/app/automations-and-integrations)
* [Release notes](https://support.attackforge.com/release-notes/2026)


---

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