Software Product Overview

The Hardware Security Manager in F29 devices contains several component blocks designed to achieve system security objectives. These include various memories, the Security Manager, cryptographic accelerator engines, peripheral modules, and the secure mailbox. The host C29 subsystem interfaces with the HSM subsystem to perform the cryptographic operations required for code authentication, secure boot, secure firmware upgrades and encrypted run-time communications.

Figure 1 HSM Block Diagram

Security Goals of F29 devices

• Modules and platform protection:

  • Protect modules (hardware and software) and defend platform from takeover and unauthorized modifications.
  • Protect critical assets and resources from hardware and software attacks
• Limit the attack surface for critical assets -
  • Isolate critical assets in protected space with heavily restricted access. Focus on protection against class-based attacks.
  • Assume rest of system is compromised to protect critical assets.
• Sand-box security:
  • Security operates in isolated environment.
  • Application modules and tasks are securely isolated from each other, even on the same CPU.

• Layered security:

  • Multi-tier approach, such that compromises do not spread and break the entire system security.
  • Each tier operates in isolation with other tiers.
• Traceability, accountability and isolation for security development:
  • Security must be developed in isolated environment so that unexpected issues can be avoided.
  • This is also required to prove security to certification entities and customers.