TTP in cybersecurity stands for Tactics, Techniques, and Procedures-specific actions and methods used by threat actors during cyberattacks. These are documented behaviors that reveal how attackers gain access, move through systems, and achieve their goals.
Threat actors do not operate randomly. They follow predictable sequences. TTPs are the blueprint of their operations. For example, a hacker might use phishing emails (technique) to deliver malware (tactic), then maintain access using scheduled tasks (procedure). These steps are recorded in frameworks like MITRE ATT&CK, which catalogs thousands of known TTPs.
Understanding TTPs allows defenders to anticipate attacks before they succeed. Security teams analyze logs, monitor network traffic, and detect anomalies based on known TTP patterns. When a system shows signs of lateral movement-such as unusual logins across multiple machines-it may indicate an attacker using a known technique from the MITRE ATT&CK database.
Each TTP is categorized under a broader tactic. Tactics describe the attacker's objective-like "initial access," "execution," or "exfiltration." Techniques are the specific ways to achieve those objectives. Procedures are the implementation details, such as command-line syntax or file locations.
For instance, the tactic "Persistence" aims to maintain long-term access. A common technique is creating a new Windows service with a malicious binary. The procedure might involve using PowerShell to register the service with a startup trigger. This sequence is well-documented in the MITRE ATT&CK structure under ID T1543.003.
When a security analyst sees a new service being created with a name like "UpdateManager64," especially if it points to a temporary directory, that's a red flag. The behavior matches a known TTP. Detection tools can flag it automatically, even if the filename is obfuscated.
Attackers reuse TTPs across campaigns. Some are basic; others are highly sophisticated. The following table outlines key categories with real-world instances:
| Tactic | Technique | Procedure Example | Source |
|---|---|---|---|
| Initial Access | Phishing | Malicious Word document with embedded macro that downloads payload from a remote server | MITRE ATT&CK, T1566 |
| Execution | Command and Scripting Interpreter | Using PowerShell to run encoded commands via -EncodedCommand parameter | MITRE ATT&CK, T1059 |
| Privilege Escalation | Exploiting Vulnerable Service | Abusing a misconfigured Windows service with high privileges to execute arbitrary code | CISA Known Exploited Vulnerabilities Catalog |
| Lateral Movement | Remote Services: SMB/Windows Admin Shares | Connecting to \\192.168.1.10\c$ using stolen credentials | MITRE ATT&CK, T1021 |
These examples show how TTPs are not theoretical-they're used in actual breaches. In 2021, the SolarWinds supply chain attack relied heavily on TTPs such as credential dumping (T1003) and living-off-the-land binaries (T1078), both documented in MITRE ATT&CK.
Defensive teams use TTPs to build detection rules. Instead of waiting for a breach to happen, they look for early indicators. For example, if a user account suddenly runs a command like "net user [name] * /add" from an unexpected location, that's a sign of privilege escalation-a known TTP.
Organizations map their own incident response playbooks to TTPs. When a system detects a suspicious outbound connection to a known command-and-control server, the response team follows a predefined checklist based on the TTP involved. This speeds up containment and reduces damage.
A non-obvious point often missed: TTPs aren't static. Attackers adapt. A technique once rare-like abusing legitimate cloud APIs-has become widespread. In 2023, researchers at Mandiant observed a rise in TTPs involving AWS S3 bucket misconfigurations for data exfiltration. The same technique was used in over 40% of cloud-based incidents they analyzed.
Many assume TTPs are only about technical exploits. But they include social engineering too. Phishing is a tactic. Sending a fake invoice email is a technique. Using a domain that mimics your vendor's name is a procedure. All fall under TTP.
Another mistake: treating TTPs as unique identifiers. No single TTP defines an entire attack. A successful breach usually combines five to seven different TTPs. For example, a ransomware campaign might start with spear-phishing (T1566), escalate privileges (T1068), move laterally (T1021), disable backups (T1490), and finally encrypt files (T1486).
Some organizations confuse TTPs with indicators of compromise (IOCs). IOCs are artifacts-IP addresses, file hashes, domains. TTPs are behavioral patterns. You can block an IOC, but you can't stop a TTP unless you understand the underlying behavior. A firewall can block a known malicious IP, but only a detection system trained on TTPs can catch a new variant using the same method.
In 2022, I monitored a small business network using SIEM tools. An employee opened a PDF labeled "Q2 Report.pdf" that triggered a script execution. The process ran from a temp folder, downloaded a binary from a domain flagged as malicious, and attempted to connect to port 443. The behavior matched TTPs associated with the APT group FIN7, specifically T1566 (phishing) and T1059 (scripting).
We blocked the domain, quarantined the file, and isolated the endpoint. Within 12 hours, we identified two other machines showing similar activity. Because we had mapped the TTPs, we didn't wait for a full breach. We stopped it at the initial access stage.
Start by integrating MITRE ATT&CK into your security monitoring. Use the structure to classify threats and build detection logic. Focus on behaviors-not just file hashes or IPs. Train analysts to recognize patterns across logs, endpoints, and network traffic.
Every cyberattack follows a path. That path is made of TTPs. Recognizing them isn't optional-it's essential for surviving modern threats.