M1041: Encrypt Sensitive Information

Encrypt Sensitive Information is a foundational mitigation for reducing the business damage of credential theft, data collection, traffic interception, and data tampering. Its value is not that encryption stops every attack, but that it can make stolen files, backups, network traffic, secrets, databases, and email data less useful to an adversary when access controls or monitoring fail.

Executive priority

Leaders should treat this as a resilience and compliance evidence issue: which sensitive data, credentials, backups, application secrets, databases, cloud storage, and email repositories are encrypted at rest, in transit, and during processing, and who can prove it? The relationship context ties this mitigation to credential access, collection, exfiltration, lateral movement, and data manipulation behaviors, so gaps can affect incident containment, breach reporting, audit readiness, and recovery confidence.

Technical view

Because ATT&CK provides no detection text for this mitigation, SOC, IR, cloud, identity, and infrastructure teams should validate control state rather than look for a single alert. Confirm encryption configuration and key protection for endpoints, backups, databases, cloud/object storage, application secrets, email transport, web applications, and sensitive repositories. Prioritize areas connected to the related techniques: OS credential material and NTDS-related data, private keys and unsecured credentials, application access tokens, email stores and forwarding exposure, cloud storage, databases, network traffic vulnerable to sniffing or adversary-in-the-middle activity, and stored data integrity risks.

Likely telemetry

Endpoint encryption inventory and compliance status for full-disk or file-level encryption
TLS/HTTPS and STARTTLS configuration evidence for web and mail services
Backup job logs and backup storage configuration showing encryption during storage and transfer
Secrets vault audit logs and configuration records for credentials, API keys, and application secrets
Database encryption settings such as transparent or column-level encryption status

Detection direction

Validate that encryption control evidence is collected centrally; absence of configuration telemetry is a major blind spot because ATT&CK does not define a behavioral detection for this mitigation.
Tune compliance checks around sensitive data locations rather than only device ownership; related techniques include email, databases, cloud storage, backups, credentials, and private keys.
Review exceptions carefully: unencrypted legacy protocols, local email caches, exported database copies, backup replicas, and unmanaged secrets can create high-value collection paths.
Correlate encryption gaps with credential-access and collection risk areas such as domain controller data, application tokens, private keys, email repositories, and cloud storage.
Avoid treating encryption as proof of protection by itself; key access, weak configuration, plaintext processing locations, and excessive administrative access can still determine real exposure.

Mitigation priorities

Start with data and credential discovery: identify sensitive repositories, credential material, private keys, backups, application secrets, email stores, databases, and cloud storage.
Implement or verify strong encryption for data at rest, in transit, backups, application secrets, and databases as described by ATT&CK.
Centralize key and secret management where feasible, with auditable access and separation from the protected data.
Prioritize domain controllers, identity infrastructure, email platforms, databases, cloud storage, and backup systems because the related techniques show these are high-value targets for credential access and collection.
Require routine evidence collection for audits and incident response, including encryption status, policy exceptions, and key-access records.

Additional notes and limits

This ATT&CK object is a course of action, not an adversary behavior. Its relationship set shows broad defensive relevance across credential access, collection, exfiltration, lateral movement, and impact techniques. The strongest Glexia validation question is whether encryption is consistently implemented and provable across the places adversaries are described as collecting or abusing sensitive data.

MITRE does not provide detection guidance, tactics, or platforms for M1041 itself. Platform references come from related techniques only. Local architecture, data classification, key-management design, and control evidence are required to determine actual coverage or risk reduction.

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Official MITRE ATT&CK definition

Encrypt 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. This mitigation can be implemented through the following measures:

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.

View the same entry on attack.mitre.org (MITRE-hosted reference; in-page links above use the Glexia ATT&CK library.)

Glexia analysis

How security teams should use this page

Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.

ATT&CK relationship table

Techniques used

This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.

Filter related techniques33 rows

