Automotive cybersecurity.
From threat analysis to type approval. Across edge, cloud and vehicle.
Vehiclesandroadsidesystemsarenetworkedcomputers.UNECER155makesacertifiedCSMSaconditionoftypeapproval.WebringTARA,HSMintegration,SecOCandpost-quantumplanningbackedbyourownmeasurements.
ISO/SAE 21434 & TARA
Lifecycle cybersecurity per ISO/SAE 21434. TARA for vehicle architectures: assets, threat scenarios, attack feasibility, risk treatment. Output: the evidence type approval requires.
UNECE R155 & CSMS Certification
CSMS aligned with UNECE R155 and ISO/PAS 5112. Processes, governance, incident response, supply chain. Objective: audit-ready for the Technical Service.
Secure Communications: SecOC, MACsec, HSMs
AUTOSAR SecOC for CAN/CAN-FD. MACsec for automotive Ethernet. HSM integration (SHE, EVITA, AURIX, S32G). Secure boot, key management, firmware signing.
Post-Quantum Cryptography Migration
Cryptographic inventory. Quantum-vulnerable components (ECDSA, ECDH, RSA) identified. Migration to ML-KEM, ML-DSA, SLH-DSA, with hybrid schemes where needed.
Frequently Asked Questions
ISO/SAE 21434 is the engineering process. UNECE R155 is the regulation that requires a CSMS for type approval. Following 21434 produces the evidence R155 asks for.
Mandatory for new vehicle types since July 2022 and for all new vehicles since July 2024 in UNECE member states. No certified CSMS, no type approval.
NIST targets 2030 for deprecating RSA, ECDSA and ECDH. The EU roadmap asks for transition plans by 2026 and critical infrastructure migrated by 2030. Vehicles designed today should plan for it.
Telematics units, OTA update paths, V2X interfaces, connected infotainment, OBD-II ports and unauthenticated CAN. Jeep Cherokee 2015 and the Tesla key-fob relay of 2018 used exactly these.