M0941: Encrypt Sensitive Information
Protect sensitive data-at-rest with strong encryption.
Security context for executives and security teams
M0941: Encrypt Sensitive Information describes Protect sensitive data-at-rest with strong encryption.
Executive priority
M0941: Encrypt Sensitive Information is an official MITRE ATT&CK mitigation. Glexia treats it as defensive behavior context for prioritizing monitoring, control validation, and response planning without using the object by itself as an attribution claim.
Technical view
Security teams should validate M0941: Encrypt Sensitive Information by reviewing the official ATT&CK relationships, mapped tactics (the mapped ATT&CK tactic context), supported platforms (the platforms named in the official object), and available local telemetry before making detection or mitigation decisions.
Likely telemetry
- Official ATT&CK relationships and object metadata
Detection direction
- Validate whether M0941: Encrypt Sensitive Information appears in your detection coverage and tabletop scenarios.
- Use the object to align executive risk language with SOC, incident response, and detection engineering work.
- Do not treat ATT&CK relationship context as attribution without corroborating evidence.
Mitigation priorities
- Map the object to existing controls and identify missing telemetry or response ownership.
- Prioritize mitigations that reduce exposure on the listed platforms and tactics.
- Review adjacent ATT&CK relationships before changing policy, detections, or reporting language.
Additional notes and limits
Baseline Glexia take generated from the official MITRE ATT&CK STIX object, source hash, tactics, platforms, and detection fields. It is safe to replace with a richer model-generated take for the same source hash later.
This baseline take is source-grounded and schema-validated, but it does not include environment-specific telemetry, incident evidence, or threat-intelligence corroboration.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Encrypt Sensitive Information
Protect sensitive data-at-rest with strong encryption.
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.
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.
| Domain | ID | Name | Relationship / procedure |
|---|---|---|---|
| ICS | T0864 | Transient Cyber Asset | Consider implementing full disk encryption, especially if engineering workstations are transient assets that are more likely to be lost, stolen, or tampered with. CitationNational Institute of Standards and Technology April 2013 |
| ICS | T1693.001 | System FirmwareSub-technique | The encryption of firmware should be considered to prevent adversaries from identifying possible vulnerabilities within the firmware. |
| ICS | T0873 | Project File Infection | When at rest, project files should be encrypted to prevent unauthorized changes.CitationNational Institute of Standards and Technology April 2013 |
| ICS | T1693 | Modify Firmware | The encryption of firmware should be considered to prevent adversaries from identifying possible vulnerabilities within the firmware. |
| ICS | T0873.001 | Siemens Project File FormatSub-technique | When at rest, project files should be encrypted to prevent unauthorized changes.CitationNational Institute of Standards and Technology April 2013 |
| ICS | T1693.002 | Module FirmwareSub-technique | The encryption of firmware should be considered to prevent adversaries from identifying possible vulnerabilities within the firmware. |
| ICS | T0893 | Data from Local System | Information which is sensitive to the operation and architecture of the process environment may be encrypted to ensure confidentiality and restrict access to only those who need to know. CitationKeith Stouffer May 2015 CitationNational Institute of Standards and Technology April 2013 |
| ICS | T0811 | Data from Information Repositories | Information which is sensitive to the operation and architecture of the process environment may be encrypted to ensure confidentiality and restrict access to only those who need to know. CitationKeith Stouffer May 2015 CitationNational Institute of Standards and Technology April 2013 |
| ICS | T0882 | Theft of Operational Information | Encrypt any operational data with strong confidentiality requirements, including organizational trade-secrets, recipes, and other intellectual property (IP). |
All related ATT&CK context
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.
Imported snapshots across ATT&CK releases(2)
| Release | Bundle imported | Object version | Modified | Status | Raw hash |
|---|---|---|---|---|---|
| 19.2 | 1.1 | Current bundle | 50a5564767d2… | ||
| 19.1 | 1.1 | Older bundle | 50a5564767d2… |
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.
External references and citations
MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.
- [1]mitre-attackM0941Open source URL
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.