Skip to content
Tutorials Center
My learning

Topics

Lesson 6 of 80 ยท Security Foundations

The Attack Lifecycle and MITRE ATT&CK

See how attacks unfold in stages, learn the Cyber Kill Chain and MITRE ATT&CK tactics, and map detections to techniques with a Python lookup table.

Attacks are rarely a single event. A break-in usually unfolds over days or weeks: someone researches the target, gets a first foothold, explores, gains more power, moves around, takes what they came for and tries to hide. That sequence is the attack lifecycle. Knowing it changes how you defend, because every stage is another chance to notice and stop the intruder, and an attacker has to succeed at all of them.

This lesson covers two widely used models of the lifecycle: the Lockheed Martin Cyber Kill Chain and the MITRE ATT&CK knowledge base. You will learn the vocabulary of tactics and techniques, see how defenders use them to describe detections and find coverage gaps, and build a small lookup table in Python. Everything here is about recognizing behavior. It is a defender's map, not an instruction manual. It follows Threat Modeling with STRIDE.

The Cyber Kill Chain

The kill chain, borrowed from military language, describes seven stages of an intrusion. Its core insight is that breaking the chain at any link stops the attack.

flowchart LR
    R["1. Reconnaissance<br/>learn about the target"] --> W["2. Weaponization<br/>prepare the payload"]
    W --> D["3. Delivery<br/>send it, e.g. phishing"]
    D --> E["4. Exploitation<br/>trigger a weakness"]
    E --> I["5. Installation<br/>gain persistence"]
    I --> C["6. Command and control<br/>remote channel"]
    C --> A["7. Actions on objectives<br/>steal, encrypt, destroy"]

Seven stages from research to goal. Defenders try to stop the attacker as early as possible, because early is cheap and late is a crisis.

A defender can map controls to each link:

Stage Example defensive controls
Reconnaissance Limit public information, monitor for scanning
Weaponization Hard to see directly; threat intelligence helps
Delivery Email filtering, web filtering, user training
Exploitation Patching, input validation, memory-safe code
Installation Endpoint protection, application allow-listing
Command and control Egress filtering, DNS monitoring
Actions on objectives Encryption, data loss prevention, backups, alerts on bulk access

The kill chain is easy to remember, but it assumes a fairly linear, malware-centric intrusion. Real attacks loop (an attacker may return to reconnaissance inside your network), and many skip steps. That is why the more detailed ATT&CK model was created.

MITRE ATT&CK in plain terms

MITRE ATT&CK (Adversarial Tactics, Techniques, and Common Knowledge) is a public, community-maintained catalog of how real attackers behave, gathered from real incident reports. It is organized in three levels:

  • Tactic: the attacker's goal at a moment ("get initial access", "move laterally"). Think of it as the "why".
  • Technique: how they achieve the goal ("phishing", "valid accounts"). Think of it as the "how". Many techniques have sub-techniques with more detail.
  • Procedure: the specific way a particular group or tool carries out a technique.

Techniques have IDs such as T1566 (Phishing) and T1566.001 (spearphishing attachment). The Enterprise matrix is organized into fourteen tactics, roughly in the order they occur:

  1. Reconnaissance
  2. Resource Development
  3. Initial Access
  4. Execution
  5. Persistence
  6. Privilege Escalation
  7. Defense Evasion
  8. Credential Access
  9. Discovery
  10. Lateral Movement
  11. Collection
  12. Command and Control
  13. Exfiltration
  14. Impact

Treat the matrix as a map of attacker behavior, not a checklist of things every attacker does. A given intrusion touches only some cells, in no fixed order. ATT&CK is updated regularly, so always use the current version when you do real work; the IDs below are well-known, stable examples.

ATT&CK describes behavior at a level that is useful for detection and defense. It deliberately does not include step-by-step instructions for performing attacks. That is also how this course uses it.

What defenders do with it

ATT&CK gives teams a shared language. Instead of "the weird thing on the server", an analyst can write "valid accounts used outside business hours (T1078), followed by data staged for exfiltration". Typical uses:

  • Describing incidents: tag what you saw in a report so others understand quickly.
  • Mapping detections: record which techniques each alert rule is meant to catch.
  • Finding gaps: list techniques relevant to your threat actors, then see which have no detection.
  • Planning tests: purple teams pick a technique, simulate it safely, and check whether the alert fires.
  • Threat intelligence: compare which techniques a known group uses with your coverage.
flowchart TD
    T["Threat actors that matter to us"] --> TECH["Techniques they use"]
    TECH --> COV{"Do we have a detection?"}
    COV -- yes --> TEST["Test that it fires"]
    COV -- no --> GAP["Coverage gap: build a detection"]
    GAP --> TEST
    TEST --> TECH

Detection engineering is a loop: choose techniques, check coverage, close gaps, test again.

Techniques and the logs that reveal them

The art of detection is knowing which evidence a behavior leaves behind. The table below uses a handful of widely documented techniques and the kind of data a defender would examine. This is a small selection, not the whole matrix.

ID Technique Tactic Where it may show up
T1566 Phishing Initial Access Mail gateway logs, user reports
T1078 Valid Accounts Initial Access / Persistence Authentication logs: odd times, places
T1110 Brute Force Credential Access Many failed logins in a short time
T1059 Command and Scripting Interpreter Execution Process creation logs
T1021 Remote Services Lateral Movement Logins between internal hosts
T1041 Exfiltration Over C2 Channel Exfiltration Unusual outbound data volume
T1486 Data Encrypted for Impact Impact Mass file renames and writes
Python A technique lookup and a coverage report

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The gap list is a to-do list: execution, lateral movement and ransomware-style impact have no detection yet. Coverage is not the same as quality, though. A rule that exists but never fires correctly is worse than a known gap because it gives false comfort, which is why the loop above ends with test that it fires.

Grouping by tactic

Because tactics are ordered, you can also ask "how far along the chain are our detections?" Early detections give more time to respond. Late ones only tell you the damage is under way.

Python How early would we notice?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Eleven of fourteen tactics are unwatched in this toy setup. A real program would not try to detect everything equally. It would prioritize the techniques used against organizations like yours and invest in chokepoints that most attacks must pass through, such as credential use and outbound traffic.

The attack lifecycle and the rest of this course

You will meet the stages again in later chapters:

Next you enter the cryptography chapter, which supplies the building blocks that protect data at rest and in transit.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the main defensive insight of the Cyber Kill Chain?

    An intrusion needs every stage to succeed, so a control at any link can stop it. Earlier stops are usually cheaper and safer.
  2. 2. In MITRE ATT&CK, what is the difference between a tactic and a technique?

    Tactics are goals such as Initial Access or Exfiltration. Techniques, like Phishing or Valid Accounts, are the ways of reaching those goals.
  3. 3. A team lists the techniques its likely attackers use and finds three with no alert rules. What are these called?

    A technique that matters to you but has no detection is a coverage gap and a candidate for new detection work.
  4. 4. Why should detections be tested after they are written?

    An untested rule may silently fail. Simulating the technique in a safe way, often in a purple-team exercise, proves the detection works.

Summary

  • Attacks unfold in stages. The Cyber Kill Chain has seven; breaking any link stops the intrusion.
  • MITRE ATT&CK is a public catalog of real attacker behavior organized into tactics (goals), techniques (methods) and procedures (specific implementations).
  • Teams use ATT&CK as a shared language to describe incidents, map detections, find gaps and plan tests.
  • Earlier detection gives more time to respond; prioritize techniques relevant to the threats you actually face.
  • Always verify that detections fire. Coverage on paper is not protection.

Next: Cryptography in Plain Language