SECURITY: CYBER
authentication, and secure boot ensures that only the signed firmware, application and file system can be loaded. Its implementation is hardware-specific • Filesystem encryption, using a secret key held in hardware. The method of key generation and storage is device-specific. Often, keys can be held securely by the application processor’s cryptographic sub-system. These can be used within that subsystem to decrypt data, which, in turn, can then provide keys to decrypt other data in a ‘Merkle tree’ arrangement • Transport Layer Security (TLS). Although the data on the device may be encrypted at rest, once in use it will usually be decrypted, and so all interfaces to the outside world must be secure • Generation of an SBOM (software bill of materials), in an approved format • A starting-point vulnerability assessment, based on the SBOM, looking for CVEs (Common Vulnerabilities and Exposures), taking into account the threat model, plus a mitigation plan • A documented ongoing monitoring, reporting and mitigation process for vulnerabilities which occur during the product lifetime • A mechanism to issue and provision secure updates, free of charge – therefore, for connected products, these must be OTA (over-the-air)
• Compliant project and product documentation
• A documented risk assessment
• A formal conformity assessment procedure and justification Undoubtedly, this represents extra cost and effort – and, to that extent, will prove an unwelcome burden for many OEMs. On the other hand, in a brave new world, where customers are awakening to the dangers of implementing insecure systems, embracing cybersecurity could deliver significant competitive advantage in markets where a foot-dragging approach is unfortunately still commonplace.
41 ELECTRONICSPECIFIER.COM
Powered by FlippingBook