A connected vehicle is a moving network of electronic control units, sensors, gateways, telematics services, diagnostic tools, mobile applications, and cloud infrastructure. Protecting just the cloud service is not enough if attackers can exploit a vehicle update mechanism, impersonate a diagnostic tester, or alter traffic across an in-vehicle interface.<\/p>\n\n\n\n
ISO\/SAE 21434<\/strong> establishes an automotive cybersecurity engineering framework that covers cybersecurity risk management across the lifecycle of road-vehicle electrical and electronic (E\/E) systems, their components, and interfaces. The published first edition is ISO\/SAE 21434:2021. A second edition has been initiated but is not yet the published replacement. There is no official universal maturity-scale ranking of organizations from Level 1 through Level 5<\/strong> in ISO\/SAE 21434.<\/p>\n\n\n\n ISO 26262 concentrates on hazards arising from malfunctioning E\/E behavior and related functional safety engineering. ISO\/SAE 21434 concentrates on cybersecurity threats and risks from malicious or unauthorized actions. Some consequences can overlap: a malicious command may cause a safety-relevant outcome, while an unintentional defect may originate from a different mechanism.<\/p>\n\n\n\n For example, a telematics ECU may be designed to tolerate accidental network faults, but an attacker could attempt to inject unauthorized control messages. The safety team and cybersecurity team must coordinate their analyses without pretending that a Hazard Analysis and Risk Assessment (HARA) is the same as a Threat Analysis and Risk Assessment (TARA)<\/strong>.<\/p>\n\n\n\n The management framework includes organizational cybersecurity management, project-dependent cybersecurity management, distributed cybersecurity activities with suppliers, continual cybersecurity activities, cybersecurity concept, product development, production, operations, maintenance, and decommissioning. Each project needs well-defined work products, responsibilities, decisions, and traceability.<\/p>\n\n\n\n Northstar Mobility supplies a telematics unit with over-the-air (OTA) firmware updates. The unit communicates with a cloud backend, receives update metadata, downloads software, verifies it, and installs it. The engineering team must preserve update authenticity, protect rollback policy, restrict administrative privileges, and maintain reliable recovery after failed updates.<\/p>\n\n\n\n These are teaching examples. A real item definition documents boundaries, interfaces, operational environment, assumptions, dependencies, and supported variants.<\/p>\n\n\n\n Define the cybersecurity manager or responsible function, project cybersecurity plan, responsibilities among OEM, Tier-1 supplier, component manufacturer, and cloud provider, and criteria for reviews and approvals. Supplier-to-customer agreements must clarify work products, security activities, information exchange, vulnerability disclosure, and responsibilities. A generic commercial contract does not automatically provide a sufficient cybersecurity interface arrangement.<\/p>\n\n\n\n Set up engineering traceability through the approved requirements and lifecycle tool. Record unique IDs for assumptions, assets, threat scenarios, TARA outputs, cybersecurity goals, requirements, design decisions, verification methods, and defects.<\/p>\n\n\n\n A TARA is more than running STRIDE against a diagram. It involves structured asset identification, damage scenario assessment, threat scenario identification, attack path analysis, impact determination, attack feasibility evaluation, and cybersecurity risk determination and treatment according to the applicable methodology.<\/p>\n\n\n\n A compact example:<\/p>\n\n\n\nCybersecurity is not identical to functional safety<\/h2>\n\n\n\n
Understand the automotive cybersecurity lifecycle<\/h2>\n\n\n\n
New threats and vulnerabilitiesOrganizational governanceConcept and item definitionTARA and cybersecurity goalsSystem and component requirementsDesign, implementation, and integrationVerification and validationProduction and post-developmentMonitoring, maintenance, and end-of-life<\/pre>\n\n\n\n
A running example: Secure over-the-air firmware updates<\/h2>\n\n\n\n
Element<\/th> Example<\/th><\/tr><\/thead> Item<\/td> Telematics ECU and firmware update functionality<\/td><\/tr> Asset<\/td> Integrity of executable firmware and update authorization<\/td><\/tr> Attack surface<\/td> Update service, cellular link, diagnostic interface, signing pipeline<\/td><\/tr> Damage scenario<\/td> Unauthorized firmware controls or disables device functions<\/td><\/tr> Threat scenario<\/td> Adversary substitutes a malicious image or update manifest<\/td><\/tr> Security objective<\/td> Only authorized, integrity-protected firmware is installed<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Step 1: Establish automotive cybersecurity responsibilities<\/h2>\n\n\n\n
Step 2: Perform a TARA<\/h2>\n\n\n\n