Symantec Connect
  • Login
  • Register
  • Security
    • All of Connect
    • Backup and Archiving
    • Endpoint Management & Virtualization
    • Storage and Clustering
    • Security
    • Inside Symantec
    • Vision User Conference
    • Partners
    • Developers
    •  
  • Overview
  • Forums
  • Articles
  • Blogs
  • Downloads
  • Events
  • Videos
  • Groups
  • Ideas
Login to participate
Security ResponseRSS

Windows Mobile 6, File Encryption and Incident Response

Ollie Whitehouse
April 24th, 2007
Tags: Endpoint Protection (AntiVirus), Mobile & Wireless, Security, Security Response
Facebook Twitter

With the advent of Windows Mobile 6 came a file system filter driver for encrypting data on Secure Digital (SD) cards, which are frequently used to store sensitive data. Previously, to gain access to users' data, an attacker could simply steal their SD card. Breaking the device's PIN protection was completely unnecessary.

In order to protect users and enterprises alike, Microsoft implemented on-device encryption for SD cards. The down side, however, is that the master key used for this encryption is non-persistent between hard resets. There is currently no escrow mechanism, which is clearly stated by Microsoft: [1]


There isn't any key escrow or recovery in this release. We realize this is very important to many enterprise customers. Feel free to add your comments about how important this is to your organization as it helps us prioritize the work for the future. If you don't want key escrow, that would also be good to hear.


As a result, if a device undergoes a hard reset, nobody will be able to recover the encrypted documents from the storage card.

Also noted by Microsoft [1] is that, when a file is encrypted on a storage card, its filename is modified. This can be useful in identifying such files to people performing incident response. The format used for encrypted files is [filename].[extension].[GUID].menc. The .menc extension tells the Windows Mobile device that it's an encrypted file and the [GUID] represents the encryption key on the device.

The implementation relies on a master key that by default is stored under the \Windows\ directory (\Windows\System\default.mky). Anyone who has to respond to incidents involving Windows Mobile 6 devices and wants any chance of decrypting files held on SD cards (and who doesn't have a spare Cray in the office) should ensure that they grab copies of the master keys.

[1] Windows Mobile 6 Storage Card Encryption FAQ
http://blogs.msdn.com/windowsmobile/archive/2007/03/26/windows-mobile-6-storage-card-encryption-faq.aspx

0 votes
  • Ollie Whitehouse's blog
  • Comments RSS Feed

About Security Response Blog

Our security research centers around the world provide unparalleled analysis of and protection from malware, security risks, vulnerabilities, and spam.
Filter by:

Recent Blog Posts

  • Beyond the Initial Compromise
    Greg Ahmad - March 18, 2010
  • Passwords—Can’t Live With ‘em, Can’t Live Without ‘em
    Kevin Haley - March 17, 2010
  • New Healthcare IT Landscape and Related Security Needs
    Alessandro Tatti - March 17, 2010
  • Fraudsters Running a Classified Ad Campaign
    Mathew Maniyara - March 16, 2010
  • Mass Phishing of Retail Electronic Payment Brands
    Mathew Maniyara - March 15, 2010

Blog Tags

10.x 11.x 9.x and Earlier Antivirus2010 Backdoor.Tidserv Brightmail Gateway Emerging Threats Endpoint Encryption Endpoint Protection (AntiVirus) Endpoint Protection Small Business Enterprise Security Manager Evolution of Security General Symantec IT Healthcare Landscape IT Risk Management Internet Security Threat Report Live PC Care Malicious Code Misleading Applications Mobile & Wireless Online Fraud Password Management Restore Security Security Risks Spam Sykipot SymbOS.Exy Symbian Trojan.FakeAV Trojan.Zbot VirusDoctor Vulnerabilities & Exploits Windows Zeus
© 2010
  • Symantec Corporation
  • Contact Us
  • Get RSS
  • Privacy Policy
  • Symantec.com