Develop Capabilities T1587
Tactic: Resource Development
Adversaries may build capabilities that can be used during targeting. Rather than purchasing, freely downloading, or stealing capabilities, adversaries may develop their own capabilities in-house. This is the process of identifying development requirements and building solutions such as malware, exploits, and self-signed certificates. Adversaries may develop capabilities to support their operations throughout numerous phases of the adversary lifecycle.
Events covered
6 catalog events are tagged with this technique by at least one rule.
| Provider | Event | Title |
|---|---|---|
| Sysmon | Event ID 1 | Process creation |
| Sysmon | Event ID 7 | Image loaded |
| Sysmon | Event ID 11 | FileCreate |
| Security-Auditing | Event ID 4688 | A new process has been created. |
| Linux-Auditd | Event ID 1300 | SYSCALL |
| Sysmon-for-Linux | Event ID 1 | Process Create |
Authoring guide
Patterns shared across the 23 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (26 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (319 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.
Exclusions (81 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 16 rules
- Conti Volume Shadow Listing
- Creation of an Executable by an Executable
- CVE-2021-1675 Print Spooler Exploitation Filename Pattern
- FoggyWeb Backdoor DLL Loading
- Formbook Process Creation
- HackTool - PurpleSharp Execution
- Linux HackTool Execution
- Mustang Panda Dropper
- Potential Privilege Escalation To LOCAL SYSTEM
- Potential PsExec Remote Execution
- Program Executions in Suspicious Folders
- PsExec/PAExec Escalation to LOCAL SYSTEM
- PUA - CsExec Execution
- Suspicious Word Cab File Write CVE-2021-40444
- Uncommon File Created In Office Startup Folder
- VHD Image Download Via Browser
Elastic 1 rule
Splunk 3 rules
- Cisco Secure Firewall - Blacklisted SSL Certificate Fingerprint
- Cisco Secure Firewall - Possibly Compromised Host
- Windows Certutil Root Certificate Addition