Cross-source coverage
T1584 / ATT&CK
Compromise Infrastructure
From MITRE ATT&CK 19.2
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.
Use of compromised infrastructure allows adversaries to stage, launch, and execute operations. Compromised infrastructure can help adversary operations blend in with traffic that is seen as normal, such as contact with high reputation or trusted sites. For example, adversaries may leverage compromised infrastructure (potentially also in conjunction with Digital Certificates) to further blend in and support staged information gathering and/or Phishing campaigns. Adversaries may also compromise numerous machines to support Proxy and/or proxyware services or to form a botnet. Additionally, adversaries may compromise infrastructure residing in close proximity to a target in order to gain Initial Access via Wi-Fi Networks.
By using compromised infrastructure, adversaries may enable follow-on malicious operations. Prior to targeting, adversaries may also compromise the infrastructure of other adversaries.
- Tactics
- Resource Development
- Platforms
- PRE
- Telemetry
-
Internet ScanDomain Name
How MITRE says to detect it DET0885
Detection of Compromise Infrastructure
PRE Analytic 2017
Once adversaries have provisioned compromised infrastructure (ex: a server for use in command and control), internet scans may help proactively discover compromised infrastructure. Consider looking for identifiable patterns such as services listening, certificates in use, SSL/TLS negotiation features, or other response artifacts associated with adversary C2 software. Consider monitoring for anomalous changes to domain registrant information and/or domain resolution information that may indicate the compromise of a domain. Efforts may need to be tailored to specific domains of interest as benign registration and resolution changes are a common occurrence on the internet. Monitor for queried domain name system (DNS) registry data that may compromise third-party infrastructure that can be used during targeting. Detection efforts may be focused on related stages of the adversary lifecycle, such as during Command and Control. Monitor for logged domain name system (DNS) data that may compromise third-party infrastructure that can be used during targeting. Detection efforts may be focused on related stages of the adversary lifecycle, such as during Command and Control. Monitor for contextual data about an Internet-facing resource gathered from a scan, such as running services or ports that may compromise third-party infrastructure that can be used during targeting. Detection efforts may be focused on related stages of the adversary lifecycle, such as during Command and Control.
Internet ScanNoneDomain NameNoneDomain NameNoneDomain NameNoneInternet ScanNone
Sub-techniques with coverage
Counted in the 13 above — a rule tagged a sub-technique covers this technique too.
SigmaHQ/sigma
4 rules| Detection | Severity | Format |
|---|---|---|
| Suspicious External WebDAV Execution | High | Sigma |
| Program Executions in Suspicious Folders | Medium | Sigma |
| WebDAV Temporary Local File Creation | Medium | Sigma |
| Windows Update Error | Informational | Sigma |
Wazuh Core Ruleset
3 ruleselastic/detection-rules
3 rules| Detection | Severity | Format |
|---|---|---|
| AWS Route 53 Domain Transfer Lock Disabled | High | Elastic TOML |
| AWS Route 53 Domain Transferred to Another Account | High | Elastic TOML |
| Entra ID Custom Domain Added or Verified | Low | Elastic TOML |
socfortress/Wazuh-Rules
3 rules · 2 families| Detection | Severity | Format |
|---|---|---|
| Detects program executions in suspicious non-program folders related to malware or hacking activity. 2 variants | High | Wazuh XML |
| Detects program executions in suspicious non-program folders related to malware or hacking activity. 2 variants | High | Wazuh XML |
| Too many critical Maltrail events triggered, possible infection detected. | High | Wazuh XML |