Cisco UCS Security Target

1y ago
27 Views
2 Downloads
949.99 KB
55 Pages
Last View : 11d ago
Last Download : 2m ago
Upload by : Mariam Herr
Transcription

Cisco Unified Computing System (UCS) SecurityTargetThis document provides the basis for an evaluation of a specific Target of Evaluation(TOE), the Cisco Unified Computing System solution. This Security Target (ST) definesa set of assumptions about the aspects of the environment, a list of threats that the productintends to counter, a set of security objectives, a set of security requirements, and the ITsecurity functions provided by the TOE which meet the set of requirements.Version 1.06 April, 2017Prepared By:Cisco Systems, Inc.170 West Tasman Dr.San Jose, CA 95134Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyright notice.

Table of Contents1.Security Target Introduction1.1.1.2.1.3.1.4.2.ST and TOE IdentificationTOE OverviewTOE Product TypeSupported non-TOE Hardware/ Software/ FirmwareTOE co UCS 5108 ChassisCisco UCS Fabric InterconnectsCisco UCS Fabric ExtendersCisco UCS Blade ServersCisco UCS Rack Mount C-Series ServersVirtual Interface Cards (VIC) and other Network AdaptersCisco UCS Manager (UCSM)Physical Scope of the TOELogical Scope of the TOE2.9.1. Audit2.9.2. Identification & Authentication2.9.3. Management2.9.4. Network Separation2.9.5. Role Based Access Control2.9.6. TOE Evaluated Configuration2.10. Conformance Claims2.10.1. Common Criteria Conformance Claim2.10.2. Protection Profile Conformance3.Security Problem 26Security Objectives27Security Objectives for the TOESecurity Objectives for the Environment2728Security Requirements28ConventionsTOE Security Functional Requirements5.2.1. Security audit (FAU)5.2.2. User Data Protection (FDP)5.2.3. Identification and Authentication (FIA)5.2.4. Security Management (FMT)5.2.5. Protection of the TSF (FPT)5.2.6. Trusted Path/Channels (FTP)2829303133343738Cisco Unified Computing System Security Target2 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyrightnotice.

5.3.5.4.TOE SFR Hierarchies and DependenciesTOE Security Assurance Requirements5.4.1. Security Assurance Requirements Rationale5.5.Assurance Measures6.38394040TOE Summary Specification6.1.6.2.7.41TOE Security Functional Requirement MeasuresTOE Bypass and interference/logical tampering Protection Measures4147Rationale7.1.7.2.48Rationale for the Security ObjectivesRationale for SFRs/TOE Objectives48518.Glossary: Acronyms and Abbreviations549.Glossary: References and Related Documents5510.Obtaining Documentation, Support, and Security Guidelines55Cisco Unified Computing System Security Target3 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyright notice.

List of TablesTable 1: ST and TOE IdentificationTable 2: Supported non-TOE Hardware/ Software/ FirmwareTable 3: Physical Scope of the TOETable 4: Privileges and Default Role AssignmentsTable 5: TOE AssumptionsTable 6: ThreatsTable 7: Security Objectives for the TOETable 8: Security Objectives for the EnvironmentTable 9: Security Functional RequirementsTable 10: Auditable EventsTable 11: Security Functional Requirement DependenciesTable 12: SAR RequirementsTable 13: Assurance MeasuresTable 14: TOE SFRs MeasuresTable 15: Summary of Mappings between Threats, Policies and the Security ObjectivesTable 16: Rationale for Mapping of Threats, Policies and the Security Objectives for the TOETable 17: Mappings of Assumptions and the Security Objectives for the OETable 18: Rationale for Mapping of Threats, Policies and Objectives for the OETable 19: Summary of Mappings between SFRs and Security ObjectivesTable 20: Summary of Mappings between IT Security Objectives and SFRsTable 21: Acronyms or 154List of FiguresFigure 1: Unified Computing System . 8Figure 2: Sample Deployment of a Subset of TOE Components . 22Figure 3: Sample TOE Deployment Interconnected with Non-TOE Components . 24Cisco Unified Computing System Security Target4 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyrightnotice.

