With Otukan, the institution keeps control of the data, keys and administrative functions in its mobile device security programme, and every exception is agreed in writing. Otukan designs each deployment against four dimensions of control: where data is stored, who operates the system, who holds the keys, and who can change the technology. You choose where Otukan’s services run and who operates them. Boot signing keys held by the device maker or chipset vendor stay with them, and Otukan shows exactly how releases signed with those keys are approved and verified.
Control dimensions
Sovereignty is often reduced to data location. For device security, location is one of four questions, and Otukan answers all four for your programme.
| Dimension | Question Otukan answers with you | What Otukan puts in writing |
|---|---|---|
| Data location | Where are device data, logs, telemetry and backups stored and processed? | Every flow, including diagnostics and support copies |
| Operational access | Who can administer the system, change device policy or read logs? | Roles, locations and approval for each |
| Keys | Who holds the keys that sign updates, verify attestation and encrypt data? | Custody and rotation per key type |
| Technology ownership | Who can change the code, rebuild the firmware and keep it running? | The builds, tools and documentation handed over |
Data location
Otukan lists every place device-related data goes: management servers, update servers, attestation verification, logs and backups. Flows that exist only during support or incident response are listed too.
Operational access
Your staff run the system day to day. Otukan separates operating the system from changing it, and records which roles, if any, need access from outside your institution.
Keys
Keys for update signing, attestation verification and data encryption are held under the custody arrangements you set for each key type. Otukan anchors keys in hardware on chipsets that provide a trusted execution environment or secure element. Some device keys are provisioned at manufacture, and Otukan builds your verification around them.
Technology ownership
Otukan hands over the builds, tools and documentation for your programme, so you know what remains with you and who can produce a security patch at every stage.
Deployment options
Otukan’s deployments differ in where the management and verification services run and who operates them. You choose the option that fits your requirements, and Otukan confirms it per model and operating system version during qualification, with a data-flow review and a control matrix.
| Deployment option | Data location | Operational access | Keys | What Otukan provides |
|---|---|---|---|---|
| Institution-hosted, institution-operated | Your environment | Your staff | You hold service keys; OEM usually holds boot keys | Update and patch delivery into your environment |
| Institution-hosted, Otukan-supported | Your environment | Your staff, with approved Otukan support | As above | Recorded, withdrawable support access |
| Isolated network | Your environment, with no external connection | Your staff on site | You hold service keys | A controlled transfer path for updates and expected values |
| Otukan-hosted | Otukan’s environment, in an agreed location | Otukan staff | Split per key type, agreed in writing | Data export and deletion on request |
Responsibilities and support access
Every party in the device chain affects control, so Otukan names each one and what it can reach. The split below applies to Android-based devices whose firmware an OEM or ODM builds. For iOS devices, Apple holds the boot chain and firmware signing.
- Device maker (OEM) and ODM. Build the firmware and usually hold the boot and update signing keys. Otukan agrees with them how releases are approved.
- Chipset vendor. Owns the boot ROM, board support package and hardware security features. Otukan documents what it can update and how.
- Otukan. Builds and maintains the embedded protection and services. Otukan states which systems, logs and devices its staff can reach.
- Hosting and network providers. Where services run outside your environment, Otukan confirms location, subcontractors and access to stored data.
For every Otukan support session, you decide:
- Who can connect, from where, and under whose approval.
- How the session is recorded, and who reviews the records.
- How access is withdrawn, and what continues to run when it is.
- How a security incident is reported, and within which process.
What a sensitive public-sector programme should specify is set out on government mobile device security. Otukan’s own approach to security and trust is covered on Otukan security and trust. Who integrates and maintains each layer is covered on deployment and control. For the wider programme, see mobile device security.