FIPS 140-2 Non-Proprietary Security Policy For The Cisco .

3y ago
38 Views
2 Downloads
423.87 KB
18 Pages
Last View : 28d ago
Last Download : 3m ago
Upload by : Bria Koontz
Transcription

FIPS 140-2 Non-Proprietary Security Policy for theCisco Unified IP Phone 6921, 6941, 6945, and 6961IntroductionThis is a non-proprietary Cryptographic Module Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961.This policy describes how the Cisco Unified IP Phone 6921, 6941, 6945, and 6961meet the requirements of FIPS 140-2.This document also includes instructions for configuring the phones in FIPS mode.This policy was prepared as part of the Level 1 FIPS 140-2 validation for the Cisco Unified IP Phone 6921, 6941, 6945, and6961.FIPS 140-2 (Federal Information Processing Standards Publication 140-2 — Security Requirements for CryptographicModules) details the U.S. Government requirements for cryptographic modules. More information about the FIPS 140-2standard and validation program is available on the NIST website at s document may be copied in its entirety and without modification. All copies must include thecopyright notice and statements on the last page.This document includes the following sections: FIPS 140-2 Submission Package Overview Physical Characteristics and Phone Interfaces Roles and Services Self-Tests Mitigation of Other Attacks Secure Operation Non-FIPS Approved Algorithms Obtaining Documentation Documentation Feedback Cisco Product Security Overview Obtaining Technical Assistance Obtaining Additional Publications and InformationFIPS 140-2 Submission PackageThe security policy document is one document in a FIPS 140-2 Submission Package. In addition to this document, thecomplete submission package contains: Vendor Evidence Finite State Machine Other supporting documentation as additional referencesv 1.0

With the exception of this non-proprietary security policy, the FIPS 140-2 validation documentation is proprietary to CiscoSystems, Inc. and is releasable only under appropriate non-disclosure agreements. For access to these documents, pleasecontact Cisco Systems, Inc. See Obtaining Technical Assistance for more information.OverviewToday, more organizations can take advantage of Cisco Unified Communications, thanks to these affordable IP endpoints.The Cisco Unified IP Phones 6921, 6941, 6945, and 6961 deliver cost-effective, full-featured voice communication servicesin a clutter-free and earth-friendly, ergonomic design. Cisco Unified IP Phones 6921, 6941, 6945, and 6961 endpoints areearth-friendly. They are made with recyclable and reground plastics, so they are earth-responsible solutions. A deep-sleeppower option, on select models, reduces power consumption by up to 50 percent in off-work hours, a feature that is good foryour company’s profitability and good for the planet too.The Data Sheet for the 6921 can be found on the Cisco website at http://goo.gl/bUerEFigure 1 - The Cisco Unified IP Phone 6921The Data Sheet for the 6941 can be found on the Cisco website at http://goo.gl/YNyOj2FIPS 140-2 Non-Proprietary Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961v 1.0

Figure 2 - The Cisco Unified IP Phone 6941The Data Sheet for the 6945 can be found on the Cisco website at http://goo.gl/VkjO5Figure 3 - The Cisco Unified IP Phone 69453FIPS 140-2 Non-Proprietary Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961v 1.0

The Data Sheet for the 6961 can be found on the Cisco website at http://goo.gl/9RtmJFigure 4 - The Cisco Unified IP Phone 6961Cryptographic Module Validation LevelValidation Level by Section lists the level of validation for each area in the FIPS PUB 140-2.Table 1Validation Level by SectionNo.Area TitleLevel1Cryptographic Module Specification12Cryptographic Module Ports and Interfaces13Roles, Services, and Authentication14Finite State Model15Physical Security16Operational EnvironmentN/A7Cryptographic Key management18Electromagnetic Interface/Electromagnetic Compatibility19Self-Tests110Design Assurance14FIPS 140-2 Non-Proprietary Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961v 1.0

