ISO 21434: Asset Identification and Damage Scenarios — A Worked Example

Date
2026-09-08
Location
Online
Host
Zach L

About this event

A live 30-minute expert session on Asset Identification and Damage Scenarios — A Worked Example (ISO 21434 — Automotive Cybersecurity). What We'll Cover: What asset identification is and where it sits at the start of the ISO/SAE 21434 TARA in Clause 15 Step-by-step: enumerate item functions, derive assets, assign C-I-A properties, and write damage scenarios for a body control ECU How asset lists and damage scenarios map to Clause 15.3 work products and feed threat scenario derivation Common mistakes: listing every signal as an asset, vague damage scenarios, and missing safety-related impacts The asset-to-damage-scenario traceability an auditor expects to see in the TARA report Related topics: asset identification · damage scenarios · tara · iso 21434 clause 15 · cybersecurity properties ·

Topics

Registration

View event page

About Functional Safety Foundations

This online session delivers expert-led instruction on the regulatory landscape and implementation approach for Functional Safety Foundations.

The cross-sector fundamentals underlying every functional safety standard: risk as severity × likelihood, the safety function concept, integrity levels, the safety lifecycle, and the split between random and systematic failures.

What it regulates

Shared vocabulary and reasoning: hazard → risk → risk reduction allocation → safety requirement → verified implementation → maintained integrity in operation.

Who must comply

Everyone entering the field — the conceptual base of the entire catalog.

Key requirements of Functional Safety Foundations

  • Hazard and risk fundamentals
  • Safety function anatomy: sensor-logic-actuator with defined safe state
  • Integrity ladders (SIL/PL/ASIL/DAL) as risk-reduction currencies
  • Random vs systematic failure treatment
  • Lifecycle and management of functional safety incl. competence

Key concepts: Functional Safety Foundations

Functional safety management
Planning, competence, documentation and assessment wrapped around technical work.
Random vs systematic
Hardware wear-out/chance failures quantified statistically versus design/process errors controlled by rigor.
Risk reduction allocation
Distributing required risk reduction among mechanical design, safeguards, control functions and procedures.
Safe state
The defined condition a function drives the equipment to on demand or fault.

Frequently asked questions: Functional Safety Foundations

Why can't testing alone prove safety?

Rare-event targets (like 1e-7/h) are unverifiable by test duration, and systematic errors evade random testing — hence the standards' dual machinery of quantified hardware analysis plus process rigor and independent assessment.

Standard information based on the published text of Functional Safety Foundations. Event content is provided by the host. For authoritative guidance, consult the official standard body.