automotive-security

Implements automotive cybersecurity controls aligned with ISO 21434, ISO 26262, and AUTOSAR 4.4.

7|2|Updated May 19, 2026
One-click install
npx skills add https://github.com/pangzhenying2025/hermes-automotive-skills --skill automotive-security-pangzhenying2025
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: automotive-security
Source: https://github.com/pangzhenying2025/hermes-automotive-skills/tree/main/skills/automotive-security
Command: npx skills add https://github.com/pangzhenying2025/hermes-automotive-skills --skill automotive-security-pangzhenying2025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automotive engineers need structured guidance for designing and validating security controls across ECU software, but security requirements are scattered across standards like ISO 21434, ISO 26262, and AUTOSAR. This Skill consolidates 198 security topics into one reference covering authentication, encryption, secure boot, secure OTA, and threat modeling. ## Core Features & Use Cases - Security Domain Coverage: Provides guidance across 11 subdomains including authentication, encryption, intrusion detection, key management, penetration testing, secure boot, secure communication, secure OTA, threat modeling, and vulnerability assessment. - Standards Alignment: Maps work to ASPICE Level 3, AUTOSAR 4.4, ISO 21434, and ISO 26262 with a consistent analyze-design-implement-validate workflow. - Use Case: When designing a secure OTA update mechanism for a production ECU, use this Skill to structure the threat model, select key management and secure boot controls, and produce the technical specification, implementation, test cases, and safety documentation. ## Quick Start Use the automotive-security skill to design a secure boot and secure OTA update flow for an AUTOSAR-based ECU compliant with ISO 21434.

Frequently Asked Questions about automotive-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement secure boot for an automotive ECU?▼

Follow the secure boot topics in this Skill: analyze requirements against ISO 21434 and ISO 26262, design the boot chain following AUTOSAR patterns, implement in C/C++, and validate with test cases and safety documentation.

How to perform threat modeling for automotive systems under ISO 21434?▼

Use the threat modeling topics to structure a TARA workflow: identify assets and attack surfaces, assess risks, and derive security goals. The Skill aligns the analysis with ISO 21434 and produces the required technical specification and documentation.

What standards does this automotive security guidance cover?▼

It covers ASPICE Level 3, AUTOSAR 4.4, ISO 21434 for cybersecurity engineering, and ISO 26262 for functional safety, applied consistently across all 198 security topics.

Does this Skill support secure OTA update design?▼

Yes, it includes 18 secure OTA topics covering update authentication, key management, and secure communication, combined with secure boot guidance to protect the full update chain on production ECUs.

What tools are required to apply this automotive security guidance?▼

The Skill assumes an AUTOSAR toolchain, MATLAB/Simulink, static analyzers such as Polyspace or Klocwork, and Vector CANoe/CANalyzer for network-level validation of security controls.