1.Security Target IntroductionThe Security Target contains the following sections: Security Target Introduction TOE Description Conformance Claims Security Problem Definition Security Objectives Security Requirements Assurance Measures TOE Summary Specification RationaleThe structure and content of this ST comply with the requirements specified in theCommon Criteria (CC), Part 1, Annex A, and Part 3, Chapter 4.1.1.ST and TOE IdentificationThis section provides information needed to identify and control this ST and its TOE.Table 1: ST and TOE IdentificationST TitleST RevisionCisco Unified Computing System Security Target1.0ST Publication Date6 April, 2017Guidance DocumentCisco Unified Computing System (UCS), version 3.1(2b) Common CriteriaOperational User Guidance and Preparative Procedures, version 1.0Vendor and ST AuthorTOE ReferenceCisco Systems, Inc.Cisco UCS 5100 Series Blade Server Chassis, B-Series Blade Servers, C-SeriesRack-Mount Servers, 2200/2300 Series Fabric Extenders, and 6200/6300 SeriesFabric Interconnects with UCSM 3.1(2b)TOE Hardware ModelsCisco UCS 5108 Blade Server Chassis, Cisco UCS Blade Servers (B200 M3,B200 M4, B260 M4, B420 M3, B420 M4, and B460 M4), Cisco UCS RackServers (C220 M3, C220 M4, C240 M3, C240 M4, and C460 M4), VirtualInterface Cards (see listing in section 2.6), Cisco UCS Fabric Interconnects(6248UP, 6296UP, 6332, 6332-16UP, and 6324), and Cisco UCS FabricExtenders (2232PP, 2204XP, 2208XP, and 2304)TOE Software VersionCisco Unified Computing System (UCS) Manager 3.1(2b)ST Evaluation StatusIn EvaluationCisco Unified Computing System Security Target5 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyright notice.

Keywords1.2.Virtualization, role-based access control, authenticationTOE OverviewThe TOE is a unified computing solution, which provides access layer networkingand servers.1.3.TOE Product TypeThe TOE, often referred to in this document as the UCS system, consists of hardwareand software components that support Cisco's unified fabric, which run multiple typesof data-center traffic over a single converged network adapter. The UCS features arole based access control policy to control the separation of administrative duties andprovide a security log of all changes made.A single Cisco Unified Computing System scales to up to forty chassis and threehundred twenty blade servers or rack-mount servers, all of which are administeredthrough a single management entity called the Cisco UCS Manager. The Cisco UCSconsists of the following primary hardware elements – Cisco UCS 5108 Blade ServerChassis, Cisco UCS Blade Servers (B200 M3, B200 M4, B260 M4, B420 M3, B420M4, and B460 M4), Cisco UCS Rack Servers (C220 M3, C220 M4, C240 M3, C240M4, and C460 M4), Virtual Interface Cards (see listing in section 2.6), Cisco UCSFabric Interconnects (6248UP, 6296UP, 6332, 6332-16UP, and 6324), and CiscoUCS Fabric Extenders (2232PP, 2204XP, 2208XP, and 2304). The FabricInterconnects and Fabric Extenders are based on the same switching technology asthe Cisco Nexus 5000 Series. Fabric Interconnects also provide additionalcentralized management capabilities that form the basis of the Cisco UCS Manager.Cisco UCS implements Cisco unified fabric within racks and groups of racks,supporting Ethernet and Fibre Channel protocols over 10 Gigabit Cisco Data CenterEthernet and Fibre Channel over Ethernet (FCoE) links. The result of this networkunification is a reduction by up to two-thirds of the switches, cables, adapters, andmanagement points. All devices in a system remain under a single managementdomain, which remains highly available through the use of redundant components.1.4.Supported non-TOE Hardware/ Software/ FirmwareThe TOE supports (in some cases optionally) the following hardware, software, andfirmware in its environment:Table 2: Supported non-TOE Hardw are/ Softw are/ Firmw areIT EnvironmentComponentRequiredUsage/ Purpose Description for TOE performanceCisco Unified Computing System Security Target6 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyrightnotice.

