FOR · INDIAN PROGRAMMES SERVING GLOBAL OEMs
India-ready, globally aligned — AIS 189 and AIS 190 on the same evidence chain you need worldwide
Indian vehicle programmes increasingly serve both domestic approvals and global Type Approval markets. KAVACH maps ISO/SAE 21434 engineering outputs to AIS 189 / AIS 190 readiness without rebuilding the evidence chain.
WHO THIS PAGE IS FOR
This page is for engineering teams operating in India whose vehicle programmes face both AIS 189 / AIS 190 readiness in India and UNECE R155 / R156 expectations from global export markets.
OWNS DECISIONS FOR
What lands on this desk
- AIS 189 CSMS readiness
- AIS 190 Type Approval evidence
- UNECE R155 / R156 alignment for export programmes
- Supplier coordination across Indian and global tiers
BUYER PAIN
Where the friction shows up
AIS 189 / AIS 190 interpretation and audit cadence are still settling — methods diverge across teams
Programmes built for global Type Approval risk reworking evidence for Indian readiness, and vice versa
Supplier coordination across Indian and global tiers compounds the Cybersecurity Interface Agreement burden
Indian and export-market assessment language differs, and translation work happens late in the programme
Documented governance often lags real engineering practice — audit-readiness gaps appear when assessors visit
WHAT YOU NEED TO PROVE
The evidence chain stakeholders expect
- 01
AIS 189 organisational Cybersecurity Management System readiness
- 02
AIS 190 vehicle-level cybersecurity assessment evidence for Indian Type Approval
- 03
Engineering evidence aligned with UNECE R155 / R156 expectations for export programmes
- 04
Supplier-side cybersecurity evidence across Indian and global suppliers
- 05
Software-update governance for AIS 190 and UNECE R156
HOW AGNILE HELPS
Engineering teams who do this work day-to-day
India-based engineering team that has worked through AIS readiness and UNECE-aligned programmes in parallel
AIS readiness sprints — gap reviews against AIS 189 organisational CSMS and AIS 190 vehicle-level expectations
One engineering evidence chain methodology that serves Indian approvals and export-market Type Approval
Supplier coordination support across Indian and global tiers
HOW KAVACH SUPPORTS THE WORKFLOW
The workspace built around this evidence chain
KAVACH produces one engineering evidence chain mapped to ISO/SAE 21434 — the same work products serve AIS 189 / 190 readiness and UNECE R155 / R156 expectations
Architecture-aware TARA aligned with ISO/SAE 21434 Clause 15 — supports the vehicle-level threat coverage AIS 190 expects
Software-update evidence linked to cybersecurity evidence — supports UNECE R156 and AIS 190 alignment
On-premise or customer-dedicated EU VPC deployment keeps sensitive programme data inside the customer-defined boundary
Engineer-in-the-loop review at every stage; AI-assisted acceleration can be configured or disabled per programme
RELATED PAGES
Where to go next
SERVICES & PRODUCT
Engagement paths
FAQ
Questions indian programmes serving global oemss typically ask
Bring a programme. We'll show where the evidence chain holds and where it doesn't.
Sixty-minute working session on a representative architecture. Honest answers on what KAVACH covers cleanly and where engineering services close the gap.