11Mitigation of Other AttacksN/AOverall Level1Physical Characteristics and Phone InterfacesThe logical interfaces and their mapping for the 6921, 6941, 6945, and 6961 Phones are described in Table 2:Table 2Cisco 6921, 6941, 6945, and 6961 Physical Interface/Logical Interface MappingPhysical InterfaceFIPS 140-2 Logical InterfacePhone Keypad, Data Port, Phone Microphone,Data InputPhone Speaker, Data Port, DisplayData OutputPhone Keypad, Data Port and Power PortControl InputPhone Display, Phone Speaker, message waitinglight, LEDsStatus Output5FIPS 140-2 Non-Proprietary Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961v 1.0

Roles and ServicesThe 6921, 6941, 6945, and 6961 phones can be accessed by plugging the phones into the network.As required by FIPS 140-2, there are two main roles in the 6921, 6941, 6945, and 6961 Phones that operators may assume: aCrypto Officer role and User role. The respective services for each role are described in the Crypto Officer Services, and theUser Services.Crypto Officer ServicesThe Crypto Officer role is responsible for the configuration and maintenance of the phones. For the purposes of this testing,the Crypto Officer will be defined as the operations and processes performed by the Cisco Unified Call Manager (CUCM).The authentication mechanism associated with the Crypto-Officer has not been tested for FIPS level one validation. TheCrypto Officer services consist of the following: Establish TLS sessions for configuration Perform configuration of the phone Transport Keys to the phone View Status of the phone Restart the phone (Restart the connection between the phone and CUCM) Reset the phone Initiate Self-tests by rebooting the phone.User ServicesA user initializes the phone by turning it on. There is no login interface for the phone, as level 1 allows for implicit roleassumptions. Some services may require the menu key to access the features. The services available to the User role consistof the following: Make and Receive Calls (Encrypt/Decrypt data) Run Self-Tests Customize keypad parameters View and edit network profile parameters (SSID, DHCP Server, TFTP Server, etc.) View and edit system configuration View and edit device information (CallManager, Network, HTTP, Locale, QoS, and UI information) Display Model Information View Phone Status (Phone status, network statistics, call statistics, firmware versions, etc.)6FIPS 140-2 Non-Proprietary Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961v 1.0

Cryptographic Key ManagementThe phone uses a variety of Critical Security Parameters during operation. Table 3 lists the cryptographic keys used by Cisco 6921,6941, 6945, and 6961 phones.Table 3Secret and Private Cryptographic Keys Used by Cisco 6921, 6941, 6945, and 6961 nFile AES-128KeyGenerated by theCUCM2sRTP MasterKey (AES)3sRTPEncryptionkey (AES)4#DescriptionStorageZeroizationKey used to decrypt theconfiguration file once itis on the phoneStored in volatilememoryPower Cycle or DeviceResetGenerated by theKey used to generateCUCM and sent to sRTP session keysphone in TLSsessionStored in volatilememoryupon end of call or devicereset.Generated via thesRTP protocolKey used toencrypt/decrypt sRTPpacketsStored in volatilememoryupon end of call or devicereset.sRTPGenerated via theAuthentication sRTP protocolkey (HMAC)Key used to authenticatesRTP packetsStored in volatilememoryupon end of call or devicereset.5CUCM TLSSessionEncryptionkey (AES)TLS sessions keys basedon the LocallySignificant Certificate(LSC) for derivationStored in volatilememoryupon end of call or devicereset.6CUCM TLSGenerated via theSessionTLS ProtocolAuthenticationkey (HMAC)TLS sessions keys based Stored in volatileon the LSC for derivation memoryupon end of call or devicereset.7Webserver TLS Generated via theSessionTLS ProtocolEncryption key(AES/TDES)TLS sessions keys basedon the LSC for derivationStored in volatilememoryupon end of call or devicereset8WebserverTLSSessionAuthenticationkey (HMAC)TLS sessions keys basedon the LSC for derivationStored in volatilememoryupon end of call or devicereset.Generated via theTLS ProtocolGenerated via theTLS Protocol7FIPS 140-2 Non-Proprietary Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961v 1.0