Domain	ID	Name	Relationship / procedure
Enterprise	T1659	Content Injection	Where possible, ensure that online traffic is appropriately encrypted through services such as trusted VPNs.
Enterprise	T1552	Unsecured Credentials	When possible, store keys on separate cryptographic hardware instead of on the local system.
Enterprise	T1557.002	ARP Cache PoisoningSub-technique	Ensure that all wired and/or wireless traffic is encrypted appropriately. Use best practices for authentication protocols, such as Kerberos, and ensure web traffic that may contain credentials is protected by SSL/TLS.
Enterprise	T1557	Adversary-in-the-Middle	Ensure that all wired and/or wireless traffic is encrypted appropriately. Use best practices for authentication protocols, such as Kerberos, and ensure web traffic that may contain credentials is protected by SSL/TLS.
Enterprise	T1070	Indicator Removal	Obfuscate/encrypt event files locally and in transit to avoid giving feedback to an adversary.
Enterprise	T1602.002	Network Device Configuration DumpSub-technique	Configure SNMPv3 to use the highest level of security (authPriv) available.[1]
Enterprise	T1003	OS Credential Dumping	Ensure Domain Controller backups are properly secured.
Enterprise	T1565.002	Transmitted Data ManipulationSub-technique	Encrypt all important data flows to reduce the impact of tailored modifications on data in transit.
Enterprise	T1565	Data Manipulation	Consider encrypting important information to reduce an adversary’s ability to perform tailored data modifications.
Enterprise	T1558	Steal or Forge Kerberos Tickets	Enable AES Kerberos encryption (or another stronger encryption algorithm), rather than RC4, where possible.[2]
Enterprise	T1530	Data from Cloud Storage	Encrypt data stored at rest in cloud storage.[3][4] Managed encryption keys can be rotated by most providers. At a minimum, ensure an incident response plan to storage breach includes rotating the keys and test for impact on client applications.[5]
Enterprise	T1213.006	DatabasesSub-technique	Encrypt data stored at rest in databases.
Enterprise	T1040	Network Sniffing	Ensure that all wired and/or wireless traffic is encrypted appropriately. Use best practices for authentication protocols, such as Kerberos, and ensure web traffic that may contain credentials is protected by SSL/TLS.
Enterprise	T1114.002	Remote Email CollectionSub-technique	Use of encryption provides an added layer of security to sensitive information sent over email. Encryption using public key cryptography requires the adversary to obtain the private certificate along with an encryption key to decrypt messages.
Enterprise	T1602.001	SNMP (MIB Dump)Sub-technique	Configure SNMPv3 to use the highest level of security (authPriv) available.[1]
Enterprise	T1685.005	Clear Windows Event LogsSub-technique	Obfuscate/encrypt event files locally and in transit to avoid giving feedback to an adversary.
Enterprise	T1119	Automated Collection	Encryption and off-system storage of sensitive information may be one way to mitigate collection of files, but may not stop an adversary from acquiring the information if an intrusion persists over a long period of time and the adversary is able to discover and access the data through other means. Strong passwords should be used on certain encrypted documents that use them to prevent offline cracking through Brute Force techniques.
Enterprise	T1649	Steal or Forge Authentication Certificates	Ensure certificates as well as associated private keys are appropriately secured. Consider utilizing additional hardware credential protections such as trusted platform modules (TPM) or hardware security modules (HSM). Enforce HTTPS and enable Extended Protection for Authentication.[6]
Enterprise	T1114.003	Email Forwarding RuleSub-technique	Use of encryption provides an added layer of security to sensitive information sent over email. Encryption using public key cryptography requires the adversary to obtain the private certificate along with an encryption key to decrypt messages.
Enterprise	T1565.001	Stored Data ManipulationSub-technique	Consider encrypting important information to reduce an adversary’s ability to perform tailored data modifications.
Enterprise	T1558.004	AS-REP RoastingSub-technique	Enable AES Kerberos encryption (or another stronger encryption algorithm), rather than RC4, where possible.[2]
Enterprise	T1669	Wi-Fi Networks	Ensure that all wired and/or wireless traffic is encrypted appropriately. Use best practices for authentication protocols, such as Kerberos, and ensure that web traffic that may contain credentials is protected by SSL/TLS.
Enterprise	T1114	Email Collection	Use of encryption provides an added layer of security to sensitive information sent over email. Encryption using public key cryptography requires the adversary to obtain the private certificate along with an encryption key to decrypt messages.
Enterprise	T1558.003	KerberoastingSub-technique	Enable AES Kerberos encryption (or another stronger encryption algorithm), rather than RC4, where possible.[2]
Enterprise	T1020.001	Traffic DuplicationSub-technique	Ensure that all wired and/or wireless traffic is encrypted appropriately. Use best practices for authentication protocols, such as Kerberos, and ensure web traffic that may contain credentials is protected by SSL/TLS.
Enterprise	T1685.006	Clear Linux or Mac System LogsSub-technique	Obfuscate/encrypt event files locally and in transit to avoid giving feedback to an adversary.
Enterprise	T1602	Data from Configuration Repository	Configure SNMPv3 to use the highest level of security (authPriv) available.[1]
Enterprise	T1003.003	NTDSSub-technique	Ensure Domain Controller backups are properly secured.[7]
Enterprise	T1552.004	Private KeysSub-technique	When possible, store keys on separate cryptographic hardware instead of on the local system. For example, on Windows systems use a TPM to secure keys and other sensitive credential material.[8]
Enterprise	T1550.001	Application Access TokenSub-technique	File encryption should be enforced across email communications containing sensitive information that may be obtained through access to email services.
Enterprise	T1114.001	Local Email CollectionSub-technique	Use of encryption provides an added layer of security to sensitive information sent over email. Encryption using public key cryptography requires the adversary to obtain the private certificate along with an encryption key to decrypt messages.
Enterprise	T1213	Data from Information Repositories	Encrypt data stored at rest in databases.
Enterprise	T1558.002	Silver TicketSub-technique	Enable AES Kerberos encryption (or another stronger encryption algorithm), rather than RC4, where possible.[2]