UCS ManagementWorkstation(The host operatingsystem upon which theUCSM clientapplication runs.)YesThe GUI client applet of the Cisco UCS Manager (UCSM) is a Javabased application that allows remote administration of UCSM overTLS. The applet, which is part of the TOE, requires Sun JRE 1.6 orlater, which is part of the IT environment. The UCS Manager uses web start1 to present the GUI and supportsthe following web browsers:– Microsoft Internet Explorer 9.0 or higher– Mozilla Firefox 7.0 or higher– Google Chrome 14.0 or higherNote that that UCS Manager runs on the Fabric Interconnectcomponent of the UCS system and the management workstation isused to connect to the UCS and run the UCSM client applet (theJava-based GUI).SSHv2 ClientNoUCSM can be managed remotely via SSHv2.SNMPv3 ClientNoUCSM can be managed remotely via SNMPv3.Remote AuthenticationServerNoA RADIUS, TACACS , or LDAP server is an optional componentof the operational environment.SNMP v3 ServerNoAn SNMPv3 server is an optional component of the operationalenvironment.Syslog ServerNoA syslog server is an optional component for use with the TOE. It isa supplemental storage system for audit logs, but it does not provideaudit log storage for the TOE. Failed authentication attempts are notlogged to the local audit log, but are sent to a remote syslog server.NTP ServerNoAn NTP server is an optional component of the operationalenvironment that would allow for synchronizing the TOE clockswith an external time source.FirewallYesThe UCS system must be separated from public/untrusted networksby an application-aware firewall such that remote access to theTOE’s management interface is prohibited from untrusted networksand only allowed from trusted networks.1Java Web Start is a network deployment method for standalone Java applications. Note that although the deployment tothe administrator’s browser is dynamic, the version deployed is a static version associated with the TOE.Cisco Unified Computing System Security Target7 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyright notice.

2.TOE DescriptionFigure 1: Unified Computing SystemThis section provides an overview of the Cisco Unified Computing System Target ofEvaluation (TOE). This section also defines the TOE components included in theevaluated configuration of the TOE. The TOE consists of a minimum of one of eachof the following components: Cisco UCS Manager (UCSM) componentso One or more Cisco UCS Fabric Interconnects [6248UP, 6296UP,6332, or 6332-16UP (for use with C-Series or B-Series Servers), or6324 (for use in the 5108 Blade Server Chassis)] Cisco UCS Manager release 3.1(2b)Server and Fabric Extenders (with software loaded from the UCSM bundle)o Blade server configurations: One or more Cisco UCS 5108 Chassis with: Zero, one or more Cisco UCS Fabric Extenders(2204XP, 2208XP, or 2304) One or more Cisco UCS Blade Servers (B200 M3,B200 M4, B260 M4, B420 M3, B420 M4, or B460 M4)o Rack-Mount Server configurations: Zero, one or more Cisco Nexus 2232PP Fabric ExtendersCisco Unified Computing System Security Target8 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyrightnotice.

One or more Cisco UCS Rack Servers (C220 M3, C220 M4,C240 M3, C240 M4, or C460 M4)Deployment note: One instance of the Cisco UCS Manager can manage: a cluster oftwo Fabric Interconnects; multiple Cisco UCS 5100 Series Chassis; 80 FabricExtenders, and hundreds of Cisco UCS B-Series Blade Servers and/or C-Series RackMount Servers. [Capacity details are provided for conceptual purposes only ascapacity testing is not covered within the scope of the Common Criteria evaluation.]2.1.Cisco UCS 5108 ChassisThe Cisco UCS 5108 Chassis physically houses blade servers and up to two fabricextenders. The enclosure is 6RU high supporting up to 56 servers per rack. The UCS5108 supports up to eight half slot or four full slot blade servers with four powersupplies and eight cooling fans. Both power supplies and fans are redundant and hotswappable. Featuring 90% efficient power supplies, front to rear cooling, andairflow optimized mid-plane, the Cisco UCS is optimized for energy efficiency andreliability.Even though the Blade Server Enclosure and Cisco UCS System can house multipleblades, each blade acts as an individual physical server. Cisco UCS System providesa centralized and simplified management paradigm for all the blades.The Cisco UCS 5108 can be managed by rack-mountable (1RU) Fabric Interconnects(6248UP, 6296UP, 6332, or 6332-16UP), or by the “UCS Mini” 6324 FabricInterconnect (installed within the 5108 Chassis). Network connectivity for B-SeriesBlade Servers is provided via one or more Fabric Extenders installed within the 5108chassis (2204XP, 2208XP, or 2304).2.2.Cisco UCS Fabric InterconnectsThe Cisco UCS 6248UP, and 6296UP Fabric Interconnects are high-throughputswitches that consolidate I/O at the system level to provide line-rate, low-latency,lossless 10 Gigabit Ethernet, Cisco Data Center Ethernet, and Fiber Channel overEthernet (FCoE). These Fabric Switches supply a unified network fabric that connectsevery server resource in the system once 10G Ethernet/FCoE downlinks and 10GEthernet and 1/2/4Gb FC uplink modules are configured. The Cisco UCS 6200 Seriesinterconnects support out-of-band management through a dedicated 10/100/1000Mbps Ethernet management port as well as in-band management. Out of bandmanagement, switch redundancy, and console-based diagnostics are enabled throughdedicated management, clustering, and RS-232 ports. A single UCS Series FabricSwitch unites up to 320 servers within a single system domain for maximumscalability.The Cisco UCS 6200 Series Fabric Switch has two flavors – a 1RU switch (6248UP48-Port Fabric Interconnect) and a 2RU switch (6296UP 96-port Fabric Interconnect).Cisco Unified Computing System Security Target9 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyright notice.

