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

# Test Suites

## Overview

The Test Suites module lets you build your own methodologies, checklists and service catalogues. Customers can choose from them when requesting a project, or you can assign them to new projects.

Test cases come from industry methodologies, imports or your own work. A test suite groups them, with execution flows and custom fields. Assign the suite to a project, and its test cases become the testers' checklist, alongside any abuse cases for that project.

When you assign a test suite to a project, its linked test cases are assigned too. This gives the pentester or auditor a checklist to work through.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FsL7Q2K97aRp3FZsTokXZ%2Ftest-suites-at-a-glance.svg?alt=media&amp;token=27a3fa55-77c4-487e-9598-a602ddceabe0" alt=""><figcaption></figcaption></figure>

## Why it matters

A test suite helps:

* **clients** understand exactly what was tested on the project
* **developers and engineers** link test cases to vulnerabilities
* **pentesters** structure their testing in a methodical, consistent and standardised way
* **organisations** create repeatable, standardised and comparable assessments, whoever performs them

Test cases can give valuable insight into a penetration test or audit. They show:

* what was tested
* how it was tested
* when it was tested
* who tested it
* what the outcome was
* what the supporting evidence is

See [Test cases](https://support.attackforge.com/app/getting-started/test-cases) for how test cases are used on projects.

## How it fits together

| Item               | What it is                                                       | Where it lives                                      |
| ------------------ | ---------------------------------------------------------------- | --------------------------------------------------- |
| **Test suite**     | A methodology, checklist or service, such as OWASP ASVS Level 2  | The Test Suites library                             |
| **Test case**      | One test within a suite                                          | Linked to a test suite                              |
| **Execution flow** | The steps, tools, processes and links for performing a test case | On a test case                                      |
| **Abuse case**     | A one-off test case for a specific project                       | On the project, tracked under `Project Abuse Cases` |

## Who uses it

| Who                                         | To                                                                     |
| ------------------------------------------- | ---------------------------------------------------------------------- |
| **Testing leads and methodology owners**    | Build and maintain test suites and test cases                          |
| **Project Coordinators and Administrators** | Assign test suites to projects, and add abuse cases                    |
| **Pentesters and auditors**                 | Work through test cases, and record outcomes and evidence              |
| **Clients**                                 | Choose a test suite when requesting a project, and see what was tested |

## My test suites

AttackForge comes with dozens of industry methodologies that you can select for any project. They're drawn from [OWASP](https://owasp.org/www-project-application-security-verification-standard/), [MITRE ATT\&CK](https://attack.mitre.org/), [OSSTMM](https://www.isecom.org/research.html), [NIST](https://www.nist.gov/) and others.

Test suites you create appear under `My Test Suites`. From the actions menu you can `Edit`, `Duplicate`, `Reorder` or `Delete` them. Click a test suite's name to see its test cases.

All test suites are shared across the library, so your peers can reuse what you build and you pool your knowledge.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FgQ6yjPHJnFThmOE8SZOD%2FScreenshot%202026-11-10%20at%203.55.08%E2%80%AFpm.png?alt=media&amp;token=19e4d216-a6f8-49c5-ae39-81f9cde54c63" alt=""><figcaption></figcaption></figure>

## Create a test suite

1. Click `New`.
2. Fill in the form and submit it. The test suite is ready for test cases straight away.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FUniE98adwolBhFo6djuv%2FScreenshot%202026-11-10%20at%203.55.39%E2%80%AFpm.png?alt=media&amp;token=0af6d72b-cf70-4d0f-9fd7-e21426543559" alt=""><figcaption></figcaption></figure>

## Add test cases

1. Open the test suite.
2. Click the `Test Cases` tab.
3. Click `Add Test Case`.
4. To save time, search the library for an existing test case. Its fields are pre-filled, so you only need to make small changes.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FeaAakQ9RX1myEun5Vb9A%2FScreenshot%202026-11-10%20at%203.56.19%E2%80%AFpm.png?alt=media&amp;token=d355d14c-0384-4c18-92ce-3d4fae06ab05" 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%2FmrAR7SFpbhIq3BdrUoJp%2FScreenshot%202026-11-10%20at%203.56.33%E2%80%AFpm.png?alt=media&amp;token=1ee17f05-2490-4968-92de-906df2ce886d" alt=""><figcaption></figcaption></figure>

## Update test cases and test suites

You can update a test case at any time from its actions menu, and a test suite at any time from the page menu.

{% hint style="info" %}
**Important:** changes to test cases in your library apply to every project that references them.
{% endhint %}

{% hint style="info" %}
**Important:** test cases added to or deleted from a test suite don't apply to existing projects. This keeps a record of what was assigned and tested, and stops a Completed project becoming Not Completed.
{% endhint %}

## Add custom fields

Create custom fields for test cases in the Administration module. See [Custom fields and forms](https://support.attackforge.com/app/getting-started/custom-fields-and-forms).

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F8tzgy5vIJJJ7wH5eSxgD%2FScreenshot%202026-11-10%20at%203.58.46%E2%80%AFpm.png?alt=media&amp;token=a4b37814-c144-4ab3-92c6-04628ed24204" 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%2FDbr8AXkHpa1JE0aQGN01%2FScreenshot%202026-11-10%20at%204.08.27%E2%80%AFpm.png?alt=media&amp;token=b5ef167a-17f1-40c5-b49e-5d0d1cc0f8a5" 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%2F2TANqo3l1nS2LBpVGUZk%2FScreenshot%202026-11-10%20at%204.09.09%E2%80%AFpm.png?alt=media&amp;token=5cacfa10-35e4-4330-b541-acdcf9f25de5" alt=""><figcaption></figcaption></figure>

## Import test cases

The AttackForge team has prepared more methodologies you can import. They're published on [GitHub](https://github.com/AttackForge/TestSuites).

### Methodologies you can import

| Category                                     | Methodology                                                                                                                                                                                      | Test cases |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- |
| **Red Teaming**                              | [MITRE ATT\&CK Enterprise Version 19.1](https://github.com/AttackForge/TestSuites/blob/main/MITRE/ATT%26CK/ENTERPRISE/mitre_attack_enterprise_19_1.json)                                         | 697        |
|                                              | [MITRE ATT\&CK Mobile Version 19.1](https://github.com/AttackForge/TestSuites/blob/main/MITRE/ATT%26CK/MOBILE/mitre_attack_mobile_19_1.json)                                                     | 124        |
|                                              | [MITRE ATT\&CK ICS Version 19.1](https://github.com/AttackForge/TestSuites/blob/main/MITRE/ATT%26CK/ICS/mitre_attack_ics_19_1.json)                                                              | 97         |
|                                              | [OSSTMM Version 3 - Human Security Testing](https://github.com/AttackForge/TestSuites/blob/main/OSSTMM/v3/Chapter%207/osstmm_human_security_testing.json)                                        | 60         |
|                                              | [OSSTMM Version 3 - Physical Security Testing](https://github.com/AttackForge/TestSuites/blob/main/OSSTMM/v3/Chapter%208/osstmm_physical_security_testing.json)                                  | 59         |
| **Artificial Intelligence (AI)**             | [MITRE ATLAS v2026.06](https://github.com/AttackForge/TestSuites/blob/main/MITRE/ATLAS/mitre_atlas_v2026.06.json)                                                                                | 173        |
|                                              | [OWASP AI Testing Guide 2026](https://github.com/AttackForge/TestSuites/blob/main/OWASP/AITG/owasp_ai_testing_guide_2026.json)                                                                   | 32         |
|                                              | [OWASP Top 10 for Large Language Model Applications 2025](https://github.com/AttackForge/TestSuites/blob/main/OWASP/Top%2010/OWASP-LLM-Applications-Top-10-2025.json)                            | 10         |
| **Desktop Applications**                     | [OWASP Desktop App Security Top 10 2021](https://github.com/AttackForge/TestSuites/blob/main/OWASP/Top%2010/OWASP-Desktop-App-Security-Top-10-2021.json)                                         | 10         |
| **Operational Technology (OT)**              | [MITRE ATT\&CK ICS Version 19.1](https://github.com/AttackForge/TestSuites/blob/main/MITRE/ATT%26CK/ICS/mitre_attack_ics_19_1.json)                                                              | 97         |
|                                              | [OWASP Operational Technology (OT) Top 10 2025](https://github.com/AttackForge/TestSuites/blob/main/OWASP/Top%2010/OWASP-Operational-Technology-%28OT%29-Top-10-2025.json)                       | 10         |
| **Web Application and API**                  | [OWASP Web Security Testing Guide Version 4.2](https://github.com/AttackForge/TestSuites/blob/main/OWASP/WSTG/owasp-wstg-4.2.json)                                                               | 107        |
|                                              | [OWASP Application Security Verification Standard (ASVS) Version 5.0.0 - Level 1](https://github.com/AttackForge/TestSuites/blob/main/OWASP/ASVS/v5/owasp_asvs_5.0.0_level_1.json)               | 70         |
|                                              | [OWASP Application Security Verification Standard (ASVS) Version 5.0.0 - Level 2](https://github.com/AttackForge/TestSuites/blob/main/OWASP/ASVS/v5/owasp_asvs_5.0.0_level_2.json)               | 253        |
|                                              | [OWASP Application Security Verification Standard (ASVS) Version 5.0.0 - Level 3](https://github.com/AttackForge/TestSuites/blob/main/OWASP/ASVS/v5/owasp_asvs_5.0.0_level_3.json)               | 345        |
|                                              | [OWASP Web Application Security Top 10 2021](https://github.com/AttackForge/TestSuites/blob/main/OWASP/Top%2010/OWASP-Web-Application-Top-10-2021.json)                                          | 10         |
|                                              | [OWASP API Security Top 10 2023](https://github.com/AttackForge/TestSuites/blob/main/OWASP/Top%2010/OWASP-API-Security-Top-10-2023.json)                                                         | 10         |
| **Mobile Application**                       | [OWASP Mobile Application Security Testing Guide (MASTG) Version 2 2026.01 - Android](https://github.com/AttackForge/TestSuites/blob/main/OWASP/MASTG/v2/owasp-mastg-2.0.0-2026.01_android.json) | 96         |
|                                              | [OWASP Mobile Application Security Testing Guide (MASTG) Version 2 2026.01 - iOS](https://github.com/AttackForge/TestSuites/blob/main/OWASP/MASTG/v2/owasp-mastg-2.0.0-2026.01_ios.json)         | 88         |
|                                              | [OWASP Mobile Top 10 2024](https://github.com/AttackForge/TestSuites/blob/main/OWASP/Top%2010/OWASP-Mobile-Top-10-2024.json)                                                                     | 10         |
|                                              | [MITRE ATT\&CK Mobile Version 19.1](https://github.com/AttackForge/TestSuites/blob/main/MITRE/ATT%26CK/MOBILE/mitre_attack_mobile_19_1.json)                                                     | 124        |
| **Network Infrastructure, Hardware and IoT** | [OSSTMM Version 3 - Telecommunications Security Testing](https://github.com/AttackForge/TestSuites/blob/main/OSSTMM/v3/Chapter%2010/osstmm_telecommunications_security_testing.json)             | 54         |
|                                              | [OSSTMM Version 3 - Data Networks Security Testing](https://github.com/AttackForge/TestSuites/blob/main/OSSTMM/v3/Chapter%2011/osstmm_data_networks_security_testing.json)                       | 52         |
|                                              | [OSSTMM Version 3 - Wireless Security Testing](https://github.com/AttackForge/TestSuites/blob/main/OSSTMM/v3/Chapter%209/osstmm_wireless_security_testing.json)                                  | 53         |
| **Cloud Configuration**                      | [CIS Amazon Web Services Foundation v1.2.0](https://github.com/AttackForge/TestSuites/blob/main/AWS/CIS-Amazon-Web-Services-Foundation-v1.2.0.json)                                              | 147        |
|                                              | [CIS Microsoft Azure Foundation v1.2.0](https://github.com/AttackForge/TestSuites/blob/main/AZURE/CIS-Microsoft-Azure-Foundation-v1.2.0.json)                                                    | 81         |
|                                              | [CIS Google Cloud Platform Foundation v1.1.0](https://github.com/AttackForge/TestSuites/blob/main/GCP/CIS-Google-Cloud-Platform-Foundation-v1.1.0.json)                                          | 119        |
|                                              | [Oracle Cloud Infrastructure](https://github.com/AttackForge/TestSuites/blob/main/OCI/Oracle-Cloud-Infrastructure.json)                                                                          | 10         |
|                                              | [Kubernetes Infrastructure](https://github.com/AttackForge/TestSuites/blob/main/KUBERNETES/Kubernetes-Infrastructure.json)                                                                       | 174        |
| **CI/CD**                                    | [OWASP Top 10 CI/CD Security Risks 2023](https://github.com/AttackForge/TestSuites/blob/main/OWASP/Top%2010/OWASP-Top-10-CI-CD-Security-Risks-2023.json)                                         | 10         |
| **Low Code/No Code**                         | [OWASP Low Code/No Code Top 10 2024](https://github.com/AttackForge/TestSuites/blob/main/OWASP/Top%2010/OWASP-Low-Code-No-Code-Top-10-2024.json)                                                 | 10         |

## Import the test cases

1. Click `New -> Import Test Cases`.
2. Choose where the test cases come from:
   * **JSON:** import from any source, using the JSON template
   * **CSV:** import from any source, using the CSV template
3. Select the test cases to import.
4. Optionally, edit them before importing.
5. Watch the import's progress.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FA6LhpX0y8Xuw3McCyRkY%2FScreenshot%202026-11-10%20at%204.02.55%E2%80%AFpm.png?alt=media&amp;token=4e949797-74eb-4fa0-85f2-7ba87228e112" 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%2FD18uHl5suf9Uq8Oq9GGA%2FScreenshot%202026-11-10%20at%204.04.49%E2%80%AFpm.png?alt=media&amp;token=8f0b17f1-f07f-4689-af90-60351e304d8e" alt=""><figcaption></figcaption></figure>

## Create test suites with the API or AI MCP

You can also create and update test suites and test cases without the import screen:

| Method                       | Use it to                                                                                                                                                                                                                                                                                       |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Self-Service RESTful API** | Create and update test suites and test cases from your own systems or scripts, such as syncing a methodology you maintain elsewhere. See [Self-Service RESTful API](https://support.attackforge.com/app/automations-and-integrations/self-service-restful-api).                                 |
| **AI MCP**                   | Let AI assistants and agents find, create and update test suites and test cases, such as drafting test cases from a new standard for review, or adding an abuse case to a project. See [AI MCP and skills](https://support.attackforge.com/app/automations-and-integrations/ai-mcp-and-skills). |

You need access to the API methods or MCP tools you use.

## Recommended import mappings

When you import test cases from the methodologies AttackForge has built, we recommend setting up these test case custom fields first, so the extra data is kept. See [Custom fields and forms](https://support.attackforge.com/app/getting-started/custom-fields-and-forms).

### **MITRE ATT\&CK Enterprise, Mobile and ICS**

| #  | Key                            | Field type | Table columns (key: type)                                                      |
| -- | ------------------------------ | ---------- | ------------------------------------------------------------------------------ |
| 1  | `x_mitre_attack_spec_version`  | Input      |                                                                                |
| 2  | `x_mitre_is_subtechnique`      | Input      |                                                                                |
| 3  | `x_mitre_permissions_required` | List       |                                                                                |
| 4  | `kill_chain_phases`            | Table      | `kill_chain_name`: Input; `phase_name`: Input                                  |
| 5  | `x_mitre_platforms`            | List       |                                                                                |
| 6  | `x_mitre_data_sources`         | List       |                                                                                |
| 7  | `external_references`          | Table      | `source_name`: Input; `description`: Input; `url`: Input; `external_id`: Input |
| 8  | `mitre_domain`                 | Input      |                                                                                |
| 9  | `mitre_tactic`                 | List       |                                                                                |
| 10 | `mitigations`                  | Table      | `mitigation`: Input; `description`: Input                                      |
| 11 | `detections`                   | Table      | `data_source`: Input; `data_component`: Input; `detects`: Input                |
| 12 | `x_mitre_defense_bypassed`     | List       |                                                                                |

## Execution flows

You can give each test case an execution flow, to document:

* the steps and procedures for performing the test case
* which tools to use
* internal processes and procedures the test case needs
* links to external resources

Add execution flows when you create or update a test case. They help every tester run the test the same way, and help new testers get up to speed.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FEAM5gL6Pw3r7NWRUJjEl%2FScreenshot%202026-11-10%20at%204.07.29%E2%80%AFpm.png?alt=media&amp;token=96e96abf-7ab5-41f5-b0b8-93b0a101fe56" alt=""><figcaption></figcaption></figure>

## Abuse cases

Abuse cases are unique test cases for one project.

For example, a pentest of a reverse auction site might cover the standard OWASP ASVS test cases. The customer also wants the bidding function tested for business logic flaws, to see if it can be cheated. You can create abuse cases for this kind of functionality, for a higher level of assurance.

Only Administrators and Project Coordinators can create abuse cases.

1. On the project, go to the test cases section.
2. Click `Add -> Abuse Case`.

Abuse cases are stored and tracked for each project under `Project Abuse Cases` in the Test Suites module. You can delete an abuse case directly from the project.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FBdPO6bE9lNI9HQcT6cVL%2FScreenshot%202026-11-10%20at%204.11.15%E2%80%AFpm.png?alt=media&amp;token=57783a5e-7a4c-4f87-a704-1114b05748c0" alt=""><figcaption></figcaption></figure>

## Use AI agents with test suites

AI agents connected through MCP can work with your test suites and test cases in many different ways. See [AI agentic workflows](https://support.attackforge.com/app/automations-and-integrations/ai-agentic-workflows).

| Use                                       | What the agent does                                                                                                                                                |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Enrich existing test cases**            | Adds detail to test cases in your library, such as bootstrapping execution flows, adding tools and references, or filling in custom fields like framework mappings |
| **Drive testing from project test cases** | Works through a project's assigned test cases as its methodology, instead of exploring freely                                                                      |
| **Register test cases during testing**    | Adds new test cases to the project as it tests, to document procedures that weren't in the suite                                                                   |
| **Build bespoke test suites on demand**   | Creates a new test suite and test cases for a specific engagement, technology or standard, such as from a scoping document                                         |

### Enrich existing test cases

Execution flows drive an agent's test plan, so the more detail they have, the better. If you can't write them all by hand, ask an agent to bootstrap your initial execution flows, then review and refine them. The same approach works for proofreading test cases, and keeping them in a consistent style.

### Drive agent testing from project test cases

When an agent works from a project's test cases, the test cases define the scope, methodology and completion criteria. This keeps the agent within scope, guarantees your methodology is followed, bounds cost, and makes results comparable with human testing. See [Driving agent test procedures from AttackForge project test cases](https://support.attackforge.com/app/automations-and-integrations/ai-agentic-workflows#id-7.-driving-agent-test-procedures-from-attackforge-project-test-cases).

For each test case, the agent:

1. pulls the test case details from the project
2. studies the test case and its execution flows, to learn the requirements and boundaries
3. creates a test plan
4. tests, based on the plan
5. documents the plan and outcome on the test case
6. if it finds a vulnerability, creates it and links it to the test case, which fails the test case
7. updates the test case's status, such as tested or not applicable
8. adds any other notes to the test case

You can split test cases between agents and people by assigning them.

MCP tools used include Count Project Test Cases, Find Project Test Cases, Patch Project Test Case, Find Project Test Case Notes, Create Project Test Case Note, Patch Project Test Case Note, Find Vulnerabilities, Get Field Structure and Get Args Schema For Tool.

### Register test cases during testing

If an agent tests something that isn't in the suite, it should add it to the project as a new test case, with its execution flow, so every deviation is traceable. Agents use the Create Abuse Case MCP tool for this. See [Dynamically registering agent test procedures as project test cases](https://support.attackforge.com/app/automations-and-integrations/ai-agentic-workflows).

### Build bespoke test suites on demand

An agent can create a test suite tailored to one engagement, for example from a scoping document, an application's architecture or a newly published standard. It creates the test suite and its test cases, with codes and execution flows, ready to assign to the project. Have a person review the suite before it's used.

## Archived test suites

Click `Archived Test Suites` to see archived test suites, and restore them if you need to.

Archived test suites can't be used for projects or project requests. Historical projects that used them aren't affected, so their test cases stay intact.

## Tips

* **Start from an industry methodology**, then duplicate and tailor it rather than building from scratch.
* **Set up the recommended custom fields before importing MITRE ATT\&CK**, so none of the extra data is lost.
* **Add execution flows** so every tester runs a test the same way.
* **Use abuse cases for business logic** and anything unique to one project.
* **Edit library test cases with care.** Changes apply to every project that references them.
* **Archive, don't delete, old test suites.** Historical projects keep their test cases.

## FAQ

**What happens when I assign a test suite to a project?** Its linked test cases are assigned too, giving testers a checklist to work through.

**Can other people use my test suites?** Yes. All test suites are shared across the library.

**If I change a test case in the library, do projects change?** Yes. Changes to test cases apply to every project that references them.

**If I add a test case to a test suite, is it added to existing projects?** No. Test cases added to or deleted from a test suite don't apply to existing projects, so a Completed project can't become Not Completed.

**Who can create abuse cases?** Administrators and Project Coordinators.

**What happens to projects when I archive a test suite?** Nothing. Historical projects keep their test cases. The test suite just can't be used for new projects or project requests.

**Can I import my own methodology?** Yes, with the JSON or CSV template, the Self-Service RESTful API or AI MCP.

## Related pages

* [Test cases](https://support.attackforge.com/app/getting-started/test-cases)
* [Projects](https://support.attackforge.com/app/modules/projects)
* [Requesting a project](https://support.attackforge.com/app/getting-started/requesting-a-project)
* [Custom fields and forms](https://support.attackforge.com/app/getting-started/custom-fields-and-forms)
* [Writeups](https://support.attackforge.com/app/modules/vulnerability-library)
* [AttackForge Test Suites on GitHub](https://github.com/AttackForge/TestSuites)


---

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