Description

This curriculum spans the breadth of an automotive cybersecurity management program, equivalent in scope to a multi-phase advisory engagement supporting the implementation of ISO/SAE 21434 across design, supply chain, operations, and governance functions within a vehicle manufacturer.

Module 1: Threat Modeling and Risk Assessment for Automotive Systems

Conducting STRIDE-based threat modeling on vehicle ECUs to identify spoofing, tampering, and information disclosure risks during system design.
Integrating attack trees into architecture reviews to quantify exploit paths targeting the CAN bus and gateway modules.
Selecting appropriate risk scoring methodologies (e.g., DREAD vs. CVSS) for prioritizing vulnerabilities in telematics units.
Facilitating cross-functional workshops with engineering and safety teams to reconcile ISO 21434 risk criteria with functional safety (ISO 26262) requirements.
Documenting and maintaining threat model artifacts under version control to support audit readiness and design traceability.
Updating risk registers in response to new threat intelligence, such as emerging CAN injection techniques observed in third-party aftermarket devices.

Module 2: Secure Architecture Design and System Integration

Specifying hardware security modules (HSMs) for secure boot and cryptographic operations in domain controllers based on performance and key management requirements.
Designing secure communication zones and conduits between IVI, ADAS, and body control modules using AUTOSAR Secure Communication (SecOC).
Implementing firewall policies at the central gateway to restrict unauthorized message flows between high- and low-criticality networks.
Evaluating the trade-offs between centralized vs. distributed security architectures for OTA update validation.
Enforcing secure inter-ECU communication using message authentication codes (MACs) with symmetric key distribution schemes.
Integrating intrusion detection systems (IDS) at network boundaries with real-time alerting and response throttling to avoid false positives affecting vehicle operation.

Module 3: Supply Chain and Third-Party Risk Management

Requiring suppliers to deliver Software Bill of Materials (SBOMs) for embedded Linux systems to track open-source component vulnerabilities.
Conducting security assessments of Tier 2 semiconductor vendors to verify secure manufacturing and programming practices for cryptographic keys.
Enforcing contractual clauses requiring vulnerability disclosure timelines and patch delivery commitments from software providers.
Validating the integrity of third-party firmware updates using code signing and secure boot chains before integration.
Managing risk from legacy components by defining compensating controls when suppliers no longer provide security support.
Performing on-site audits of supplier development environments to confirm adherence to secure coding and change management procedures.

Module 4: Vehicle Lifecycle Security Operations

Establishing a vehicle security operations center (vSOC) to monitor and correlate security events from telematics and ECU logs.
Developing playbooks for responding to CAN bus anomalies, including procedures for safe degradation and driver notification.
Implementing secure remote diagnostics access with multi-factor authentication and session logging for service technicians.
Coordinating with fleet operators to prioritize and deploy security patches based on vehicle usage and exposure profiles.
Managing cryptographic key lifecycle events such as rotation, revocation, and emergency deactivation for compromised vehicles.
Documenting incident response actions in accordance with ISO/SAE 21434 process evidence requirements for regulatory audits.

Module 5: Over-the-Air (OTA) Update Security

Designing dual-signed update packages using both manufacturer and PKI infrastructure keys to prevent unauthorized rollouts.
Implementing delta update verification mechanisms to ensure partial patches are not tampered with during transmission.
Configuring rollback protection to prevent downgrade attacks while allowing recovery from failed updates.
Validating update integrity at the ECU level using hardware-backed secure boot before applying new firmware.
Segmenting OTA traffic on cellular networks using dedicated APNs and IPsec tunnels to reduce exposure to MITM attacks.
Monitoring update success rates and failure modes across vehicle fleets to detect potential exploitation attempts.

Module 6: Compliance, Standards, and Regulatory Alignment

Mapping organizational security controls to ISO/SAE 21434 requirements for cybersecurity management system (CSMS) certification.
Preparing audit documentation for UNECE WP.29 R155 compliance, including risk assessment records and incident response plans.
Aligning vulnerability disclosure policies with regional regulations such as GDPR for handling personal data in security events.
Integrating cybersecurity type approval processes into vehicle homologation workflows for global markets.
Updating compliance posture when new attack vectors are classified under regulatory threat catalogs (e.g., ENISA threat landscape).
Coordinating with legal teams to classify security incidents as reportable under mandatory breach notification laws.

Module 7: Penetration Testing and Red Team Operations

Planning physical access assessments targeting OBD-II ports with tamper-resistant logging enabled on diagnostic gateways.
Executing wireless penetration tests on Bluetooth, Wi-Fi, and cellular interfaces to identify authentication bypass flaws.
Simulating ECU reprogramming attacks using bench testing of exposed debug interfaces (JTAG, UART).
Validating the effectiveness of runtime protection mechanisms by injecting malicious CAN messages during vehicle operation.
Reporting findings using standardized formats (e.g., MITRE ATT&CK for Vehicles) to enable consistent remediation tracking.
Conducting post-engagement reviews with engineering teams to verify patch efficacy and prevent recurrence.

Module 8: Security Governance and Executive Oversight

Establishing a cybersecurity steering committee with representation from engineering, legal, and product leadership to prioritize initiatives.
Defining key risk indicators (KRIs) such as mean time to patch and exploit attempt frequency for board-level reporting.
Allocating budget for security tooling (e.g., fuzzing frameworks, static analysis) based on historical vulnerability data.
Overseeing the integration of security gates into stage-gate product development processes.
Reviewing third-party audit findings and mandating corrective action plans with defined ownership and deadlines.
Ensuring continuity of security operations during organizational changes, such as mergers or supplier transitions.