The 1RU Fabric switch supports 48 fixed 10G FCoE ports, up to 960 Gbpsthroughput, 1 expansion module, 2 fan modules, and redundant power supplies. The2RU Fabric switch supports 96 fixed 10G FCoE ports up to 1920 Gbps throughput, 3expansion modules, 4 fan modules, and redundant power supplies.The Cisco UCS 6300 Series Fabric Interconnects include two appliance-based (standalone) models (6332, and 6332-16UP), and one “UCS Mini” model (6324) installedwithin a 5108 Blade Chassis. The UCS Mini 6324 supports up to 20 servers, whilethe 6332 and 6332-16UP each support up to 160 servers. The 6332 supports 32 40Gbps ports in one 1 rack unit (RU), while the 6332-16UP has 24 40-Gigabit Ethernetand Fibre Channel over Ethernet (FCoE) ports plus 16 ports that provide 1-10 Gbpsand FCoE or can be configured as 4-,8-, and 16-Gbps Fibre Channel unified ports.The external authentication server can act as a repository for authenticationcredentials. The Cisco UCS Fabric switch implements SSHv2, and TLS1.0/1.1/1.2for secure network management, and SNMPv3 for monitoring (read only). Theexpansion modules supported on the Cisco UCS 6200 Series Fabric Switch can beused to increase the number of 10-Gbit Ethernet, FCoE and FC ports. The unified portmodule provides up to 16 ports that can be configured for 10 Gigabit Ethernet, FCoEand/or 1/2/4/8-Gbps native Fibre Channel using the SFP.2.3.Cisco UCS Fabric ExtendersThe Cisco UCS 2204XP and 2208XP Fabric Extenders extends the I/O fabric into theblade server enclosure (the 5108 Blade Server Chassis) providing a direct 10Gbsconnection between blade servers and fabric switch simplifying diagnostics, cabling,and management. The fabric extender multiplexes and forwards all traffic using a cutthrough architecture over one to four 10Gbps unified fabric.The 2304 Fabric Extender is also installed into the 5108 Blade Server Chassis. Itincludes four 40 Gigabit Ethernet, FCoE-capable, Quad Small Form-Factor Pluggable(QSFP ) ports that connect the blade chassis to the fabric interconnect. Each CiscoUCS 2304 has four 40 Gigabit Ethernet ports connected through the midplane to eachhalf-width slot in the chassis. Typically configured in pairs for redundancy, two fabricextenders provide up to 320 Gbps of I/O to the chassis.The Cisco UCS 2232PP Fabric Extender is a stand-alone appliance (not installed intothe blade server chassis) and provides 32 10 Gb Ethernet and Fibre Channel overEthernet (FCoE) Small Form-Factor Pluggable Plus (SFP ) server ports and eight 10Gb Ethernet and FCoE ports in a 1RU form factor. The 2232PP extends the I/Ofabric between Fabric Interconnect hardware and Rack Servers (C-Series servers).Cisco Unified Computing System Security Target10 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyrightnotice.

