Topic starter
11/11/2026 6:01 pm
TL;DR: Cybersecurity assurance levels in ISO/SAE 21434 fix the rigor of verification, review independence and exploratory testing based on worst-case impact and attack reach, according to Block Harbor. Vehicle programmes need a shared assurance baseline before design changes make risk arguments harder to compare.
Editorial analysis by NHI Mgmt Group, based on content published by Block Harbor: “Cybersecurity Assurance Levels in Product Development Lifecycle”.
Key questions
Q: What does a higher assurance level change in vehicle cybersecurity testing?
A: A higher assurance level increases the depth, rigour, and evidence expected in vehicle cybersecurity testing.
Q: How should suppliers use assurance levels in interface agreements?
A: Suppliers should use assurance levels to fix the expected security depth for each interface, including authentication, authorisation, message integrity, diagnostic access, and update channels.
Q: How is a cybersecurity assurance level determined in automotive security?
A: A cybersecurity assurance level is set from the worst credible impact of a threat scenario and the attack vector that makes the item reachable.
Practitioner guidance
- Define CAL in the concept phase Assign the assurance level from worst-case impact and attack vector before detailed design starts, then lock the rationale into the programme record.
- Use CAL to scope verification depth Expand fuzzing, penetration testing and interaction testing as the level rises, so test effort matches the confidence the programme needs.
- Separate reviewer independence from authoring teams Map higher assurance levels to independent verification and assessment roles, not just a second pair of eyes inside the same delivery team.
Bottom line: Cybersecurity assurance levels are a governance tool for automotive programmes, translating threat severity and reach into a fixed assurance target.
Glossary terms: Cybersecurity Assurance, Targeted Attack Feasibility, Cybersecurity Interface Agreement, Threat Assessment And Risk Analysis
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:08 pm
CAL is a supply-chain governance mechanism, not a control catalogue. Its value is that it gives customers and suppliers a shared assurance target before implementation choices diverge. That makes it easier to argue about evidence quality, review independence and verification depth without pretending the rating itself secures the vehicle. Practitioners should treat it as the governance layer above engineering controls, not as a substitute for them.
A question worth separating out:
Q: What is the difference between fuzz testing and penetration testing in automotive security?
A: Fuzz testing sends malformed, unexpected, or random inputs to find crashes, parsing flaws, and memory-safety bugs. Penetration testing is a goal-driven attack simulation that tries to exploit realistic weaknesses in systems, interfaces, and configurations. In automotive security, fuzzing is usually broader and more automated, while penetration testing is more targeted and scenario based.
👉 Read our full editorial: Cybersecurity assurance levels set test depth for automotive risk