Home/ATT&CK Technique/Transmitted Data Manipulation
ATT&CK Technique

Transmitted Data Manipulation

T1565.002 · impact

Adversaries may alter data en route to storage or other systems in order to manipulate external outcomes or hide activity, thus threatening the integrity of the data. By manipulating transmitted data, adversaries may attempt to affect a business process, organizational understanding, and decision making. Manipulation may be possible over a network connection or between system processes where there is an opportunity deploy a tool that will intercept and change information.

The type of modification and the impact it will have depends on the target transmission mechanism as well as the goals and objectives of the adversary. For complex systems, an adversary would likely need special expertise and possibly access to specialized software related to the system that would typically be gained through a prolonged information gathering campaign in order to have the desired impact.

LinuxmacOSWindows
◆

Actors Using This

14
north_koreaAPT38
brazilBanbra
brazilBizarro
russia_apt_sandwormBlackEnergy
russia_apt_sandwormCaddyWiper
russia_speaking_cybercrimeCarbanak
russia_apt_sandworm_adjacentHermeticWiper
russia_apt_sandwormIndustroyer / CrashOverride / Industroyer2
brazilKrachulka
brazilLokorrito
russia_apt_sandwormNotPetya
russia_apt_sandwormOlympic Destroyer
turkeySea Turtle
us_israel_joint_offensive_cyberStuxnet
◈

Likely Attack Path

Techniques the same actors pair with this one distinctively - those showing up among actors who use this technique noticeably more than across all actors (lift > 1.15), grouped by kill-chain phase. The × is that lift multiplier; the shared-actor count is in the tooltip. A near-universal technique pairs with everything at baseline, so its list is short by design.
persistence earlier
T1547.004 · Winlogon Helper DLL ×13.22T1037.003 · Network Logon Script ×7.93
lateral-movement earlier
T0843 · Program Download ×7.93
collection earlier
T1056.004 · Credential API Hooking ×8.81
impact same
T1488 · Disk Content Wipe ×9.44T1565.001 · Stored Data Manipulation ×9.37T1495 · Firmware Corruption ×9.15T1496 · Resource Hijacking ×6.61T1499.004 · Application or System Exploitation ×6.61T0815 · Denial of View ×6.61T0828 · Loss of Productivity and Revenue ×6.61T0831 · Manipulation of Control ×6.61T1565 · Data Manipulation ×6.26T1561.002 · Disk Structure Wipe ×5.95
other same
T0816 · Device Restart/Shutdown ×5.67
▣

Mitigations

1
MITRE ATT&CK mitigations - vendor-agnostic guidance for reducing exposure to this technique.
M1041Encrypt Sensitive Information

Protect sensitive information at rest, in transit, and during processing by using strong encryption algorithms. Encryption ensures the confidentiality and integrity of data, preventing unauthorized access or tampering.

Encrypt Data at Rest
  • Use Case: Use full-disk encryption or file-level encryption to secure sensitive data stored on devices.
  • Implementation: Implement BitLocker for Windows systems or FileVault for macOS devices to encrypt hard drives.
Encrypt Data in Transit
  • Use Case: Use secure communication protocols (e.g., TLS, HTTPS) to encrypt sensitive data as it travels over networks.
  • Implementation: Enable HTTPS for all web applications and configure mail servers to enforce STARTTLS for email encryption.
Encrypt Backups
  • Use Case: Ensure that backup data is encrypted both during storage and transfer to prevent unauthorized access.
  • Implementation: Encrypt cloud backups using AES-256 before uploading them to Amazon S3 or Google Cloud.
Encrypt Application Secrets
  • Use Case: Store sensitive credentials, API keys, and configuration files in encrypted vaults.
  • Implementation: Use HashiCorp Vault or AWS Secrets Manager to manage and encrypt secrets.
Database Encryption
  • Use Case: Enable Transparent Data Encryption (TDE) or column-level encryption in database management systems.
  • Implementation: Use MySQL’s built-in encryption features to encrypt sensitive database fields such as social security numbers.
◈

Detection Coverage

1/6 layers
Coverage across standard detection surfaces. Rows marked none have no rule of that type mapped. Some are real blind spots worth closing; others are simply not applicable to this technique (e.g. YARA matches malware files, not network behaviour).
Behavioral / log (Sigma) 2
Analytics (MITRE CAR) none
Runtime / container (Falco) none
File / malware (YARA) none
Network (Suricata/Snort) none
Vuln scan (Nuclei) none
▣

Comply & Defend

NIST 800-53AC-16, AC-17, AC-18, AC-19, AC-20, CM-02, CM-06, CM-08, SC-04, SI-04, SI-07, SI-12
D3FEND9 defensive techniques
Intelligence Graph · click any node to traverse
CVETechnique ActorTool Family
drag to reposition · click any node to traverse · button top-right enlarges
External lookups - second-class, for what we don’t hold ourselves
MITRE ATT&CKAtomic Red Teamcar (MITRE)
Vulnerabilities
CISA KEV catalog
CWE weaknesses
CAPEC attack patterns
Package vulnerabilities
Threat intelligence
Threat actors
Tools & malware
ATT&CK techniques
IOCs
Detection & defense
Sigma rules
YARA rules
Atomic Red Team tests
D3FEND countermeasures
Compliance
NIST 800-53
ISO 27001:2022
SOC 2 TSC
PCI-DSS v4.0
CIS Controls v8.1
About
All capabilities
Live statistics
Data sources
Privacy policy
Terms of service
threatengine.sh  ·  Open-source threat intelligence platform  ·  100+ authoritative sources  ·  Every fact traces to its origin