1. What Is Automotive SPICE for Cybersecurity?
Automotive SPICE for Cybersecurity is a process-assessment and improvement framework for evaluating how effectively an organization performs automotive cybersecurity engineering. It extends Automotive SPICE with cybersecurity-specific processes rather than replacing the underlying development model. Its focus is the capability of engineering processes, not a security rating for a vehicle.
For passenger vehicle manufacturers, the practical question is whether development teams and suppliers can consistently translate cybersecurity risks into requirements, implemented protections, and credible verification evidence. Consultants can use the framework to structure that evaluation and identify improvements before a platform launch or software release.
2. Origin and Background
The VDA Quality Management Center’s Project Group 13 published the first version on July 16, 2021. Version 2.0, dated March 28, 2025, was developed through Working Group 13 and aligned with Automotive SPICE 4.0.
The extension addressed a specific gap: conventional development-process assessments needed additional cybersecurity content. Its process reference and assessment model provided a structured basis for evaluating cybersecurity engineering, with assessor training supporting its application. It was automotive-specific from the outset, rather than a generic management tool subsequently adapted to vehicles.
3. How Automotive SPICE for Cybersecurity Works
The framework combines two dimensions: which processes are performed and how capable those processes are. Assessors examine objective evidence and evaluate individual processes within a defined assessment scope. There is no consolidated Automotive SPICE capability level for an entire company.
What SPICE means
SPICE stands for Software Process Improvement and Capability dEtermination; VDA also uses the broader expression “Systems/Software.” The components describe its purpose:
- S — Systems/software: The engineering activities being evaluated.
- P — Process: The repeatable work used to produce development outcomes.
- I — Improvement: Strengthening weak or inconsistent practices.
- C — Capability: How reliably a process achieves its purpose.
- E — dEtermination: Evaluating capability through evidence.
The cybersecurity process dimension
| Process | Executive interpretation |
|---|---|
| ACQ.2 — Supplier Request and Selection | Evaluate supplier capabilities and establish appropriate commitments. |
| MAN.7 — Cybersecurity Risk Management | Identify, analyze, treat, and monitor cybersecurity risks. |
| SEC.1 — Cybersecurity Requirements Elicitation | Translate threat scenarios into cybersecurity goals and requirements. |
| SEC.2 — Cybersecurity Implementation | Refine system, software, and hardware designs and implement requirements. |
| SEC.3 — Risk Treatment Verification | Check whether implemented risk treatments meet their specified requirements. |
| SEC.4 — Risk Treatment Validation | Confirm that the integrated system achieves cybersecurity goals. |
These processes supplement the relevant engineering, management, and supporting processes in Automotive SPICE.
The capability dimension
The six capability levels are 0: Incomplete; 1: Performed; 2: Managed; 3: Established; 4: Predictable; and 5: Innovating. Process attributes are rated as not, partially, largely, or fully achieved. Higher levels require satisfaction of the applicable lower-level attributes, not an average of favorable scores.
For a connected gateway, distinguish evidence that cybersecurity requirements were implemented from evidence that implementation was planned, reviewed, controlled, and repeatable. Treat the output as a process-capability profile for the assessed project—not a league table of vehicle security.
4. When to Use Automotive SPICE for Cybersecurity
Use the framework when deciding whether a development program has dependable cybersecurity engineering practices, whether a supplier needs corrective action, or where to invest in engineering governance. It is particularly useful when responsibilities span embedded software, hardware, vehicle integration, and external development partners.
For automotive suppliers, a useful application is testing whether customer requirements can be supported by consistent evidence across releases. Define the supplied component’s boundaries and separate the supplier’s responsibilities from the manufacturer’s integration and vehicle-level validation responsibilities.
The analysis needs development records, interviews, and access to actual project repositories. Effort depends on process scope, project complexity, evidence accessibility, and the number of supplier interfaces. A workshop can identify suspected gaps; it cannot substitute for a properly planned assessment.
Do not use the framework as a replacement for technical security testing or regulatory approval. Where UN Regulation No. 155 applies, vehicle approval and cybersecurity management-system obligations remain separate considerations. Process capability alone cannot establish compliance.
5. How to Apply Automotive SPICE for Cybersecurity: Step-by-Step
- Clarify the decision and scope.
Specify whether the objective is supplier selection, release readiness, customer-assessment preparation, or process improvement. Agree the model version, development project, product boundaries, relevant processes, and target capability levels before collecting evidence.
- Gather development evidence.
Request risk analyses, cybersecurity goals, requirements, architecture decisions, implementation records, verification and validation results, supplier agreements, and configuration histories. Interview engineering, cybersecurity, quality, procurement, and program leaders. Sample actual work rather than relying on procedure manuals.
- Define the units of analysis.
Assess each selected process in its project context. For example, evaluate requirements elicitation for a telematics control unit and risk-treatment validation for the integrated connectivity function. Avoid combining unrelated platforms merely because they share an organizational owner.
- Build an evidence matrix.
Map expected process outcomes and capability attributes to evidence references, interview findings, responsible owners, preliminary judgments, and unresolved questions. Keep formal assessment judgments distinguishable from management’s remediation priorities.
- Interpret gaps and challenge explanations.
Separate absent outcomes from weak management discipline. Ask whether records describe the released configuration, whether requirement links are meaningful, and whether supplier assumptions remain valid. Resolve contradictory evidence before declaring a process effective or ineffective.
- Translate findings into operating changes.
Assign accountable owners, resources, milestones, and closure evidence. Prioritize missing risk treatments and consequential supplier-interface gaps over cosmetic documentation improvements. Where ownership is fragmented, security operating model design can clarify engineering responsibilities and escalation paths.
- Test alternative assumptions.
Reconsider conclusions under different product configurations, supplier responsibilities, release boundaries, and customer targets. Distinguish a process that was legitimately outside scope from one that was omitted to improve the apparent result.
- Align stakeholders and repeat.
Review findings with product cybersecurity, engineering, quality, supplier management, and release authorities. Resolve ownership disputes and test corrective actions on subsequent work. Closure should demonstrate changed behavior, not simply a newly issued template.
6. Example: Automotive SPICE for Cybersecurity in Action
Fictional example: Northbridge Mobility is preparing a connected passenger-vehicle platform with remote diagnostics and over-the-air software updates. Its engineering vice president wants confidence that the gateway supplier and internal integration team can support a defensible release decision.
The team selects Automotive SPICE for Cybersecurity because the concern is inconsistent engineering execution—not simply whether one penetration test found vulnerabilities. Assessment scope covers supplier selection, risk management, requirements, implementation, verification, and integrated validation.
Reviewers sample gateway requirements, update-authentication designs, supplier commitments, test results, and two release configurations. They discover that an update-authentication goal has supporting implementation and verification evidence, but the validation results refer to an earlier configuration. They also find no agreed owner for reassessing risks after a supplier library update.
The findings distinguish technical progress from process weaknesses. Management postpones the affected feature’s release, updates the risk analysis, assigns responsibility for dependency changes, and requires validation evidence for the intended configuration.
Northbridge then pilots a revised evidence-review routine on the next release. Success means that engineers can demonstrate current, coherent evidence and clear ownership—not that the organization has acquired a blanket “cybersecure” designation.
7. Strengths and Limitations
Strengths
- Specific diagnosis: Separates weak requirements, supplier commitments, implementation evidence, and process management.
- Shared language: Gives engineering, quality, procurement, and cybersecurity leaders a common basis for discussing development discipline.
- Actionable investment choices: Helps distinguish needs for specialist testing, better tooling, clearer accountability, or stronger review routines.
When corrective actions span suppliers, test laboratories, and multiple engineering teams, program management support can coordinate commitments, dependencies, and evidence-based closure.
Limitations
A process assessment does not include an in-depth technical analysis and cannot prove that a product is attack-proof. It also does not replace an organizational cybersecurity management-system audit.
Management should therefore avoid overgeneralizing from the assessed project. Strong evidence on one gateway program does not establish equivalent execution on another platform. Furthermore, remediation requires engineering capacity and supplier cooperation; the framework identifies weaknesses but does not supply those capabilities.
8. Common Pitfalls and How to Avoid Them
- Chasing a badge: A headline level can conceal weak individual processes. Report the capability profile, assessment scope, and consequential findings.
- Confusing verification and validation: Checking a specified protection is not the same as demonstrating that the integrated system achieves its cybersecurity goal. Keep both questions visible.
- Counting links instead of checking meaning: Requirements linked to obsolete designs or irrelevant tests create false confidence. Review consistency and configuration relevance, not link totals.
- Ignoring supplier boundaries: Unassigned integration duties can leave evidence gaps. Agree responsibility for requirements, risk updates, verification, and validation before assessment preparation.
- Preparing documents retrospectively: An assessment-ready folder may not reflect normal execution. Sample contemporaneous records and ask engineers to explain actual decisions.
- Closing actions administratively: A published procedure is not proof of adoption. Verify its use on a subsequent development increment.
9. How Automotive SPICE for Cybersecurity Relates to Other Frameworks
Automotive SPICE
The base model evaluates broader development processes. Use it alongside the cybersecurity extension so that security-specific findings remain connected to requirements management, integration, configuration control, and project execution. The extension is explicitly designed to supplement Automotive SPICE 4.0.
Threat Analysis and Risk Assessment
Threat Analysis and Risk Assessment, or TARA, examines assets, threat scenarios, attack paths, and resulting risks. It supplies substantive inputs to cybersecurity engineering. Prefer TARA when the immediate question is what could go wrong; use Automotive SPICE for Cybersecurity when the question is whether the organization performs the relevant work dependably. Iterate both as designs change.
ISO/SAE 21434
ISO/SAE 21434 establishes cybersecurity engineering requirements across the road-vehicle electrical and electronic lifecycle. Use it to understand lifecycle obligations and Automotive SPICE for Cybersecurity to assess relevant development-process capability. Neither should be treated as a substitute for the other.
10. Key Takeaways
- Use the framework to assess engineering-process capability, not to declare a vehicle secure.
- Define the project, product configuration, supplier boundaries, and assessment scope first.
- Follow the connection from risks to goals, requirements, implementation, and evidence.
- Keep verification and integrated validation distinct.
- Turn findings into accountable operating changes and test their adoption.
11. FAQs About Automotive SPICE for Cybersecurity
Is Automotive SPICE for Cybersecurity a product certification?
No. It evaluates process capability within an agreed scope. It does not certify that a vehicle is free from vulnerabilities or replace technical cybersecurity evaluation and vehicle-approval requirements.
Is capability level 3 always the right target?
Agree targets with the customer and assessment sponsor for the relevant processes. Do not assume a universal minimum. Focus first on achieving necessary outcomes, then on the management and institutionalization needed to sustain them.
Can smaller automotive suppliers use the framework?
Yes. Start with one customer program and proportionate evidence-management practices. Combine responsibilities where appropriate, but preserve clear accountability and review discipline. Avoid purchasing complex tooling before understanding the underlying process gaps.
What evidence should an executive team request first?
Request one coherent example connecting a current threat scenario to a cybersecurity goal, requirement, implemented protection, and relevant test evidence. Then ask who owns the chain, which configuration it covers, and how changes trigger reassessment.
