TL;DR: Removable media encryption only satisfies compliance expectations when organisations can classify what was copied, enforce policy at write time, and preserve audit evidence, according to Strac’s analysis of SOC 2, GDPR, and US privacy requirements. Encryption alone reduces exposure, but governed content inspection is what turns portable media controls into defensible evidence.
Editorial analysis by NHI Mgmt Group, based on content published by Strac: “Removable Media Encryption SOC 2 GDPR”.
Key questions
Q: What breaks when removable-media policies do not inspect file content?
A: If the endpoint cannot inspect content, the organisation cannot distinguish benign transfers from copies of regulated data.
Q: Why do SOC 2 and privacy teams care about removable media controls?
A: They care because the control must show reasonable protection, not just technical encryption.
Q: How should teams decide when to block removable media transfers?
A: Block transfers when the file class is regulated, when the destination is unmanaged, or when the organisation cannot preserve an audit trail.
Practitioner guidance
- Implement write-time content classification Inspect every file before it is written to removable media and classify it against your policy tiers so regulated data can be blocked or forced into encrypted handling.
- Enforce policy by data class Use separate Block, Warn and Audit actions for different sensitivity classes so the response matches the risk of the file being copied.
- Require encryption only for permitted transfers Allow removable media use only when the destination device can be encrypted and the user action is within policy, otherwise prevent the copy.
Bottom line: Encryption on removable media reduces exposure, but it does not by itself establish what data left the organisation or whether the transfer was permitted.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Removable media encryption is an export-control problem, not a storage-control problem. Once data leaves the endpoint, the question is no longer whether the file is encrypted, but whether the organisation can prove the transfer was allowed. That shifts the control objective from protecting a device to governing a decision. For practitioners, this means policy must sit at the write event, not only at the file system layer.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
- Business leaders plan to spend $124 million on average on AI in 2026, and 91% say data security and risk will shape their AI strategy.
A question worth separating out:
Q: What should a defensible portable-media control prove?
A: It should prove that the file was classified before transfer, that policy was enforced at write time, and that the organisation can reconstruct the event later. Those three elements turn encryption into an accountable control rather than a best-effort protection layer.
👉 Read our full editorial: Removable media encryption is a governance problem, not just a tool choice