Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

MITRE ATT&CK 101

A practical first pass through the Enterprise matrix, from an observed behavior to a checked detection gap.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
4 min read
Abstract matrix columns narrowing to one observed behavior

101 Guide · Beginner · 4 Min Read

  • Cyber Threat Intelligence
Level
Beginner
Length
4 min read
For
SOC, CTI and response analyst, Security leader
Track
Cyber Threat Intelligence

MITRE ATT&CK is a knowledge base that organizes observed adversary behavior into tactics, techniques, and more specific sub-techniques. This guide shows how to read an Enterprise technique page and compare it with your own evidence and logs.

MITRE ATT&CK 101: Enterprise Matrix

The Enterprise matrix arranges adversary behaviors under tactical goals. Read a column as a question about purpose, then open a technique to learn how that goal can be pursued. The columns are not a required sequence of events.

If you need a short definition first, read our MITRE ATT&CK glossary entry. This guide focuses on the analyst’s next step: using the matrix to investigate an observation. Brandefense Cyber Threat Intelligence supports the intelligence side of that work.

Pick the Enterprise domain for an enterprise or cloud question. Check the platform before carrying a technique into your environment. A column or technique appearing in the matrix does not mean it applies to every system you run.

Separate Goal, Behavior, And Observation

MITRE calls a tactical goal a tactic: the reason for an action. A technique describes how the action supports that goal, while a sub-technique names a more specific behavior. A procedure is an observed implementation by an adversary, shown in the Procedure Examples section.

For example, Valid Accounts (T1078) is a technique. Cloud Accounts (T1078.004) is its more specific sub-technique. MITRE lists several tactics for that sub-technique, so one behavior can serve different goals.

Do not label an alert with a procedure just because the alert resembles one example. First describe the observed action in ordinary words. Then choose the narrowest ATT&CK behavior that the evidence supports.

Follow A Cloud Account Example

Suppose an identity alert shows an unusual cloud sign-in. Open MITRE’s Cloud Accounts (T1078.004) page and check its parent technique, tactics, and platforms. Its listed platforms include identity providers, office suites, software services, and cloud infrastructure.

The sign-in is a lead, not proof that an adversary used a valid account. Compare the sign-in with the account’s normal activity, role, and authorized work. Confirm the action and context before mapping it to T1078.004.

MITRE also links Brute Force from the Cloud Accounts page as one possible route to account access. Our Brute Force (T1110) profile shows a different technique to investigate when the evidence is repeated login attempts. An unusual successful sign-in alone does not establish brute force.

Read The Technique Page In Order

Start with the description, ID, tactics, and platforms. The platform list tells you where MITRE says the behavior applies; it does not tell you which systems your organization monitors. Procedure Examples are reported uses, not a complete list of ways the technique can occur.

Next, read the Mitigations section as possible ways to reduce exposure. On T1078.004, MITRE lists controls such as multi-factor authentication and privileged account management. Those entries do not prove that your controls are configured or effective.

Finally, follow the page’s Detection Strategy link. The linked DET0546 strategy names analytics and their log sources, including authentication and cloud account activity. Data components and named channels are prompts to inspect your own records, not a promise that a named log is available in your tenant.

Map An Observation To Your Telemetry

Write a short evidence statement before selecting a technique: what happened, where, when, and which record shows it? For a suspicious cloud sign-in, keep the identity, application, result, and time from the original record. Avoid adding a motive that the record cannot show.

  • Check the ATT&CK ID and platform against the live technique page.
  • Find the detection strategy and identify the data component that could show the behavior.
  • Verify that your environment collects the matching event with the fields and retention you need.
  • Test the analytic against known activity, then review false alerts and gaps.

If the needed log is absent, record a telemetry gap. If the log exists but no rule has been tested, record a detection gap. This distinction gives the team a concrete next step without claiming coverage it has not demonstrated.

Describe Coverage Honestly

MITRE cautions against aiming for every matrix cell. Some behaviors will not fit your systems or threat priorities. One working analytic also does not cover every way an adversary can perform a technique.

Keep a small coverage record for each relevant behavior: the technique ID, affected platform, evidence source, detection owner, test result, and known blind spots. Recheck the ATT&CK page when you revisit the mapping because the knowledge base changes. Keep version and matrix counts out of permanent coverage claims.

Use the result to choose the next action. A missing event calls for collection work; an untested rule calls for validation; a clear observation may justify a deeper hunt. The matrix helps organize those decisions, but it cannot replace local evidence.

Frequently Asked Questions

What is the difference between a tactic and a technique?

A tactic is the adversary's goal. A technique describes an action used toward that goal. MITRE may place one technique under several tactics.

Is an ATT&CK procedure the same as a sub-technique?

No. A sub-technique is a more specific behavior category. A procedure is a reported instance of how an adversary carried out a behavior.

Does mapping an alert to T1078.004 prove cloud account compromise?

No. Verify the sign-in, account, and authorized activity first. The mapping describes a possible behavior, not an incident verdict.

Where can I find the logs needed for a detection?

Follow the technique page's Detection Strategy link and inspect its analytics, data components, and log sources. Then confirm those events and fields exist in your own environment.

Sources

  1. MITRE ATT&CK Get Started
  2. MITRE ATT&CK FAQ
  3. Enterprise matrix
  4. Cloud Accounts T1078.004
  5. Detection strategy DET0546
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →