ATT&CK coverage › Technique

Stage Capabilities T1608

Adversaries may upload, install, or otherwise set up capabilities that can be used during targeting. To support their operations, an adversary may need to take capabilities they developed (Develop Capabilities) or obtained (Obtain Capabilities) and stage them on infrastructure under their control. These capabilities may be staged on infrastructure that was previously purchased/rented by the adversary (Acquire Infrastructure) or was otherwise compromised by them (Compromise Infrastructure). Capabilities may also be staged on web services, such as GitHub or Pastebin, or on Platform-as-a-Service (PaaS) offerings that enable users to easily provision applications.

Events covered

5 catalog events are tagged with this technique by at least one rule.

ProviderEvent IDTitle
Sysmon1Process creation
Sysmon12RegistryEvent (Object create and delete)
Sysmon13RegistryEvent (Value Set)
Sysmon14RegistryEvent (Key and Value Rename)
Security-Auditing4688A new process has been created.

Authoring guide

Patterns shared across the 2 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized 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 (5 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.

FieldRulesHowSample values
EventType1eq 1SetValue
Details1match 1Microsoft.HybridConnectionManager.Listener.exe
TargetObject1match 1\Services\HybridConnectionManager
Image1ends_with 1\curl.exe, \wget.exe
CommandLine1match 1Start-BitsTransfer, .DownloadString(, .DownloadFile(

Top indicator values (14 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.

FieldKindValueRules (here)Corpus reach
DetailsmatchMicrosoft.HybridConnectionManager.Listener.exe1
EventTypeeqSetValue13
TargetObjectmatch\Services\HybridConnectionManager1
Imageends_with\wget.exe16
CommandLinematchwget 17
CommandLinematchhttps://onenoteonlinesync.onenote.com/onenoteonlinesync/1
CommandLinematchiwr 18
Imageends_with\curl.exe119
CommandLinematchcurl 18
CommandLinematch.DownloadString(13
CommandLinematchInvoke-WebRequest16
CommandLinematchhttps://attachment.outlook.live.net/owa/1
CommandLinematch.DownloadFile(13
CommandLinematchStart-BitsTransfer12

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 2 rules