Indicator Removal: Clear Network Connection History and Configurations
- ID
- T1070.007
- Tactics
- TA0005 Stealth
- Sub-technique of
- T1070 Indicator Removal
- Platforms
- Linux, macOS, Windows, Network Devices
- Data sources
- Windows Registry Key Modification, Process Creation, Command Execution, Firewall Rule Modification, File Modification, Network Traffic Content
- Source
- attack.mitre.org
- MITRE last modified
- 12 May 2026
Adversaries may clear or remove evidence of malicious network connections in order to clean up traces of their operations. Configuration settings as well as various artifacts that highlight connection history may be created on a system and/or in application logs from behaviors that require network connections, such as Remote Services or External Remote Services. Defenders may use these artifacts to monitor or otherwise analyze network connections created by adversaries.
Network connection history may be stored in various locations. For example, RDP connection history may be stored in Windows Registry values under [1]:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\DefaultHKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Servers
Windows may also store information about recent RDP connections in files such as C:\Users\\%username%\Documents\Default.rdp and C:\Users\%username%\AppData\Local\Microsoft\Terminal.[2] Similarly, macOS and Linux hosts may store information highlighting connection history in system logs (such as those stored in
Server Client\Cache\/Library/Logs and/or /var/log/).[3][4][5]
Malicious network connections may also require changes to third-party applications or network configuration settings, such as Disable or Modify System Firewall or tampering to enable Proxy. Adversaries may delete or modify this data to conceal indicators and/or impede defensive analysis.
Detection
- DET0049 Behavioral Detection of Network History and Configuration Tampering
Data components: Windows Registry Key Modification, Process Creation, Command Execution, Firewall Rule Modification, File Modification, Network Traffic Content
Mitigations (2)
- M1024 Restrict Registry Permissions
Protect generated event files and logs that are stored locally with proper permissions and authentication and limit opportunities for adversaries to increase privileges by preventing Privilege Escalation opportunities.
- M1029 Remote Data Storage
Automatically forward events to a log server or data repository to prevent conditions in which the adversary can locate and manipulate data on the local system. When possible, minimize time delay on event reporting to avoid prolonged storage on the local system.