DualDAR

How DualDAR works

DualDAR is a device-level encryption design that creates two encrypted protection layers so sensitive corporate content can be isolated from the rest of the phone or tablet storage. That separation helps keep managed data protected even when the broader device environment is not fully trusted.

At a practical level, DualDAR is about splitting access paths: one layer protects general device data, while another layer protects managed content with tighter controls. That lets organisations treat corporate information differently from personal or unmanaged data on the same device.

Why DualDAR matters for managed mobile devices

DualDAR is useful because mobile devices are exposed to loss, theft, jailbreak or compromise, and mixed-use storage can otherwise collapse one failure into total data exposure. If the device is lost, the additional encryption boundary reduces how much protected content is reachable from raw storage access.

It also matters in bring-your-own-device and enterprise mobility scenarios, where corporate policy needs to preserve control over work data without taking over the entire device. Separate encryption boundaries make it easier to keep organisational content governed without assuming the rest of the device is equally trustworthy.

How DualDAR changes access control

DualDAR is not just about encryption strength, it is about control separation. Managed content can be tied to corporate policy, managed apps, and conditional access decisions without making every part of the device equally available.

That separation helps reduce lateral exposure inside the device. If a user profile, consumer app, or lower-trust storage area is compromised, the corporate layer is still expected to remain independently protected by its own access rules and encryption state.

This model is especially relevant when organisations need to distinguish between device ownership, user convenience, and corporate custody of data. The encryption architecture supports that distinction by making the protected content layer independently governed rather than merely hidden inside the same storage container.

Limits and operational considerations

DualDAR improves exposure reduction, but it does not replace endpoint hygiene, mobile device management, or identity controls around the people and services that can unlock protected content. If the device is already fully compromised in memory or at the application layer, encryption alone may not prevent misuse of data that has been legitimately decrypted.

Operationally, the value of DualDAR depends on correct device enrollment, policy enforcement, and recovery procedures. If administrators cannot consistently apply the feature across the managed fleet, the protection becomes uneven and the organisation may assume a separation that does not actually exist.

Risk and Threat Considerations

DualDAR reduces the blast radius of mobile compromise, but the main risk is false confidence. If organisations assume the second encrypted layer protects every corporate use case, they may overlook threats that operate after the device has been unlocked, enrolled, or partially compromised.

Failure mechanism: An attacker or unauthorized user may gain access through a stolen device, compromised user session, or malware that operates after normal unlock, then target decrypted or policy-exposed corporate data rather than raw storage.

Impact: Corporate files, credentials, cached tokens, and sensitive app data can be exposed even when the underlying storage remains encrypted, especially if monitoring, revocation, or app-level containment is weak.

Practitioner Guidance

Why practitioners should care: DualDAR only delivers value when it is part of a broader mobile control model, not when it is treated as a standalone safeguard. Treat it as one layer in a managed-device posture that also covers enrollment, app trust, and post-compromise response.

What to watch for: Verify that corporate data actually remains in the protected layer across device types, operating system versions, and management states. Pay particular attention to device loss scenarios, shared device models, and any workflow that moves data between managed and unmanaged storage.

Practitioner takeaway: The important question is not whether DualDAR is enabled, but whether your mobile controls preserve separation when the device, profile, or session is no longer trustworthy.