Chip lifecycle / Vehicle cybersecurity lifecycle / Software Update Management & Update Campaigns

Software Update Management & Update Campaigns

Running the software update management system: identifying every software version that bears on type approval, assessing each update for its effect on safety, cybersecurity and approved functions, building, signing and verifying update packages, checking compatibility with each vehicle configuration, informing users, delivering updates over the air or in the workshop safely, and recording each campaign, as UN R156 and ISO 24089 describe.

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

^A09 Production & Release for Post-Development

^A10 Software Update Management & Update CampaignsYou are here

^O11 Monitoring & Vulnerability Management

Organisation, approval and support milestones

TGType approval granted PRRelease for post-development UCUpdate campaign review

Cybersecurity engineering milestones

SRSUMS ready MRMonitoring and response ready VRVulnerability management review

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

Freeze

Software security^D

Freeze

Type approval and homologation^A

1.0

Production security^A

Freeze

Software update management^A

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: Software Update Management & Update CampaignsAI 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
- 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.
- Monitoring & Vulnerability Management: 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
- 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.
- Monitoring & Vulnerability Management: 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
- 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.
- Monitoring & Vulnerability Management: 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
- 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
- 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.
- Monitoring & Vulnerability Management: 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.
Type approval and homologation^A
- 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.
- Monitoring & Vulnerability Management: 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
- 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
- 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 & Vulnerability Management: 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
- 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.
- Monitoring & Vulnerability Management: maturity 1.0, Complete. First vulnerability management review held, with records current and the monitoring report issued; afterwards monitoring continues until the end of support.
Incident response^A
- 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.
- Monitoring & Vulnerability Management: maturity 0.8, Feature complete. Incident response plan approved and rehearsed, and incidents handled as they arise.

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.