Knox Guard 24.09 release notes

Ability to restrict Android Debug Bridge

Starting with the Knox Guard 24.09 release, you can restrict Android Debug Bridge (adb) for enhanced security. To do so, request for the permission to block adb on your Knox Guard enabled devices with Android 15 and higher. With the permission granted, use the Block/unblock the ADB command API to enable or disable adb on select devices or the corresponding Async API to enable or disable adb for multiple devices in bulk.

Restricted Android Enterprise provisioning

Previously, you could enroll Knox Guard activated devices into Android Enterprise as managed devices. With the Knox Guard 24.09 release, Knox Guard activated devices manufactured with Android 15 and higher OS can’t be enrolled into Android Enterprise and managed with a UEM. This blocks IT admins from enabling fully managed and work profile device provisioning. The Fully managed device provisioning mode — also known as device owner (DO) provisioning mode — provides full device management control to the enterprise management app. The Work profile device provisioning mode — also known as profile owner (PO) provisioning mode — allows personal devices to be enrolled as managed devices.

To manage devices with Android Enterprise, you must unblock device provisioning in Knox Guard. Only select partners can submit a request to Samsung admins for Android Enterprise provisioning permissions. With the permission granted, use the Block/unblock Android Enterprise provisioning API to block or unblock device provisioning on select devices or the corresponding Async API to block or unblock device provisioning for multiple devices in bulk.

Learn more about admin features

To learn about features available to admins in this release, see Knox Guard 24.09 release notes in the admin guide.

Back to release notes