26.11.2012 Views

Beyond Bits VII - Freescale Semiconductor

Beyond Bits VII - Freescale Semiconductor

Beyond Bits VII - Freescale Semiconductor

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Back to Table of Contents<br />

Security Subsystem<br />

Secure your applications in an insecure world<br />

Security is an increasingly<br />

important feature for industrial<br />

and consumer applications as the<br />

number of hacking incidents that<br />

expose sensitive information and<br />

unauthorized use of copyrighted<br />

content is on the rise. Helping to<br />

ensure secure applications is a<br />

high priority for the Vybrid platform.<br />

Sensitive information and digital rights<br />

management data can be stored in a<br />

protected manner and used, allowing<br />

e-commerce and advanced contentbased<br />

subscriber services.<br />

Security Block Diagram<br />

Security<br />

Crypytography Module<br />

(CAAM)<br />

Tamper Detect<br />

Secure RTC<br />

Real-Time Integrity<br />

Checker (RTIC)<br />

Secure RAM<br />

Secure Fuses<br />

Secure WDOG<br />

Secure JTAG<br />

freescale.com/Vybrid<br />

Security Subsystem:<br />

A Trusted Platform<br />

The foundation of a secure system<br />

consists of the hardware platform<br />

and the critical code that executes on<br />

that platform. This foundation is built<br />

with an on-chip ROM-based boot-up<br />

process that initiates validation of the<br />

platform, including the following tasks:<br />

• Examining key hardware elements<br />

to help ensure that they are<br />

functioning properly<br />

• Verifying the authenticity and<br />

integrity of the critical code that<br />

controls the overall operation of<br />

the system<br />

The boot process gains control of<br />

the system immediately after reset<br />

by executing known boot code that<br />

is resident in the on-chip ROM. After<br />

verifying the authenticity of a start-up<br />

script residing in external memory (i.e.,<br />

NOR or NAND flash) the boot process<br />

follows that script using established<br />

cryptographic techniques to validate<br />

the authenticity and integrity of the<br />

operating system code and data in<br />

external memory.<br />

<strong>Beyond</strong> <strong>Bits</strong> Vybrid Edition<br />

More flexibility is achieved by using<br />

electrically programmable fuses to<br />

enable or disable particular system<br />

functions. For example, it is possible<br />

to configure a production version,<br />

security-enabled device so that<br />

the JTAG debug port is completely<br />

disabled. For early prototype devices,<br />

portions of the security system can be<br />

selectively disabled, allowing access<br />

to otherwise inaccessible areas of the<br />

device. Full flexibility between these<br />

two extremes is possible.<br />

Software that is security aware is<br />

imperative for those products that<br />

need security. Sensitive data in<br />

plaintext form must not appear on<br />

external data buses, and it should be<br />

restricted to the minimum number of<br />

data paths internal to the chip.<br />

High Assurance Boot<br />

The high assurance boot (HAB) feature<br />

in the system boot ROM protects the<br />

platform from executing unauthorized<br />

software (malware) during the boot<br />

sequence. Unauthorized software can<br />

enter the platform during upgrades or<br />

re-provisioning or when booting from<br />

USB/UART connections or removable<br />

devices. If permitted to gain control<br />

of the boot sequence, unauthorized<br />

software can be the attack vector for<br />

a variety of goals including exposing<br />

stored secrets, circumventing access<br />

controls to sensitive data, services or<br />

networks and re-purposing the<br />

27

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!