2.4.Cisco UCS Blade ServersCisco UCS Blade Servers (B200 M3, B200 M4, B260 M4, B420 M3, B420 M4, andB460 M4) are designed for compatibility, performance, energy efficiency, largememory footprints, manageability, and unified I/O connectivity. Based on Intel Xeon 5500 series processors, B-Series Blade Servers adapt to application demands,scale energy use, and offer a platform for virtualization. Each Cisco UCS B-SeriesBlade Server utilizes converged network adapters for consolidated access to theunified fabric with various levels of transparency to the operating system. This designreduces the number of adapters, cables, and access-layer switches for LAN and SANconnectivity at the rack level.The Blade Servers support network adapters from a number of manufacturers that donot provide any of the security functionality described in the ST. For a fullcompatibility matrix, refer to the Hardware and Software Interoperability Matrix forB-Series Servers referenced from the Cisco UCS B-Series Servers DocumentationRoadmap available at Cisco.com. Any software installed to the Blade servers,including hypervisors and guest operating systems, is outside the TOE boundary.2.5.Cisco UCS Rack Mount C-Series ServersUCS Rack Mount Servers, also known as C-Series Servers (C220 M3, C220 M4,C240 M3, C240 M4, and C460 M4) extend UCS functionality to an industry-standardform factor and are designed for compatibility, and performance, and enableorganizations to deploy systems incrementally, using as many or as few servers asneeded.The Rack Mount Servers support certain optional network adapters, none of whichprovides security functionality described in the ST. For a full compatibility matrix,refer to the Hardware and Software Interoperability Matrix for C-Series Serversreferenced from the Cisco UCS C-Series Servers Documentation Roadmap availableat Cisco.com. Any software installed to the Blade servers, including hypervisors andguest operating systems, is outside the TOE boundary.2.6.Virtual Interface Cards (VIC) and other NetworkAdaptersSeveral network adapters, including Cisco UCS Virtual Interface Cards (VIC) arecompatible with the TOE but do not enforce the security functionality described inthis Security Target.Network Adapters and Virtual Interface Cards compatible with B-Series Servers: Cisco UCS VIC 1240Cisco UCS VIC 1280Cisco UCS VIC 1340Cisco Unified Computing System Security Target11 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyright notice.

Cisco UCS VIC 1380Cisco UCS 82598KR-10 Gigabit Ethernet Network AdapterCisco UCS M71KR-Q QLogic Converged Network AdapterCisco UCS M71KR-E Emulex Converged Network AdapterCisco UCS M81KR Virtual Interface CardCisco UCS M72KR-Q QLogic Converged Network AdapterCisco UCS M72KR-E Emulex Converged Network AdapterCisco UCS M61KR-I Intel Converged Network AdapterCisco UCS NIC M51KR-B Broadcom BCM57711 Network AdapterNetwork Adapters and Virtual Interface Cards compatible with C-Series Servers: 2.7.Cisco UCS VIC 1225Cisco UCS VIC 1225TCisco UCS VIC 1285Cisco UCS P81E Virtual Interface CardEmulex OneConnect Universal Converged Network AdapterQLogic QLE8152 Dual Port 10 Gb Ethernet to PCIe Converged Network AdapterCisco UCS X520 Intel Converged Network AdapterBroadcom NetXtreme II 5709 Quad Port Ethernet PCIe Adapter Card with TOE andiSCSI HBABroadcom NetXtreme II 57711 Dual Port 10 Gb Ethernet PCIe Adapter Card withTOE and iSCSI HBAEmulex LightPulse LPe11002 4 Gbps Fibre Channel PCI Express Dual ChannelHBAQLogic SANblade QLE2462, Dual Port 4 Gbps Fibre Channel to PCI Express HBACisco UCS Manager (UCSM)The Cisco UCS Manager software integrates the components of a Cisco UnifiedComputing System into a single, seamless entity. It can manage up to three hundredand twenty blade servers as a single logical domain via the UCSM XML API, withboth CLI and GUI options, enabling near real time configuration and reconfigurationof resources.The software’s role-based design supports existing best practices, allowing server,network, and storage administrators to contribute their specific subject matterexpertise to a system design. Any user’s role may be limited to a subset of thesystem’s resources using organizations and locales, so that a Cisco UnifiedComputing System can be partitioned and shared between organizations using amulti-tenant model. It allows secure management of the TOE using TLS1.0/1.1/1.2,and SSHv2, and monitoring using SNMPv3 (read only).Cisco Unified Computing System Security Target12 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyrightnotice.

