Automotive Skills Autonomous
c21a84a6ae
Autonomous daily run (Fri DOCS). - CHANGELOG.md [Unreleased] staged with W23 polish (cs-concept, tara, fmeda) and docs entries - New example README stubs: cs-concept-builder, tara-builder, fmeda-builder (coverage 7.9% -> 11.8%) - STATUS.md regen restores canonical domain spread (safety=15, quality=10) from Tue 2026-06-02 rules - Open issues: 12 (was 13 Thu - external delta, no autonomous label/close actions this run) Generated by automotive-skills-daily-standup scheduled task.
1.3 KiB
tara-builder — Example
What this skill produces: An ISO/SAE 21434 Clause 15 Threat Analysis and Risk Assessment (TARA) xlsx with assumptions, asset inventory, STRIDE-coverage threat catalog, impact / feasibility analysis, risk-determination matrix, treatment decisions, and derived cybersecurity goals — audit-ready for ISO/SAE 21434 concept-phase work products and UN R155 type-approval evidence.
Typical input shape: Item definition (system identity, cybersecurity-relevant assets), threat scenarios per STRIDE category, impact ratings (safety / financial / operational / privacy), feasibility ratings (elapsed time, expertise, knowledge, window of opportunity, equipment), and an existing-controls inventory.
Expected output: <item>-tara.xlsx — multi-tab workbook (Assumptions, Assets, STRIDE Threat Catalog, Impact, Feasibility, Risk Matrix, Treatment, Derived CS Goals, Traceability) with risk value auto-computed from impact × feasibility lookup and CAL-level color coding.
Sample I/O: Input a body-control ECU asset list (12 assets) + 28 threat scenarios → Output BCM-tara.xlsx with 28 threats rated, 9 high-risk items flagged, and 6 cybersecurity goals derived for hand-off to cs-goals-builder.
Run: Trigger by phrasing, e.g. "Build a TARA for the body control module — 12 assets and 28 STRIDE threats".