Tactics, Techniques and Procedures: Read the Evidence Carefully
Tactics describe an adversary's tactical objective, techniques describe the method and procedures describe a particular implementation reported in an event or campaign. Defenders use these levels to organise evidence and ask useful investigation questions. They do not reveal a person's thoughts or identify an actor automatically. Keep the source narrative, platform, uncertainty and framework version with a mapping.
Topic: AI in Cybersecurity in Cybersecurity & Ethical Hacking · Explainer
Quick answer: Tactics describe an adversary's tactical objective, techniques describe the method and procedures describe a particular implementation reported in an event or campaign. Defenders use these levels to organise evidence and ask useful investigation questions. They do not reveal a person's thoughts or identify an actor automatically. Keep the source narrative, platform, uncertainty and framework version with a mapping. An observed administrative action may also have a legitimate explanation, so separate the behaviour you can describe from claims about malicious purpose, attribution or complete detection coverage.
Key takeaways
- Keep tactical objective, method and reported implementation at different levels.
- Map the evidence actually described instead of guessing missing steps.
- Check platform-specific sub-techniques and current definitions.
- Separate legitimate administrative behaviour from adversarial use.
- Retain source and version context without treating shared techniques as attribution.
Table of Contents
- What does a tactic mean in a defensive analysis?
- How is a technique different from a procedure?
- How can a scheduled-task example be mapped without overclaiming?
- Why does legitimate administration belong in the comparison?
- Can shared TTPs identify a specific threat group?
- Why should a TTP mapping retain its version and source?
- What should the finished defensive mapping help someone do?
- References
What does a tactic mean in a defensive analysis?
The MITRE Enterprise tactics page defines a tactic as the tactical reason for an action. This is an intermediate operational objective, such as maintaining a foothold, rather than a complete explanation of an adversary's personal or financial motive. Keep those different meanings of why separate.
A source may clearly describe a behaviour while leaving its objective unresolved. Record that limit instead of assigning a dramatic goal merely because one appears in a matrix. A mapping should help another analyst understand the evidence. It should not add an unobserved theft, disruption or intent to a record that says only that an administrative mechanism was used.
How is a technique different from a procedure?
The Enterprise technique catalogue describes methods used to achieve tactical goals. A sub-technique can provide a more specific implementation category. A procedure describes how a particular reported actor or event used that method, including the details the source actually supplies. Product names and business motives do not automatically fit those levels.
For example, a scheduled-task mechanism can be described at a general level, while a report may specify a platform and the condition under which a task ran. Use the more specific category only when the evidence supports it. Preserve the narrative beside the identifier so a reviewer can see why that mapping was chosen and which details remain unknown.
| Level | Question it answers | Mistake to avoid |
|---|---|---|
| Tactic | Which tactical objective is supported? | Replacing evidence with a guessed business motive |
| Technique or sub-technique | Which method and platform are described? | Selecting specificity absent from the source |
| Procedure | How did this reported implementation use the method? | Treating a tool name as the whole procedure |
| Attribution | Who is reliably associated with the event? | Inferring identity from one shared method |
How can a scheduled-task example be mapped without overclaiming?
In a fictional training report, the examiner records a Windows scheduled task running a supplied component at logon. The report's supporting narrative states that the task was used to regain execution after sign-in. A trainee labels the activity data exfiltration because the component has a suspicious name. Nothing in the supplied report describes a transfer.
The Scheduled Task sub-technique page describes adversarial use of Windows Task Scheduler, including recurring execution. The trainee can map that described method and the supported persistence-related purpose, while leaving exfiltration unclaimed. The report still needs its underlying evidence and authority. This is a paper classification exercise, not instructions to create a task or run a component.
| Supplied detail | Supported treatment | Unresolved or unsupported claim |
|---|---|---|
| Windows scheduled task | Consider the platform-specific scheduled-task method | Other platforms use the same exact mechanism |
| Runs at logon for recurring access | Record the source-supported tactical purpose | Every possible purpose of the component is known |
| Suspicious component name | A lead to validate against the artifact | The name proves data theft |
| No transfer evidence supplied | Do not add an exfiltration finding | No transfer could ever have occurred |
Why does legitimate administration belong in the comparison?
Scheduling is also useful for ordinary maintenance. The existence of a task, interpreter or remote-administration technology does not settle whether its use was authorised. Compare the relevant owner, account, approved purpose and activity context. The same broad mechanism can occur in both benign and adversarial work.
For the classroom report, add a separately supplied approved backup task as a benign comparison. Ask which facts distinguish it from the reported recurring-access case. Students should identify the relevant approval and behavioural evidence, rather than treat every scheduled action as an incident. This practice improves the explanation without requiring any active simulation, persistence configuration or collection from a real endpoint.
Can shared TTPs identify a specific threat group?
The ATT&CK group introduction describes activity clusters, partially overlapping names and mappings based on public reporting. It explicitly warns that associated names are not exact overlaps. Many methods are available to more than one actor, and a dataset of reported uses is not a complete record of everything those actors have done.
Treat a matching technique as one comparison point, not a fingerprint that identifies the operator. Retain the original source and its attribution wording when summarising a documented campaign. In the invented scheduled-task exercise, no group is named or established. A useful analyst can explain the method and its limits while leaving attribution to a separate investigation with appropriate evidence.
Why should a TTP mapping retain its version and source?
The MITRE version history identifies the current catalogue as v20.1 from 13 October 2026. Categories, descriptions and related objects can change. A saved report should retain the mapping date and applicable version so a reviewer can interpret the terminology used at that time.
The ATT&CK FAQ explains how the knowledge base is organised and used. Read the current definitions rather than assuming the matrix is a mandatory linear sequence every incident follows. An event may contain repeated, overlapping or unobserved behaviour. Avoid filling a report's gaps with a complete attack story simply to make every column in a diagram look occupied.
What should the finished defensive mapping help someone do?
The finished record should identify the source observation, the proposed method, any supported tactical purpose and the evidence needed to resolve uncertainty. It can guide a detection engineer toward relevant telemetry or help an incident lead ask a focused follow-up question. Those next uses require their own implementation and validation work.
For the scheduled-task case, the handoff asks whether the reported task and its associated activity are visible in the approved monitoring sources, and whether the authorisation context is available. It does not claim the technique is fully detected merely because an identifier is assigned. Keep the mapping as a traceable explanation that another defender can challenge, revise and use.
Related reading: Checking evidence behind detection coverage; Investigating an alert without premature conclusions.
If you want instructor feedback, ask WebAsha for a syllabus, supervised lab arrangements and written access terms before enrolling.
References
Frequently Asked Questions
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Wow
0
Sad
0
Angry
0