As automotive SoCs grow in size, heterogeneity, and software content, meeting ISO 26262 ASIL targets requires scalable verification, connected safety workflows, and evidence-ready outputs. Synopsys helps automotive teams close on ASIL D programs with confidence. 

What's New for Automotive Safety Engineers

Technical whitepapers, articles, and webinars to help automotive semiconductor teams navigate ISO 26262 requirements, demonstrate ASIL compliance, and reduce sign-off risk on complex SoCs.

Key Benefits

Trusted by Leading Automotive Innovators

How Synopsys Helps Meet ISO 26262 Requirements for Automotive SoCs

Increasing SoC complexity and ASIL expectations

Challenge:  Automotive SoCs are larger, more heterogeneous, and more software-driven—while safety expectations continue to rise, including ISO 26262 ASIL D programs. 
How Synopsys helps:  Scalable verification and safety analysis workflows built for complex SoCs, helping teams validate safety mechanisms and maintain verification rigor as designs grow.

Related Resources

Aligning safety requirements across hardware, firmware, and ISO 26262 software

Challenge: Safety goals and functional safety requirements can drift from implementation when artifacts live in different tools and teams. 
How Synopsys helps:  Safety planning and traceability capabilities that connect safety goals and requirements to architecture, implementation, and verification results—helping teams identify gaps earlier and keep evidence consistent.

Related Resources

Proving diagnostic coverage with scalable fault injection

Challenge:  Fault campaigns can become a schedule bottleneck, especially when teams need measurable results to justify safety mechanism effectiveness. 
How Synopsys helps:  High-performance fault simulation and targeted campaigns that scale to large designs and produce clear diagnostic coverage outputs aligned to ASIL objectives.

Related Resources

Getting earlier visibility into safety status and closure risk

Challenge: Teams often discover coverage gaps and safety issues late—when changes are expensive and schedules are tight. 
How Synopsys helps:  Earlier insight into verification progress and safety closure trends so teams can prioritize the right fixes sooner and reduce rework near tape-out.

Related Resources

Reducing evidence overhead for reviews and assessment readiness

Challenge: ISO 26262 programs can stall on documentation—collecting artifacts, maintaining traceability, and preparing for reviews. 
How Synopsys helps: Centralized safety management and evidence collection to support consistent reporting and assessor-ready documentation, reducing manual effort and improving repeatability across projects.

Related Resources

Solutions for Automotive Functional Safety Verification

Use the tools that directly support ISO 26262 SoC sign-off and ASIL-driven verification

Resources for Automotive Safety Engineers

Hand-picked content to help your team execute on ISO 26262 for complex SoCs with confidence.

Get the ISO 26262 Confirmation Measures Playbook

Learn how leading automotive teams pass first-time assessments and reduce sign-off risk on complex SoCs.

  • How to structure reviews and audits that pass first-time assessments
  • Where formal verification accelerates safety coverage closure
  • Scalable fault injection techniques that quantify diagnostic coverage
  • Building an assessor-ready safety case with less manual effort
 

Download

Frequently Asked Questions

Synopsys supports ISO 26262 sign-off through a connected workflow spanning safety planning, verification, and evidence generation. VC Z01X enables high-performance fault simulation to quantify diagnostic coverage, VC Formal FuSa provides exhaustive formal-based safety analysis to validate safety mechanisms, and Safety Manager connects safety goals, requirements, and verification results into traceable, assessor-ready work products — helping teams close ASIL targets with greater consistency and less rework near tape-out.

ASIL D represents the highest integrity level in ISO 26262 and demands rigorous verification evidence across hardware, firmware, and software. Teams must demonstrate that safety mechanisms achieve the required diagnostic coverage targets — including Single-Point Fault Metric (SPFM) and Latent Fault Metric (LFM) thresholds — with full traceability from safety goals through implementation to verification results. Scalable fault campaigns, exhaustive safety mechanism analysis, and structured evidence generation are all essential to closing an ASIL D program on modern, heterogeneous SoCs.

Diagnostic coverage for ISO 26262 is demonstrated through targeted fault injection campaigns that evaluate the effectiveness of safety mechanisms against defined fault models. The results — expressed as SPFM and LFM metrics — provide measurable evidence that safety mechanisms detect or control the required proportion of faults at a given ASIL level. VC Z01X supports this with high-performance fault simulation at scale, while VC Formal FuSa complements simulation with exhaustive formal analysis to address unreachable and hard-to-activate faults.

Assessors typically expect a structured set of work products aligned to the ISO 26262 lifecycle, including a safety plan, Hazard Analysis and Risk Assessment (HARA) outputs, safety goals, functional and technical safety requirements, Dependent Failure Analysis (DFA) results, hardware and software verification reports, and traceability demonstrating that safety requirements are implemented and verified. Diagnostic coverage evidence, confirmation measures, and a consistent audit trail from safety concept to sign-off are critical for assessment readiness. Safety Manager supports the creation and maintenance of these artifacts throughout the development program.

Fault simulation is the primary method for validating that safety mechanisms in hardware designs perform as intended and achieve the diagnostic coverage required by ISO 26262. By injecting fault models — including stuck-at, transition, and cell-aware faults — into a gate-level design and measuring detection rates, teams generate the quantitative evidence needed to justify SPFM and LFM values for a given ASIL target. VC Z01X is built for this, delivering the throughput and campaign scalability needed to complete fault analysis on large, complex SoCs without becoming a schedule bottleneck.

Assessor engagement often extends when safety artifacts are inconsistent, incomplete, or spread across disconnected tools. Synopsys addresses this by connecting safety planning, traceability, and verification results in a centralized workflow — so teams can generate structured, consistent documentation throughout development rather than assembling evidence under deadline pressure. Safety Manager supports this with traceable work products aligned to ISO 26262 requirements, reducing the manual effort needed to prepare for reviews and enabling teams to respond to assessor queries with greater confidence and speed.

“Certification” can refer to training certificates, product assessments, or audit readiness. Synopsys is not a certification body; Synopsys provides solutions that help teams execute ISO 26262-aligned verification and documentation to support compliance programs and assessment preparation.

They support safety planning and traceability, scalable fault injection and analysis, and consistent evidence generation to help teams close ASIL targets and reduce late-stage risk.

ASK
BETA
Ask BETA This experience is in beta mode. Please double check responses for accuracy.

End Chat

Closing this window clears your chat history and ends your session. Are you sure you want to end this chat?