Quantum-Safe OTA Security Architecture for Svashasan OS
Purpose: Our internal reference for how over-the-air (OTA) updates work in Svashasan OS: how an update is built, signed, delivered, verified, installed and recovered, and where the quantum-safe security layer fits in. Scoped to software updates; perception, autonomy, kernel internals and vehicle control are out of scope.
Status note. This is our designed reference architecture. The quantum-safe security layer is subject to interface and capability validation, and its exact modules and deployment interfaces are still to be finalised. It is not yet a deployed or certified quantum-secure OTA product.
Orchestrate · Svashasan
What ships, to which vehicle, when
Release pipeline, signed manifests, compatibility rules, staged rollout and audit.
Protect · Security layer
Cryptography that outlasts the vehicle
Post-quantum signatures, protected delivery and the full key lifecycle.
Recover · Vehicle
Verify locally, never brick
Checks before install, health checks after, and a known-good version always bootable.
1. Why OTA Is a Security Problem
OTA is both a product capability and a safety and security risk. The same channel that lets Svashasan fix a bug across a fleet overnight could, if compromised, push malicious code to every vehicle at once. The architecture starts from the threats, not the features.
Figure 1. Why OTA is a security problem first. The update channel is the one interface built to change vehicle software remotely, so each hop carries its own threat. Threats taken from the Svashasan cybersecurity threat model.
2. The Architecture at a Glance
Four Svashasan OS stages, with a quantum-safe security layer between the cloud and the vehicle and a feedback loop back to both.
Figure 2. The architecture at a glance. The security layer sits between the release pipeline and the vehicle; it supplies cryptography, protected delivery and key lifecycle, while Svashasan OS keeps control of what ships, to which vehicle, and how it installs and recovers.
One update, end to end
Figure 3. One update, end to end. Svashasan OS builds and targets the release, the security layer signs it and protects the channel, and the vehicle verifies everything locally before it installs.
3. Release Pipeline and Signed Manifests
Every update is built, tested across unit, HIL, simulation, security and compatibility suites, then signed in a controlled step. The vehicle never trusts a file; it trusts a signed manifest that describes the file.
Figure 4. The release pipeline. Signing is a controlled, audited step separated from the build, so a compromised build server cannot produce a trusted update.
Anatomy of a signed manifest
Figure 5. What the vehicle checks before it trusts an update. Hashes, versions, dependencies and applicability come from the Svashasan OTA design; the expiry field follows Uptane-style freshness practice and is a recommended addition.
4. The Quantum-Safe Layer
The quantum-safe layer provides post-quantum cryptography, protected update delivery and key management to Svashasan OTA through a defined, API-based security interface. Which capabilities we use is set by what an automotive deployment needs, and each is subject to interface and capability validation.
Figure 6. What the security layer provides. Exact modules and deployment interfaces are still to be finalised; these are the capability areas the OTA design is built around.
Why quantum-safe, and why now
Figure 7. Why plan for quantum-safe cryptography now. Vehicle lifetimes outlast today's cryptographic assumptions; nobody knows when large quantum computers arrive, which is exactly why agility matters more than any single algorithm.
Cryptographic agility
Figure 8. Cryptographic agility. Svashasan OS talks to an abstraction layer, not to an algorithm, so moving from classical to hybrid to post-quantum signatures is a configuration change, not a rewrite. The hybrid option is a recommended transition step.
The key lifecycle
Figure 9. The key lifecycle. Rotation keeps the same trust chain alive with fresh keys; revocation is the emergency branch for a compromised key. The security layer provides key management; Svashasan OS defines the update workflow and authorisation rules.
5. Inside the Vehicle
The Svashasan OS OTA agent receives updates, verifies signed metadata and package integrity, and enforces compatibility and installation policy. Its job is to say no to anything it cannot prove is right for this vehicle.
Figure 10. What the vehicle does with an update. Three checks happen before anything is written; a health check decides commit or rollback afterwards; every path, including rejection, ends in an audit record.
Install without bricking
Figure 11. Atomic install with an inactive slot. The new version is written beside the running one and only becomes permanent after it proves healthy. Applies where the target hardware supports dual-slot storage; otherwise an equivalent recovery path is required.
6. Rolling Out Safely
Figure 12. Staged rollout. Updates widen from bench to engineering fleet to a limited pilot before any wider release, and each gate needs acceptance, not a calendar date.
The ten OTA controls
Figure 13. The ten OTA controls in the Svashasan design, and who carries each. The security layer strengthens the cryptographic controls; Svashasan OS owns the controls that decide whether an update is right for a vehicle.
7. Defence in Depth and Feedback
Figure 14. Defence in depth. The quantum-safe layer complements, rather than replaces, signed metadata, local verification, rollback protection and recovery. An attacker who defeats one layer still meets the next.
Security feedback loop
Figure 15. The feedback loop. Verification failures, key-status events and update outcomes feed security and OTA monitoring, which can stop a rollout, revoke credentials or ship a fix.
8. Responsibility Boundary
Figure 16. Who does what. The security layer provides cryptographic capabilities; Svashasan OS keeps OTA orchestration and update-lifecycle control, and its OS architecture stays ours.
Svashasan OS
Quantum-safe security layer
Owns OTA orchestration and release workflow
Supplies quantum-safe security capabilities
Defines update packages and compatibility rules
Supports cryptographic services and key lifecycle
Controls installation, validation and recovery logic
Protects supported security interfaces and communications
Integrates security services into Svashasan OS
Passes security testing and integration validation before use
End result: quantum-safe OTA for Svashasan OS that protects software-update communications and cryptographic trust, while the OS architecture and update decisions stay with us.
9. Standards Alignment
The design follows the automotive update-security principles of the Uptane Standard and is built to support ISO/SAE 21434 cybersecurity engineering and the UNECE R155 and R156 management systems where they apply.
Figure 17. Standards the design is built to align with, by architecture element. Following their practices is not the same as certification or type approval; that needs OEM-specific evidence and assessment. Mapping is indicative.
10. Status and Next Steps
Figure 18. Where this architecture is on its path. Designed; the proof of concept, security validation and OEM pilot are still ahead.
Open design questions
Which security-layer modules are in scope, and through which interfaces does Svashasan OS call them?
Which post-quantum signature schemes, and do signatures fit the storage and verification-time budget of the target ECUs?
Where do trust anchors and signing keys live: dedicated security hardware, an OEM HSM, or both?
How does the quantum-safe channel behave over constrained or intermittent vehicle connectivity?
What are the acceptance criteria for the proof of concept, agreed before integration starts?
Svashasan OS decides what an update is and whether it belongs on a vehicle; the quantum-safe layer makes sure nobody can forge, read or replay it, today or after quantum computers arrive.