Relationship explorer

All related ATT&CK context

Change history

Object version and sync metadata

The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates.

ATT&CK release: 19.1
Object version: 1.1
Created: Jun 11, 2019, 16:43 UTC (UTC+00:00)
Modified: Apr 2, 2025, 17:28 UTC (UTC+00:00)
Raw hash: 8ad3dddbc0255329...

Imported snapshots across ATT&CK releases(1)

Release	Bundle imported	Object version	Modified	Status	Raw hash
19.1	Jul 14, 2026, 09:14 UTC (UTC+00:00)	1.1	Apr 2, 2025, 17:28 UTC (UTC+00:00)	Current bundle	`8ad3dddbc025…`

Raw source

Mirrored ATT&CK source object

The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.

Open mirrored raw JSON Open MITRE-hosted copy

Source references

External references and citations

MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.

[1]
US-CERT TA17-156A SNMP Abuse 2017
US-CERT. (2017, June 5). Reducing the Risk of SNMP Abuse. Retrieved October 19, 2020.
Open source URL
[2]
AdSecurity Cracking Kerberos Dec 2015
Metcalf, S. (2015, December 31). Cracking Kerberos TGS Tickets Using Kerberoast – Exploiting Kerberos to Compromise the Active Directory Domain. Retrieved March 22, 2018.
Open source URL
[3]
Amazon S3 Security, 2019
Amazon. (2019, May 17). How can I secure the files in my Amazon S3 bucket?. Retrieved October 4, 2019.
Open source URL
[4]
Microsoft Azure Storage Security, 2019
Amlekar, M., Brooks, C., Claman, L., et. al.. (2019, March 20). Azure Storage security guide. Retrieved October 4, 2019.
Open source URL
[5]
Google Cloud Encryption Key Rotation
Google. (n.d.). Key rotation. Retrieved October 18, 2019.
Open source URL
[6]
SpecterOps Certified Pre Owned
Schroeder, W. & Christensen, L. (2021, June 22). Certified Pre-Owned - Abusing Active Directory Certificate Services. Retrieved August 2, 2022.
Open source URL
[7]
Metcalf 2015
Metcalf, S. (2015, January 19). Attackers Can Now Use Mimikatz to Implant Skeleton Key on Domain Controllers & BackDoor Your Active Directory Forest. Retrieved February 3, 2015.
[8]
Microsoft Primary Refresh Token
Microsoft. (2022, September 9). What is a Primary Refresh Token?. Retrieved February 21, 2023.
Open source URL
[9]
mitre-attackM1041
Open source URL
[10]
mitre-attackM1041
Open source URL
[11]
mitre-attackM1041
Open source URL
[12]
US-CERT TA17-156A SNMP Abuse 2017
US-CERT. (2017, June 5). Reducing the Risk of SNMP Abuse. Retrieved October 19, 2020.
Open source URL
[13]
AdSecurity Cracking Kerberos Dec 2015
Metcalf, S. (2015, December 31). Cracking Kerberos TGS Tickets Using Kerberoast – Exploiting Kerberos to Compromise the Active Directory Domain. Retrieved March 22, 2018.
Open source URL
[14]
Amazon S3 Security, 2019
Amazon. (2019, May 17). How can I secure the files in my Amazon S3 bucket?. Retrieved October 4, 2019.
Open source URL
[15]
Google Cloud Encryption Key Rotation
Google. (n.d.). Key rotation. Retrieved October 18, 2019.
Open source URL
[16]
Microsoft Azure Storage Security, 2019
Amlekar, M., Brooks, C., Claman, L., et. al.. (2019, March 20). Azure Storage security guide. Retrieved October 4, 2019.
Open source URL
[17]
US-CERT TA17-156A SNMP Abuse 2017
US-CERT. (2017, June 5). Reducing the Risk of SNMP Abuse. Retrieved October 19, 2020.
Open source URL
[18]
US-CERT TA17-156A SNMP Abuse 2017
US-CERT. (2017, June 5). Reducing the Risk of SNMP Abuse. Retrieved October 19, 2020.
Open source URL
[19]
SpecterOps Certified Pre Owned
Schroeder, W. & Christensen, L. (2021, June 22). Certified Pre-Owned - Abusing Active Directory Certificate Services. Retrieved August 2, 2022.
Open source URL
[20]
AdSecurity Cracking Kerberos Dec 2015
Metcalf, S. (2015, December 31). Cracking Kerberos TGS Tickets Using Kerberoast – Exploiting Kerberos to Compromise the Active Directory Domain. Retrieved March 22, 2018.
Open source URL
[21]
AdSecurity Cracking Kerberos Dec 2015
Metcalf, S. (2015, December 31). Cracking Kerberos TGS Tickets Using Kerberoast – Exploiting Kerberos to Compromise the Active Directory Domain. Retrieved March 22, 2018.
Open source URL
[22]
AdSecurity Cracking Kerberos Dec 2015
Metcalf, S. (2015, December 31). Cracking Kerberos TGS Tickets Using Kerberoast – Exploiting Kerberos to Compromise the Active Directory Domain. Retrieved March 22, 2018.
Open source URL
[23]
AdSecurity Cracking Kerberos Dec 2015
Metcalf, S. (2015, December 31). Cracking Kerberos TGS Tickets Using Kerberoast – Exploiting Kerberos to Compromise the Active Directory Domain. Retrieved March 22, 2018.
Open source URL
[24]
US-CERT TA17-156A SNMP Abuse 2017
US-CERT. (2017, June 5). Reducing the Risk of SNMP Abuse. Retrieved October 19, 2020.
Open source URL
[25]
US-CERT TA17-156A SNMP Abuse 2017
US-CERT. (2017, June 5). Reducing the Risk of SNMP Abuse. Retrieved October 19, 2020.
Open source URL
[26]
AdSecurity Cracking Kerberos Dec 2015
Metcalf, S. (2015, December 31). Cracking Kerberos TGS Tickets Using Kerberoast – Exploiting Kerberos to Compromise the Active Directory Domain. Retrieved March 22, 2018.
Open source URL

Source and licensing

Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.

Official MITRE ATT&CK site Official STIX data repository MITRE ATT&CK terms of use