Automotive SoCs are particularly challenging because they often integrate safety-critical domains (ASIL-B/C/D) alongside non-safety QM domains. Preventing interference between them — freedom-from-interference (FFI) — is critical, enforced through safety controllers, fault managers, and memory protection hardware. Verification of these mechanisms must happen at subsystem and SoC level, not just at isolated IPs. Many designs also follow the SEooC (Safety Element out of Context) model, meaning the SoC is delivered with assumptions about the larger system — and those assumptions themselves need verification evidence.