After cyberattacks on refrigeration systems in European supermarkets, stores had to discard food. Refrigeration systems operated by a service provider for the French blood donation service were also tampered with. According to the blood donation service, the safety of the blood products was not affected.
What does secure programming mean in volume production?
The attacks show what can happen when connected equipment is tampered with in operation. They do not show that it was programmed insecurely. For manufacturers, protecting a device in service and securing how it is programmed before shipment are two distinct tasks.
Secure programming protects firmware and other sensitive data as they are transferred to the microcontroller. A programming record makes it possible to trace which firmware was loaded onto which component. If the product’s security design calls for individual device identities, the record can also show which certificate was assigned to each component. Securing remote access and providing security updates remain separate tasks once the device is in use.
Which firmware was actually loaded?
A release record tells you which version was approved. A programming record tells you which version was loaded. If your product requires component-level traceability, check that the record can be linked to the individual component.
How are firmware and device identities protected?
If you outsource programming, ask where confidential data is decrypted and whether unencrypted copies are left behind. If your devices need individual certificates, ask how each certificate is assigned to the correct component and who controls the root certificate authority’s private key.
What evidence will you have later?
Before signing off on volume production, ask to see the programming record for a sample component. Check that it identifies the component, shows which firmware version was actually loaded and confirms whether programming was successful. If the device is assigned an individual identity, ask which certificate was assigned to that specific component. This lets you check before production starts whether the record will answer the questions that may come up in a later quality review.
If you are still defining your production requirements, compare
standard programming and secure programming.
How btv protects the programming step
With the process behind btv SEEL®, programming data is supplied in encrypted form and decrypted only in volatile memory. Unencrypted data is not written to persistent storage. Where required, btv can integrate the manufacturer’s certificate infrastructure. The root certificate authority’s private key stays with the manufacturer.
With btv SEEL® UNLIMITED, individual device identities can be assigned in volume production, with programming and certificate assignment documented down to the individual component. For a connected medical device, for example, that identity can be used to authenticate to a maintenance system. The production record lets the manufacturer check which certificate was assigned during programming.
Secure programming does not replace safeguards in operation or a security strategy for the finished product. It addresses one specific question before shipment: Can you show what happened when this component was programmed?
See how btv SEEL® protects firmware and device identities during programming