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

# Security

Security Is Built Into Our DNA - For Peace of Mind

## Overview

Security is built into our DNA, for peace of mind. AttackForge holds penetration test findings, which are some of your most sensitive data, so we protect them with controls across people, processes and technology.

* **People:** our engineers have security backgrounds.
* **Processes:** our systems are assessed by third parties, including through penetration testing.
* **Certification:** AttackForge is SOC 2 Type 2 certified, for Security, Confidentiality and Availability.

{% hint style="info" %}
**Found a vulnerability?** Please disclose it responsibly to <security@attackforge.com>. See Report a vulnerability.
{% endhint %}

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F1Baxu2WAVpfKwv3yjSq1%2Fsecurity-at-a-glance.svg?alt=media&amp;token=7327cfb1-abfe-49ae-97c9-394cb5355d9b" alt=""><figcaption></figcaption></figure>

## Choose a deployment

|                         | Enterprise Cloud                                                          | On-Premises                                             |
| ----------------------- | ------------------------------------------------------------------------- | ------------------------------------------------------- |
| **Runs on**             | Microsoft Azure and MongoDB Cloud                                         | Your own Linux x64 server, with Docker or Podman        |
| **Infrastructure**      | Dedicated to you (single-tenant)                                          | Yours                                                   |
| **Location**            | Any Azure region you choose                                               | Wherever your server is, including air-gapped networks  |
| **Internet needed**     | Yes                                                                       | No. It installs offline, with no external dependencies. |
| **Where data is kept**  | Azure and MongoDB, in your region                                         | Docker or Podman volumes on your server                 |
| **Who can access data** | A small, closely managed group of AttackForge administrators, for support | Only you. AttackForge has no access.                    |
| **Who runs it**         | AttackForge                                                               | You: installation, operation, backups and updates       |
| **Security settings**   | Managed by AttackForge                                                    | Tune them to your own risk requirements                 |

## Why it matters

| Benefit                     | What it means                                                      |
| --------------------------- | ------------------------------------------------------------------ |
| **Your data stays yours**   | We don't share customer data with third parties                    |
| **Choose where data lives** | Any Azure region, or your own servers                              |
| **Independent assurance**   | SOC 2 Type 2, and third-party penetration testing                  |
| **Strong account security** | Mandatory multi-factor authentication, and bcrypt password hashing |
| **Encrypted throughout**    | Data is encrypted in transit and at rest, including backups        |

## Who uses it

| Role                            | Typical use                                           |
| ------------------------------- | ----------------------------------------------------- |
| **Security and risk teams**     | Assess AttackForge as a vendor                        |
| **Procurement and legal**       | Answer security questionnaires and contract questions |
| **IT and infrastructure teams** | Plan a cloud or on-premises deployment                |
| **Security researchers**        | Report a vulnerability                                |

## Where is my data stored?

### Enterprise Cloud

We store, analyse and back up your data with Microsoft Azure and MongoDB services, so it benefits from their security standards. Your servers run in the Azure region you choose.

Among others, these services hold:

| Service             | Standards                                                                 |
| ------------------- | ------------------------------------------------------------------------- |
| **Microsoft Azure** | ISO 27001, 27017, 27018 · SOC 1, 2 and 3 · FIPS 140-2 · GDPR              |
| **MongoDB**         | ISO 27001 · SOC 2 Type II · GDPR · HIPAA · PCI DSS · EU-US Privacy Shield |

### On-Premises

All your data stays on your own Linux server, in Docker or Podman volumes.

## Who has access to my data?

### Enterprise Cloud

* We don't share your data with third parties.
* Only a small, closely managed group of AttackForge administrators has administrative access, to provide support.
* Access to production follows the principle of least privilege.

### On-Premises

* AttackForge has no access to your data.
* The solution runs as three containers: a NGINX reverse proxy, a Web Application Server and a Database Server.
* All data is stored in Docker volumes on your server.
* You control installation, operation and backups.
* We publish regular updates on an online portal. You download and apply them when you choose.

## How is my data protected?

This section describes Enterprise Cloud. On-premises, you control your own network, system and storage security, and the application's account security works the same way.

