A use case is worth evaluating when it names who owns the device, who can change its firmware and who answers for it years later. Start from your own role. A device maker builds protection into its range. An institution buys devices and needs them to arrive trusted. An operator runs dedicated devices in the field. Otukan’s firmware-level protection serves each situation on Android-based devices, and every use case below shows where Otukan’s part begins and where the device maker, chipset vendor or institution keeps control.
Integration boundary
The integrator changes with the use case. A device maker gives Otukan build access directly. An institution usually works through its supplier, so Otukan agrees the split with the OEM on the institution’s behalf.
Control scope
A kiosk fleet leans on management policy and runtime state, while a government handset leans on hardware-backed keys and signed firmware. Otukan sets out which firmware, hardware and update dependencies apply to each use case.
Qualification
Every use case starts with the same record: the models in scope, who approves updates, and how long devices stay supported. The device maker’s situation is covered on device manufacturers. Kiosk, field and single-purpose devices are covered on dedicated operational devices. Devices an OEM runs for its own staff are covered on OEM internal fleets. Public sector programmes are covered on government mobile device security. Utilities, transport and energy operators should read critical infrastructure mobile device security.