> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/risk-management/alerts/tactical-alert-matrix.md).

# Tactical alert matrix

DoControl alerts are based on the MITRE ATT\&CK adversary model and framework, which describes an adversary’s actions to compromise and operate within an enterprise network.

In the Alerts page, each DoControl alert is mapped to a specific MITRE ATT\&CK tactic and technique:

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F98PKKuUlnJAjlvzGl3Iz%2FMITRE%20alert%20info.png?alt=media&amp;token=4f4ac443-87b8-431f-9663-975fd9951564" alt=""><figcaption><p>Clicking the tactic and technique links opens the relevant MITRE ATT&#x26;CK documentation</p></figcaption></figure>

## About MITRE ATT\&CK

MITRE ATT\&CK (Adversarial Tactics, Techniques, and Common Knowledge) is based on real-world observations, and includes a comprehensive matrix of tactics and techniques that help your organization to classify cyberattacks and assess your risk. The matrix expands the knowledge of network defenders and prioritizes network defense by detailing the tactics, techniques, and procedures (TTPs) cyber threats use to gain access and execute their objectives when operating inside a network.

The aim of ATT\&CK is to break down and classify attacks clearly and consistently, making it easier to compare them and discover how the attacker exploited networks and endpoints in a successful compromise. With this knowledge at hand, your organization can identify the weak link in your chain of defense, and prioritize security issues based on risk.

{% hint style="info" %}
For more information, see the MITRE ATT\&CK [SaaS matrix](https://attack.mitre.org/matrices/enterprise/cloud/saas/) and[ FAQs](https://attack.mitre.org/resources/faq/).
{% endhint %}

Following are the tactics and techniques representing the MITRE ATT\&CK matrix for Enterprise covering cloud-based techniques for the SaaS platform:

* MITRE attack tactics that are covered by DoControl alerts are highlighted in **dark gray**.
* MITRE attack techniques that are covered by DoControl alerts are highlighted in <mark style="color:purple;">**purple**</mark>.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FIzoCVRzPeCvvGCmcAeyQ%2FMITRE%20matrix%20by%20DoControl.svg?alt=media&amp;token=737080b5-07dc-4830-b734-8d4ec981e4a2" alt=""><figcaption><p>MITRE ATT&#x26;CK SaaS matrix covered by DoControl</p></figcaption></figure>

## DoControl alert coverage

DoControl's alert types address a variety of MITRE ATT\&CK tactics and attack techniques. The following infographic maps DoControl alert types to the relevant SaaS-based MITRE ATT\&CK categories.

These alerts help your organization to mitigate the risk and exposure associated with each potential attack.&#x20;

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FuJY2hI4YnpeHarplVjpS%2FDoControl%20alerts%20for%20MITRE.svg?alt=media&amp;token=df387c4e-e80a-4dcb-ad7c-11670ce82b3d" alt=""><figcaption></figcaption></figure>

A **MITRE tactic** represents why an adversary performs an action, or the adversary's tactical goal. For example, an adversary wants to get credential access.

A **MITRE attack technique** represents how an adversary achieves a tactical goal by performing an action. For example, an adversary might dump credentials to achieve credential access.&#x20;

The DoControl alert-MITRE ATT\&CK matrix below provides links with more information about each  tactic and attack technique:

<table><thead><tr><th width="172.33333333333331">MITRE tactic</th><th width="170">Attack technique</th><th>DoControl alert</th></tr></thead><tbody><tr><td><a href="https://attack.mitre.org/tactics/TA0001/">Initial access</a></td><td><a href="https://attack.mitre.org/techniques/T1078">Valid accounts</a></td><td><ul><li>MFA disabled for a user (DC82)</li><li>MFA disabled for a team (DC83)</li></ul></td></tr><tr><td><a href="https://attack.mitre.org/tactics/TA0043/">Reconnaissance</a></td><td><a href="https://attack.mitre.org/techniques/T1589/001/">Gather Victim Identity Information: Credentials</a></td><td><ul><li>Password strength requirements changed for team (DC84)</li></ul></td></tr><tr><td><a href="https://attack.mitre.org/tactics/TA0003/">Persistance</a></td><td><a href="https://attack.mitre.org/techniques/T1078/">Valid accounts</a></td><td><ul><li>Possible former employee accessed assets (DC30)</li></ul></td></tr><tr><td><a href="https://attack.mitre.org/tactics/TA0006/">Credential access</a></td><td><a href="https://attack.mitre.org/techniques/T1552/">Unsecured credentials</a></td><td><ul><li>Encryption keys uploaded to public channels (DC80)</li><li>Public sharing of encryption keys (DC81)</li></ul></td></tr><tr><td><a href="https://attack.mitre.org/tactics/TA0009/">Collection</a></td><td><a href="https://attack.mitre.org/techniques/T1213/">Data from information repositories</a></td><td><ul><li>External sharing of sensitive files (DC3)</li><li>Shared with private email (DC7)</li><li>External user shared with 4th party (DC10)</li><li>Extensive public burst sharing (DC5)</li><li>Public sharing of sensitive files (DC6)</li><li>External user publicly shared (DC11)</li><li>Shared with malicious domain (DC100)</li><li>Publicly shared by malicious domain (DC102)</li><li>Unprotected sensitive cloud recording is public (DC105)</li></ul></td></tr><tr><td><a href="https://attack.mitre.org/tactics/TA0010/">Exfiltration</a></td><td><a href="https://attack.mitre.org/techniques/T1537/">Transfer data to cloud account</a></td><td><ul><li>Shared with personal email (DC8)</li><li>Extensive file download by external user (DC14)</li><li>File download by about-to-leave employee (DC33)</li><li>Shared by malicious domain (DC101)</li></ul></td></tr></tbody></table>

{% hint style="info" %}
For more information about DoControl alerts, see the DoControl Alert Specifications in **DoControl > Help**.
{% endhint %}


---

# 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://docs.docontrol.io/docontrol-user-guide/risk-management/alerts/tactical-alert-matrix.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.