9RNG SeedKeyMultiple data bytes Seed Key used to(16-bytes) retrieved randomize thefrom a 32-bytesinitialization of the RNGHardware basedentropy source(time, clock,thermal noise,interrupts, andmemory, etc).Stored in volatilememoryReset or loss of power10RNG SeedMultiple data bytes Seed used to randomize(16-bytes) retrieved the initialization of thefrom a 32-bytesRNGHardware basedentropy source(time, clock,thermal noise,interrupts, andmemory, etc).Stored in volatilememoryReset or loss of power11LSC PrivateKey (RSA)Generated by themodule butconverted into acertificate by theCAPF/CUCM(Note that theRSA keysgenerated must beat least a 1024 bitkey)/flash0/sec/lsc0/phoneKey.pvtZeroized by resetting phoneto default settingsPrivate key for locallyissued certificates. Usedfor TLS negotiation withCUCM and Web ClientsThe services accessing the Critical Service Parameters (CSPs), the type of access and which role accesses the CSPs are listedin Table 4.CSP 11CSP 10CSP 9CSP 8CSP 7CSP 6CSP 5CSP 4CSP 3CSP 2CSP/Role/ServiceAccess PolicyCSP 1Cisco 6921, 6941, 6945, and 6961 Phones Validation Level by SectionCritical SecurityParameterTable 4Role/ServiceUser RoleMake and ReceiveCallsRun Self-Tests8FIPS 140-2 Non-Proprietary Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961v 1.0

Customize Sound,Display, andkeypad parametersView and EditNetwork ProfileParametersView and EditSystemConfigurationView and EditDevice informationDisplay ModelInformationView Phone StatusCrypto-OfficerRoler readw writeEstablish TLSsessions erformconfiguration of thephonerwdrwdrwdrwdrwdrwdrwdrwdrwdrwdrwdTransport Keys tothe phonerwdrwdrwdrwdrwdrwdrwdrwdrwdrwdrwdView Status of thephonerrrrrrrrrrrReboot the phoneddddddddddReset the phoneddddddddddInitiate Self-testsdddddddddddd deleteSelf-TestsThe 6921, 6941, 6945, and 6961 Phones include an array of self-tests that are run during startup and periodically duringoperations to prevent any secure data from being released and to ensure all components are functioning correctly.9FIPS 140-2 Non-Proprietary Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961v 1.0

Table 56921, 6941, 6945, and 6961 Power-On Self-TestsImplementationTests PerformedTI DSP Library AES KAT HMAC SHA-1 KAT RSA KAT (signature/verification) AES KAT Triple-DES KAT HMAC SHA-1 KAT RNG KATSMAPI from BroadcomEPT library AES KAT HMAC SHA-1 KATModule Firmware Firmware Integrity TestOpenSSL 0.9.8KThe phone performs all power-on self-tests automatically at boot when FIPS mode is enabled. The power-on self-tests areperformed after the cryptographic systems are initialized. In the unlikely event that a power-on self-test fails, the moduletransitions into an error state and an error message is displayed via status output interface.Table 6 lists the conditional self-tests that the 6921, 6941, 6945, and 6961 phones perform.Table 66921, 6941, 6945, and 6961 Conditional Self-TestsImplementationTests PerformedTI DSP Library Conditional Bypass testOpenSSL 0.9.8K Pairwise consistency test for RSA Continuous Random Number Generator Test for theFIPS-approved RNG Conditional Bypass testSMAPI from BroadcomEPT libraryMitigation of Other AttacksThe 6921, 6941, 6945, and 6961 do not claim to mitigate any attacks in a FIPS-approved mode of operation.10FIPS 140-2 Non-Proprietary Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961v 1.0

