- Home
- Techniques
- Enterprise
- Compromise Infrastructure
- Web Services
Compromise Infrastructure: Web Services
Other sub-techniques of Compromise Infrastructure (6)
| ID | Name |
|---|---|
| T1584.001 | Domains |
| T1584.002 | DNS Server |
| T1584.003 | Virtual Private Server |
| T1584.004 | Server |
| T1584.005 | Botnet |
| T1584.006 | Web Services |
Before compromising a victim, adversaries may compromise access to third-party web services that can be used during targeting. A variety of popular websites exist for legitimate users to register for web-based services, such as GitHub, Twitter, Dropbox, Google, etc. Adversaries may try to take ownership of a legitimate user's access to a web service and use that web service as infrastructure in support of cyber operations. Such web services can be abused during later stages of the adversary lifecycle, such as during Command and Control (Web Service) or Exfiltration Over Web Service.[1] Using common services, such as those offered by Google or Twitter, makes it easier for adversaries to hide in expected noise. By utilizing a web service, particularly when access is stolen from legitimate users, adversaries can make it difficult to physically tie back operations to them.
Procedure Examples
| Name | Description |
|---|---|
| Turla |
Turla has frequently used compromised WordPress sites for C2 infrastructure.[1] |
Mitigations
| Mitigation | Description |
|---|---|
| Pre-compromise |
This technique cannot be easily mitigated with preventive controls since it is based on behaviors performed outside of the scope of enterprise defenses and controls. |
Detection
Much of this activity will take place outside the visibility of the target organization, making detection of this behavior difficult. Detection efforts may be focused on related stages of the adversary lifecycle, such as during Command and Control (Web Service) or Exfiltration Over Web Service.