Impact Rating & Risk Determination - Automotive Cybersecurity

Impact Category Ratings (ISO/SAE 21434 Table 1)

Category	Level 0	Level 1	Level 2	Level 3
Safety (S)	No injury	Light injury (S1)	Severe/life-threatening (S2)	Fatal (S3)
Financial (F)	Negligible	Moderate ≤ €1M (F1)	Significant €1M–10M (F2)	Severe > €10M (F3)
Operational (O)	No degradation	Minor (O1)	Significant (O2)	Loss of primary function (O3)
Privacy (P)	No violation	Minor violation (P1)	Severe violation (P2)	Life-affecting violation (P3)

💡 Overall Impact = Highest Category

When a damage scenario has ratings across multiple categories (e.g., S3 for safety + F2 for financial + O3 for operational), the overall impact rating equals the highest single category — S3 in this example. This ensures safety consequences always dominate the risk calculation. A threat with S3 impact requires treatment regardless of how low the financial or operational impact is.

Impact Rating Procedure

Pythonimpact_rating.py

#!/usr/bin/env python3
# ISO/SAE 21434 impact rating per damage scenario

damage_scenarios = [
    {
        "id": "DS-07",
        "description": "Attacker injects false ABS commands causing uncontrolled deceleration at highway speed",
        "safety":      3,  # S3: potentially fatal multi-vehicle collision
        "financial":   2,  # F2: recall cost €1M–10M
        "operational": 3,  # O3: complete loss of braking function
        "privacy":     0,  # P0: no privacy impact
    },
    {
        "id": "DS-11",
        "description": "Attacker reads GPS location history via Bluetooth without authentication",
        "safety":      0,  # S0: no safety impact
        "financial":   1,  # F1: minor GDPR fine
        "operational": 0,  # O0: no operational impact
        "privacy":     2,  # P2: severe PII violation — tracking of individual
    },
    {
        "id": "DS-03",
        "description": "OTA update unavailable for 72 hours due to DoS on backend",
        "safety":      0,  # S0: no immediate safety impact
        "financial":   1,  # F1: customer satisfaction impact
        "operational": 2,  # O2: significant — security patches delayed
        "privacy":     0,
    },
]

for ds in damage_scenarios:
    ratings = [ds["safety"], ds["financial"], ds["operational"], ds["privacy"]]
    overall = max(ratings)
    level_names = {0:"Negligible", 1:"Low", 2:"Significant", 3:"Critical/Severe"}
    print(f"[{ds['id']}] {ds['description'][:60]}")
    print(f"  S:{ds['safety']} F:{ds['financial']} O:{ds['operational']} P:{ds['privacy']}")
    print(f"  → Overall Impact: {overall} ({level_names[overall]})")
    print()

Risk Value Matrix: Impact × Feasibility

	High Feasibility	Medium Feasibility	Low Feasibility	Very Low Feasibility
S3 / Critical	Unacceptable	High	Medium	Low
S2 / Severe	High	Medium	Low	Negligible
S1 / Moderate	Medium	Low	Negligible	Negligible
S0 / No harm	Low	Negligible	Negligible	Negligible

Risk Treatment Documentation

Pythontara_risk_record.py

#!/usr/bin/env python3
# TARA risk treatment record: original risk → countermeasure → residual risk

risk_records = [
    {
        "threat_scenario": "TS-09: Remote attacker obtains extended UDS session",
        "original_risk": {
            "impact": "S2/F2", "feasibility": "High", "risk_value": "Unacceptable"
        },
        "treatment": "Reduce",
        "countermeasures": [
            "CM-09.1: Require SecurityAccess 0x27 with 256-bit random challenge before extended session",
            "CM-09.2: Enforce TLS 1.3 mTLS for all remote diagnostic connections (OEM client cert required)",
        ],
        "residual_risk": {
            "impact": "S2/F2",      # unchanged — consequence same if broken
            "feasibility": "Very Low",  # need forge mTLS cert + bypass seed-key: ET > 6 months
            "risk_value": "Acceptable",
        },
        "review_trigger": "New CVE published for TLS library used in remote diagnostic stack",
        "sign_off": "CISO sign-off 2026-03-15",
    },
]

for r in risk_records:
    print(f"Threat: {r['threat_scenario']}")
    print(f"  Original:  {r['original_risk']['impact']} × {r['original_risk']['feasibility']} = {r['original_risk']['risk_value']}")
    print(f"  Treatment: {r['treatment']}")
    for cm in r['countermeasures']: print(f"    → {cm}")
    print(f"  Residual:  {r['residual_risk']['impact']} × {r['residual_risk']['feasibility']} = {r['residual_risk']['risk_value']}")
    print(f"  Review trigger: {r['review_trigger']}")
    print()

Summary

Impact rating is objective: use ISO/SAE 21434 Table 1 definitions to assign S/F/O/P levels per damage scenario, then take the highest as the overall impact. Combined with the AFR-derived feasibility level, the risk matrix produces a risk value that drives the treatment decision. Every Unacceptable and High risk requires a documented countermeasure, a recalculated residual risk, and a review trigger tied to specific events (new CVE, architecture change, new attack research) — not just an annual review date.

🔬 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.