Secure Boot Overview
Cisco Secure Boot places the Root of Trust in a hardware chip device on a circuit card where it cannot be
changed. The first code (microloader) that executes immediately after power on is guaranteed to be legitimate
code from Cisco and programmed during the time of system manufacturing. Furthermore, all software images
can be cryptographically verified against modifications prior to load/execution.
The goal of Cisco Secure Boot technology is to address potential issues associated with unprotected boot
code.
Once a piece of code is validated, it can be trusted and is allowed to assume control of the processor. Each
step of the boot sequence verifies the next step of the boot module via a code-signed module (Chain of Trust).
MIO2 Support for Secure Boot
The ASR 5500 MIO2 supports Secure Boot with a digitally signed image having a Release key. Production
MIO2 cards require an image filename signed with a Release key suffix of
.SPA
. For example,
asr5500-21.0.0.bin.SPA
MIO, DPC and DPC2 cards will also have digitally signed boot images, but they will ignore the signature.
Important
Image Naming Conventions
To distinguish signed from unsigned images, Release Engineering adds suffixes to build names for images
that are signed. For example, asr5500-20.0.0.bin.
SPA
indicates a Release key signed as deployable in a
customer network.
Verifying Authenticity
The Exec mode
show software authenticity
command displays information about the chain of trust and
authentication process for starfile images.
The syntax for this commend is:
show software authenticity { file url [ validate ] | keys | running }
Notes:
•
file url [ validate ]
displays authenticity information for starfile images on flash or over the network.
The
validate
option performs digital signature validation of the image.
•
keys
displays public StarOS key information for each of the key storage regions (Primary, Backup), as
well as Rollover key information.
•
running
displays information about the chain of trust for all running software images: StarOS, CFE
(bootstrap), BIOS/UEFI (Unified Extensible Firmware Interface) and the microloader.
For additional information about this command, see the
Command Line Interface Reference
.
ASR 5500 System Administration Guide, StarOS Release 21.5
404
Cisco Secure Boot
Secure Boot Overview
Содержание ASR 5500
Страница 100: ...ASR 5500 System Administration Guide StarOS Release 21 5 74 System Interfaces and Ports VLANs and Management Ports ...
Страница 136: ...ASR 5500 System Administration Guide StarOS Release 21 5 110 Smart Licensing Smart Licensing Bulk Statistics ...
Страница 140: ...ASR 5500 System Administration Guide StarOS Release 21 5 114 Monitoring the System Clearing Statistics and Counters ...
Страница 260: ...ASR 5500 System Administration Guide StarOS Release 21 5 234 Routing Viewing Routing Information ...
Страница 278: ...ASR 5500 System Administration Guide StarOS Release 21 5 252 BGP MPLS VPNs VPN Related CLI Commands ...
Страница 292: ...ASR 5500 System Administration Guide StarOS Release 21 5 266 Session Recovery Sample Output for show rct stats verbose ...
Страница 324: ...ASR 5500 System Administration Guide StarOS Release 21 5 298 Interchassis Session Recovery Fallback Procedure ...
Страница 338: ...ASR 5500 System Administration Guide StarOS Release 21 5 312 Engineering Rules ECMP Groups ...
Страница 362: ...ASR 5500 System Administration Guide StarOS Release 21 5 336 StarOS Tasks Management Processes ...