ATT&CK coverage › Technique

Compromise Infrastructure T1584

Adversaries may compromise third-party infrastructure that can be used during targeting. Infrastructure solutions include physical or cloud servers, domains, network devices, and third-party web and DNS services. Instead of buying, leasing, or renting infrastructure an adversary may compromise infrastructure and use it during other phases of the adversary lifecycle. Additionally, adversaries may compromise numerous machines to form a botnet they can leverage.

Events covered

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

ProviderEvent IDTitle
WindowsUpdateClient16Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the...
WindowsUpdateClient20Installation Failure: Windows failed to install the following update with error errorCode: updateTitle.
WindowsUpdateClient24Uninstallation Failure: Windows failed to uninstall the following update with error errorCode: updatelist.
WindowsUpdateClient213Revert Failure: Windows failed to revert the following update with error errorCode: updatelist.
WindowsUpdateClient217Commit Failure: Windows failed to commit the following update with error errorCode: updatelist.

Authoring guide

Patterns shared across the 1 rule 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 (1 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
Provider_Name1eq 1Microsoft-Windows-WindowsUpdateClient

Top indicator values (1 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
Provider_NameeqMicrosoft-Windows-WindowsUpdateClient1

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 1 rule