| Knox | |
|---|---|
| | |
| Developer | Samsung |
| Initial release | March 2013 |
| Stable release | 3.12 / 10 July 2025 [1] |
| Operating system | Android and Tizen |
| Website | www |
Samsung Knox is a mobile device management (MDM) and trusted computing framework pre-installed on most Samsung mobile devices, and implements ARM TrustZone in hardware. It allows the management of work devices, such as employee mobile phones, interactive kiosks, and barcode scanners. [2] Like other MDMs, Knox allows organizations to control a device's pre-loaded applications, settings, boot-up animations, home screens, and lock screens. [3]
Knox provides trusted computing and mobile device management (MDM) features. Knox's hardware is based on an implementation of ARM TrustZone, a bootloader ROM, and secure boot (similar to dm-verity and AVB). [4] [5] These trusted computing environments are used to store sensitive data, like cryptographic materials and certificates. [6]
MDM allow businesses to customize their devices for their needs. IT administrators can register new devices, identify a unified endpoint management (UEM) system, define the organizational rules that govern the use of devices, and upgrade device firmware over-the-air. [7] Knox's MDM services are registered and accessed through the web, [8] APIs, or proprietary SDKs. [9]
A few Samsung devices with Knox were approved for US governmental use in 2014, as long as they're not used to store classified data. [10]
Since Android 8, Knox is used to prevent root access to apps even after a successful rooting. [11]
In October 2014, a security researcher discovered that Samsung Knox stores PINs in plain text rather than storing salted and hashed PINs and processing them by obfuscated code. [12]
In May 2016, Israeli researchers Uri Kanonov and Avishai Wool found three vulnerabilities in specific versions of Knox. [13]
Several security flaws were discovered in Knox in 2017 by Project Zero. [14] [15]
Samsung Knox devices use an e-fuse to indicate whether or not an "untrusted" (non-Samsung) boot path has ever been run. The e-Fuse will be set in any of the following cases:
When set, the text "Set warranty bit: <reason>" appears. Once the e-fuse is set, a device can no longer create a Knox Workspace container or access the data previously stored in an existing Knox Workspace. [17] In the United States, this information may be used by Samsung to deny warranty service to devices that have been modified in this manner. [18] Voiding consumer warranties in this manner may be prohibited by the Magnuson–Moss Warranty Act of 1975, at least in cases where the phone's problem is not directly caused by rooting. [19] In addition to voiding the warranty, tripping the e-fuse also prevents some preinstalled apps from running, such as Secure Folder and Samsung Pay. [20] For some older versions of Knox, it may be possible to clear the e-fuse by flashing a custom firmware. [21]
Galaxy AI was first introduced on the Galaxy S24 series and later expanded to the Galaxy S25 series and foldable models such as the Samsung Galaxy Z Fold 7 and Samsung Galaxy Z Flip 7. On these devices, Samsung uses Knox as the security platform for selected Galaxy AI features. [22] [23] These features use on-device processing components, including the Personal Data Engine, which creates personalized outputs from data stored locally on the device. Information used or generated by these functions is saved in Knox Vault, [24] a hardware-backed secure environment designed to keep sensitive data separate from the main operating system. Some Galaxy AI features that operate across multiple Samsung devices use encrypted communication channels provided by Knox. [25] Users can also choose settings that limit cloud AI processing or require features to run only on the device. In enterprise environments, administrators using Knox Manage or other Knox tools can turn specific Galaxy AI features on or off, or restrict them based on organizational policies. [26]
Installing Magisk WILL trip your Knox Warranty Bit, this action is not reversible in any way.
The sole purpose of this fuse-burning action is to memorize that a kernel or critical initialization scripts or data that is not under Samsung's control has been put on the device. Once the e-fuse bit is burned, a Samsung KNOX-enabled device can no longer create a KNOX Container or access the data previously stored in an existing KNOX Container.
Some apps like Samsung Pay, Samsung Pass, Samsung Health, and Secure Folder will also stop working when Knox is tripped, albeit you can use unofficial workarounds to get some of them to work again.