MDM Work Container: Key Hierarchy & Crypto-Shred Wipe |…

Key Hierarchy Overview

In an MDM (Mobile Device Management) work container setup, a hardware root key serves as the foundation for deriving other keys. This root key is used to generate a container key-encryption key (CKEK), which in turn wraps every managed app's data key. The CKEK ensures that all data within the container remains secure and isolated from unauthorized access.

The hierarchical structure of these keys provides robust security, as any compromise at one level does not necessarily affect the others. This design is crucial for maintaining the integrity and confidentiality of work-related data on mobile devices.

App-Sandboxing Mechanisms

App-sandboxing is a critical security feature that isolates managed apps from personal applications, preventing unauthorized access to sensitive information. Each app within the container has its own sandboxed environment, which limits its ability to interact with other parts of the device or with personal data.

This isolation ensures that even if a rogue application manages to gain access, it cannot cross the sandbox boundary and compromise other managed apps or personal data stored on the device.

live demo · related simulation● LIVE

Remote Wipe Mechanism

A remote wipe is a powerful feature in MDM that allows administrators to instantly destroy all managed data on a device. When triggered, this process involves crypto-shredding the container key, which effectively renders all wrapped data keys useless and thus inaccessible.

This capability ensures that sensitive work data cannot be accessed by unauthorized parties if a device is lost or stolen.

Key Length Considerations

The length of the app's data key, typically specified as AES-128 or AES-256, significantly impacts the security strength. AES-256 provides a higher level of security due to its larger key size compared to AES-128.

Choosing the appropriate key length is crucial for balancing security requirements with performance considerations in enterprise environments.

Frequently asked questions

How does app-sandboxing prevent data leakage?

App-sandboxing creates isolated environments for each managed application, ensuring that they cannot access or communicate with personal applications or other parts of the device. This isolation prevents unauthorized data leakage and maintains security.

What is crypto-shredding in the context of MDM?

Crypto-shredding involves using cryptographic techniques to irreversibly destroy a key, making any data encrypted with that key inaccessible. In MDM, it ensures that all managed app data on a device is securely deleted when a remote wipe is initiated.

Why is the hardware root key important?

The hardware root key serves as the foundation for deriving other keys in the hierarchy. It provides a secure and trusted source of encryption, ensuring that all data within the work container remains protected against unauthorized access.

Can personal apps access managed app data through sandboxing?

No, app-sandboxing blocks personal applications from accessing or interacting with managed apps. This isolation ensures that sensitive work data is not compromised by rogue or malicious personal applications.

Try it live

Everything above runs in your browser — open MDM Work Container: Key Hierarchy & Crypto-Shred Wipe and change the parameters while it is running. Nothing is installed, nothing is uploaded, the whole model lives in one tab.

▶ Open MDM Work Container: Key Hierarchy & Crypto-Shred Wipe simulation