Chip lifecycle / Vehicle cybersecurity lifecycle / Production & Release for Post-Development

Production & Release for Post-Development

Making sure the item is built as designed and secured: the production control plan for cybersecurity, secure key and certificate provisioning, end-of-line configuration, locking of debug and test access, protection of production tools and data, and the release for post-development, which confirms that monitoring, incident response and updates are ready before vehicles reach customers.

Where this stage sits

This stage with its neighbours. Each row is a discipline active here, shaded by how mature its work is by the end of each stage.

Stage

^A08 Cybersecurity Case, Assessment & Type Approval

^A09 Production & Release for Post-DevelopmentYou are here

^A10 Software Update Management & Update Campaigns

Organisation, approval and support milestones

TGType approval granted PRRelease for post-development UCUpdate campaign review

Cybersecurity engineering milestones

VCCybersecurity validation complete ACCybersecurity assessment complete SRSUMS ready MRMonitoring and response ready

Cybersecurity management and governance^A

1.0

Supplier and interface management^A

1.0

Threat analysis and risk assessment^A

1.0

Hardware security and chip suppliers^A

Validation and penetration testing^A

1.0

Type approval and homologation^A

1.0

Production security^A

1.0

Freeze

Software update management^A

0.8

1.0

Monitoring and vulnerability management^O

Key0.0Planned0.3Outlined0.5Analysed0.8Feature complete1.0CompleteFreezeFrozenFaded block: still at the step shown before it, Held below Complete or Maintained under change control once complete or frozenFreeze or sign-off pointMilestone for one item; the rest of the work carries onMilestone gateYou are here: Production & Release for Post-DevelopmentAI impactDisruption (red)Augmentation (blue)Opportunity (green)How AI is changing the workWhat the steps mean What the codes mean

Show this chart as a list

Stages

Organisation, approval and support milestones

Cybersecurity engineering milestones

Disciplines

Cybersecurity management and governance^A
- Cybersecurity Case, Assessment & Type Approval: maturity 1.0, Complete. Independent assessment complete and the plan closed for development; from here the lane keeps the CSMS audited, the records current and the archive complete to the end of support.
- Production & Release for Post-Development: maturity 1.0, Complete. Independent assessment complete and the plan closed for development; from here the lane keeps the CSMS audited, the records current and the archive complete to the end of support.
- Software Update Management & Update Campaigns: maturity 1.0, Complete. Independent assessment complete and the plan closed for development; from here the lane keeps the CSMS audited, the records current and the archive complete to the end of support.
Supplier and interface management^A
- Cybersecurity Case, Assessment & Type Approval: maturity 1.0, Complete. Supplier cybersecurity evidence received and accepted for type approval and the release; afterwards vulnerability notification with suppliers is kept working in both directions.
- Production & Release for Post-Development: maturity 1.0, Complete. Supplier cybersecurity evidence received and accepted for type approval and the release; afterwards vulnerability notification with suppliers is kept working in both directions.
- Software Update Management & Update Campaigns: maturity 1.0, Complete. Supplier cybersecurity evidence received and accepted for type approval and the release; afterwards vulnerability notification with suppliers is kept working in both directions.
Threat analysis and risk assessment^A
- Cybersecurity Case, Assessment & Type Approval: maturity 1.0, Complete. TARA confirmed by verification and penetration testing and the residual risk accepted; afterwards it is updated for every change and every field finding.
- Production & Release for Post-Development: maturity 1.0, Complete. TARA confirmed by verification and penetration testing and the residual risk accepted; afterwards it is updated for every change and every field finding.
- Software Update Management & Update Campaigns: maturity 1.0, Complete. TARA confirmed by verification and penetration testing and the residual risk accepted; afterwards it is updated for every change and every field finding.
Hardware security and chip suppliers^A
- Cybersecurity Case, Assessment & Type Approval: maturity 1.0, Complete. Hardware security confirmed by validation and penetration testing on the item; the lock configuration is prepared for production.
- Production & Release for Post-Development: maturity Freeze, Frozen. Debug and test access locked in production configuration and key storage released; any change goes through change control and a type approval impact assessment.
Software security^D
- Cybersecurity Case, Assessment & Type Approval: maturity 1.0, Complete. Security software confirmed by validation and penetration testing, with no open weakness above the agreed level.
- Production & Release for Post-Development: maturity Freeze, Frozen. Security software released and under change control for the vehicle type; field fixes are built, assessed for type approval and delivered through the update management system.
- Software Update Management & Update Campaigns: maturity Freeze, Frozen. Security software released and under change control for the vehicle type; field fixes are built, assessed for type approval and delivered through the update management system.
Validation and penetration testing^A
- Cybersecurity Case, Assessment & Type Approval: maturity 1.0, Complete. Cybersecurity goals shown to be achieved, penetration testing complete with findings dispositioned and residual risk accepted; the cybersecurity case is assembled from the evidence.
Type approval and homologation^A
- Cybersecurity Case, Assessment & Type Approval: maturity 1.0, Complete. Type approval granted or the evidence accepted by the customer; afterwards SUMS evidence, monitoring reports and approval changes are kept current with the authority.
- Production & Release for Post-Development: maturity 1.0, Complete. Type approval granted or the evidence accepted by the customer; afterwards SUMS evidence, monitoring reports and approval changes are kept current with the authority.
- Software Update Management & Update Campaigns: maturity 1.0, Complete. Type approval granted or the evidence accepted by the customer; afterwards SUMS evidence, monitoring reports and approval changes are kept current with the authority.
Production security^A
- Cybersecurity Case, Assessment & Type Approval: maturity 1.0, Complete. Control plan checked and key provisioning qualified and audited; ready for the release for post-development.
- Production & Release for Post-Development: maturity Freeze, Frozen. Released for post-development: production controls in force, keys provisioned under audit and debug locked; changes go through change control.
Software update management^A
- Cybersecurity Case, Assessment & Type Approval: maturity 0.8, Feature complete. Update path built and tested end to end on integrated items, and the SUMS processes written for the vehicle type.
- Production & Release for Post-Development: maturity 1.0, Complete. SUMS ready for the vehicle type: processes approved and deployed, the software identification register complete and the update path secured; afterwards update campaigns run under it.
- Software Update Management & Update Campaigns: maturity 1.0, Complete. SUMS ready for the vehicle type: processes approved and deployed, the software identification register complete and the update path secured; afterwards update campaigns run under it.
Monitoring and vulnerability management^O
- Cybersecurity Case, Assessment & Type Approval: maturity 0.3, Outlined. Monitoring approach outlined for type approval: sources, triggers and how events reach the people who evaluate them.
- Production & Release for Post-Development: maturity 0.5, Analysed. Cybersecurity monitoring plan and event evaluation procedure drafted, with sources, triggers and supplier contacts named.
- Software Update Management & Update Campaigns: maturity 0.8, Feature complete. Monitoring running for the item in the field: plan approved, events evaluated and vulnerabilities analysed against the TARA.
Incident response^A
- Cybersecurity Case, Assessment & Type Approval: maturity 0.0, Planned. Incident response lead named for the vehicle type and the item added to the CSMS incident process, with the response team and contacts estimated; no plan for the item yet.
- Production & Release for Post-Development: maturity 0.3, Outlined. Incident response approach outlined: roles, contacts, severity levels and how incidents reach suppliers and authorities.
- Software Update Management & Update Campaigns: maturity 0.5, Analysed. Incident response plan drafted, with a playbook for each main attack path in the TARA.

Register or sign in to read on

The full lifecycle detail, with its charts, flows, tables and every section, is for registered members. Registration is free and takes a minute. You come back to this page afterwards.