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

# Projects

## Overview

A project is where a single piece of security testing lives, from setup through to the final report. Everything in AttackForge is organised around projects. Each project holds its **scope** (the assets being tested) and its **findings** (the vulnerabilities discovered), and every vulnerability is linked to the assets it affects.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FzessLjNhCvDXE5WOpmUC%2Fimage.png?alt=media&amp;token=f9d6d050-4eb0-4557-8536-86626705d9c8" alt=""><figcaption></figcaption></figure>

Projects can be any kind of security testing, including, but not limited to:

| Project type                                    | What it covers                                                                                                                                                                                                            |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Red Team and Purple Team Assessments**        | Simulated real-world attacks against people, processes and technology. Purple team assessments work with defenders to improve detection and response.                                                                     |
| **Web Application Penetration Test**            | Testing a web application for vulnerabilities such as injection, broken access control and session flaws                                                                                                                  |
| **Web Services / API Penetration Test**         | Testing APIs and web services for authentication, authorisation and data exposure issues                                                                                                                                  |
| **Mobile Application Penetration Test**         | Testing iOS and Android apps, including how they store data and talk to back-end services                                                                                                                                 |
| **Network and Infrastructure Penetration Test** | Testing internal and external networks, servers and devices for exploitable weaknesses                                                                                                                                    |
| **Wireless Network Assessment**                 | Testing wireless networks for weak encryption, rogue access points and poor segmentation                                                                                                                                  |
| **Source Code Review**                          | Reviewing application source code to find security flaws before or alongside testing                                                                                                                                      |
| **Configuration Audit**                         | Checking systems, cloud services and devices against secure configuration baselines                                                                                                                                       |
| **PCI-DSS Assessment**                          | Testing to support compliance with the Payment Card Industry Data Security Standard                                                                                                                                       |
| **SCADA Assessment**                            | Testing industrial control and operational technology systems                                                                                                                                                             |
| **OSINT Assessment**                            | Gathering open-source intelligence to show what attackers can learn about your organisation                                                                                                                               |
| **Physical Security Audit**                     | Testing physical controls, such as building access, locks and staff procedures                                                                                                                                            |
| **Agentic Testing**                             | Testing carried out by AI agents, which record their progress, findings and evidence in AttackForge through its APIs and MCP tools. See [AI agentic workflows](https://support.attackforge.com/app/ai-agentic-workflows). |
| **Continuous Testing**                          | Ongoing testing of an application or environment, rather than a single point-in-time test, so new vulnerabilities are found as changes are made                                                                           |
| **Bug Bounty**                                  | A programme that rewards external security researchers for finding and reporting valid vulnerabilities in an agreed scope                                                                                                 |
| **Vulnerability Disclosure Program (VDP)**      | A public way for anyone to report vulnerabilities they find in your systems, usually without a reward, so you can triage and fix them                                                                                     |
| **Cloud Security Assessments**                  | Testing and reviewing cloud environments, such as AWS, Azure and Google Cloud, for misconfigurations, excessive permissions and exposed services                                                                          |
| **Vulnerability Scanning**                      | Automated scanning of networks, hosts and applications for known vulnerabilities, with results imported into AttackForge so they're tracked alongside manual findings                                                     |
| **DevSecOps**                                   | Security testing built into the software delivery pipeline, such as SAST, DAST and dependency scanning, with findings sent to AttackForge through its APIs                                                                |

The Projects module is where you find, open and manage your projects, see what belongs to them, plan your team's work, and handle requests for new projects.

Administrators, Project Coordinators and delegated users create projects. Everyone else requests them, and an approved request creates the project automatically. Work on one project, or use the details view to see vulnerabilities, test cases and retests across many. When a project is finished, archive it. You can restore it at any time, or destroy it permanently.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FM37Zi8ltTCBtGVX4K6Q2%2Fprojects-at-a-glance.svg?alt=media&amp;token=8bd45769-1722-4490-8328-911f35644620" alt=""><figcaption></figcaption></figure>

## Why it matters

* **Every test has a home.** Scope, findings, test cases, retests and reports for each engagement are kept together.
* **See across projects, not just within them.** The details view lists vulnerabilities, test cases and retest rounds across many projects in one table.
* **Plan with real data.** User Projects shows what each person is working on, so you can balance workloads.
* **A controlled way to start new work.** Project requests let anyone ask for testing, while only authorised people create projects.

## Who uses it

| Who                                 | To                                                                         |
| ----------------------------------- | -------------------------------------------------------------------------- |
| **Administrators**                  | Create, archive, restore and destroy projects, and review project requests |
| **Project Coordinators**            | Create projects, review project requests, and plan their team's work       |
| **Testers**                         | Find the projects they're working on and record their progress             |
| **Clients and stakeholders**        | Follow the projects they've been invited to, and request new testing       |
| **Security and programme managers** | See vulnerabilities, test cases and retests across many projects           |

Only Administrators, Project Coordinators and delegated users can create a new project. Everyone else can request one. See [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access).

## My Projects

The Projects module is where you can see all of your projects, including the ones you created and the ones other users have invited you to.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FNapMPkGIui5GeRE6Ghge%2FScreenshot%202026-11-10%20at%2010.34.00%E2%80%AFam.png?alt=media&amp;token=decf3d07-a5f5-4341-b3ae-dd556c2aa234" alt=""><figcaption></figcaption></figure>

### Create or request a project

* **If you can create projects** (Administrators, Project Coordinators and delegated users), select `New -> Project` from the page menu.
* **Everyone else** can request a new project by selecting `New -> Project Request`.

See [Getting started](https://support.attackforge.com/app/getting-started) for more on how to [create a new project](https://support.attackforge.com/app/getting-started/creating-and-managing-projects) or [request a new project](https://support.attackforge.com/app/getting-started/requesting-a-project).

### Open a project

Click any project to drill down into the project view. From there, you can view testing progress, view vulnerabilities, download reports and more.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FHmdRp4FQO61lZdQ3pJgi%2FScreenshot%202026-11-10%20at%2010.34.53%E2%80%AFam.png?alt=media&amp;token=7631cf9a-f73e-4849-9332-c1bbd0de4b66" alt=""><figcaption></figcaption></figure>

### See related data across your projects

Your project lists open into a details view. It lets you see what belongs to many projects at once, such as every open vulnerability across one client's projects, without opening each one.

* **Select one or more projects**, and the pane beside them lists their vulnerabilities, test cases or retest rounds across every project you selected, in one table.
* **Select nothing**, and you see the related data for every project your current filters match.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FalkLSvXAaew7Y3cTolQi%2FScreenshot%202026-11-10%20at%2010.35.30%E2%80%AFam.png?alt=media&amp;token=311b06a4-301a-4547-9856-0f1c3208cd08" alt=""><figcaption></figcaption></figure>

#### Open the details view

1. Click the handle on the left edge of any projects table.
2. The table folds into a compact list that keeps your filters, search and sorting, so you can keep narrowing projects while you browse what belongs to them.
3. Choose a tab to see related data.

#### What each tab shows

| Tab                      | What it shows                                                                                                                         |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
| **Vulnerabilities**      | Every vulnerability across the selected projects, with the same filters, columns, saved views and export you have on a single project |
| **Test Cases**           | Test cases across projects, with status, outcome, assignee, assigned assets and your custom fields                                    |
| **Retesting**            | Every retest round across the selected projects, with its project, window, scope and retested vulnerabilities                         |
| **Compact project list** | Filter, search, sort and page through projects without leaving the details view                                                       |

Each tab remembers its own columns and layout, so `Groups`, `Portfolios`, `Streams` and your own project lists can each be set up the way that suits them.

The details view is available on `My Projects`, `User Projects`, `Archived Projects`, and the projects tab of `Groups`, `Portfolios` and `Streams`.

## User Projects

Project Cooridnators and Adminstrators can view projects on behalf of another user. This helps with resource management and team planning, such as checking who's free to take on a new test, or what someone is working on while they're away.

1. Select `User Projects` from the menu.
2. Select a user.
3. To narrow the results, search for projects where the user is assigned a particular role.
4. Toggle between a list view and a calendar view. The calendar view shows when each project is scheduled.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FUh8DjQ1wAm3IqZATK4N2%2FScreenshot%202026-11-10%20at%2010.38.44%E2%80%AFam.png?alt=media&amp;token=74bb2756-5b5f-4a5c-9a3f-5c40bfbb6bbd" 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%2FZHdIvfRfIgrTUI1vb7cN%2FScreenshot%202026-11-10%20at%2010.39.47%E2%80%AFam.png?alt=media&amp;token=effbb419-9e7e-48e5-9972-7e83a115dad4" alt=""><figcaption></figcaption></figure>

## Archived Projects

Archived Projects lists all projects that have been archived. Archiving keeps a finished or cancelled project's history, without it showing up in everyday lists and numbers.

* Archived projects are hidden, and only Administrators can access them.
* The results from archived projects, such as vulnerabilities, aren't included in Analytics or other sections of AttackForge.

### Restore a project

You can restore an archived project at any time. Select `Restore Project` from the actions menu.

### Destroy a project

You can also delete a project entirely. Select `Destroy Project Data` from the actions menu.

{% hint style="info" %}
**Warning:** once a project has been destroyed, there's no way to recover it or its data.
{% endhint %}

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FlzM69qRUNjISKd7uD3EL%2FScreenshot%202026-11-10%20at%2010.41.27%E2%80%AFam.png?alt=media&amp;token=e4d01d96-4214-4379-bf82-a2cc6b3aba1f" alt=""><figcaption></figcaption></figure>

## Pending Requests

Pending Requests lists all project requests that are waiting to be reviewed and actioned. Requests give everyone a single way to ask for testing, and give the people who approve testing one place to review it.

### What happens when someone requests a project

1. The authorised users are notified when a new project request is submitted, and can start the review.
2. The person who submitted it is notified by email that their request is pending review.
3. The submitter can change their request while it's pending.
4. Authorised users can `Approve` or `Reject` the request.
5. If it's approved, the project is created automatically, and the person who requested it is invited to the project. They're notified by email that their request was approved.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FzLQYdEx99UhsDdCxDZwK%2FScreenshot%202026-11-10%20at%2010.42.24%E2%80%AFam.png?alt=media&amp;token=453ed8ba-78cf-4449-bc39-db760c857790" alt=""><figcaption></figcaption></figure>

See [Requesting a project](https://support.attackforge.com/app/getting-started/requesting-a-project) for more on project requests.

## Actioned Requests

All users can see the history of their project requests in `Actioned Requests`. Click a request to drill down into the information that was submitted and reviewed.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FQGgHxJ9VR1NB2UQdL6Rh%2FScreenshot%202026-11-10%20at%2010.42.24%E2%80%AFam.png?alt=media&amp;token=1d67769f-ae9e-4840-8126-fd188c037ecc" alt=""><figcaption></figcaption></figure>

## Tips

* **Use the details view for cross-project questions**, such as every open Critical vulnerability for one client, instead of opening each project.
* **Filter projects first, then select nothing** to see related data for every project that matches.
* **Set up each list once.** Each tab remembers its columns and layout for each list.
* **Use User Projects before assigning new work**, to see who's already booked.
* **Archive, don't destroy, when in doubt.** Archived projects can be restored. Destroyed projects can't.
* **Point people to project requests.** It gives you one place to review new testing, and keeps everyone informed by email.

## FAQ

**Who can create a project?** Administrators, Project Coordinators and delegated users. Everyone else can request one with `New -> Project Request`.

**Which projects appear in My Projects?** The ones you created, and the ones other users have invited you to.

**Can I see vulnerabilities across several projects at once?** Yes. Open the details view, select the projects, and choose the Vulnerabilities tab. Select nothing to see every project your filters match.

**Do archived projects count in Analytics?** No. Results from archived projects, such as vulnerabilities, aren't included in Analytics or other sections of AttackForge.

**Who can see archived projects?** Only Administrators.

**Can I get back a destroyed project?** No. Once a project has been destroyed, there's no way to recover it or its data.

**Can I change a project request after submitting it?** Yes, while it's pending.

**What happens when a request is approved?** The project is created automatically, the person who requested it is invited to it, and they're notified by email.

## Related pages

* [Creating and managing projects](https://support.attackforge.com/app/getting-started/creating-and-managing-projects)
* [Requesting a project](https://support.attackforge.com/app/getting-started/requesting-a-project)
* [Vulnerabilities](https://support.attackforge.com/app/modules/vulnerabilities)
* [Retesting](https://support.attackforge.com/app/getting-started/retesting)
* [Reporting](https://support.attackforge.com/app/getting-started/reporting)
* [Analytics](https://support.attackforge.com/app/modules/analytics)
* [Groups](https://support.attackforge.com/app/modules/groups)
* [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/projects.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.
