| Element | Content | Evidence for Audit |
|---|---|---|
| Cybersecurity Policy | Scope, objectives (CIA properties), CISO reporting line, minimum training hours | Policy document signed by executive; organisation chart |
| Cybersecurity Culture Programme | Awareness training, secure-by-design principles, responsible disclosure | Training records; completion rates per role; training content |
| Competence Management | Role profiles: security architect, TARA engineer, penetration tester | Competence matrix with qualification and experience per person |
| Management Review | Annual CSMS effectiveness review: KPIs, incidents, findings, improvement actions | Meeting minutes; action log; KPI trend reports |
CSMS Organisational Elements (ISO/SAE 21434 Clause 5)
Cybersecurity Plan per Project
Pythoncybersecurity_plan_generator.py
#!/usr/bin/env python3
# Generate Cybersecurity Plan skeleton per ISO/SAE 21434 Clause 6
csm_plan = {
"project": "Telematics Control Unit (TCU) v4.0",
"version": "1.2",
"scope": "TCU SW + HW; interfaces: LTE, Bluetooth 5.0, CAN gateway, OTA client",
"activities": [
{"id": "CP-01", "activity": "Item Definition",
"owner": "System Architect", "start": "2025-11-01", "end": "2025-11-30",
"exit_criteria": "Item boundary + interface diagram approved by CS Manager"},
{"id": "CP-02", "activity": "TARA",
"owner": "CS Analyst", "start": "2025-12-01", "end": "2026-02-28",
"exit_criteria": "TARA report with all risks treated or accepted, signed by CISO"},
{"id": "CP-03", "activity": "Cybersecurity Concept",
"owner": "CS Architect", "start": "2026-01-15", "end": "2026-03-15",
"exit_criteria": "Security goals allocated to components; requirements in DOORS"},
{"id": "CP-04", "activity": "Security Testing (unit + integration)",
"owner": "CS Test Engineer", "start": "2026-07-01", "end": "2026-08-31",
"exit_criteria": "All TSRs verified; zero critical/high open findings"},
{"id": "CP-05", "activity": "Penetration Testing",
"owner": "External Pentest Firm", "start": "2026-09-01", "end": "2026-09-30",
"exit_criteria": "Pentest report with all critical findings remediated"},
{"id": "CP-06", "activity": "Cybersecurity Validation",
"owner": "CS Architect", "start": "2026-10-01", "end": "2026-10-31",
"exit_criteria": "Validation report confirming security goals satisfied"},
],
}
import json
print(json.dumps(csm_plan, indent=2))Information Security Controls in CSMS
| Control Domain | Control | Implementation |
|---|---|---|
| Access Control | Role-based access to TARA reports, key material, pentest findings | IAM system; need-to-know; quarterly access review |
| Secure Development Environment | Code signing infrastructure, HSM access audit log, binary integrity in CI | Git signing; HSM audit log retention 3 years; checksec in CI |
| Incident Reporting | Breach/incident within 72 hours per OEM PSIRT policy | PSIRT SOP; escalation matrix; 72h SLA monitored |
| Cryptographic Material | Key storage in hardware HSM; no plaintext keys in code or config files | Secret scanning in CI; HSM audit log; key management SOP |
CSMS Audit Process
CSMS Certification Audit Flow
Pre-audit: OEM submits CSMS manual + evidence package
│ Technical Service reviews documents (2–4 weeks)
▼
On-site audit (3–5 days):
├── Day 1–2: Management interviews (CISO, CS Manager, TARA leads)
├── Day 2–3: Process walkthroughs (TARA demo, incident response drill)
└── Day 4–5: Artifact spot-checks (TARA sample, pentest report, CIA samples)
│
▼
Finding categorisation:
├── Major non-conformity: BLOCKS certification; corrective action + re-audit required
├── Minor non-conformity: Corrective action plan within 90 days; certificate issued
└── Observation: Advisory only; no timeline required
│
▼
Certificate issuance (valid 3 years)
│ Annual surveillance audits (1–2 days) verify no regressionSummary
The CSMS is the organisational backbone of automotive cybersecurity compliance — without it, no vehicle type approval is possible under UNECE R155. Building an auditable CSMS requires policy documents, training records, competence matrices, and management review minutes that an external Technical Service assessor can independently verify. The cybersecurity plan per project is the project-level instrument linking the organisational CSMS to specific development activities, deliverables, and exit criteria.
🔬 Deep Dive — Core Concepts Expanded
This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.
Key principles to reinforce:
- Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
- Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
- Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.