iPad compliance shows Data Protection or application security warning in HexnodeSolved

For iPads, internal storage encryption is handled by Apple at the hardware and OS level. There is no separate Hexnode policy option to manually enable SSD or internal storage encryption on iPadOS. To enforce Data Protection on an iPad, ensure that a passcode is required on the device. When a passcode is set, iPadOS uses it as part of the cryptographic protection for device data. In Hexnode, this is typically managed by applying a passcode policy to the device. If the compliance state does not update immediately after the requirement is met, reapplying or syncing the policy can refresh the compliance status.

That makes sense. So for iPads, there is no separate “enable encryption” checkbox like we might expect on a desktop device. The passcode requirement is what satisfies Data Protection?

Correct. On iPadOS, encryption is built in by default, and Data Protection becomes effective when a passcode is configured. From a compliance perspective, make sure the device has a passcode and that the Hexnode passcode policy is applied successfully.

For the earlier application compliance warning, reapplying the policy can help if the device had not reported the latest compliance state yet.

Reapplying the policy refreshed the app compliance status, and after confirming the passcode was enabled, the Data Protection item also showed compliant. No separate SSD encryption policy was needed.