| Area                 | Protections                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Network security** | All traffic is encrypted with TLS v1.2+ · Strong TLS cipher suites are enforced · Systems are firewalled to a minimal number of access points                                                                                                                                                                                                                                                                                                                                                    |
| **Account security** | Multi-factor authentication (TOTP) is mandatory on all application and administrative interfaces · A strong password policy is enforced · Passwords are hashed and salted · Role-based access controls at user and project level · Account access and actions are logged, tracked and audited · Anti-automation controls block brute-force login attempts · Session monitoring and management prevent authenticated abuse · Email notifications for events such as a login from a new IP address |
| **System security**  | Azure and MongoDB manage, patch and maintain the operating systems · Unnecessary users, services and components are disabled · Systems are monitored continuously                                                                                                                                                                                                                                                                                                                                |
| **Data storage**     | Data is stored on virtualised servers on Azure and MongoDB · Data is encrypted in transit and at rest · Database backups are always encrypted, in storage and in transit · Pentest reports are generated in memory when you request them, and are never stored                                                                                                                                                                                                                                   |

## Integrations and AI

Access to every integration is off by default, including for administrators. An administrator grants each user, or group, only what they need.

| Integration                                                                                                               | How it's secured                                                                                                                                                                                 |
| ------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [**Self-Service RESTful API**](https://support.attackforge.com/app/automations-and-integrations/self-service-restful-api) | Each API method is granted separately. Each user has their own API key, which only they can create, view or rotate. Run-As requests can't add permissions.                                       |
| [**Self-Service Events API**](https://support.attackforge.com/app/automations-and-integrations/self-service-events-api)   | Each event is granted separately, and needs the user's own API key                                                                                                                               |
| [**AI MCP**](https://support.attackforge.com/app/automations-and-integrations/ai-mcp-and-skills)                          | Turned on by an administrator. Each tool is granted separately. Each user signs in with OAuth 2.1 and approves their own AI assistant. AttackForge data isn't sent to AI providers for training. |
| [**Local MCP**](https://support.attackforge.com/app/automations-and-integrations/ai-mcp-and-skills)                       | Runs on the user's own computer with their API key, and can use a local AI model so data never leaves it                                                                                         |

## Report a vulnerability

If you find a vulnerability in any AttackForge system, please disclose it responsibly to <security@attackforge.com>.

Include:

* what you found, and where
* steps to reproduce it
* the impact you think it has

## Tips

* **Choose your region to suit data residency rules.** Enterprise Cloud runs in any Azure region.
* **Need no internet at all?** Use On-Premises. It installs and runs offline, including in air-gapped networks.
* **Grant the least access you can.** Use roles, project access, and group-based access to APIs, events and MCP tools.
* **Use groups for access.** They're easier to review than access granted user by user.
* **Review access regularly,** and remove it promptly when people leave.
* **Rotate API keys** on a schedule, and straight away if one may have been exposed.
* **On-Premises, apply updates promptly,** and back up your Docker volumes.
* **For a vendor assessment, ask for the SOC 2 Type 2 report.**

## FAQ

**Is AttackForge SOC 2 certified?** Yes. AttackForge holds SOC 2 Type 2 for Security, Confidentiality and Availability.

**Where is my data stored?** In Enterprise Cloud, in the Azure region you choose. On-Premises, on your own server.

**Is Enterprise Cloud shared with other customers?** No. It runs on infrastructure dedicated to you.

**Can AttackForge see my data?** In Enterprise Cloud, only a small, closely managed group of administrators can, to provide support. On-Premises, AttackForge has no access.

**Is multi-factor authentication required?** Yes. TOTP multi-factor authentication is mandatory on all application and administrative interfaces in Enterprise Cloud.

**Are reports stored?** No. Reports are generated in memory when you request them, and aren't stored.

**Is my data used to train AI models?** No. AttackForge data isn't sent to AI providers for training. If you connect your own AI assistant through MCP, check that provider's data settings.

**Does On-Premises need internet access?** No. It installs and runs offline, with no external dependencies.

**How do I report a vulnerability?** Email <security@attackforge.com>.

## Related pages

* [Self-Service RESTful API](https://support.attackforge.com/app/automations-and-integrations/self-service-restful-api): API keys and access to API methods.
* [Self-Service Events API](https://support.attackforge.com/app/automations-and-integrations/self-service-events-api): access to events.
* [AI MCP and Skills](https://support.attackforge.com/app/automations-and-integrations/ai-mcp-and-skills): how AI assistants connect securely.
* [Administration](https://support.attackforge.com/app/modules/administration): users, groups, roles and security settings.
* [Raising support tickets](https://support.attackforge.com/enterprise/raising-support-tickets): report a security incident as Priority 1.
* [Microsoft Azure compliance offerings](https://learn.microsoft.com/en-us/azure/compliance/): Azure's current certifications.
* [MongoDB Trust Center](https://www.mongodb.com/products/platform/trust): MongoDB's current certifications.


---

# 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/other/security.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.
