Cisco ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, ASA 5512-X, ASA 5515-X, ASA 5516-X, ASA 5525-X, ASA 5545-X, ASA 5555-X, ASA 5585-X SSP-10, 5585-X SSP-20, 5585-X SSP-40 and 5585-X SSP-60 Adaptive Security Appliances FIPS 140-2 Non Proprietary Security Policy Level 2 Validation Version 1.2 April 12, 2016 Table of Contents 1 INTRODUCTION.................................................................................................................... 1 1.1 PURPOSE ............................................................................................................................. 1 1.2 MODULE VALIDATION LEVEL ............................................................................................ 1 1.3 REFERENCES ....................................................................................................................... 1 1.4 TERMINOLOGY ................................................................................................................... 2 1.5 DOCUMENT ORGANIZATION ............................................................................................... 2 2 CISCO ASA 5500-X SERIES SECURITY APPLIANCES ............................................... 3 2.1 CRYPTOGRAPHIC MODULE PHYSICAL CHARACTERISTICS .................................................. 3 2.2 CRYPTOGRAPHIC BOUNDARY ............................................................................................. 4 2.3 MODULE INTERFACES ......................................................................................................... 4 2.4 ROLES AND SERVICES ....................................................................................................... 13 2.5 USER SERVICES ................................................................................................................ 14 2.6 CRYPTO OFFICER SERVICES.............................................................................................. 15 2.7 NON-FIPS MODE SERVICES .............................................................................................. 16 2.8 UNAUTHENTICATED SERVICES ......................................................................................... 17 2.9 CRYPTOGRAPHIC KEY/CSP MANAGEMENT ...................................................................... 17 2.10 CRYPTOGRAPHIC ALGORITHMS ........................................................................................ 22 Approved Cryptographic Algorithms ................................................................................................................................ 22 Non-FIPS Approved Algorithms Allowed in FIPS Mode ................................................................................................. 23 Non-Approved Cryptographic Algorithms ........................................................................................................................ 23 2.11 SELF-TESTS ...................................................................................................................... 23 2.12 PHYSICAL SECURITY......................................................................................................... 24 2.12.1 Opacity Shield Security .......................................................................................................................................... 25 ASA 5506-X, 5506H-X and 5506W-X Opacity Shield................................................................................................. 25 ASA 5508-X and ASA 5516-X Opacity Shield ............................................................................................................ 26 ASA 5585-X Opacity Shield ......................................................................................................................................... 26 2.12.2 Tamper Evidence Labels (TELs) ............................................................................................................................ 27 Appling Tamper Evidence Labels ................................................................................................................................. 44 3 SECURE OPERATION ...................................................................................................... 45 3.1 CRYPTO OFFICER GUIDANCE - SYSTEM INITIALIZATION .................................................. 45 3.2 CRYPTO OFFICER GUIDANCE - SYSTEM CONFIGURATION................................................. 46 3.3 IDENTIFYING ROUTER OPERATION IN AN APPROVED MODE ............................................. 47 TABLES TABLE 1 MODULE VALIDATION LEVEL ............................................................................................................................................................ 1 TABLE 2 MODULE INTERFACES......................................................................................................................................................................... 5 TABLE 3 USER SERVICES ..................................................................................................................................................................................15 TABLE 4 CRYPTO OFFICER SERVICES .............................................................................................................................................................16 TABLE 5 NON-APPROVED SERVICES ..............................................................................................................................................................16 TABLE 6 CRYPTOGRAPHIC KEYS AND CSPS ..................................................................................................................................................21 TABLE 7 APPROVED CRYPTOGRAPHIC ALGORITHMS AND ASSOCIATED CERTIFICATE NUMBER.........................................................22 TABLE 8 TAMPER LABELS AND OPACITY SHIELD QUANTITIES .................................................................................................................25 DIAGRAMS DIAGRAM 1 BLOCK DIAGRAM ............................................................................................................................................................................ 4 FIGURES FIGURE 1 CISCO ASA 5506-X AND ASA 5506W-X APPLIANCE FONT PANEL ..................................................................................... 5 FIGURE 2 CISCO ASA 5506-X AND ASA 5506W-X APPLIANCE REAR PANEL ...................................................................................... 5 FIGURE 3 ASA 5506H-X APPLIANCE REAR PANEL...................................................................................................................................... 6 FIGURE 4 ASA 5506H-X APPLIANCE FRONT PANEL .................................................................................................................................. 6 FIGURE 5 ASA 5508-X AND ASA 5516-X APPLIANCES REAR PANEL .................................................................................................... 7 FIGURE 6 ASA 5508-X AND ASA 5516-X APPLIANCES FRONT PANEL.................................................................................................. 8 1 Introduction 1.1 Purpose This is a non-proprietary Cryptographic Module Security Policy for the Cisco ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, ASA 5512-X, ASA 5515-X, ASA 5516-X, ASA 5525-X, ASA 5545-X, ASA 5555-X, ASA 5585-X SSP-10, 5585-X SSP-20, 5585-X SSP-40 and 5585-X SSP-60 Adaptive Security Appliances running Firmware 9.4; referred to in this document as appliances. This security policy describes how the modules meet the security requirements of FIPS 140-2 Level 2 and how to run the modules in a FIPS 140-2 mode of operation and may be freely distributed. FIPS 140-2 (Federal Information Processing Standards Publication 140-2 — Security Requirements for Cryptographic Modules) details the U.S. Government requirements for cryptographic modules. More information about the FIPS 140-2 standard and validation program is available on the NIST website at http://csrc.nist.gov/groups/STM/index.html. 1.2 Module Validation Level The following table lists the level of validation for each area in the FIPS PUB 140-2. No. Area Title Level 1 Cryptographic Module Specification 2 2 Cryptographic Module Ports and Interfaces 2 3 Roles, Services, and Authentication 3 4 Finite State Model 2 5 Physical Security 2 6 Operational Environment N/A 7 Cryptographic Key management 2 8 Electromagnetic Interface/Electromagnetic Compatibility 2 9 Self-Tests 2 10 Design Assurance 2 11 Mitigation of Other Attacks N/A Overall module validation level 2 Table 1 Module Validation Level 1.3 References This document deals with the specification of the security rules listed in Table 1 above, under which the Cisco ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, ASA 5512-X, ASA 5515-X, ASA 5516-X, ASA 5525-X, ASA 5545-X, ASA 5555-X, ASA 5585-X SSP-10, 5585-X SSP-20, 5585-X SSP-40 and 5585-X SSP-60 cryptographic modules will operate, including the rules derived from the requirements of FIPS 140-2, FIPS 140-2IG and additional rules imposed by Cisco Systems, Inc. More information is available on the routers from the following sources: The Cisco Systems website contains information on the full line of Cisco Systems security. Please refer to the following website: http://www.cisco.com/c/en/us/products/index.html © Copyright 2016 Cisco Systems, Inc. 1 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. http://www.cisco.com/en/US/products/ps6120/index.html For answers to technical or sales related questions please refer to the contacts listed on the Cisco Systems website at www.cisco.com. The NIST Validated Modules website (http://csrc.nist.gov/groups/STM/cmvp/validation.html) contains contact information for answers to technical or sales-related questions for the module. 1.4 Terminology In this document, the Cisco ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, ASA 5512-X, ASA 5515-X, ASA 5516-X, ASA 5525-X, ASA 5545-X, ASA 5555-X, ASA 5585-X SSP-10, 5585-X SSP-20, 5585-X SSP-40 and 5585-X SSP-60 models identified are referred to as ASA 5500 Security Appliances, ASA, Modules, Appliances or the Systems. 1.5 Document Organization The Security Policy document is part of the FIPS 140-2 Submission Package. In addition to this document, the Submission Package contains: Vendor Evidence document Finite State Machine Other supporting documentation as additional references This document provides an overview of the Cisco ASA 5500 Security Appliances models identified in section 1.2 above and explains the secure configuration and operation of the module. This introduction section is followed by Section 2, which details the general features and functionality of the appliances. Section 3 specifically addresses the required configuration for the FIPS-mode of operation. With the exception of this Non-Proprietary Security Policy, the FIPS 140-2 Validation Submission Documentation is Cisco-proprietary and is releasable only under appropriate non- disclosure agreements. For access to these documents, please contact Cisco Systems. © Copyright 2016 Cisco Systems, Inc. 2 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. 2 Cisco ASA 5500-X Series Security Appliances Cisco® Adaptive Security Appliances, ASA 5500-X Series Next-Generation Firewalls provide balanced security effectiveness with productivity. This solution offers the combination of the industry's most deployed stateful firewall with a comprehensive range of next-generation network security services, intrusion prevention system (IPS), content security, secure unified communications, TLSv1, SSHv2, IKEv2, Remote Access VPN [With TLSv1/ DTLSv1 and IKEv2/ ESPv3] and Suite B. Cisco Adaptive Security Appliance (ASA) Software is the core operating system for the Cisco ASA Family. It delivers enterprise-class firewall capabilities for the ASA devices in an array of form factors - standalone appliances tailor-made small and midsize businesses, midsize appliances for businesses improving security at the Internet edge, high performance and throughput appliances for demanding enterprise data centers, high-performance blades that integrate with the Cisco Catalyst 6500 Series Switches and virtual instances to provide enterprise-class security for private and public clouds. Small Scale Models:  ASA 5506-X  ASA 5506H-X  ASA 5506W-X  ASA 5508-X  ASA 5512-X  ASA 5515-X  ASA 5516-X Medium Scale Models:  ASA 5525-X  ASA 5545-X  ASA 5555-X Large Enterprise Models:  ASA 5585-X SSP-10  ASA 5585-X SSP-20  ASA 5585-X SSP-40  ASA 5585-X SSP-60 2.1 Cryptographic Module Physical Characteristics The Cisco ASA 5500-X Series Security Appliances deliver enterprise-class security for business- to-enterprise networks in a modular, purpose-built appliance. Its versatile one-rack unit (1RU, ASA 5506-X, 5506H-X, 5506W-X, 5508-X, 5512-X, 5515-X, 5516-X, 5525-X, 5545-X, and 5555-X) and two-rack unit (2RU, ASA 5585-10, 5585-20, 5585-40 and 5585-60). © Copyright 2016 Cisco Systems, Inc. 3 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. 2.2 Cryptographic Boundary The Cisco ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, ASA 5512-X, ASA 5515-X, ASA 5516-X, ASA 5525-X, ASA 5545-X, ASA 5555-X, ASA 5585-X SSP-10, 5585-X SSP-20, 5585-X SSP-40 and 5585-X SSP-60 contain a multiple-chip standalone cryptographic module. The cryptographic boundary is defined as-the entire modules’ chassis unit encompassing the "top," "front," "left," "right," “rear” and "bottom" surfaces of the case along with associated opacity shields. Physical boundary ASA System Intel Processor Control/Service Plane Crypto Module Cryptographic boundary Diagram 1 Block Diagram 2.3 Module Interfaces The module provides a number of physical and logical interfaces to the device, and the physical interfaces provided by the module are mapped to the following FIPS 140-2 defined logical interfaces: data input, data output, control input, status output, and power. The module provided no power to external devices and takes in its power through normal power input/cord. The logical interfaces and their mapping are described in the following tables: FIPS 140-2 ASA 5506-X, ASA 5506W-X, ASA 5506H-X, ASA ASA 5585-X Logical 5508-X, ASA 5516-X, ASA 5512-X, ASA 5515-X, Physical Interface ASA 5525-X, Interface ASA 5545-X, ASA 5555-X Physical Interface Ethernet ports Data Input MGMT Port Interface Console Port © Copyright 2016 Cisco Systems, Inc. 4 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Ethernet ports Data MGMT Port Output Console Port Interface Ethernet ports Ethernet ports Control MGMT Port MGMT Port Input Console Port Console Port Interface Reset Pin/Switch/Button (only on 5506-X, 5506H-X, Eject/Reset 5506W-X, 5508-X, 5512-X 5515-X, 5516-X, 5525-X) Switch (not currently in use) Ethernet ports Status MGMT Port Output LEDs Interface Console Port Power Plug Power Interface USB Port USB Port Unused Aux Port Interface Table 2 Module Interfaces Figure 1 Cisco ASA 5506-X and ASA 5506W-X Appliance Font Panel 8 5 6 9 10 Figure 2 Cisco ASA 5506-X and ASA 5506W-X Appliance Rear Panel 1 Power LED: 6 Console Ports: Green -> power applied OK RJ-45 and mini-USB Connector if mini-USB is connected, RJ-45 becomes disconnected 2 Status LED: 7 GE Management Port Green blinking -> system is booting up Green solid -> successful boot Orange -> error during boot-up USB port for external storage – shows up as 3 Active LED: 8 Green -> unit is Active in failover pair disk1 Orange -> unit is Standby in failover pair Off -> not part of a failover pair 4 WLAN Module 9 Reset Pin Only lit for 5506W-X Controlled by AP module, same color/blink behavior as existing AP702i Access Point 5 GE ports: 10 Power Supply Left-side LED Green -> link Right-side LED blinking -> network activity © Copyright 2016 Cisco Systems, Inc. 5 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 3 ASA 5506H-X Appliance Rear Panel Power cord socket. The chassis power-supply socket. See Power Supply for more information 1 about the chassis power supply. The ASA is powered on when you plug in the AC power supply. Note Status LEDs The locations and meanings of the status LEDs are described in Status Lights. 2 Network data ports Four Gigabit Ethernet RJ-45 (8P8C) network I/O interfaces. The ports are 3 numbered (from top to bottom) 1, 2, 3, 4,. Each port includes a pair of LEDs, one each for connection status and link status. The ports are named and numbered Gigabit Ethernet 1/1 through Gigabit Ethernet 1/4. See Network Ports for additional information. Management port A Gigabit Ethernet interface restricted to network management access only. 4 Connect with an RJ-45 cable. Console ports Two serial ports, a standard RJ-45 (8P8C), and a mini USB Type B, are 5 provided for management access via an external system. See Console Ports for additional information. USB port A standard USB Type A port is provided that allows the attachment of an 6 external device, such as mass storage. See Internal and External Flash Storage for additional information. Reset button A small recessed button that if pressed for longer than three seconds resets the 7 ASA to its default “as-shipped” state following the next reboot. Configuration variables are reset to factory default. However, the flash is not erased and no files are removed. You can use the service sw-reset-button to disable the reset button. Note The default is enabled. Figure 4 ASA 5506H-X Appliance Front Panel © Copyright 2016 Cisco Systems, Inc. 6 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 5 ASA 5508-X and ASA 5516-X Appliances Rear Panel © Copyright 2016 Cisco Systems, Inc. 7 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 6 ASA 5508-X and ASA 5516-X Appliances Front Panel Figure 7 ASA 5512-X, ASA 5515-X and ASA 5525-X Appliances Front Panel LED Description 1 Power Button A hard switch that turns the system on and off. Once depressed, the button stays in the "on" position:  On–The power symbol on the button illuminates.  Off–The power symbol on the button is dark. For information about the power state, see the “Power Supply Considerations” section. 2 Hard disk release Releases the hard disk from the device. button 3 Alarm Indicates system operating status:  Off–Normal operating system function.  Flashing amber–Critical Alarm indicting one or more of the following: - a major failure of a hardware or software component. - an over-temperature condition. - power voltage is outside of the tolerance range. 4 VPN Indicates VPN tunnel status:  Solid green–VPN tunnel is established.  Off–No VPN tunnel is established. 5 HD Indicates Hard Disk Drive status:  Flashing green–Proportioned to read/write activity.  Solid amber–Hard disk drive failure.  Off–The power symbol on the button is dark. 6 PS Indicates the power supply status. 7 Active Indicates the status of the failover pair:  Solid green–Failover pair is operating normally.  Off– Failover is not operational. © Copyright 2016 Cisco Systems, Inc. 8 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. 8 Boot Indicates power-up diagnostics:  Flashing green–Power-up diagnostics are running, or system is booting.  Solid amber–System has passed power-up diagnostics.  Off– Power-up diagnostics are not operational. Figure 8 ASA 5512-X, ASA 5515-X and ASA 5525-X Appliances Rear Panel Description 1 Management 0/0 Indicates the Gigabit Ethernet Interface that is restricted to management use only. interface Connect with an RJ-45 cable. (See the “Management 0/0 Interface on the ASA 5500-S Series” section.) 2 Power supply Indicates the chassis power supply. 3 RJ-45 Ethernet Indicates the Gigabit Ethernet customer data interfaces. ports The top row port numbers are (from left to right) 5, 3, 1. The bottom row port numbers are (from left to right) 4, 2, 0. 4 USB ports Indicates the two USP standard ports. (See the “External USP Support” section.) 5 Console port Indicates the console port that directly connects a computer to the ASA. © Copyright 2016 Cisco Systems, Inc. 9 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 9 ASA 5545-X and ASA 5555-X Appliances Front Panel 4 © Copyright 2016 Cisco Systems, Inc. 10 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 10 ASA 5545-X and ASA 5555-X Appliances Rear Panel Figure 11 ASA 5585-X SSP-10 and SSP-20 Appliance Front Panel © Copyright 2016 Cisco Systems, Inc. 11 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 12 ASA 5585-X SSP-40 and SSP-60 Appliance Front Panel Reserved bays for hard-disk drives Auxiliary Port (RJ45) 1 9 Ethernet ports (not present on SSP 10 or SSP 20) Vent (on Console Port (RJ45) 2 10 SSP 10 and SSP 20) Ethernet ports Eject/Reset (Reserved for future OIR use) 3 11 Vent (on SSP 40 and SSP 60) and Ethernet ports (on SSP SSP/IPS SSP removal screws 4 12 10 or SSP 20) Ethernet ports IPS SSP 5 13 Management ports SSP 6 14 USB port 7 Front Panel Indicators 8 Figure 13 ASA 5585-X Appliance Front Panel Indicators 1 PWR 6 PS1 2 BOOT 7 PS0 3 ALARM 8 HDD1 4 ACT 9 HDD2 5 VPN © Copyright 2016 Cisco Systems, Inc. 12 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 14 ASA 5585-X Appliance Rear Panel 1 Power supply module 5 Power supply module indicators 2 Power supply module/fan module removal 6 Power supply module or fan screws module handle 3 Power supply module plug 7 Fan module 4 Toggle On/Off switch for power 8 Fan module indicator Figure 15 ASA 5585-X Appliance Rear Panel Indicators 1 AC ON 2 FAN OK 3 OUT FAIL 2.4 Roles and Services The security appliances can be accessed in one of the following ways: • Console Port • Telnet over IPsec • SSH v2 • ASDM via HTTPS/TLS Authentication is identity-based. Each user is authenticated by the module upon initial access to the module. As required by FIPS 140-2, there are two roles in the security appliances that operators may assume: Crypto Officer role and User role. The administrator of the security appliances assumes the Crypto Officer role in order to configure and maintain the router using Crypto Officer services, while the Users exercise only the basic User services. The module also supports RADIUS and TACACS+ as another means of authentication, allowing the storage of usernames and passwords on an external server as opposed to using the module’s internal database for storage. © Copyright 2016 Cisco Systems, Inc. 13 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. The User and Crypto Officer passwords and all shared secrets must each be at a minimum eight (8) characters long. There must be at least one special character and at least one number character (enforced procedurally) along with six additional characters taken from the 26 upper case, 26 lower case, 10 numbers and 32 special characters. See the Secure Operation section for more information. If six (6) special/alpha/number characters, one (1) special character and one (1) number are used without repetition for an eight (8) digit value, the probability of randomly guessing the correct sequence is one (1) in 187,595,543,116,800. This is calculated by performing 94 x 93 x 92 x 91 x 90 x 89 x 32 x 10. In order to successfully guess the sequence in one minute would require the ability to make over 3,126,592,385,280 guesses per second, which far exceeds the operational capabilities of the module. Additionally, when using RSA based authentication, RSA key pair has modulus size of 2048 bits, thus providing 112 bits of strength. Assuming the low end of that range, an attacker would have a 1 in 2112 chance of randomly obtaining the key, which is much stronger than the one in a million chance required by FIPS 140-2. To exceed a one in 100,000 probability of a successful random key guess in one minute, an attacker would have to be capable of approximately 1.8x1021 attempts per minute, which far exceeds the operational capabilities of the modules to support. The User and Crypto Officer passwords and all shared secrets must each be at least eight (8) characters long, including at least one letter and at least one number character, in length (enforced procedurally). 2.5 User Services A User enters the system by accessing the console port with a terminal program or via IPsec protected telnet or SSH session to an Ethernet port or ASDM via HTTPS/TLS. The module prompts the User for username and password. If the password is correct, the User is allowed entry to the module management functionality. The other means of accessing the console is via an IPsec session. This session is authenticated either using a shared secret or RSA digital signature authentication mechanism. The services available to the User role accessing the CSPs, the type of access – read (r), write (w) and zeroized/delete (d) – and which role accesses the CSPs are listed below: Services Description Keys and CSPs Access Status Functions View state of interfaces and protocols, version of IOS currently running. Operator password (r) Terminal Functions Adjust the terminal session (e.g., lock the terminal, adjust flow control). Operator password (r) Directory Services Display directory of files kept in flash memory. Operator password (r) Self-Tests Execute the FIPS 140 start-up tests on demand N/A IPsec VPN Negotiation and encrypted data transport via IPSec VPN Operator password (r, w, d) and [skeyid, skeyid_d, SKEYSEED, IKE session encrypt key, IKE session authentication key, ISAKMP preshared, IKE authentication private Key, IKE authentication public key, © Copyright 2016 Cisco Systems, Inc. 14 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Services Description Keys and CSPs Access IPsec encryption key, IPsec authentication key] (d) SSH Functions Negotiation and encrypted data transport via SSH Operator password (r.w.d), SSH Traffic Keys (d) HTTPS Functions (TLS) Negotiation and encrypted data transport via HTTPS Operator password (r, w, d) and [TLS pre-master secret, TLS Traffic Keys] (d) Table 3 User Services 2.6 Crypto Officer Services The Crypto Officer role is responsible for the configuration and maintenance of the security appliances and authenticates from the enable command (for local authentication) or the login command (for AAA authentication) from the user services. The Crypto Officer services consist of the following: The Crypto Officer role is responsible for the configuration of the router. The services available to the Crypto Officer role accessing the CSPs, the type of access – read (r), write (w) and zeroized/delete (d) – and which role accesses the CSPs are listed below: Services Description Keys and CSPs Access Configure the Security Blade Define network interfaces and settings, create command [ISAKMP preshared, Operator password, aliases, set the protocols the router will support, enable Enable password] - (r, w, d), [IKE session interfaces and network services, set system date and time, and encrypt key, IKE session authentication key, load authentication information. IKE authentication private Key, IKE authentication public key, IPsec encryption key, IPsec authentication key] – (w, d) Define Rules and Filters Create packet Filters that are applied to User data streams on Operator password, Enable password - (r, w, d) each interface. Each Filter consists of a set of Rules, which define a set of packets to permit or deny based on characteristics such as protocol ID, addresses, ports, TCP connection establishment, or packet direction. View Status Functions View the router configuration, routing tables, active sessions Operator password, Enable password - (r, w, d) health, temperature, memory status, voltage, packet statistics, review accounting logs, and view physical interface status. Manage the Security Blade Log off users, shutdown or reload the router, erase the flash Operator password, Enable password - (r, w, d) memory, manually back up router configurations, view complete configurations, manager user rights, and restore router configurations. Configure Encryption/Bypass Set up the configuration tables for IP tunneling. Set preshared [ISAKMP preshared, Operator password, keys and algorithms to be used for each IP range or allow Enable password] - (r, w, d); [IKE session plaintext packets to be set from specified IP address. encrypt key, IKE session authentication key, IKE authentication private Key, IKE authentication public key, IPsec encryption key, IPsec authentication key] – (w, d) TLS pre-master secret, TLS Traffic Keys – (r, TLS VPN (TLSv1.0) Configure SSL VPN parameters, provide entry and output of CSPs. w, d) SSH v2 Configure SSH v2 parameter, provide entry and output of SSHv2 Private Key, SSHv2 Public Key and CSPs. SSHv2 session key (r, w, d) © Copyright 2016 Cisco Systems, Inc. 15 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. IPsec VPN Configure IPsec VPN parameters, provide entry and output of ISAKMP preshared (r, w, d), [skeyid, skeyid_d, CSPs. SKEYSEED, IKE session encrypt key, IKE session authentication key, IKE authentication private Key, IKE authentication public key, IPsec encryption key, IPsec authentication key] – (w, d) Self-Tests Execute the FIPS 140 start-up tests on demand N/A User services The Crypto Officer has access to all User services. Operator password (r, w, d) Local Certificate Authority Allows the ASA to be configured as a Root Certificate N/A Authority and issue user certificates for SSL VPN use (AnyConnect and Clientless). The ASA can then be configured to require client certificates for authentication. Zeroization Zeroize cryptographic keys/CSPs by running the zeroization All CSPs (d) methods classified in table 7, Zeroization column. Table 4 Crypto Officer Services 2.7 Non-FIPS mode Services The cryptographic module in addition to the above listed FIPS mode of operation can operate in a non-FIPS mode of operation. This is not a recommended operational mode but because the associated RFC’s for the following protocols allow for non-approved algorithms and non- approved key sizes a non-approved mode of operation exist. So those services listed above with their FIPS approved algorithms in addition to the following services with their non-approved algorithms and non-approved keys sizes are available to the User and the Crypto Officer. Prior to using any of the Non-Approved services in Section 2.7, the Crypto Officer must zeroize all CSPs which places the module into the non-FIPS mode of operation. Services 1 Non-Approved Algorithms Hashing: MD5, MACing: HMAC-SHA-1, MD5 IPsec Symmetric: DES, RC4 Asymmetric: 768-bit/1024-bit RSA (key transport), 1024-bit Diffie-Hellman Hashing: MD5, MACing: HMAC MD5 SSH Symmetric: DES Asymmetric: 768-bit/1024-bit RSA (key transport), 1024-bit Diffie-Hellman Hashing: MD5, MACing: HMAC-SHA-1, MD5 TLS Symmetric: DES, RC4 Asymmetric: 768-bit/1024-bit RSA (key transport), 1024-bit Diffie-Hellman Table 5 Non-approved algorithms in the Non-FIPS mode services Neither the User nor the Crypto Officer are allowed to operate any of these services while in FIPS mode of operation. 1 These approved services become non-approved when using any of non-approved algorithms or non-approved key or curve sizes. When using approved algorithms and key sizes these services are approved. © Copyright 2016 Cisco Systems, Inc. 16 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. All services available can be found at http://www.cisco.com/c/en/us/support/security/asa-5500- series-next-generation-firewalls/products-installation-and-configuration-guides-list.html. This site lists all configuration guides for the ASA systems 2.8 Unauthenticated Services The services for someone without an authorized role are to view the status output from the module’s LED pins and cycle power. 2.9 Cryptographic Key/CSP Management The module administers both cryptographic keys and other critical security parameters such as passwords. All keys and CSPs are protected by the password-protection of the Crypto Officer role login, and can be zeroized by the Crypto Officer. Zeroization consists of overwriting the memory that stored the key or refreshing the volatile memory. Keys are both manually and electronically distributed but entered electronically. Persistent keys with manual distribution are used for pre-shared keys whereas protocols such as IKE, TLS and SSH are used for electronic distribution. All pre-shared keys are associated with the CO role that created the keys, and the CO role is protected by a password. Therefore, the CO password is associated with all the pre-shared keys. The Crypto Officer needs to be authenticated to store keys. Only an authenticated Crypto Officer can view the keys. All Diffie-Hellman (DH) keys agreed upon for individual tunnels are directly associated with that specific tunnel only via the IKE protocol. RSA Public keys are entered into the modules using digital certificates which contain relevant data such as the name of the public key's owner, which associates the key with the correct entity. All other keys are associated with the user/role that entered them. The module pulls in 32 bytes of entropy from a high-jitter free-running oscillators for use with the DRBG. This equates to greater than 256 bits of entropy. Name CSP Type Size Storage Zeroization Description/Generation DRBG entropy SP800-90A 256-bits This is the entropy for SP 800- DRAM Power cycle the input HASH_DRBG (using 90A HASH_DRBG. (plaintext) device SHA-512) HW (onboard Cavium cryptographic processor) based entropy source used to construct seed. DRBG Seed SP800-90A 384-bits Input to the DRBG that DRAM Power cycle the HASH_DRBG (using determines the internal state of (plaintext) device SHA-512) the DRBG. Generated using DRBG derivation function that includes the entropy input from hardware-based entropy source. © Copyright 2016 Cisco Systems, Inc. 17 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Name CSP Type Size Storage Zeroization Description/Generation DRBG V SP800-90A 128-bits The DRBG V is one of the DRAM Power cycle the HASH_DRBG (using critical values of the internal (plaintext) device SHA-512) state upon which the security of this DRBG mechanism depends. Generated first during DRBG instantiation and then subsequently updated using the DRBG update function. DRBG C SP800-90A 256-bits Internal critical value used as DRAM Power cycle the HASH_DRBG (using part of SP 800-90A (plaintext) device SHA-512) HASH_DRBG. Established per SP 800-90A HASH_DRBG. 2048 – 4096 bits The shared secret used in Diffie-Hellman DH DRAM Power cycle the Shared Secret Diffie-Hellman (DH) exchange. (plaintext) device Established per the Diffie- Hellman key agreement. Diffie Hellman DH 224-379 bits The private key used in Diffie- DRAM Power cycle the private key Hellman (DH) exchange. This (plaintext) device key is generated by calling SP800-90A DRBG. 2048 – 4096 bits The public key used in Diffie- Diffie Hellman DH DRAM Power cycle the public key Hellman (DH) exchange. This (plaintext) device key is derived per the Diffie- Hellman key agreement. skeyid Shared Secret 160 bits A shared secret known only to DRAM Power cycle the IKE peers. It was established (plaintext) device via key derivation function defined in SP800-135 KDF and it will be used for deriving other keys in IKE protocol implementation. skeyid_d Shared Secret 160 bits A shared secret known only to DRAM Power cycle the IKE peers. It was derived via (plaintext) device key derivation function defined in SP800-135 KDF (IKEv2) and it will be used for deriving IKE session authentication key. SKEYSEED Shared Secret 160 bits A shared secret known only to DRAM Power cycle the IKE peers. It was derived via (plaintext) device key derivation function defined in SP800-135 KDF (IKEv2) and it will be used for deriving IKE session authentication key. © Copyright 2016 Cisco Systems, Inc. 18 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Name CSP Type Size Storage Zeroization Description/Generation IKE session Triple-DES/AES 168 bits Triple- The IKE session (IKE Phase I) DRAM Power cycle the encrypt key DES or encrypt key. This key is derived (plaintext) device 128/192/256 bits via key derivation function AES defined in SP800-135 KDF (IKEv2). IKE session HMAC SHA-1 160 bits The IKE session (IKE Phase I) DRAM Power cycle the authentication authentication key. This key is (plaintext) device key derived via key derivation function defined in SP800-135 KDF (IKEv2). By running ‘# ISAKMP Pre-shared secret Variable 8 plus The secret used to derive IKE NVRAM preshared characters skeyid when using preshared (plaintext) no crypto secret authentication. This CSP isakmp key’ is entered by the Crypto command Officer. IKE RSA/ ECDSA RSA (2048 bits) RSA/ECDSA private key used NVRAM By running ‘#crypto key authentication or ECDSA in IKE authentication. This key (plaintext) zeroize’ private Key (Curves: P- is generated by calling SP800- 256/P-384) 90A DRBG. command IKE RSA/ ECDSA RSA (2048 bits) RSA/ECDSA public key used NVRAM By running ‘#crypto key authentication or ECDSA in IKE authentication. (plaintext) zeroize’ public key (Curves: P- Internally generated by the 256/P-384) module command IPsec encryption Triple-DES, AES and 168 bits Triple- The IPsec (IKE phase II) DRAM Power cycle the key AES-GCM DES or encryption key. This key is (plaintext) device 128/192/256 bits derived via a key derivation AES function defined in SP800-135 KDF (IKEv2). IPsec HMAC SHA-1 160 bits The IPsec (IKE Phase II) DRAM Power cycle the authentication authentication key. This key is (plaintext) device key derived via a key derivation function defined in SP800-135 KDF (IKEv2). Operator Password 8 plus characters The password of the User role. NVRAM Overwrite with password This CSP is entered by the (plaintext) new password User. Enable password Password 8 plus characters The password of the CO role. NVRAM Overwrite with This CSP is entered by the (plaintext) new password Crypto Officer. By running ‘# RADIUS secret Shared Secret 16 characters The RADIUS shared secret. NVRAM Used for RADIUS (plaintext), no radius-server key’ command Client/Server authentication. This CSP is entered by the Crypto Officer. © Copyright 2016 Cisco Systems, Inc. 19 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Name CSP Type Size Storage Zeroization Description/Generation By running ‘# TACACS+ Shared Secret 16 characters The TACACS+ shared secret. NVRAM secret Used for TACACS+ (plaintext), no tacacs-server key’ command Client/Server authentication. This CSP is entered by the Crypto Officer. By running ‘# SSHv2 Private RSA 2048 bits The SSHv2 private key used in NVRAM Key modulus SSHv2 connection. This key is (plaintext) crypto key zeroize rsa’ generated by calling SP 800- 90A DRBG. command By running ‘# SSHv2 Public RSA 2048 bits The SSHv2 public key used in NVRAM Key modulus SSHv2 connection. This key is (plaintext) crypto key zeroize rsa’ internally generated by the module. command SSHv2 Session Triple-DES/AES 168 bits Triple- This is the SSHv2 session key. DRAM Power cycle the Key DES or It is used to encrypt all SSHv2 (plaintext) device 128/192/256 bits data traffics traversing between AES the SSHv2 Client and SSHv2 Server. This key is derived via key derivation function defined in SP800-135 KDF (SSH). DRAM ECDSA private ECDSA Curves: P- Key pair generation, signature Zeroized upon (plaintext) key 256,384,521 generation/Verification. This API call “#crypto key key is generated by calling SP zeroize ecdsa” 800-90A DRBG. DRAM ECDSA public ECDSA Curves: P- Key pair generation, signature Zeroized upon (plaintext) key 256,384,521 generation/Verification. This API call “#crypto key key is generated by calling SP zeroize ecdsa” 800-90A DRBG. The obfuscated password of the NVRAM Enable secret Shared Secret At least eight Overwrite with (plaintext) characters CO role. However, the new password algorithm used to obfuscate this password is not FIPS approved. Therefore, this password is considered plaintext for FIPS purposes. This password is zeroized by overwriting it with a new password. The Cryptographic Operator optionally configures the module to obfuscate the Enable password. This CSP is entered by the Cryptographic Officer. © Copyright 2016 Cisco Systems, Inc. 20 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Name CSP Type Size Storage Zeroization Description/Generation NVRAM RSA private keys RSA 2048 bits Identity certificates for the Zeroized by “#crypto key (plaintext) security appliance itself and zeroize rsa”, also used in IPSec, TLS, and SSH negotiations. This key was write to startup generated by calling FIPS config, followed approved DRBG. by a module reboot NVRAM RSA public keys RSA 2048 bits Identity certificates for the Zeroized by “#crypto key (plain text) security appliance itself and zeroize rsa”, also used in IPSec, TLS, and SSH negotiations. This key was write to startup generated by calling FIPS config, followed approved DRBG. by a module reboot TLS pre-master Shared Secret At least eight Shared secret created/derived DRAM Automatically secret characters using asymmetric cryptography (plaintext) when TLS from which new HTTPS session is session keys can be created. terminated. This key entered into the module in cipher text form, encrypted by RSA public key. TLS traffic keys Triple-DES/AES 168 bits Triple- Used in HTTPS connections. DRAM Automatically 128/192/256 DES or Generated using TLS protocol. (plain text) when TLS HMAC- 128/192/256 bits This key was derived in the session is SHA1/256/384/512 AES module. terminated Zeroized by Integrity test key RSA-2048 Public key 2048 bits A hard coded key used for Hard coded “#erase flash:” firmware power-up/load for firmware command (or integrity verification. integrity replacing), write testing to startup config, followed by a module reboot Table 6 Cryptographic Keys and CSPs © Copyright 2016 Cisco Systems, Inc. 21 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. 2.10 Cryptographic Algorithms The module implements a variety of approved and non-approved algorithms. Approved Cryptographic Algorithms The routers support the following FIPS 140-2 approved algorithm implementations: Algorithm ASA OS ASA On-board ASA On-board ASA On-board ASA On-board (Firmware) (Cavium (Cavium (Cavium (Cavium Octeon III) Octeon III) Nitrox PX) Nitrox PX) (ASA 5506-X, (ASA 5508-X, (ASA 5512-X, (ASA 5545-X, 5506H-X, 5516-X) 5515-X, 5525- 5555-X, 5585- 5506W-X) X) X SSP10, 5585-X SSP20, 5585- X SSP40, 5585-X SSP60) ASA OS 9.4 ASA CN7020 ASA CN7130 ASA CN1610 ASA CN1620 or CN7130 AES (128/192/256 CBC, GCM) 3439 3301 3301 2472 2050 & 2444 Triple-DES (CBC, 3-key) 1937 1881 1881 1513 1321 SHS (SHA-1/256/384/512) 2839 2737 2737 2091 1794 HMAC (SHA-1/256/384/512) 2188 2095 2095 1514 1247 RSA (PKCS1_V1_5; 2048 bits) 1760 ECDSA (P-256, P-384, P-521) 693 DRBG (SHA-512) 838 819 819 336 332 CVL Component (IKEv2, TLS, SSH) 525 Table 7 Approved Cryptographic Algorithms and Associated Certificate Number Note:  There are some algorithm modes that were tested but not implemented by the module. Only the algorithms, modes, and key sizes that are implemented by the module are shown in this table.  The module's AES-GCM implementation conforms to IG A.5 scenario #3. The module uses a 96-bit IV, which is comprised of a 4 byte salt unique to the crypto session and 8 byte monotonically increasing counter. The module generates new AES-GCM keys if the module loses power.  The SSH, TLS and IPSec protocols have not been reviewed or tested by the CAVP and CMVP. © Copyright 2016 Cisco Systems, Inc. 22 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Non-FIPS Approved Algorithms Allowed in FIPS Mode The module supports the following non-FIPS approved algorithms which are permitted for use in the FIPS approved mode:  Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength)  RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)  NDRNG  HMAC MD5 is allowed in FIPS mode strictly for TLS.  MD5 is allowed in FIPS mode strictly for TLS. Non-Approved Cryptographic Algorithms The module supports the following non-approved cryptographic algorithms that shall not be used in FIPS mode of operation:  DES  HMAC MD5  MD5  RC4  HMAC-SHA1 is not allowed with key size under 112-bits 2.11 Self-Tests The modules include an array of self-tests that are run during startup and periodically during operations to prevent any secure data from being released and to insure all components are functioning correctly. Self-tests performed  ASA Self Tests o POSTs – Adaptive Security Appliance OS (Firmware)  AES Encrypt/Decrypt KATs  DRBG KAT (Note: DRBG Health Tests as specified in SP800-90A Section 11.3 are performed)  ECDSA (sign/verify)  Firmware Integrity Test (using SHA-512 and RSA 2048)  HMAC-SHA-1 KAT  HMAC-SHA-256 KAT  HMAC-SHA-384 KAT  HMAC-SHA-512 KAT  RSA (sign/verify) KATs  SHA-1 KAT © Copyright 2016 Cisco Systems, Inc. 23 This document may be freely reproduced and distributed whole and intact including this Copyright Notice.  SHA-256 KAT  SHA–384 KAT  SHA-512 KAT  Triple-DES Encrypt/Decrypt KATs o POSTs – ASA On-board (Hardware)  AES Encrypt/Decrypt KATs  DRBG KAT (Note: DRBG Health Tests as specified in SP800-90A Section 11.3 are performed)  HMAC-SHA-1 KAT  HMAC-SHA-256 KAT (5585 models only)  HMAC-SHA-384 KAT (5585 models only)  HMAC-SHA-512 KAT (5585 models only)  SHA-1 KAT  SHA-256 KAT (5585 models only)  SHA-384 KAT (5585 models only)  SHA-512 KAT (5585 models only)  Triple-DES Encrypt/Decrypt KATs o Conditional tests - Adaptive Security Appliance OS (Firmware)  RSA pairwise consistency test (encrypt/decrypt and sign/verify)  ECDSA pairwise consistency test  Conditional IPSec Bypass test  Continuous Random Number Generator test for SP800-90A DRBG  Continuous Random Number Generator test for NDRNG o Conditional tests - ASA On-board (Hardware)  Continuous Random Number Generator test for SP800-90A DRBG  Continuous Random Number Generator test for NDRNG The security appliances perform all power-on self-tests automatically when the power is applied. All power-on self-tests must be passed before a User/Crypto Officer can perform services. The power-on self-tests are performed after the cryptographic systems are initialized but prior to the initialization of the LAN’s interfaces; this prevents the security appliances from passing any data during a power-on self-test failure. In the unlikely event that a power-on self-test fails, an error message is displayed on the console followed by a security appliance reboot. 2.12 Physical Security The FIPS 140-2 level 2 physical security requirements for the modules are met by the use of opacity shields covering the front panels of modules to provide the required opacity and tamper evident seals to provide the required tamper evidence. © Copyright 2016 Cisco Systems, Inc. 24 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. 2.12.1 Opacity Shield Security The following table shows the tamper labels and opacity shields that shall be installed on the modules to operate in a FIPS approved mode of operation. The CO is responsible for using, securing and having control at all times of any unused tamper evident labels. Actions to be taken when any evidence of tampering should be addressed within site security program. ASA Models Number Tamper Evident Labels Number Opacity Shields Tamper Opacity labels Shields 5506-X 4 ASA5506-FIPS-KIT= 1 ASA5506-FIPS-KIT= 5506H-X 4 ASA5506-FIPS-KIT= 1 ASA5506-FIPS-KIT= 5506W-X 4 ASA5506-FIPS-KIT= 1 ASA5506-FIPS-KIT= 5508-X 5 ASA5500X-FIPS-KIT= 1 ASA5508-FIPS-KIT= 5512-X 3 ASA5500X-FIPS-KIT= 0 None 5516-X 5 ASA5500X-FIPS-KIT= 1 ASA5516-FIPS-KIT= 5515-X, 5525-X, 5545-X, 3 CISCO-FIPS-KIT= 0 None 5555-X 5585-X 8 ASA5585-X-FIPS-KIT 1 ASA5585-X-FIPS-KIT Table 8 Tamper Labels and Opacity Shield Quantities Please note that the model 5585-X in table 8 above covers 5508-X SSP-10, 5585-X SSP-20, 5585-X SSP-40 and 5585-X SSP-60. ASA 5506-X, 5506H-X and 5506W-X Opacity Shield To install an opacity shield on the ASA 5506-X, 5506H-X and 5506W-X, follow these steps: Step 1: Remove the three screws from the bottom of the Cisco ASA 5506-X, 5506H-X and 5506W-X Step 2: Slide the ASA 5506-X, 5506H-X and 5506W-X into the FIPS enclosure Step 3: Turn the FIPS enclosure with the chassis securely inside and use the three screws you removed in Step 1 to screw the FIPS enclosure to the Cisco ASA 5506-X, 5506H-X and 5506W- X. Step 4: Apply the tamper evident label over the screw on the bottom. Please see Figure 25 for placement of the TEL. Step 5: Apply another tamper evident label so that one half of the tamper evident label attaches to the enclosure and the other half attaches to the Cisco ASA 5506-X, 5506H-X and 5506W-X chassis. Please see Figure 24 for placement of the TEL. © Copyright 2016 Cisco Systems, Inc. 25 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 16 ASA 5506-X, ASA 5506H-X and ASA 5506W-X Opacity Shield Placement ASA 5508-X and ASA 5516-X Opacity Shield To install an opacity shield on the ASA 5508-X or ASA 5516-X rear, follow these steps: Step 1: Power off the ASA. Step 2: Remove the two screws. Step 3: Place the shield over the vent areas and insert the screws. Figure 17 ASA 5508-X and ASA 5516-X Opacity Shield Placement ASA 5585-X Opacity Shield Step 1: Position the rear shield assembly on the rear of the chassis and align the rear shield panel holes with the holes on the rear of the chassis. Step 2: Secure the shield into place using the screws provided in the kit. Step 3: Connect the power source and power on the chassis. To install an opacity shield on the ASA 5585-X, follow these steps: Step 1: Power off the ASA 5585-X. If you have not installed the cable management brackets, you can do it now. The cable management brackets will make it easier to manage all your cables. Step 2: Position the cable management brackets on the front side of the ASA 5585-X and line up the bracket screws with the screw holes on the ASA 5585-X. © Copyright 2016 Cisco Systems, Inc. 26 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Step 3: Tighten the screws in to the rack. Step 4: Screw the rods to the holes above the cable management brackets. Step 5: Place the FIPS opacity shield over the rods, align the holes on the FIPS opacity shield with the holes on the rods. Step 6: Tighten the screws. Figure 18 ASA 5585-X Opacity Shield Placement 2.12.2 Tamper Evidence Labels (TELs) The tamper evident seals (hereinafter referred to as tamper evident labels (TEL)) shall be installed on the security devices containing the module prior to operating in FIPS mode. TELs shall be applied as depicted in the figures below. Any unused TELs must be securely stored, accounted for, and maintained by the CO in a protected location. Should the CO have to remove, change or replace TELs (tamper-evidence labels) for any reason, the CO must examine the location from which the TEL was removed and ensure that no residual debris is still remaining on the chassis or card. If residual debris remains, the CO must remove the debris using a damp cloth. Any deviation of the TELs placement such as tearing, misconfiguration, removal, change, replace or any other change in the TEL’s from its original configuration as depicted below by unauthorized operators shall mean the module is no longer in FIPS mode of operation. Returning the system back to FIPS mode of operation require the replacement of the TEL as © Copyright 2016 Cisco Systems, Inc. 27 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. depicted below and any additional requirement per the site security policy which are out of scope of this Security Policy To seal the system, apply tamper-evidence labels as depicted in the figures below. Figure 19 ASA 5506-X and ASA 5506W-X Front TEL Placement Figure 20 ASA 5506-X and ASA 5506W-X Right Side TEL Placement Figure 21 ASA 5506-X and ASA 5506W-X Left Side TEL Placement Figure 22 ASA 5506-X and ASA 5506W-X Rear TEL Placement © Copyright 2016 Cisco Systems, Inc. 28 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 23 ASA 5506-X and ASA 5506W-X Top TEL Placement Figure 24 ASA 5506-X and ASA 5506W-X Bottom TEL Placement Figure 25 ASA 5506H-X Front TEL Placement © Copyright 2016 Cisco Systems, Inc. 29 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 26 ASA 5506H-X Right Side TEL Placement Figure 27 ASA 5506H-X Rear TEL Placement Figure 28 ASA 5506H-X Left Side TEL Placement Figure 29 ASA 5506H-X Top TEL Placement © Copyright 2016 Cisco Systems, Inc. 30 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 30 ASA 5506H-X Bottom TEL Placement Figure 31 ASA 5508-X Front TEL Placement Figure 32 ASA 5508-X Left Side TEL Placement Figure 33 ASA 5508-X Rear TEL Placement Figure 34 ASA 5508-X Right Side TEL Placement © Copyright 2016 Cisco Systems, Inc. 31 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 35 ASA 5508-X Top TEL Placement Figure 36 ASA 5508-X Bottom TEL Placement Figure 37 ASA 5512-X Front TEL Placement © Copyright 2016 Cisco Systems, Inc. 32 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 38 ASA 5512-X Right Side TEL Placement Figure 39 ASA 5512-X Rear TEL Placement Figure 40 ASA 5512-X Left Side TEL Placement Figure 41 ASA 5512-X Top TEL Placement © Copyright 2016 Cisco Systems, Inc. 33 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 42 ASA 5512-X Bottom TEL Placement Figure 43 ASA 5515-X Front TEL Placement Figure 44 ASA 5515-X Right Side TEL Placement Figure 45 ASA 5515-X Rear TEL Placement © Copyright 2016 Cisco Systems, Inc. 34 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 46 ASA 5515-X Left Side TEL Placement Figure 47 ASA 5515-X Top TEL Placement Figure 48 ASA 5515-X Bottom TEL Placement © Copyright 2016 Cisco Systems, Inc. 35 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 49 ASA 5516-X Front TEL Placement Figure 50 ASA 5516-X Rear TEL Placement Figure 51 ASA 5516-X Right Side TEL Placement Figure 52 ASA 5516-X Left Side TEL Placement © Copyright 2016 Cisco Systems, Inc. 36 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 53 ASA 5516-X Top TEL Placement Figure 54 ASA 5516-X Bottom TEL Placement © Copyright 2016 Cisco Systems, Inc. 37 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 55 ASA 5525-X Front TEL Placement Figure 56 ASA 5525-X Right Side TEL Placement Figure 57 ASA 5525-X Rear TEL Placement Figure 58 ASA 5525-X Left Side TEL Placement © Copyright 2016 Cisco Systems, Inc. 38 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 59 ASA 5525-X Top TEL Placement Figure 60 ASA 5525-X Bottom TEL Placement Figure 61 ASA 5545-X Front TEL Placement © Copyright 2016 Cisco Systems, Inc. 39 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 62 ASA 5545-X Right Side TEL Placement Figure 63 ASA 5545-X Rear TEL Placement Figure 64 ASA 5545-X Left Side TEL Placement Figure 65 ASA 5545-X Top TEL Placement © Copyright 2016 Cisco Systems, Inc. 40 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 66 ASA 5545-X Bottom TEL Placement Figure 67 ASA 5555-X Front TEL Placement Figure 68 ASA 5555-X Right Side TEL Placement Figure 69 ASA 5555-X Rear TEL Placement © Copyright 2016 Cisco Systems, Inc. 41 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 70 ASA 5555-X Left Side TEL Placement Figure 71 ASA 5555-X Top TEL Placement Figure 72 ASA 5555-X Bottom TEL Placement © Copyright 2016 Cisco Systems, Inc. 42 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. : Figure 73 ASA 5585-X Opacity Shield and Front TEL Placement Figure 74 ASA 5585-X Rear TEL Placement Figure 75 ASA 5585-X Bottom TEL Placement © Copyright 2016 Cisco Systems, Inc. 43 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Figure 76 ASA 5585-X Top TEL Placement Figure 77 ASA 5585-X Left Side TEL Placement Figure 78 ASA 5585-X Right Side TEL Placement Appling Tamper Evidence Labels Step 1: Turn off and unplug the system before cleaning the chassis and applying labels. Step 2: Clean the chassis of any grease, dirt, or oil before applying the tamper evident labels. Alcohol-based cleaning pads are recommended for this purpose. Step 3: Apply a label to cover the security appliance as shown in figures above. © Copyright 2016 Cisco Systems, Inc. 44 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. The tamper evident seals are produced from a special thin gauge vinyl with self-adhesive backing. Any attempt to open the device will damage the tamper evident seals or the material of the security appliance cover. Because the tamper evident seals have non-repeated serial numbers, they may be inspected for damage and compared against the applied serial numbers to verify that the security appliance has not been tampered with. Tamper evident seals can also be inspected for signs of tampering, which include the following: curled corners, rips, and slices. The word “OPEN” may appear if the label was peeled back. 3 Secure Operation The module meets all the Level 2 requirements for FIPS 140-2. The module is shipped only to authorized operators by the vendor, and the modules are shipped in Cisco boxes with Cisco adhesive, so if tampered with the recipient will notice. Follow the setting instructions provided below to place the module in FIPS-approved mode. Operating this router without maintaining the following settings will remove the module from the FIPS approved mode of operation. 3.1 Crypto Officer Guidance - System Initialization The Cisco ASA 5500-X series security appliances were validated with adaptive security appliance firmware version 9.4 (File name: asa941-8-lfbff-k8.SPA and asa941-8-smp-k8.bin). The ASA 5506-X, 5508-X, and 5516-X run the asa941-8-lfbff-k8.SPA firmware image. The ASA 5512-X, 5515-X, 5525-X, 5545-X, 5555-X, and 5585-X run the asa941-8-smp-k8.bin. These are the only allowable images for FIPS-approved mode of operation. The Crypto Officer must configure and enforce the following initialization steps: Step 1: Disable the console output of system crash information, using the following command: (config)#crashinfo console disable Step 2: Install Triple-DES/AES licenses to require the security appliances to use Triple- DES and AES (for data traffic and SSH). Step 3: Enable “FIPS Mode” to allow the security appliances to internally enforce FIPS- compliant behavior, such as run power-on self-tests and bypass test, using the following command: (config)# fips enable Step 4: Disable password recovery. (config)#no service password-recovery Step 5: Set the configuration register to bypass ROMMON prompt at boot. (config)# config-register 0x10011 © Copyright 2016 Cisco Systems, Inc. 45 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Step 6: If using a Radius/TACACS+ server for authentication, perform the following steps.(see Operator manual for specific TACACS+ commands) Otherwise, skip to step 7 (config)# aaa-server radius-server protocol radius (config)# aaa-server radius-server host Configure an IPsec tunnel to secure traffic between the ASA and the Radius server. The pre-shared key must be at least 8 characters long. Step 7: Enable AAA authentication for the console. (config)#aaa authentication serial console LOCAL (config)#username password Step 8: Enable AAA authentication for SSH. (config)#aaa authentication ssh console LOCAL Step 9: Enable AAA authentication for Enable mode. (config)#aaa authentication enable console LOCAL Step 10: Specify Privilege Level 15 for Crypto Officer and Privilege Level 1 for User and set up username/password for each role. (config)#username password privilege 15 (config)#username password privilege 1 Step 11: Ensure passwords are at least 8 characters long. Step 12: All default passwords, such as enable and telnet, must be replaced with new passwords. Step 13: Apply tamper evident labels as described in the “Physical Security” section on page 17. Step 14: Reboot the security appliances. 3.2 Crypto Officer Guidance - System Configuration To operate in FIPS mode, the Crypto Officer must perform the following steps: Step 1: Assign users a Privilege Level of 1. Step 2: Define RADIUS and TACACS+ shared secret keys that are at least 8 characters long and secure traffic between the security appliances and the RADIUS/TACACS+ server via IPSec tunnel. Note: Perform this step only if RADIUS/TACAS+ is configured, otherwise proceed to step 3. © Copyright 2016 Cisco Systems, Inc. 46 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. Step 3: Configure the TLS protocol when using HTTPS to protect administrative functions. Due to known issues relating to the use of TLS with certain versions of the Java plugin, we require that you upgrade to JRE 1.5.0_05 or later. The following configuration settings are known to work when launching ASDM in a TLS-only environment with JRE 1.5.0_05: a. Configure the device to allow only TLSv1 packets using the following command: (config)# ssl server-version tlsv1-only (config)# ssl client-version tlsv1-only b. Uncheck SSL Version 2.0 in both the web browser and JRE security settings. c. Check TLS V1.0 in both the web browser and JRE security settings. Step 4: Configure the security appliances to use SSHv2. Note that all operators must still authenticate after remote access is granted. (config)# ssh version 2 Step 5: Configure the security appliances such that any remote connections via Telnet are secured through IPSec. Step 6: Configure the security appliances such that only FIPS-approved algorithms are used for IPSec tunnels. Step 7: Configure the security appliances such that error messages can only be viewed by Crypto Officer. Step 8: Configure SNMP to always use a secure IPSec tunnel. Step 9: Disable the TFTP server. Step 10: Disable HTTP for performing system management in FIPS mode of operation. HTTPS with TLS should always be used for Web-based management. Step 11: Ensure that installed digital certificates are signed using FIPS approved algorithms. 3.3 Identifying Router Operation in an Approved Mode The following activities are required to verify that that the module is operating in an Approved mode of operation. 1. Verify that the tamper evidence labels and FIPS opacity shields have been properly placed on the module based on the instructions specified in the “Physical Security” and “Secure Operation” sections of this document. 2. Verify that the length of User and Crypto Officer passwords and all shared secrets are at least eight (8) characters long, include at least one letter, and include at least one number character, as specified in the “Secure Operation” section of this document. © Copyright 2016 Cisco Systems, Inc. 47 This document may be freely reproduced and distributed whole and intact including this Copyright Notice. 3. Issue the following commands: 'show crypto IPSec sa' and 'show crypto isakmp policy' to verify that only FIPS approved algorithms are used. © Copyright 2016 Cisco Systems, Inc. 48 This document may be freely reproduced and distributed whole and intact including this Copyright Notice.