Secure OperationThe Cisco 6921, 6941, 6945, and 6961 phones meet FIPS 140-2 Level 1 requirements. This section describes how to placeand keep the phone in a FIPS-approved mode of operation. Operating the phone without maintaining the following settingswill remove the phone from the FIPS-approved mode of operation.Crypto Officer Guidance – System InitializationThe Crypto Officer must create a device security profile in Call manager. Below, find instructions on creating the devicesecurity profile.1.Login to Call Manager2.Navigate to System - Security Profile - Phone Security Profile.3.Click the Add New button4.Select “Cisco 6921, 6941, 6945 or 6961” from the drop down box and click next.5.From the Drop down box, select SCCP for the security protocol profile and click next.6.In the Name box, give an appropriate name such as “Cisco 6921, 6941, 6945 or 6961 FIPS Security Profile”,or “Cisco 69xx FIPS Security Profile”, followed by an appropriate description.7.In the section titled, “Phone Security Profile CAPF Information, Select the “Authentication Mode” to be“By Existing Certificate (Precedence to LSC), and select the key size to be 2048 bits.8.While still in the “Phone Security Profile CAPF Information”, select the device security mode to“encrypted”9.Click “Save”Crypto Officer Guidance – System ConfigurationThe Cisco 6921, 6941, 6945, and 6961 phones were validated with software version 9.2(1)SR1 or 9.4(1) SR1. This is the onlyallowable image for the FIPS-approved mode of operation. The image names can be found below, in Table 7Table 7FIPS Image namesCisco Unified IP Phone model9.2.1 SR19.4(1) SR16921, 6941, and cop.sgncmterm-6945-sccp.9-4-13SR1.cop.sgnThe Crypto Officer must configure and enforce the following initialization steps:Login to Call Manager Navigate to phone page Select the 6921, 6941, 6945 or 6961 in the list of phones Click on the phone in question to navigate to the configuration page.11FIPS 140-2 Non-Proprietary Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961v 1.0

