PROOF CENTER

How automotive cybersecurity work becomes reviewable evidence

The Proof Center shows how automotive cybersecurity work products move from architecture context to TARA, attack paths, risk treatment, and reviewable evidence — the engineering workflow behind every KAVACH and Agnile programme.

See KAVACH On Your ArchitectureExplore Compliance Hub

WHAT THE PROOF CENTER SHOWS

The Proof Center shows how the automotive cybersecurity workflow is structured — the engineering scenarios, inputs, and work products that move a programme from architecture context to reviewable evidence.

PROOF CATEGORIES

Six workflows the Proof Center covers

  • 01

    Architecture-Aware TARA Workflow

    How vehicle architecture context — ECUs, networks, interfaces, data flows — drives asset, threat, attack-path, and risk-treatment structuring.

  • 02

    Attack Path Review Workflow

    How attack trees and attack paths are constructed, feasibility-reviewed, and connected to risk-treatment decisions.

  • 03

    ISO/SAE 21434 Evidence Workflow

    How work products across Clauses 5–15 connect into one reviewable engineering evidence chain.

  • 04

    UNECE R155 / CSMS Readiness Workflow

    How engineering evidence is structured for CSMS readiness discussions and Annex 5 threat coverage.

  • 05

    AIS 189 / AIS 190 Readiness Workflow

    How one engineering evidence chain supports Indian AIS readiness and UNECE alignment.

  • 06

    KAVACH Manual / Deterministic / AI-Assisted Workflow

    How the three operating modes structure the work, with engineer review as the source of truth in every mode.

ENGINEERING SCENARIOS

How the workflow is structured

Each scenario below walks through a complete engineering workflow — the inputs a programme brings, the work products it produces, and the compliance and trust topics it connects to.

Engineering Workflow

Connected Body Domain Controller TARA Workflow

How a body-domain controller's architecture context drives architecture-aware TARA — from asset identification through damage scenarios, threats, attack paths, risk determination, and risk treatment.

Discuss A Scoped Demo

Inputs required

  • Architecture description of the body-domain controller
  • ECU, interface, and network list with data flows
  • Trust boundaries and external exposure

Outputs produced

  • Structured TARA draft — damage scenarios, threats, attack paths, risk determination, risk treatment
  • Control mapping aligned with ISO/SAE 21434 Clause 15
  • Cybersecurity Case fragments for review

Related compliance

Related trust / deployment

Engineering Workflow

OTA Update Evidence Workflow

How software-update authorisation, dependency analysis, and traceability evidence is structured to support UNECE R156 and AIS 190 alignment.

Discuss A Scoped Demo

Inputs required

  • Software-update process description
  • Dependency information across software, calibration, and configuration
  • Affected-configuration scope

Outputs produced

  • Update authorisation evidence with documented decision criteria
  • Dependency-analysis records
  • Software-update traceability for the affected Vehicle Types

Related compliance

Related trust / deployment

Engineering Workflow

Supplier ECU Cybersecurity Evidence Workflow

How a Tier-1 supplier structures cybersecurity work products and Cybersecurity Interface Agreement evidence so an OEM customer can review it without translation.

Discuss A Scoped Demo

Inputs required

  • ECU architecture and cybersecurity scope
  • OEM evidence-format requirements
  • Cybersecurity Interface Agreement scope

Outputs produced

  • Supplier-side TARA and control evidence
  • Cybersecurity Interface Agreement records
  • OEM-reviewable work products

Related compliance

Related trust / deployment

Engineering Workflow

Vehicle Gateway Attack Path Review

How attack trees and attack paths for a vehicle gateway are constructed, feasibility-reviewed by engineers, and connected to risk-treatment decisions.

Discuss A Scoped Demo

Inputs required

  • Gateway architecture and interface exposure
  • Network topology and external connectivity
  • Relevant threat landscape

Outputs produced

  • Attack trees with structured OR/AND logic
  • Attack paths with engineer-reviewed feasibility reasoning
  • Linkage from attack paths to risk treatment

Related compliance

Related trust / deployment

Engineering Workflow

AIS 189 / AIS 190 Readiness Review

How an Indian programme maps ISO/SAE 21434 engineering outputs to AIS 189 organisational CSMS readiness and AIS 190 vehicle-level readiness — India-ready, globally aligned.

Discuss A Scoped Demo

Inputs required

  • Existing engineering evidence and programme scope
  • AIS readiness questions for the programme
  • Supplier coordination context

Outputs produced

  • Readiness gap analysis against AIS 189 and AIS 190 expectations
  • Evidence-mapping records linking ISO/SAE 21434 outputs to AIS readiness
  • Recommended next-step scope

Related compliance

Related trust / deployment

The Resources section hosts a broader library of engineering scenarios written as educational reference — a deeper technical companion to the workflows above.

REVIEW NEXT

Where reviewers go from here

The Trust Center covers KAVACH deployment, security, and data-handling posture. The Compliance Hub covers the standards and regulations these workflows support.

FAQ

Proof Center FAQ

Want to see the workflow on your own architecture? Bring it.

These scenarios show how the work is structured. A scoped demo runs the same workflow on a real architecture you bring — with clear answers on fit and integration effort.