Why this environment matters
For in-vehicle infotainment systems, the system runs media, navigation, app integration, voice control and passenger connectivity inside the vehicle. The risk extends beyond a conventional endpoint: complex parsers, browsers and third-party apps create a large attack surface close to more sensitive vehicle networks. A NØNOS deployment concept would treat every software component, data source and device interface as separately authorised rather than assuming that anything running on the host should be broadly trusted.
The security challenge
Connected vehicles combine public-facing radios, third-party content, diagnostics and hardware that can affect motion. Security therefore has to control both information flow and authority over physical functions. For this system, the primary attack path is that complex parsers, browsers and third-party apps create a large attack surface close to more sensitive vehicle networks. Conventional general-purpose hosts often place parsers, management tools, network services and privileged drivers in one broad trust domain, allowing a flaw in a low-value feature to reach a high-consequence function.
How the capsule model could help
NØNOS could be placed at the operator, gateway, edge or application-compute layer and configured to confine media codecs, browsers, phone projection and voice services to separate capsules that lack ambient access to safety-relevant buses. The most relevant controls are signed capsule updates, hardware capability isolation, verified boot and attestation and minimal persistent state. This would make privileges explicit: a service that reads a sensor, displays data or contacts a cloud API would not automatically be able to issue a physical command or use a signing key.
Deployment requirements
Any in-vehicle deployment would require OEM integration, hardware-specific drivers, deterministic timing analysis, functional-safety assessment and validation against the vehicle's existing safety architecture.
Current public-beta limitations, hardware support and application availability must be assessed before any pilot. Neither this use case nor an industry source establishes NONOS certification or a current customer deployment.
Who could buy or integrate it?
- Vehicle OEMs choosing cockpit computing platforms
- Cockpit Tier 1 suppliers integrating application environments
- Connected-service developers supplying approved vehicle applications
Industry examples: Aptiv, Bosch. These are research prospects, not represented as NONOS customers, partners or endorsers.