05 · Architecture & Security
Security and data boundaries: permission is responsibility
An MDM platform inherently holds device-level privileges, so OneNexus MDM builds permission governance and operation audit into the product, and defines the security boundary in writing at project kick-off as a baseline deliverable.
- Deployed in an environment you control — the system runs on customer-provided Tomcat and PostgreSQL, in your data centre or a hosted cloud; the data path never leaves your infrastructure.
- Encrypted transport — HTTPS certificates can be issued by your own operations team; the link between console and device is encrypted end to end.
- Least privilege, separated roles — user, role and device group form a three-layer boundary; accounts receive only the scope they need.
- Traceable operations — key actions are written to the audit log; platform operations and logs are auditable for security and compliance review.
- Controlled artefacts — APKs, images and provisioning scripts are managed locally, so delivery never introduces uncontrolled sources.
- Minimum necessary data collection — only the Android APIs and MDM permission data the platform needs are collected; exact fields are confirmed on site during implementation.
“What level of account touched this device, and what did it do?” — answered during initialisation and acceptance, as a check item for preventing privilege escalation and for customer sign-off; the boundary is agreed before any device enrolls.