The UCS Manager software is divided into two components: server and client side.The server side component is installed on the 6248UP or 6296UP Fabric Interconnecthardware. The server side component contains the XML based server daemon (XMLAPI) that receives requests from the three different client access methods: GUI, CLI,and XML. The client side component (UCSM GUI) is a java application thatprovides the GUI for the administrator.The UCS Manager software may be deployed in a standalone configuration (on asingle Fabric Interconnect), or in a clustered configuration with one pair of FabricInterconnects. When clustered, management configuration data and event log storageare centralized in the primary Fabric Interconnect and accessed by the subordinatemember of the cluster. In a cluster configuration the two Fabric Interconnectappliances use a pair of directly-connected Ethernet ports allowing these crossconnects to operate within the protected network boundary. Clustered FI are to bedeployed in close proximity to each other such that the network cables between themare protected by a single physically secure environment that protects both FI.2.8.Physical Scope of the TOEThe TOE is a hardware and software solution that makes up the Cisco UnifiedComputing System, and the TOE guidance documentation.The software / firmware for the TOE is bundled in a single image and is distributed tocomponents within the TOE by Cisco UCS Manager. The individual componentfirmware versions are identified with the version listed in the Software / Firmwaresection of the table below.The TOE is comprised hardware identified in the following table.Cisco Unified Computing System Security Target13 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyright notice.

Table 3: Physical Scope of the TOEFabricInterconnectsFabricExtendersC-SeriesRack ServersCisco UCS5108ChassisFabricInterconnectsfor B-SeriesFabricExtendersfor B-SeriesB-SeriesBlade ServersImageTOEComponentModelNumbersUCS 6248UPUCS 6296UPUCS 6332UCS 633216UPNexus 2232PPUCS C220 M3UCS C220 M4UCS C240 M3UCS 5108UCS 6324UCS 2204XPUCS 2208XPUCS 2304UCS B200 M3UCS B200 M4UCS B260 M4UCS C240 M4UCS B420 M3UCS C460 M4UCS B420 M4UCS B460 M4C-Series NICs:B-Series NICs:As listed inAs listed insection 2.6.section 2.6.Unified Computing System (UCS) Complete Software Bundle version 3.1(2b) which includes Cisco UCS Manager 3.1(2b), and theSoftware /UCSM Client GUI Java-based applet.Firmware“Cisco Unified Computing System (UCS), version 3.1(2b) Common Criteria Operational User Guidance and Preparative Procedures”GuidanceDocumentation (Including all supplemental guidance documents referenced therein.)Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyright notice.

2.9.Logical Scope of the TOEThe TOE is comprised of several security features. Each of the security featuresconsists of several security functions, as identified below.1. Audit2. Identification & Authentication3. Management4. Network Separation5. Role Based Access ControlThese features are described in more detail in the subsections below.2.9.1. AuditThe Unified Computing System stores audit information in three different formats:audit log, events, and faults. This information is compiled to assist the administratorin monitoring the security state of the UCS as well as trouble shooting variousproblems that arise throughout the operation of the system. All three types ofinformation are stored within a SQLite database stored on the Fabric Interconnect aspart of UCSM. The database is internal only and does not provide any externallyvisible interfaces for communication. When UCS is deployed in a clusteredconfiguration all instances of the UCS Manager record audit information with theprimary UCS Manager instance. In standalone mode, all audit data is stored locally.Regardless of standalone or clustered configuration, the TOE may be configured tosend records to an external syslog server, in which case syslog is a supplementalservice for monitoring, alerting and reporting, not the audit log storage mechanism ofthe TOE. Audit log storage and protection functionality comes from the TOE itself.The UCS Manager TOE component provides the ability to audit the actions taken byauthorized administrators. Audited events include start-up and shutdown,configuration changes, administrative authentication, and administrative log-off. TheTOE provides the capability for authorized administrators to review the audit recordsstored within the TOE.2.9.2. Identification & AuthenticationCisco UCS supports two methods of authenticating administrator logins on the CiscoUCS Manager: a local user database of passwords (and optionally SSH keys) or aremote authentication server accessed either via LDAP, RADIUS, or TACACS .The TOE may be configured to use either the local user database or one of the remoteauthentication methods, but multiple authentication methods may not be selected.Remote authentication may be used to centralize user account management to anexternal authentication server. When UCS is deployed in a clustered configuration allinstances of the UCS Manager share the local user database.The system has a default user account, admin, which cannot be modified or deleted.This account is the system administrator account and has full privileges.Cisco Unified Computing System Security Target15 2017 Cisco Systems, Inc. All rights reserved.This document may be freely reproduced and distributed whole and intact including this copyright notice.

