300-625 practice question 11 of 15
Which feature on MDS platforms ensures that the code that is running on the hardware platform is authentic and unmodified, while also validating the BIOS to eliminate any rootkits.
Full set: 60 questionsCisco Secure Boot is a comprehensive, hardware-anchored process that ensures the integrity of the device from power-on. It establishes a chain of trust starting from an immutable hardware component, the Trust Anchor module (TAm). This process cryptographically verifies each piece of software, including the BIOS/UEFI firmware and the NX-OS operating system image, before it is loaded. This validation ensures that the code is authentic, published by Cisco, and has not been tampered with, thereby preventing persistent malware like rootkits from compromising the system at its most fundamental level.
B. UEFI Secure Boot: This is a generic industry standard. Cisco Secure Boot is a more comprehensive, vendor-specific implementation that includes hardware-level validation preceding the UEFI process.
C. Secure Unique Device Identifier: SUDI is a hardware-based certificate that provides a unique, non-tamperable identity for the device, but it does not validate the boot software's integrity.
D. BIOS Secure Boot: This is not a standard term. BIOS is the legacy firmware interface, and the modern, secure standard is UEFI Secure Boot, which is part of the larger Cisco Secure Boot architecture.
1. Cisco MDS 9000 Series NX-OS Security Configuration Guide, Release 9.3(x), Chapter: System Security, Section: "Secure Boot". The document states, "Cisco Secure Boot is a secure startup process that the switch performs each time it is powered on. It ensures that the code running on the switch platform is authentic and unmodified... The hardware-anchored secure boot feature is based on an immutable device identity that is stored in a tamper-resistant Trust Anchor module (TAm)."
2. Cisco Trustworthy Systems At-A-Glance, Document ID: C45-731421-05, Section: "Hardware-anchored secure boot". This document explains, "Hardware-anchored secure boot helps ensure that the code that is executed on Cisco hardware platforms is authentic and unmodified. The process begins with a hardware root of trust that validates the integrity of the next piece of code in the boot sequence, creating a chain of trust."
3. Cisco MDS 9700 Series Supervisor-4 Module Data Sheet, Document ID: C78-743699-01, Table 1: Features and Benefits. The data sheet lists "Hardware-based Cisco Trust Anchor module (TAm)" which "enables security features such as Secure Boot". This directly links the hardware module to the Secure Boot feature on MDS platforms.
Keep practicing
Take the free 300-625 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other 300-625 practice questions
- Question 1A Cisco MDS Series Switch with the POAP feature boots and does not find the startup confi…
- Question 2What is the effect of a non-graceful virtual machine shutdown on a virtualized server tha…
- Question 3A domain ID conflict is detected on a switch. Which action resolves the issue in the shor…
- Question 6A network engineer is configuring a Cisco MDS switch for FCoE. Which two conditions must …
- Question 7A storage administrator is connecting two previously configured switches to make a single…
- Question 8After user account attributes are modified in Cisco NX-OS, when do changes to the user’s …
