ARM TrustZone · SIM Governance · MVNO-Native
A Rust + WebAssembly mobile OS where MVNO operations run natively on the microkernel stack. Every SIM activation, data policy change, and roaming agreement is a CITADEL governance event — auditable, immutable, NIS2-compliant.
From ARM TrustZone hardware to the secure dialer — every layer enforces isolation. MVNO operations run at L3 inside the microkernel stack.
Mobile Virtual Network Operator: provides mobile services without owning spectrum. Every operation is a governance event — auditable under NIS2 Article 21.
Full SIM lifecycle management with cryptographic Kerkese submission, MARSHAL evaluation, and immutable WORM audit trail.
Remote eSIM provisioning and profile switching. Every profile change governed by CITADEL with full audit trail.
Per-user and per-service data allowances. Policy changes require regulatory evidence reference through Gate 4.
Voice over IP through MVNO network. Calls encrypted end-to-end with hash integrity verification.
Roaming configuration enforces Separation of Duties. CDR hashes stored in WORM chain for regulatory proof.
Isolated network slices per service tier. Each slice operates within a dedicated CITADEL-governed sandbox.
Every MVNO operation passes through CITADEL MARSHAL gates. All outcomes are written to the immutable WORM chain.
Security starts at silicon. ARM TrustZone provides the hardware root of trust.
Hardware isolation between secure and non-secure worlds. Cryptographic keys never leave the Secure Enclave. CITADEL runtime operates in the secure world.
Dedicated security processor for key storage, biometric validation, and attestation. Ed25519 signing keys hardware-bound.
Trusted Platform Module for measured boot, platform integrity verification, and sealed storage. Boot chain hashed into WORM log.
Radio Interface Layer runs as an isolated user-space process. Baseband has zero access to application memory or CITADEL governance data.
MVNO operations touch critical infrastructure — NIS2 Article 21 applies fully.
Every SIM activation and data policy change is a governance event. Article 21 measures enforced at OS level through CITADEL controls.
User data isolation via grid sandboxes. CDR records hashed and stored in WORM chain. PII cannot leak between operator and application cells.
Secure-by-default mobile configuration. Hardware-attested boot chain. OTA updates governed by MARSHAL gates.
Communications metadata protected at OS level. VoIP encrypted end-to-end with hash integrity verification in WORM log.
Regulatory proof of policy enforcement for national telecom authorities. WORM chain provides immutable compliance evidence.
Digital identity wallets secured in ARM TrustZone Secure Enclave. CITADEL MARSHAL governs identity lifecycle operations.