Each local user account must have a unique user name that does not start with anumber. For authentication purposes, a password is required for each user account.User accounts can be configured to expire at a predefined time. When the expirationtime is reached the account is locked and must be unlocked by an authorizedadministrator. By default, user accounts do not expire.2.9.3. ManagementUCS can be managed using the graphical user interface (over TLS1.0/1.1/1.2), thecommand line (over SSHv2 or by local console access via the RS-232 port), or bymanipulating an XML API. Each of these interfaces can be used in the evaluatedconfiguration to administer the UCS. The interfaces all operate on the same XMLdata structures and provide identical functionality. For all management channels,users have a default read-only authorization to access non-sensitive managementobjects (keys and passwords are never exposed to an external management interface).Additional user privileges each grant access to modify specific management objects.An administrator can use Cisco UCS Manager to perform management tasks for allphysical and virtual devices within a Cisco UCS instance.2.9.3.1.Cisco UCS Hardware ManagementAn administrator can use Cisco UCS Manager to manage all hardware within a CiscoUCS instance, including the following: 2.9.3.2.Chassis (not security-relevant to the TSF)ServersFabric interconnectsFans (not security-relevant to the TSF)PortsCardsSlotsI/O modulesCisco UCS Resource ManagementAn administrator can use Cisco UCS Manager to create and

2.1. Cisco UCS 5108 Chassis 9 2.2. Cisco UCS Fabric Interconnects 9 2.3. Cisco UCS Fabric Extenders 10 2.4. Cisco UCS Blade Servers 11 2.5. Cisco UCS Rack Mount C-Series Servers 11 2.6. Virtual Interface Cards (VIC) and other Network Adapters 11 2.7. Cisco UCS Manager (UCSM) 12 2.8. Physical Scope of the TOE 13 2.9. Logical Scope of the TOE 15

Related Documents:

Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unified Computing System (Cisco UCS), Cisco UCS B-Series Blade Servers, Cisco UCS C-Series Rack Servers, Cisco UCS S-Series Storage Servers, Cisco UCS Manager, Cisco UCS

Cisco UCS anatomy gives a nuts-and-bolts description of Cisco UCS in terms of how our components—Cisco Unified Fabric, Cisco UCS management, and Cisco UCS servers—combine to create a single unified system. The next three sections, Unified I/O architecture, Cisco UCS management, and Cisco UCS servers take a deep dive into the

Cisco UCS S-Series Storage Servers, Cisco UCS Manager, Cisco UCS Management Software, Cisco Unified Fabric, Cisco Application Centric Infrastructure, Cisco Nexus 9000 Series, Cisco Nexus 7000 Series. Cisco Prime Data Center Network Manager, Cisco NX-OS Software, Cisco MDS Series, Cisco Unity, Collaboration Without

Cisco UCS Fabric Interconnects (Read Only / Cut Through Interfaces) SNMP, Syslog, SMTP, SMASH CLP, CIM XML, Smart Call Home 20, 40, 48, and 96 portsCisco UCS I/O Modules and FEX's Cisco UCS Blade Server Chassis Cisco UCS Blade and Rack Servers (Cut through Interfaces to CIMC) Serial over LAN, KVM, IPMI Cisco UCS I/O Adapters Cisco UCS Manager

Cisco UCS Manager PowerTool Release 3.x User Guide Cisco IMC PowerTool, Release 3.x User Guide Cisco UCS Central PowerTool, Release 3.x User Guide Cisco UCS Documentation Roadmap Cisco UCS C-Series Documentation Roadmap Cisco UCS Central ConfigurationGuides OtherDocumentationResources

SQL Server 2016 Databases on Cisco HyperFlex 3.5.1a and Cisco UCS C240 M5 All-Flash Systems with Windows Server 2016 Hy-per-V Last Updated: December 14, 2018 . 2 . Blade Servers, Cisco UCS C-Series Rack Servers, Cisco UCS S-Series Storage Servers, Cisco UCS Manager, Cisco UCS Management Software, Cisco Unified Fabric, Cisco Application .

Cisco UCS 6454 provides the management and communication backbone for the Cisco UCS B-Series Blade Servers, UCS 5108 B-series server chassis, UCS Managed C-Series rack servers, and UCS S-Series storage servers. All severs attached to the Cisco UCS 6454 Fabric Interconnect bec

AS 8 PROTEIN SYNTHESIS QUESTIONSHEET 10 (b) (i) genetic code on DNA is copied into mRNA; double helix of DNA unwinds (in region to be copied); complementary nucleotides line up along coding strand of DNA; A to U and C to G; assemble together to make a complementary strand of mRNA; under influence of RNA polymerase; mRNA unzips from DNA template and passes to ribosomes; max 5 (ii) ATP provides .