Find the section titled “Product Specific Configuration Layout” and make sure that both web accessand SSH are disabled Find the section titled “Protocol Specific Information” and select the device security profile that youcreated in the previous section above. At the bottom of the list of configuration items, select to enable FIPS mode. Save the configurations by clicking on save. Reset the phone by clicking resetApproved Cryptographic AlgorithmsThe Cisco 6921, 6941, 6945, and 6961 phones support many different cryptographic algorithms; however, when configuredfor FIPS compliant operation (by following the instructions of this section, the module will only utilize FIPS-approved andFIPS allowed cryptographic algorithms. Table 8 lists all FIPS approved algorithms supported by the module.Table 8Algorithm6921, 6941, 6945, and 6961 Algorithm CertificatesTI DSP LibraryOpenSSL LibrarySMAPI from 3515331538HMAC SHA-1102510231028RNGN/A930N/ARSAN/A867N/ANon-FIPS Approved AlgorithmsThe 6921, 6941, 6945, and 6961 implement the following non-FIPS-approved cryptographic algorithms: MD5 MD5 HMAC RSA (allowed in FIPS mode for key transport) (key wrapping; key establishment methodology provides 80 or 112 bits ofencryption strength)Related DocumentationThis document deals only with operations and capabilities of the phone in the technical terms of a FIPS 140-2 cryptographicdevice security policy. More information is available on the phone from the sources listed in this section and from thefollowing source: The NIST Cryptographic Module Validation Program website (http://csrc.nist.gov/cryptval/) contains contactinformation for answers to technical or sales-related questions for the 6921, 6941, 6945, and 6961 phones.12FIPS 140-2 Non-Proprietary Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961v 1.0

Obtaining DocumentationCisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtaintechnical assistance and other technical resources. These sections explain how to obtain technical information from CiscoSystems.Cisco.comYou can access the most current Cisco documentation at this URL:http://www.cisco.com/techsupportYou can access the Cisco website at this URL:http://www.cisco.comYou can access international Cisco websites at this URL:http://www.cisco.com/public/countries languages.shtmlProduct Documentation DVDCisco documentation and additional literature are available in the Product Documentation DVD package, which may haveshipped with your product. The Product Documentation DVD is updated regularly and may be more current than printeddocumentation.The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. TheDVD enables you to access multiple versions of hardware and software installation, configuration, and command guides forCisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentationthat is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of thedocumentation available.The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco directcustomers) can order a Product Documentation DVD (product number DOC-DOCDVD ) from Cisco Marketplace at ng DocumentationBeginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store inthe Cisco Marketplace at this red Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT bycalling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also orderdocumentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States andCanada, or elsewhere at 011 408 519-5001.13FIPS 140-2 Non-Proprietary Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961v 1.0

Documentation FeedbackYou can rate and provide feedback about Cisco technical documents by completing the online feedback form that appearswith the technical documents on Cisco.com.You can send comments about Cisco documentation to bug-doc@cisco.com.You can submit comments by using the response card (if present) behind the front cover of your document or by writing tothe following address:Cisco SystemsAttn: Customer Document Ordering170 West Tasman DriveSan Jose, CA 95134-9883We appreciate your comments.Cisco Product Security OverviewCisco provides a free online Security Vulnerability Policy portal at this URL:http://www.cisco.com/en/US/products/products security vulnerability policy.htmlFrom this site, you can perform these tasks: Report security vulnerabilities in Cisco products. Obtain assistance with security incidents that involve Cisco products. Register to receive security information from Cisco.A current list of security advisories and notices for Cisco products is available at this URL:http://www.cisco.com/go/psirtIf you prefer to see advisories and notices as they are updated in real time, you can access a Product Security IncidentResponse Team Really Simple Syndication (PSIRT RSS) feed from this URL:http://www.cisco.com/en/US/products/products psirt rss feed.htmlReporting Security Problems in Cisco ProductsCisco is committed to delivering secure products. We test our products internally before we release them, and we strive tocorrect all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contactPSIRT: Emergencies — security-alert@cisco.comAn emergency is either a condition in which a system is under active attack or a condition for which a severe and urgentsecurity vulnerability should be reported. All other conditions ar

Cisco Unified IP Phone 6921, 6941, 6945, and 6961 Introduction This is a non-proprietary Cryptographic Module Security Policy for the Cisco Unified IP Phone 6921, 6941, 6945, and 6961. This policy describes how the Cisco Unified IP Phone 6921, 6941, 6945, and 6961meet the requirements of FIPS 140-2.

Related Documents:

FIPS 140-2 Security Policy KeyPair FIPS Object Module for OpenSSL Page 4 of 18 1 Introduction This document is the non-proprietary security policy for the KeyPair FIPS Object Module for OpenSSL (FIPS 140-2 Cert. #3503), hereafter referred to as the Module. The Module is a software library providing a C language application program interface (API) for use by

Wireless Access Points with FIPS 140-2 Level 2 validation from Aruba Networks. This security policy describes how the AP meets the security requirements of FIPS 140-2 Level 2, and how to place and maintain the AP in a secure FIPS 140-2 mode. This policy was prepared as part of the FIPS 140-2 Level 2 validation of the product.

This Security Policy describes how the Dual Interface Security Controller SLE78 and Java Card Platform binary code meets the security requirements of FIPS 140-2 and CM’s operation in a secure FIPS 140-2 mode. This policy was prepared as part of the Level 3 FIPS 140-2 validation of the module. FIPS 140-2

LogRhythm FIPS Object Module FIPS 140-2 Security Policy Page 3 of 33 References Reference Full Specification Name [ANS X9.31] Digital Signatures Using Reversible Public Key Cryptography for the Financial Services Industry (rDSA) [FIPS 140-2] Security Requirements for Cryptographic modules, May 25, 2001 [FIPS 180-4] Secure Hash Standard

FIPS 140-2 mode. This policy was prepared as part of the Level 2 FIPS 140-2 validation of the module. Note This document may be copied in its entirety and without modification. All copies must include the copyright notice and statements on the last page. FIPS 140-2 (Federal Information Processing Standards Publication 140-2 — Security .

918 - OpenSSL FIPS Object Module v1.1.2 - 02/29/2008 140-2 L1 1051 - OpenSSL FIPS Object Module v 1.2 - 11/17/2008 140-2 L1 1111 - OpenSSL FIPS Runtime Module v 1.2 - 4/03/2009 140-2 L1 Note: Windows FIPS algorithms used in this product may have only been tested when the FIPS mode bit was set. While the

FIPS 140-2 Non-Proprietary Security Policy for WatchGuard Technologies Inc. Firebox Page 5 of 52 1 Introduction This document is a FIPS 140-2 Security Policy for WatchGuard [s Firebox Security System. This policy describes how the Firebox M270, M370, M470, M570, and M670 models (hereafter referred to as the

FortiOS 5.2 FIPS 140-2 Security Policy 01-525-296259-20151016 2 Overview This document is a FIPS 140-2 Security Policy for Fortinet Incorporated’s FortiOS 5.2 firmware, which runs on the FortiGate family of security appliances. This policy describes how the FortiOS 5.2 firmware (hereafter referred to as the ‘module’) meets the FIPS 140-2