McAfee, Inc. McAfee Firewall Enterprise 1100F, 2150F, and 4150F Hardware Part Numbers: NSA-1100-FWEX-F, NSA-2150-FWEX-F, and NSA-4150-FWEX-F Firmware Version: 8.3.2 with patch number 8.3.2E14 FIPS 140-2 Non-Proprietary Security Policy FIPS Security Level: 2 Document Version: 0.4 Prepared for: Prepared by: McAfee, Inc. Corsec Security, Inc. 2821 Mission College Boulevard 13135 Lee Jackson Memorial Highway, Suite 220 Santa Clara, California 95054 Fairfax, Virginia 22033 United States of America United States of America Phone: +1 408 988 3832 Phone: +1 703 267 6050 http://www.mcafee.com http://www.corsec.com Security Policy, Version 0.4 July 16, 2014 Table of Contents 1 INTRODUCTION ................................................................................................................... 4 1.1 PURPOSE ................................................................................................................................................................ 4 1.2 REFERENCES .......................................................................................................................................................... 4 1.3 DOCUMENT ORGANIZATION ............................................................................................................................ 4 2 MFE F-SERIES APPLIANCES ................................................................................................. 5 2.1 OVERVIEW ............................................................................................................................................................. 5 2.2 MODULE SPECIFICATION..................................................................................................................................... 8 2.3 MODULE INTERFACES ........................................................................................................................................10 2.4 ROLES, SERVICES, AND AUTHENTICATION .....................................................................................................16 2.4.1 Authorized Roles .................................................................................................................................................. 16 2.4.2 Services ................................................................................................................................................................... 16 2.4.3 Authentication Mechanisms ............................................................................................................................. 20 2.5 PHYSICAL SECURITY ...........................................................................................................................................22 2.6 OPERATIONAL ENVIRONMENT.........................................................................................................................23 2.7 CRYPTOGRAPHIC KEY MANAGEMENT ............................................................................................................23 2.8 SELF-TESTS ..........................................................................................................................................................28 2.8.1 Power-Up Self-Tests ............................................................................................................................................ 28 2.8.2 Conditional Self-Tests ......................................................................................................................................... 28 2.9 MITIGATION OF OTHER ATTACKS ..................................................................................................................29 3 SECURE OPERATION ......................................................................................................... 30 3.1 CRYPTO-OFFICER GUIDANCE ..........................................................................................................................30 3.1.1 Appliance Setup ................................................................................................................................................... 30 3.1.2 Installation.............................................................................................................................................................. 37 3.1.3 Initialization ........................................................................................................................................................... 39 3.1.4 Management ........................................................................................................................................................ 41 3.1.5 Physical Inspection............................................................................................................................................... 42 3.1.6 Monitoring Status ................................................................................................................................................ 42 3.1.7 Zeroization ............................................................................................................................................................ 42 3.2 USER GUIDANCE ................................................................................................................................................43 3.3 NON-APPROVED MODE OF OPERATION .......................................................................................................43 4 ACRONYMS .......................................................................................................................... 44 Table of Figures FIGURE 1 – TYPICAL DEPLOYMENT SCENARIO .....................................................................................................................5 FIGURE 2 – MCAFEE MFE 1100F ............................................................................................................................................6 FIGURE 3 – MCAFEE MFE 2150F ............................................................................................................................................6 FIGURE 4 – MCAFEE MFE 4150F ............................................................................................................................................7 FIGURE 5 – 1100F FRONT PANEL FEATURES AND INDICATORS...................................................................................... 11 FIGURE 6 – 1100F HARD DRIVE INDICATORS ................................................................................................................... 11 FIGURE 7 – 1100F BACK PANEL FEATURES AND INDICATORS ........................................................................................ 12 FIGURE 8 – 2150F FRONT PANEL FEATURES AND INDICATORS...................................................................................... 13 FIGURE 9 – 2150F HARD DRIVE INDICATORS ................................................................................................................... 13 FIGURE 10 – 2150F BACK PANEL FEATURES AND INDICATORS ...................................................................................... 14 FIGURE 11 – 4150F FRONT PANEL FEATURES AND INDICATORS ................................................................................... 14 FIGURE 12 – 4150F HARD DRIVE INDICATORS ................................................................................................................. 15 FIGURE 13 – 4150F BACK PANEL FEATURES AND INDICATORS ...................................................................................... 15 FIGURE 14 – VELCRO STRIP PLACEMENT ON 1100F TOP COVER (BAFFLE #1) ............................................................ 31 FIGURE 15 – VELCRO STRIP PLACEMENT IN REAR OF 1100F CHASSIS (BAFFLE #2) ..................................................... 32 FIGURE 16 – VELCRO STRIP PLACEMENT ON 2150F TOP COVER (BAFFLE #1) ............................................................ 32 McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 2 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 FIGURE 17 – VELCRO STRIP PLACEMENT IN REAR OF 2150F CHASSIS (BAFFLE #2) ..................................................... 33 FIGURE 18 – VELCRO STRIP PLACEMENT OVER 2150F EXPANSION SLOTS (BAFFLES #3, #4, AND #5)..................... 33 FIGURE 19 – VELCRO STRIP PLACEMENT IN REAR OF 4150F CHASSIS (BAFFLE #1) ..................................................... 33 FIGURE 20 – 1100F TAMPER-EVIDENT SEAL APPLICATION POSITIONS .......................................................................... 35 FIGURE 21 – 1100F TAMPER-EVIDENT SEAL APPLICATION POSITIONS (POWER SUPPLIES) ......................................... 35 FIGURE 22 – 2015F TAMPER-EVIDENT SEAL APPLICATION POSITION (FRONT BEZEL) ............................................... 36 FIGURE 23 – 2150F TAMPER-EVIDENT SEAL APPLICATION POSITION (TOP COVER) .................................................. 36 FIGURE 24 – 2150F TAMPER-EVIDENT SEAL APPLICATION POSITIONS (POWER SUPPLIES) ......................................... 36 FIGURE 25 – 4150F TAMPER-EVIDENT SEAL APPLICATION POSITION (FRONT BEZEL) ............................................... 37 FIGURE 26 – 4150F TAMPER-EVIDENT SEAL APPLICATION POSITIONS (POWER SUPPLIES) ......................................... 37 FIGURE 27 – RULES WINDOW ............................................................................................................................................. 39 FIGURE 28 – ACTIVE RULES POPUP ...................................................................................................................................... 40 FIGURE 29 – CONFIGURING FOR FIPS ................................................................................................................................ 41 List of Tables TABLE 1 – SECURITY LEVEL PER FIPS 140-2 SECTION .........................................................................................................8 TABLE 2 – APPROVED SECURITY FUNCTIONS .......................................................................................................................8 TABLE 3 – APPROVED KEY DERIVATION FUNCTIONS ...................................................................................................... 10 TABLE 4 – FIPS 140-2 LOGICAL INTERFACE MAPPINGS ................................................................................................... 16 TABLE 5 – AUTHORIZED OPERATOR SERVICES .................................................................................................................. 17 TABLE 6 – AUTHENTICATION MECHANISMS EMPLOYED BY THE MODULE .................................................................... 21 TABLE 7 – CRYPTOGRAPHIC KEYS, CRYPTOGRAPHIC KEY COMPONENTS, AND CSPS............................................... 24 TABLE 8 – POWER-UP CRYPTOGRAPHIC ALGORITHM SELF-TESTS ................................................................................ 28 TABLE 9 – CONDITIONAL CRYPTOGRAPHIC ALGORITHM SELF-TESTS .......................................................................... 28 TABLE 10 – ACRONYMS ........................................................................................................................................................ 44 McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 3 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 1 Introduction 1.1 Purpose This is a non-proprietary Cryptographic Module Security Policy for the McAfee Firewall Enterprise 1100F, 2150F, and 4150F from McAfee, Inc. This Security Policy describes how the McAfee Firewall Enterprise 1100F, 2150F, and 4150F appliances (Hardware Part Numbers: NSA-1100-FWEX-F, NSA-2150-FWEX-F, and NSA-4150-FWEX-F; Firmware Version: 8.3.2 with patch number 8.3.2E14) meet the security requirements of Federal Information Processing Standards (FIPS) Publication 140-2, which details the U.S. and Canadian Government requirements for cryptographic modules. More information about the FIPS 140-2 standard and validation program is available on the National Institute of Standards and Technology (NIST) and the Communications Security Establishment Canada (CSEC) Cryptographic Module Validation Program (CMVP) website at http://csrc.nist.gov/groups/STM/cmvp. This document also describes how to run the module in a secure FIPS-Approved mode of operation. This policy was prepared as part of the Level 2 FIPS 140-2 validation of the module. The McAfee Firewall Enterprise 1100F, 2150F, and 4150F are referred to in this document collectively as the MFE F-Series, the cryptographic module, or the module. 1.2 References This document deals only with operations and capabilities of the module in the technical terms of a FIPS 140-2 cryptographic module security policy. More information is available on the module from the following sources:  The McAfee corporate website (http://www.mcafee.com) contains information on the full line of products from McAfee.  The CMVP website (http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm) contains contact information for individuals to answer technical or sales-related questions for the module. 1.3 Document Organization The Security Policy document is one document in a FIPS 140-2 Submission Package. In addition to this document, the Submission Package contains:  Vendor Evidence document  Finite State Model document  Validation Submission Summary document  Other supporting documentation as additional references This Security Policy and the other validation submission documentation were produced by Corsec Security, Inc. under contract to McAfee. With the exception of this Non-Proprietary Security Policy, the FIPS 140-2 Submission Package is proprietary to McAfee and is releasable only under appropriate non-disclosure agreements. For access to these documents, please contact McAfee. McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 4 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 2 MFE F-Series Appliances 2.1 Overview McAfee, Inc. is a global leader in Enterprise Security solutions. The company’s comprehensive portfolio of network security products and solutions provides unmatched protection for the enterprise in the most mission-critical and sensitive environments. The McAfee Firewall Enterprise 1100F, 2150F, and 4150F appliance line is created to meet the specific needs of organizations of all types and enable those organizations to reduce costs and mitigate the evolving risks that threaten today's networks and applications. Consolidating all major perimeter security functions into one system, McAfee's Firewall Enterprise appliances are the strongest self-defending perimeter firewalls in the world. Built with a comprehensive combination of high-speed application proxies, reputation-based threat intelligence and signature-based security services, Firewall Enterprise defends networks and Internet-facing applications from all types of malicious threats, both known and unknown. Figure 1 – Typical Deployment Scenario Firewall Enterprise appliances are market-leading, next-generation firewalls that provide application visibility and control even beyond Unified Threat Management (UTM) for multi-layer security – and the highest network performance. Global visibility of dynamic threats is the centerpiece of Firewall Enterprise and one of the key reasons for its superior ability to detect unknown threats along with the known. Firewall Enterprise appliances deliver the best-of-breed in security systems to block attacks, including:  Viruses  Worms  Trojans  Intrusion attempts  Spam and phishing tactics  Cross-site scripting  Structured Query Language (SQL) injections  Denial of service (DoS)  Attacks hiding in encrypted protocols McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 5 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Firewall Enterprise security features include:  Firewall feature for full application filtering, web application filtering, and Network Address Translation (NAT)  Authentication using local database, Active Directory, LDAP 1, RADIUS2, Windows Domain Authentication, and more  High Availability (HA)  Geo-location filtering  Encrypted application filtering using TLS 3 and IPsec4 protocols  Intrusion Prevention System  Networking and Routing  Management via Simple Network Management Protocol (SNMP) version 3  Per-connection auditing and policy enforcement of endpoints via DTLS 5 protocol The MFE 1100F is a 1U rack-mountable appliance appropriate for mid- to large-sized organizations. The MFE 2150F is a 2U rack-mountable appliance appropriate for mid- to large-sized organizations. The MFE 4150F is an enterprise-class 5U rack-mountable appliance appropriate for mid- to large-sized organizations. The appliances are shown in Figure 2, Figure 3, and Figure 4 below. Figure 2 – McAfee MFE 1100F Figure 3 – McAfee MFE 2150F LDAP – Lightweight Directory Access Protocol 1 RADIUS – Remote Authentication Dial-In User Service 2 TLS – Transport Layer Security 3 IPsec – Internet Protocol Security 4 DTLS – Datagram Transport Layer Security 5 McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 6 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Figure 4 – McAfee MFE 4150F The MFE F-Series can be managed locally or remotely using one of the following management tools:  Administration Console – The Administration Console (or Admin Console) is the graphical software that runs on a Windows computer within a connected network. Admin Console is McAfee’s proprietary GUI management software tool that needs to be installed on a Windows- based workstation. This is the primary management tool. All Admin Console sessions are protected over secure TLS channels.  Command Line Interface (CLI) – A UNIX-based CLI is also available for configuring the firewall and performing troubleshooting functions. It can be used as an alternative to the Admin Console to perform most administration tasks. The CLI is accessed locally over the serial port or by a direct-connected keyboard and mouse, while remote access is via Secure Shell (SSH) session.  MFE SNMP Agent – The MFE F-Series can use the SNMP v3 protocol for remote management, and to provide information about the state and statistics as part of a Network Management System (NMS). Although SNMP v3 can support AES encryption, the protocol employs a non-Approved key generation method. However, the module’s SNMP Agent does not support “set” requests, preventing the modification of any critical security parameters (CSPs) through this interface. Additionally, because the module’s CSPs are not defined in the Firewall’s MIB 6, information about those CSPs is not made available to be transmitted or viewed over this interface. Thus, this interface provides management for non-FIPS-relevant information only, and offers no ability to alter or view CSPs.  MFE Control Center – Control Center is an enterprise-class management appliance that enables scalable centralized management and monitoring of the McAfee Firewall Enterprise solutions, allowing network administrators to centrally define firewall policy, deploy updates, inventory their firewall products, generate reports, and demonstrate regulatory compliance. Control Center is designed to run on an administrator’s workstation, and allows network administrators to fully mange their firewall solutions from the network edge to the core. Management communications between the MFE and Control Center are secured over a TLS session. MIB – Management Information Base 6 McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 7 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 For more information regarding Control Center, please refer to McAfee’s Control Center product documentation. The MFE F-Series is validated at the FIPS 140-2 Section levels shown in Table 1. Table 1 – Security Level Per FIPS 140-2 Section Section Section Title Level 1 Cryptographic Module Specification 2 2 Cryptographic Module Ports and Interfaces 2 3 Roles, Services, and Authentication 2 4 Finite State Model 2 5 Physical Security 2 6 Operational Environment N/A 7 Cryptographic Key Management 2 EMI/EMC7 8 2 9 Self-tests 2 10 Design Assurance 2 11 Mitigation of Other Attacks N/A 2.2 Module Specification The MFE F-Series is a multi-chip standalone hardware module that meets overall Level 2 FIPS 140-2 requirements. The cryptographic boundary of the MFE F-Series is defined by the hard metal chassis, which surrounds all the hardware and firmware components. The module implements three firmware cryptographic libraries to offer secure networking protocols and cryptographic functionalities. The firmware libraries for the module are:  McAfee Firewall Enterprise 32-bit Cryptographic Engine v8.3.2  McAfee Firewall Enterprise 64-bit Cryptographic Engine v8.3.2  Kernel Cryptographic Library for SecureOS® (KCLSOS) v8.2 Security functions offered by the libraries in the module’s Approved mode of operation (and their associated algorithm implementation certificate numbers) are listed in Table 2. Table 2 – Approved Security Functions Certificate # Approved Security Function 32-Bit 64-Bit KCLSOS Symmetric Key Advanced Encryption Standard (AES) 128/192/256-bit in CBC8, #2711 #2713 - ECB9, OFB10, CFB12811, CTR12 modes EMI/EMC – Electromagnetic Interference / Electromagnetic Compatibility 7 8 CBC – Cipher-Block Chaining 9 ECB – Electronic Codebook OFB – Output Feedback 10 CFB128 – 128-bit Cipher Feedback 11 McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 8 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Certificate # Approved Security Function 32-Bit 64-Bit KCLSOS AES 128/192/256-bit in CBC, ECB modes - - #1833 Triple Data Encryption Standard (DES) 2- and 3-key options in #1628 #1630 - CBC, ECB, OFB, CFB64 modes Triple-DES 2- and 3-key options in CBC mode - - #1185 Asymmetric Key RSA ANSI X9.31 key generation: 2048/3072-bit #1407 #1409 - RSA13 PKCS14 #1 signature generation: 2048/3072-bit #1407 #1409 - RSA PKCS #1 signature verification: #1407 #1409 - 1024/1536/2048/3072/4096-bit DSA15 PQG generation: 2048-bit #828 #830 - DSA PQG verification: 1024/2048/3072-bit #828 #830 - DSA key generation: 2048/3072-bit #828 #830 - DSA signature generation: 2048/3072-bit #828 #830 - DSA signature verification: 1024/2048/3072-bit #828 #830 - ECDSA16 key generation (2048-bit); signature #472 #474 - generation/verification (2048/256-bit) Secure Hash Standard SHA17-1, SHA-256, SHA-384, and SHA-512 #2276 #2278 #1612 Message Authentication HMAC18 using SHA-1, SHA-256, SHA-384, and SHA-512 #1690 #1692 #1086 Random Number Generators (RNG) ANSI19 X9.31 Appendix A.2.4 PRNG - - #964 SP 800-90 Counter-based DRBG20 #448 #450 - Key Agreement Scheme (KAS) Diffie-Hellman (DH): 2048 bits21 Non-approved, Non-approved, - but allowed but allowed Key Transport RSA encrypt/decrypt22 2048/3072-bit Non-approved, Non-approved, - but allowed but allowed CTR – Counter 12 13 RSA – Rivest, Shamir, and Adleman PKCS – Public Key Cryptography Standard 14 DSA – Digital Signature Algorithm 15 ECDSA – Elliptic Curve DSA 16 SHA – Secure Hash Algorithm 17 HMAC – (Keyed-) Hash Message Authentication Code 18 ANSI – American National Standards Institute 19 DRBG – Deterministic Random Bit Generator 20 21 Caveat: : Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)) 22 Caveat: RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength; non-compliant less than 112 bits of encryption strength) McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 9 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 NOTE: As of December 31, 2010, the following algorithms listed in the table above are considered “restricted” or “legacy-use”. For details regarding algorithm deprecation, please refer to NIST Special Publication 800-131A.  Two-key Triple DES23  1024-bit DSA PQG verification  1024-bit DSA digital signature verification  1024/1536-bit RSA digital signature verification The module also includes the following non-compliant algorithms:  1024/1536/4096-bit RSA ANSI X9.31 key generation  1024/1536/4096-bit RSA PKCS #1 signature generation  2048/3072-bit RSA PKCS #1 signature generation with SHA-1  1024-bit DSA PQG generation, key generation, and signature generation  2048-bit DSA signature generation with SHA-1  1024-bit Diffie-Hellman  1024/1536/4096-bit RSA encrypt/decrypt The module employs a hardware-based RNG which acts as an entropy-gathering mechanism to provide seeding material for the KCLSOS PRNG. The module also includes two library/executable collections that provide the key derivation function (KDF) implementations for the various protocols. These engines provide KDF functionality to both 32-bit and 64-bit applications resident on the module. They are:  McAfee Firewall Enterprise 32-bit Protocol Engine v8.3.2  McAfee Firewall Enterprise 64-bit Protocol Engine v8.3.2 Table 3 lists the key derivation functions (and their associated CVL24 certificate numbers) implemented by the module. Table 3 – Approved Key Derivation Functions Certificate # Approved KDF 32-Bit Protocol 64-Bit Protocol Engine Engine Transport Layer Security (TLS) v1.0 #168 #171 Secure Shell (SSH) #168 - Internet Key Exchange (IKE) v1 and v2 #168 - Simple Network Management Protocol (SNMP) v3 - #171 2.3 Module Interfaces Interfaces on the module can be categorized as the following FIPS 140-2 logical interfaces:  Data Input Interface  Data Output Interface  Control Input interface  Status Output Interface  Power Interface 23 Caveat: To use the two-key Triple DES algorithm to encrypt data (or wrap keys) in an Approved mode of operation, the module operator shall ensure that the same two-key Triple DES key is not used for encrypting data (or wrapping keys) with more than 2 20 plaintext data (or plaintext keys). CVL – Component Validation List 24 McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 10 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 The physical ports and interfaces for the various models are shown below. Note the following acronyms used in the figures below:  iDRAC6 – Integrated Dell™ Remote Access Controller 6  LCD – Liquid Crystal Display  NIC – Network Interface Card  NMI – Non-Maskable Interrupt  PCI - Peripheral Component Interconnect  PCIe - Peripheral Component Interconnect Express  USB – Universal Serial Bus The physical ports and interfaces for the MFE 1100F are depicted in Figure 5, Figure 6, and Figure 7 below. 1. Power-on indicator, power button 6. LCD panel 2. NMI button 7. System identification button 3. USB connectors (2) 8. Hard drives (8) 4. Video connector 9. Optical drive (optional) 5. LCD menu buttons 10. System identification panel Figure 5 – 1100F Front Panel Features and Indicators 1. Drive-activity indicator (green) 2. Drive-status indicator (green/amber) Figure 6 – 1100F Hard Drive Indicators McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 11 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 1. iDRAC6 Enterprise port (optional) 8. 10/100/1000 Ethernet connectors (4) 2. iDRAC6 Vflash media slot (optional) 9. System status indicator connector 3. Serial connector 10. System status indicator 4. PCIe slot 1 11. System identification button 5. Video connector 12. Power supply 1 6. USB connectors (2) 13. Power supply 2 7. PCIe slot 2 Figure 7 – 1100F Back Panel Features and Indicators McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 12 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 The physical ports and interfaces for the MFE 2150F are depicted in Figure 8, Figure 9, and Figure 10 below. 1. Information tag 7. LCD panel 2. Power-on indicator, power button 8. System identification button 3. NMI button 9. Optical drive (optional) 4. USB connector (2) 10. Hard drives (8) 5. Video connector 11. Flex bay 6. LCD menu buttons Figure 8 – 2150F Front Panel Features and Indicators 1. Drive-activity indicator (green) 2. Drive-status indicator (green/amber) Figure 9 – 2150F Hard Drive Indicators McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 13 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 1. PCIe slot 1 9. System status indicator connector 2. PCIe slot 2 10. 10/100/1000 Ethernet connectors (4) 3. PCIe slot 3 11. USB connectors (2) 4. PCIe slot 4 12. Video connector 5. Power supply 1 13. Serial connector 6. Power supply 2 14. iDRAC6 Enterprise port (optional) 7. System identification button 15. iDRAC6 media slot 8. System status indicator Figure 10 – 2150F Back Panel Features and Indicators The physical ports and interfaces for the MFE 4150F are depicted in Figure 11, Figure 12, and Figure 13 below. 1. Front bezel 6. LCD menu buttons 2. USB connectors (2) 7. LCD panel 3. NMI button 8. Optical drive (optional) 4. Power-on indicator, power button 9. Tape drive (optional) 5. System identification button 10. Front bezel lock Figure 11 – 4150F Front Panel Features and Indicators McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 14 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 1. Drive-activity indicator (green) 2. Drive-status indicator (green/amber) Figure 12 – 4150F Hard Drive Indicators 1. PCIe expansion card slots (5) 7. iDRAC6 Enterprise port (optional) 2. System identification button 8. iDRAC6 VFlash media slot (optional) 3. Ethernet connectors (2) 9. Power supply 1 4. Video connector 10. Power supply 2 5. Serial connector. 11. Security cable slot 6. USB connectors (6) Figure 13 – 4150F Back Panel Features and Indicators All of these physical interfaces are separated into logical interfaces defined by FIPS 140-2, as described in Table 4. McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 15 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Table 4 – FIPS 140-2 Logical Interface Mappings FIPS 140-2 Logical Module Interface Interface Data Input Connectors (network) Data Output Connectors (network) Control Input Buttons (NMI, power, LCD panel, system identification) and connectors (network, USB, serial) Status Output Connectors (video, network, serial), and LED indicators (power-on, drive activity, drive status, system status) Power Connectors (power) A lockable metal bezel is mounted to the front of the 1100F and 2150F chassis (see Figure 2 and Figure 3). The lock is used to prevent unauthorized access to system peripherals, hard drives, and the control panel. Of the available front panel features and indicators (see Figure 5 and Figure 8), only the LCD panel and hard drive LEDs are accessible when the bezel is installed. A lockable metal bezel is also mounted to the front of the 4150F chassis (see Figure 4). The lock prevents unauthorized access to system hard drives and the system cover latch. All other front panel features and indicators (see Figure 11) are still accessible when the bezel is installed. 2.4 Roles, Services, and Authentication The following sections described the authorized roles supported by the module, the services provided for those roles, and the authentication mechanisms employed. 2.4.1 Authorized Roles There are two authorized roles in the module that an operator may assume: a Crypto-Officer (CO) role and a User role.  Crypto-Officer – The Crypto-Officer role performs administrative services on the module, such as initialization, configuration, and monitoring of the module.  User – Users employ the services of the modules for establishing VPN 25 or TLS connections via Ethernet port. 2.4.2 Services The services that require operators to assume an authorized role (Crypto-Officer or User) are listed in Table 5 below. Please note that the keys and Critical Security Parameters (CSPs) listed in Table 5 use the following indicators to show the type of access required:  R (Read): The CSP is read  W (Write): The CSP is established, generated, modified, or zeroized  X (Execute): The CSP is used within an Approved or Allowed security function or authentication mechanism VPN – Virtual Private Network 25 McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 16 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Table 5 – Authorized Operator Services Role Service Description CSP and Type of Access CO User Authenticate to the Allows administrators to Administrator Password - R Admin Console login to the appliance using the Firewall x Enterprise Admin Console Authenticate to the Allows administrators to Administrator Password - R Admin Console login to the appliance using Common with CAC authentication x Access Card (CAC) to access the Firewall Enterprise Admin Console Authenticate to the Allows administrators to Administrator Password - R Admin CLI login to the appliance x using the Firewall Enterprise Admin CLI Authenticate to the Allows administrators to Administrator Password - R Admin CLI using login to the appliance CAC with CAC authentication x to access the Firewall Enterprise Admin CLI Authenticate to the Allows administrators to Administrator Password - R local console login to the appliance via x the local console Change password Allows external users to Firewall Authentication Keys - R use a browser to change Key Agreement Key - R their Firewall Enterprise, TLS Session Authentication Key - R/W x SafeWord TLS Session Key - R/W PremierAccess, or LDAP Administrative Password - R/W login password Manage network Allows administrators to Firewall Authentication Keys - R objects view, create, and Key Agreement Key - R maintain network TLS Session Authentication Key - R/W objects, manage TLS Session Key - R/W x netgroup memberships, and manage access control rules’ time periods Configure identity Allows administrators to Firewall Authentication Keys - R validation method select identity validation Key Agreement Key - R x settings TLS Session Authentication Key - R/W TLS Session Key - R/W Configure cluster Provides services Firewall Authentication Keys - R communication required to communicate Key Agreement Key - R with each other in x TLS Session Authentication Key - R/W Firewall Enterprise multi- TLS Session Key - R/W appliance configurations McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 17 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Role Service Description CSP and Type of Access CO User Configure and Generates and exchanges  Firewall Authentication Keys - R monitor Virtual keys for VPN sessions  Key Agreement Key - R Private Network  TLS Session Authentication Key - R/W (VPN) services  x TLS Session Key - R/W  IKE Preshared key - W  IPsec Session Key - W  IPsec Authentication Key - W Create and Creates and monitors Firewall Authentication Keys - R configure bypass IPsec policy table that Key Agreement Key - R x mode governs alternating TLS Session Authentication Key - R/W bypass mode TLS Session Key - R/W Manage web filter Manages configuration Firewall Authentication Keys - R with the SmartFilter Key Agreement Key - R x TLS Session Authentication Key - R/W TLS Session Key - R/W Manage Control Verifies registration and Firewall Authentication Keys - R Center oversees communication Key Agreement Key - R communication among the Control TLS Session Authentication Key - R/W x Center and managed TLS Session Key - R/W Firewall Enterprise appliances Configure Network Configures NIA Firewall Authentication Keys - R Integrity Agent authentication and Key Agreement Key - R (NIA) settings certificate settings, TLS Session Authentication Key - R/W enable agent discovery, TLS Session Key - R/W x modify connection settings, and create explicit NIA communication rules Configure content Configures settings for Firewall Authentication Keys - R inspection settings content inspection Key Agreement Key - R methods x TLS Session Authentication Key - R/W TLS Session Key - R/W Manage applications Manages applications, Firewall Authentication Keys - R and Application application groups, and Key Agreement Key - R Defense Application Defense x TLS Session Authentication Key - R/W information settings TLS Session Key - R/W Manage access Manages rules enforcing Firewall Authentication Keys - R control rules policy on network flows Key Agreement Key - R x to or through the TLS Session Authentication Key - R/W firewall TLS Session Key - R/W Manage SSL rules Manages SSL rules for Firewall Authentication Keys - R processing SSL Key Agreement Key - R x connections TLS Session Authentication Key - R/W TLS Session Key - R/W McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 18 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Role Service Description CSP and Type of Access CO User Process audit data Allows administrators to Firewall Authentication Keys - R view and export audit Key Agreement Key - R data, transfer audit x DTLS Session Authentication Key - R/W records, and manage log DTLS Session Key - R/W files. Manage attack and Configures how the Firewall Authentication Keys - R system responses firewall should respond Key Agreement Key - R to audit events that TLS Session Authentication Key - R/W x indicate abnormal and TLS Session Key - R/W potentially threatening activities Configure network Customizes audit output Firewall Authentication Keys - R defenses for attacks on specific Key Agreement Key - R x networks stopped by the TLS Session Authentication Key - R/W firewall TLS Session Key - R/W View active hosts Provides a method to Firewall Authentication Keys - R view active hosts Key Agreement Key - R x connected to a Firewall TLS Session Authentication Key - R/W Enterprise appliance TLS Session Key - R/W Configure the Configures the SNMP SNMP v3 Session Key - R SNMP Agent Agent for status x monitoring of non-FIPS- relevant information Configure Configures and manages Firewall Authentication Keys - R networking network characteristics, Key Agreement Key - R security zones, and x TLS Session Authentication Key - R/W Quality of Service TLS Session Key - R/W profiles. Manage email Manages email options Firewall Authentication Keys - R services and ‘sendmail’ features Key Agreement Key - R x TLS Session Authentication Key - R/W TLS Session Key - R/W Perform self-tests Run self-tests on demand None x via reboot Enable FIPS mode Configures the module in Firewall Authentication Keys - R FIPS mode Key Agreement Key - R x TLS Session Authentication Key - R/W TLS Session Key - R/W Show status Allows Crypto-Officer to None check whether FIPS x mode is enabled McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 19 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Role Service Description CSP and Type of Access CO User Zeroize Resets the module to its Common Access Card Authentication keys - R/W factory default state Firewall Authentication public/private keys - R/W Peer public keys - R/W Local CA public/private keys - R/W x IKE Preshared Key - R/W IPsec Session Authentication Key - R/W Administrator Passwords - R/W SSL CA key - R/W SSL Server Certificate key - R/W Establish an Establish a TLS Firewall Authentication Keys - R authenticated TLS connection (requires Key Agreement Key - R connection operator authentication)  TLS Session Authentication Key - R/W x TLS Session Key - R/W SSL CA key - R SSL Server Certificate key - R Establish a VPN Establish a VPN Firewall Authentication Keys - R connection connection over IPsec Key Agreement Key - R tunnel IKE Session Authentication Key - W x IKE Session Key - W IKE Preshared Key - R IPsec Session Key - R/W IPsec Authentication Key - R/W 2.4.3 Authentication Mechanisms The module supports role-based authentication. Module operators must authenticate to the module before being allowed access to services which require the assumption of an authorized role. The module employs the authentication methods described in Table 6 to authenticate Crypto-Officers and Users. McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 20 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Table 6 – Authentication Mechanisms Employed by the Module Role Type of Authentication Authentication Strength Crypto-Officer Password Passwords are required to be at least 8 characters long. The password requirement is enforced by the Security Policy. The maximum password length is 64 characters. Case-sensitive alphanumeric characters and special characters can be used with repetition, which gives a total of 94 characters to choose from. The chance of a random attempt falsely succeeding is 1:948, or 1: 6,095,689,385,410,816. This would require about 60,956,893,854 attempts in one minute to raise the random attempt success rate to more than 1:100,000. The fastest connection supported by the module is 1 Gbps. Hence, at most 60,000,000,000 bits of data (1000 × 106 × 60 seconds, or 6 x 1010) can be transmitted in one minute. At that rate and assuming no overhead, a maximum of 812,759 attempts can be transmitted over the connection in one minute. The maximum number of attempts that this connection can support is less than the amount required per minute to achieve a 1:100,000 chance of a random attempt falsely succeeding. Common Access Card One-time passwords are required to be at least 8 characters long. The password requirement is enforced by the Security Policy. The maximum password length is 128 characters. The password consists of a modified base-64 alphabet, which gives a total of 64 characters to choose from. With the possibility of using repeating characters, the chance of a random attempt falsely succeeding is 1:648, or 1:281,474,976,710,656. This would require about 2,814,749,767 attempts in one minute to raise the random attempt success rate to more than 1:100,000. The fastest connection supported by the module is 1 Gbps. Hence, at most 60,000,000,000 bits of data (1000 × 106 × 60 seconds, or 6 x 1010) can be transmitted in one minute. At that rate, and assuming no overhead, a maximum of only 937,500,000 8-character passwords can be transmitted over the connection in one minute. The maximum number of attempts that this connection can support is less than the amount required per minute to achieve a 1:100,000 chance of a random attempt falsely succeeding. McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 21 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Role Type of Authentication Authentication Strength User Password or Certificate Passwords are required to be at least 8 characters long. The password requirement is enforced by the Security Policy. The maximum password length is 64 characters. Case-sensitive alphanumeric characters and special characters can be used with repetition, which gives a total of 94 characters to choose from. The chance of a random attempt falsely succeeding is 1:948, or 1: 6,095,689,385,410,816. This would require about 60,956,893,854 attempts in one minute to raise the random attempt success rate to more than 1:100,000. The fastest connection supported by the module is 1 Gbps. Hence, at most 60,000,000,000 bits of data (1000 × 106 × 60 seconds, or 6 x 1010) can be transmitted in one minute. At that rate and assuming no overhead, a maximum of 812,759 attempts can be transmitted over the connection in one minute. The maximum number of attempts that this connection can support is less than the amount required per minute to achieve a 1:100,000 chance of a random attempt falsely succeeding. Certificates used as part of TLS, SSH, and IKE26/IPsec are at a minimum 1024 bits. The chance of a random attempt falsely succeeding is 1:280, or 1: 1.20893 x 1024. The fastest network connection supported by the module is 1000 Mbps. Hence, at most 60,000,000,000 bits of data (1000 × 106 × 60 seconds, or 6 × 1010) can be transmitted in one minute. The certificates are sent to the module via security protocols IPsec, TLS, and SSH. These protocols provide strong encryption (AES 128-bit key at minimum, providing 128 bits of security) and require large computational and transmission capability. The probability that a random attempt will succeed or a false acceptance will occur is less than 1:2 128 x 948. 2.5 Physical Security The MFE F-Series is a multi-chip standalone cryptographic module. The module is contained in a hard metal chassis which is defined as the cryptographic boundary of the module. The module’s chassis is opaque within the visible spectrum. The enclosure of the module has been designed to satisfy Level 2 physical security requirements. There are a limited set of ventilation holes provided in the case that, when coupled with the installation of opacity baffles, obscure the internal components of the module. Tamper- evident seals are applied to the case to provide physical evidence of attempts to remove the chassis cover or front bezel. Additionally, the tamper-evident seals must be inspected periodically for signs of tampering. The placement of the opacity baffles and tamper-evident seals can be found in Secure Operation section of this document. The MFE F-Series has been tested and found conformant to the EMI/EMC requirements specified by 47 Code of Federal Regulations, Part 15, Subpart B, Unintentional Radiators, Digital Devices, Class A (i.e., for business use). IKE – Internet Key Exchange 26 McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 22 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 2.6 Operational Environment The requirements in this section are not applicable, as the module does not provide a general-purpose operating system (OS) to module operators. McAfee’s proprietary SecureOS version 8.3 provides a limited operational environment, and only the module’s custom-written image can be run on the OS. The module provides a method to update the firmware in the module with a new version. This method involves downloading a digitally-signed firmware update to the module. 2.7 Cryptographic Key Management The module supports the CSPs listed below in Table 7. McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 23 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Table 7 – Cryptographic Keys, Cryptographic Key Components, and CSPs Generation / Key/CSP Key/CSP Type Output Storage Zeroization Use Input SNMPv3 Session Key AES 128-bit CFB key Internally generated Never exits the Resides in volatile Power cycle or Provides secured channel for using a non-compliant module memory in plaintext session SNMPv3 management method termination Common Access RSA 2048-bit key Imported Never exits the Stored in plaintext on Erasing the Common Access Card Card Authentication DSA 2048-bit key electronically in module the hard disk system image Authentication for generation keys plaintext of one-time password Firewall RSA 2048-bit key Internally generated Output in Stored in plaintext on Erasing the - Peer Authentication of TLS, Authentication public encrypted form the hard disk system image IKE, and SSH sessions key via network port - Audit log signing or in plaintext form via local management port RSA 2048-bit key Imported Never exits the Resides in volatile Erasing the electronically in module memory in plaintext system image plaintext via local management port Firewall RSA 2048-bit key Internally generated Never exits the Stored in plaintext on Erasing the - Peer Authentication of TLS, Authentication module the hard disk system image IKE, and SSH sessions private key - Audit log signing Peer public key RSA 2048-bit key Imported Never exits the Stored in plaintext on Erasing the Peer Authentication for TLS, electronically in module the hard disk system image SSH, and IKE sessions plaintext during handshake protocol Local CA27 public key RSA 2048-bit key Internally generated Public key Stored in plaintext on Erasing the Local signing of firewall certificate the hard disk system image certificates and establish exported trusted point in peer entity electronically in plaintext via local management port CA – Certificate Authority 27 McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 24 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Generation / Key/CSP Key/CSP Type Output Storage Zeroization Use Input Local CA private key RSA 2048-bit key Internally generated Never exits the Stored in plaintext on Erasing the Local signing of firewall module the hard disk system image certificates and establish trusted point in peer entity Key Agreement Key Diffie-Hellman 2048-bit key Internally generated Public exponent Resides in volatile Power cycle or Key exchange/agreement for RSA 2048/3072-bit key electronically in memory in plaintext session DTLS, TLS, IKE/IPsec and SSH plaintext, private termination sessions component not exported TLS Session HMAC SHA-1 key Internally generated Never exits the Resides in volatile Power cycle or Data authentication for TLS Authentication Key module memory in plaintext session sessions termination TLS Session Key Triple-DES, AES-128, AES- Internally generated Never exits the Resides in volatile Power cycle or Data encryption/decryption 256 key module memory in plaintext session for TLS sessions termination DTLS Session HMAC SHA-1 key Internally generated Never exits the Resides in volatile Power cycle or Data authentication for DTLS Authentication Key module memory in plaintext session sessions termination DTLS Session Key Triple-DES, AES-128, AES- Internally generated Never exits the Resides in volatile Power cycle or Data encryption/decryption 256 key module memory in plaintext session for DTLS sessions termination IKE Session HMAC SHA-1 key Internally generated Never exists the Resides in volatile Power cycle or Data authentication for IKE Authentication Key module memory in plaintext session sessions termination IKE Session Key Triple-DES, AES-128, AES- Internally generated Never exits the Resides in volatile Power cycle or Data encryption/decryption 256 key module memory in plaintext session for IKE sessions termination IKE Preshared Key Triple-DES, AES-128, AES- - Imported in Never exits the Stored in plaintext on Erasing the Data encryption/decryption 256 key encrypted form module the hard disk system image for IKE sessions over network port or local management port in plaintext - Manually entered McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 25 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Generation / Key/CSP Key/CSP Type Output Storage Zeroization Use Input IPsec Session HMAC SHA-1 key - Imported in Never exits the - Stored in plaintext Power cycle Data authentication for IPsec Authentication Key encrypted form module on the hard disk sessions over network port - Resides in volatile or local memory management port in plaintext - Internally generated - Manually entered IPsec Session Key Triple-DES, AES-128, AES- Internally generated Never exits the Resides in volatile Power cycle Data encryption/decryption 256 key module memory in plaintext for IPsec sessions IPsec Preshared Triple-DES, AES-128, AES- - Imported in Exported Stored in plaintext on Power cycle Data encryption/decryption Session Key 256 key encrypted form electronically in the hard disk for IPsec sessions over network port plaintext or local management port in plaintext - Manually entered SSH Session HMAC-SHA1 key Internally generated Never exists the Resides in volatile Power cycle or Data authentication for SSH Authentication Key module memory in plaintext session sessions termination SSH Session Key Triple-DES, AES-128, AES- Internally generated Never exists the Resides in volatile Power cycle or Data encryption/decryption 256 key module memory in plaintext session for SSH sessions termination Package Distribution DSA 1024-bit public key Externally generated Never exits the Hard coded in Erasing the Verifies the signature Public Key and hard coded in the module plaintext system image associated with a firewall image update package License Management DSA 1024-bit public key Externally generated Never exits the Hard coded in Erasing the Verifies the signature Public Key and hard coded in the module plaintext system image associated with a firewall image license Administrator PIN Manually or Never exits the Stored on the hard Erasing the Standard Unix authentication Password electronically module disk through one-way system image for administrator login imported hash obscurement McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 26 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Generation / Key/CSP Key/CSP Type Output Storage Zeroization Use Input Common Access 8-character (minimum) Internally generated; Exported Resides in volatile Password Common Access Card Card One-Time ASCII string Manually or electronically in memory inside the expiration, authentication for Password electronically encrypted form CAC Warder process session administrator login imported over TLS termination, or power cycle MFE CE32 ANSI 16 bytes of seed value Internally generated by Never exits the Resides in volatile Power cycle Generates FIPS-Approved X9.31 PRNG Seed KCLSOS PRNG module memory in plaintext random number MFE CE32 ANSI AES-256 key Internally generated by Never exits the Resides in volatile Power cycle Generates FIPS-Approved X9.31 PRNG Key KCLSOS PRNG module memory in plaintext random number MFE CE64 ANSI 16 bytes of seed value Internally generated by Never exits the Resides in volatile Power cycle Generates FIPS-Approved X9.31 PRNG Seed KCLSOS PRNG module memory in plaintext random number MFE CE64 ANSI AES-256 key Internally generated by Never exits the Resides in volatile Power cycle Generates FIPS-Approved X9.31 PRNG Key KCLSOS PRNG module memory in plaintext random number KCLSOS ANSI X9.31 16 bytes of seed value Internally generated Never exits the Resides in volatile Power cycle Generates FIPS-Approved PRNG Seed from entropy sources module memory in plaintext random number KCLSOS ANSI X9.31 AES-256 key Internally generated Never exits the Resides in volatile Power cycle Generates FIPS-Approved PRNG Key from entropy sources module memory in plaintext random number SSL CA Key RSA 2048-bit key Internally generated Exported Stored in plaintext on Erasing the Signing temporary server DSA 2048-bit key electronically in the hard disk system image certificates for TLS re- ciphertext via encryption network port or in plaintext via local management port SSL Server RSA 2048-bit key Internally generated or Exported Stored in plaintext on Erasing the Peer authentication for TLS Certificate Key DSA 2048-bit key imported electronically in the hard disk system image sessions (TLS re-encryption) electronically in ciphertext via plaintext via local network port or management port in plaintext via local management port McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 27 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 2.8 Self-Tests 2.8.1 Power-Up Self-Tests At power-up, the MFE F-Series automatically performs a firmware integrity check using HMAC SHA-256. The module also conducts cryptographic algorithm tests at power-up in the form of Known Answer Tests (KAT) and Pairwise Consistency Tests as list in Table 8 (note that the table indicates the library with which each test is associated). Table 8 – Power-Up Cryptographic Algorithm Self-Tests Algorithm Self-Test 32/64-Bit KCLSOS AES KATs for encrypt and decrypt   Triple DES KATs for encrypt and decrypt   RSA KAT for sign and verify -  RSA KAT for encrypt and decrypt -  DSA pairwise consistency check -  ECDSA pairwise consistency check -  SHA-1 KAT, SHA-256 KAT, SHA-384 KAT, and SHA-512 KAT   HMAC KAT with SHA-1, SHA-256, SHA-384, and SHA-512   DRBG KAT -  PRNG KAT  - If any of the tests listed above fails to perform successfully, the module enters into a critical error state during which all cryptographic operations and output of any data is inhibited. An error message is logged for the CO to review and requires action on the Crypto-Officer’s part to clear the error state. 2.8.2 Conditional Self-Tests The McAfee Firewall Enterprise 1100F, 2150F, and 4150F conducts conditional cryptographic algorithm self-tests as indicated in Table 9 (again, note that the table indicates the library with which each test is associated). Table 9 – Conditional Cryptographic Algorithm Self-Tests Algorithm Self-Test 32/64-Bit KCLSOS Continuous RNG Test (CRNGT) for PRNG  - Continuous RNG Test (CRNGT) for DRBG  - RSA pairwise consistency test for key pair generation  - DSA pairwise consistency test for key pair generation -  ECDSA pairwise consistency test for key pair generation -  McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 28 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 The module also performs the following conditional self-tests during module operation:  Manual key entry test  Bypass test using SHA-1  Firmware Load Test using DSA signature verification Failure of the Bypass test or the PRNG CRNGT leads the module to a critical error state. Failure of any other conditional test listed above leads the module to a soft error state and logs an error message. Upon reaching the critical error or soft error state, all cryptographic operations and data output is inhibited. 2.9 Mitigation of Other Attacks This section is not applicable. The module does not claim to mitigate any attacks beyond the FIPS 140-2 Level 2 requirements for this validation. McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 29 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 3 Secure Operation The MFE F-Series meets Level 2 requirements for FIPS 140-2. The sections below describe how to place and keep the module in its Approved mode of operation. The use of any interfaces and services not documented herein are prohibited and considered in violation of this Security Policy, and shall result in the non-compliant operation of the module. 3.1 Crypto-Officer Guidance The Crypto-Officer will receive the module from the vendor via trusted delivery services (UPS, FedEx, etc.). The Crypto-Officer shall ensure that the shipment contains the following:  MFE F-Series appliance  Media and Documents  Activation Certificate  Setup Guide  Port Identification Guide  Management Tools CD28  Firewall Enterprise Installation Media USB drive (for appliances without a CD-ROM29 drive)  Power cord  Rack mount kit For appliance setup, the Crypto-Officer receives a FIPS Kit separately, also via trusted delivery service. The FIPS Kit (part number FRU-686-0089-00) includes the FIPS Kit instructions, a new warranty seal, and tamper-evident seals. The Crypto-Officer is responsible for the proper initial setup of the Admin Console Management Tool software and the cryptographic module. Setup of the Admin Console software is done by installing the software on an appropriate Windows® workstation (refer to the McAfee Firewall Enterprise version 8.3.2 Product Guide for details regarding installation of management tools) on the same network as the module. Once the Admin Console is installed, a link to the documents page is added to the “Start” menu of the computer. To view the Firewall Enterprise documents on the McAfee web site, select Start > Programs > McAfee > Firewall Enterprise > Online Manuals Additional product manuals, configuration-specific application notes, and the KnowledgeBase are available at http://mysupport.mcafee.com. 3.1.1 Appliance Setup Before the module can be placed into its Approved mode of operation, the Crypto-Officer shall install all required physical security mechanisms. 3.1.1.1 Installing Opacity Baffles The CO must install opacity baffles as described in the instructions provided below. Installation of the opacity baffles requires access to inside of the module; therefore, this step must be completed before applying the tamper-evident seals. Before beginning to install the opacity baffles, it is important to protect against electrostatic discharge (ESD). Because of the need to access the inside of the module, the CO must prevent electrostatic damage to CD – Compact Disc 28 CD-ROM – Compact Disc – Read-Only Memory 29 McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 30 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 inner components as well as personal injury. Follow these precautionary procedures to prevent against ESD:  Do not remove components from their antistatic packing material until you are ready to install them in the appliance. Just before unwrapping the antistatic package, discharge static electricity from your body by touching the power supply or any unpainted metal surface on the appliance chassis  Handle all electrostatic sensitive components in a static-safe area. If possible, use antistatic floor pads and workbench pads  Discharge static electricity from your body before you touch any electronic components 3.1.1.1.1 Prepare Module for Baffle Installation Prior to installing the opacity baffles, complete the following steps: 1. Turn off the appliance and disconnect all cords and cables. a. Use the Admin Console to “Halt System” and turn off the appliance. b. Disconnect the appliance and all attached devices from their electrical outlets. c. Press the power button to ground the system. d. Unplug all network cables from the appliance. 2. Remove the front bezel (if applicable) and top cover of the appliance. Note: this will break the McAfee warranty seal. This seal will be replaced after installing the opacity baffles. a. Rotate the latch release lock counter clockwise to unlock the top cover. b. Lift up on the latch and slide the cover back. c. Grasp the cover on both sides and lift away from the system. 3.1.1.1.2 1100F Opacity Baffle Installation Install two (2) opacity baffles over the ventilation holes as described in the instructions provided below: 1. Turn the cover upside down. 2. Apply the adhesive Velcro strips around the inside edges of the vent (Figure 14). Note: do not apply an adhesive Velcro strip to the outside edge of the cover. 3. Apply the rectangular opacity baffle to the Velcro strips. 4. Inside the chassis, remove each expansion card (remember to follow ESD guidance above). a. Open the expansion card latch. b. Grasp the card by its edges and carefully remove it from the expansion slot. 5. Install one opacity baffle to the rear of the appliance. a. Apply the adhesive Velcro strips to the inside of the rear of the chassis as highlighted in Figure 15. b. Apply the form-fitted opacity baffle to the Velcro strips. Figure 14 – Velcro Strip Placement on 1100F Top Cover (Baffle #1) McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 31 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Figure 15 – Velcro Strip Placement in Rear of 1100F Chassis (Baffle #2) 3.1.1.1.3 2150F Opacity Baffle Installation Install five (5) opacity baffles over the ventilation holes as described in the instructions provided below: 1. Turn the cover upside down. 2. Apply the adhesive Velcro strips around the inside edges of the vent (Figure 16). Note: do not apply an adhesive Velcro strip to the outside edge of the cover. 3. Apply the rectangular opacity baffle to the Velcro strips. 4. Inside the chassis, remove each expansion card (remember to follow ESD guidance above). a. Open the expansion card latch. b. Grasp the card by its edges and carefully remove it from the expansion slot. 5. Install one opacity baffle to the rear of the appliance. a. Apply the adhesive Velcro strips to the inside of the rear of the chassis as highlighted in Figure 17. b. Apply the form-fitted opacity baffle to the Velcro strips. 6. Install one opacity baffle on each of three expansion slot covers. a. Apply the adhesive Velcro strips to each expansion slot cover as highlighted in Figure 18 b. Apply form-fitted opacity baffles to the Velcro strips. Figure 16 – Velcro Strip Placement on 2150F Top Cover (Baffle #1) McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 32 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Figure 17 – Velcro Strip Placement in Rear of 2150F Chassis (Baffle #2) Figure 18 – Velcro Strip Placement over 2150F Expansion Slots (Baffles #3, #4, and #5) 3.1.1.1.4 4150F Opacity Baffle Installation Install one (1) opacity baffle over the ventilation holes as described in the instructions provided below: 1. Apply the adhesive Velcro strips to the inside of the rear of the chassis as highlighted in red in Figure 19. 2. Apply the opacity baffle to the Velcro strips. Figure 19 – Velcro Strip Placement in Rear of 4150F Chassis (Baffle #1) 3.1.1.1.5 Finish Baffle Installation McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 33 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 To complete the installation of the opacity baffles and prepare the module for the application of the tamper- evident seals, follow these steps: 1. Re-install the expansion cards (as applicable). 2. Re-attach the appliance cover. 3. Apply the replacement McAfee warranty seal over the previously broken seal. 4. Connect all cords and cables. 5. Turn on the appliance. 6. Attach the front bezel to the appliance and lock it (turning the release clock clockwise). 3.1.1.2 Applying Tamper-Evident Seals The CO must place tamper-evident seals on the module as described in the information provided below. After the seals are placed as instructed below, the module can be powered up and the Crypto-Officer may proceed with initial configuration. 3.1.1.2.1 Prepare Module for Tamper-Evident Seal Application To apply the seals, the appliance surfaces and front bezel must first be cleaned with isopropyl alcohol in the area where the tamper-evident seals will be placed. Prior to affixing the seals, the front bezel must be attached. 3.1.1.2.2 1100F Tamper-Evident Seal Application The module has the following removable components that must be secured:  a front bezel, which covers the removable hard drives  a top panel, which can expose internal components when removed  dual power supplies on the rear panel The CO must place four (4) tamper-evident seals on the appliance as indicated in red in the figures below. Follow these instructions to securely place the seals to the bezel and top panel: 1. To secure the front bezel, place a tamper-evident seal on the front bezel such that the seal overlaps the front bezel and metal cover at the top of the chassis (see Figure 20). 2. To secure the top panel, place a tamper-evident seal on the top cover such that the seal is affixed to both the top cover and side of the chassis (see Figure 20). 3. To secure the power supplies, place tamper-evident seals on the power supplies such that the seals are affixed to where the power supplies and the chassis meet (see Figure 21). McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 34 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 #1 #2 Figure 20 – 1100F Tamper-Evident Seal Application Positions #3 #4 Figure 21 – 1100F Tamper-Evident Seal Application Positions (Power Supplies) 3.1.1.2.3 2150F Tamper-Evident Seal Application The module has the following removable components that must be secured:  a front bezel, which covers the removable hard drives  a top panel, which can expose internal components when removed  dual power supplies on the rear panel The CO must place four (4) tamper-evident seals on the appliance as indicated in red in the figures below. Instructions to place the seals to secure the bezel and top panel are as follows: 1. To secure the front bezel, place a tamper-evident seal on the front bezel such that the seal overlaps the front bezel and metal cover at the top of the chassis (see Figure 22). McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 35 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 2. To secure the top panel, place a tamper-evident seal on the top cover such that the seal is affixed to both the top cover and side of the chassis (see Figure 23). 3. To secure the power supplies, place tamper-evident seals on the power supplies such that the seals are affixed to where the power supplies and the chassis meet (see Figure 24). #1 #1 Figure 22 – 2015F Tamper-Evident Seal Application Position (Front Bezel) #2 Figure 23 – 2150F Tamper-Evident Seal Application Position (Top Cover) #3 #4 Figure 24 – 2150F Tamper-Evident Seal Application Positions (Power Supplies) McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 36 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 3.1.1.2.4 4150F Tamper-Evident Seal Application The module has the following removable components that must be secured:  a front bezel, which covers the removable hard drives  a top panel, which can expose internal components when removed  dual power supplies on the rear panel The CO must place three (3) tamper-evident seals on the appliance as shown in red in the figures below. Instructions to place the seals to secure the bezel and top panel are as follows: 1. To secure the front bezel, place a tamper-evident seal on the front bezel such that the seal overlaps the front bezel and metal cover at the top of the chassis (see Figure 25). 2. To secure the power supplies, place tamper-evident seals on the power supplies such that the seals are affixed to where the power supplies and the chassis meet (see Figure 26). #1 Figure 25 – 4150F Tamper-Evident Seal Application Position (Front Bezel) #3 #2 Figure 26 – 4150F Tamper-Evident Seal Application Positions (Power Supplies) 3.1.2 Installation The cryptographic module requires that proper firmware version (including baseline version and patch code) be installed on the appliance. As part of installation, the Crypto-Officer must perform the following activities: McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 37 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014  Modify the BIOS30  Install the module firmware 3.1.2.1 Modifying the BIOS Enter the module’s System Setup program to enforce the following module usage policies:  Booting the module from any device other than the FIPS-enabled hard drive is prohibited.  Only authenticated operators are allowed to enter the System Setup program. Additionally, since the module’s power button is not accessible, the AC Power Recovery setting must be modified. Follow the instructions below to update the BIOS settings (requires the connection of a monitor and keyboard): 1. From the command line, restart the firewall. 2. When the F2 = System Setup menu line appears in the upper right corner of the screen, press the key. The BIOS window appears. 3. To disable other bootable devices: a. Select Boot Settings and then press . b. Select Boot Sequence and then press . c. Verify that the hard drive is enabled. If necessary, use the space bar to enable the hard drive. d. Select all other devices and use the space bar to disable them. e. Press twice to return to the main BIOS menu. Note: PXE31 booting on Ethernet devices is not allowed. If PXE booting is enabled on an onboard NIC32, select Integrated Devices, select the appropriate NIC, and use the right arrow to select Enabled (do not select Enabled with PXE). 4. To create a password for accessing the System Setup program and set the power recovery option: a. Select System Security and then press . b. Select Setup Password and then press . c. Enter a password and a confirmation and then press . d. Select AC Power Recovery and then press . e. Use the space bar to set AC Power Recovery to “On”. f. Press to return to the main BIOS menu. 5. Press , select Save Changes and Exit, and then press . The firewall will then complete its startup process. 3.1.2.2 Installing the Module Firmware The Crypto-Officer must have a McAfee-provided grant number in order to download the required image. Grant numbers are sent to McAfee customers via email after the purchase of a McAfee product. To download Firewall Enterprise version 8.3.2, the Crypto-Officer must: 1. In a web browser, navigate to www.mcafee.com/us/downloads. 2. Enter the grant number, and then navigate to the appropriate product and version. 3. Click View Available Downloads, and then click the link for the latest version. 4. Click I Agree to accept the license agreement. 5. Download the installation USB image (.zip). 6. Write the image to a USB drive. To install the firmware image onto the appliance, the Crypto-Officer must: 1. Insert the USB drive and start/restart the firewall. 2. Enter the boot menu, and then select the installation USB drive. The firewall boots from the installation media. 3. At the McAfee Inc. menu, accept the default, which is the Operational System. BIOS – Basic Input/Output System 30 PXE – Preboot Execution Environment 31 NIC – Network Interface Card 32 McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 38 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 4. At the Welcome to McAfee Firewall Enterprise menu, select the appropriate Firewall Enterprise boot option. 5. When the installation complete message appears, remove the installation media from the firewall. Press “R” to restart the firewall, and then press “Enter”. The firewall restarts and displays 6. standard restart information. Version 8.3.2 is now installed on the appliance. Then, to apply the 8.3.2E14 patch, the Crypto-Officer must: 1. Log into the Admin Console. 2. Click Maintenance. 3. Click Software Management. 4. Click the Manage Packages tab. 5. Select the appropriate patch from the available packages table, and then click Install. Select “Install now”, and then click OK. 6. 3.1.3 Initialization The Crypto-Officer is responsible for initialization and security-relevant configuration and management activities for the module. Initialization and configuration instructions for the module can also be found in the McAfee Firewall Enterprise version 8.3.x Quick Start Guide, McAfee Firewall Enterprise version 8.3.2 Product Guide, and this FIPS 140-2 Security Policy. The initial Administration account, including username and password for login authentication to the module, is created during the startup configuration using the Quick Start Wizard. Before enforcing FIPS on the module, the CO must check that no non-Approved service is running on the module. Services and proxies are automatically enabled when rules are created that reference those services/proxies. To view the services that are currently used in enabled rules, select “Policy / Access Control Rules”. The Access Control Rules window appears as shown in Figure 27 below. From here, click the “Active Rules” button in the upper right corner of the window (see Figure 28). If the window lists any non-Approved protocols, then those protocols must be disabled before the module is considered to be in its Approved mode of operation. Figure 27 – Rules Window McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 39 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Figure 28 – Active Rules Popup The process to enable Approved mode is provided below: Under “Policy/Application Defenses/ Defenses/HTTPS”, disable all non-Approved versions of 1. SSL, leaving only TLS 1.0 operational. Under “Maintenance / Certificate Management”, ensure that the certificates only use Approved 2. cryptographic algorithms. Select “Maintenance / FIPS”. The FIPS check box appears in the right pane (shown in Figure 3. 29). Select “Enable FIPS 140-2 processing”. 4. 5. Save the configuration change. Select “Maintenance / System Shutdown” to reboot the firewall to the Operational kernel to 6. activate the change. McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 40 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Figure 29 – Configuring For FIPS Whether the module has been upgraded to a validated firmware version from an earlier firmware, or shipped with a validated firmware version already present, it is required to delete and recreate all required cryptographic keys and CSPs necessary for the module's secure operation. The keys and CSPs existing on the module were generated outside of the module’s Approved mode of operation, and they must now be re- created for use in Approved mode. To ensure the module’s secure operation, the CO shall replace the following keys and CSPs:  Firewall Authentication private key  Local CA private key The module is now operating in the Approved mode of operation. 3.1.4 Management When configured according to the Crypto-Officer guidance in this Security Policy, the module only runs in an Approved mode of operation. While in Approved mode, only Approved and Allowed algorithms may be used; the use of non-Approved algorithms is prohibited. The Crypto-Officer is able to monitor and configure the module via the web interface (GUI over TLS), SSH, serial port, or direct-connected keyboard/monitor. Detailed instructions to monitor and troubleshoot the systems are provided in the McAfee Firewall Enterprise 8.3.2 Product Guide. The CO must monitor that only Approved algorithms as listed in Table 2 are being used for TLS, DTLS, and SSH sessions. If any irregular activity is noticed or the module is consistently reporting errors, then McAfee Customer Service should be contacted. McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 41 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 3.1.5 Physical Inspection For the module to operate in its Approved mode, the tamper-evident seals must be placed by the CO role as specified in Section 3.1.1.2 above. Per FIPS 140-2 Implementation Guidance (IG) 14.4, the CO is also responsible for the following:  securing and having control at all times of any unused seals  direct control and observation of any changes to the module where the tamper-evident seals are removed or installed to ensure that the security of the module is maintained during such changes and that the module is returned to its Approved state The CO is also required to periodically inspect the module for evidence of tampering at intervals specified per end-user policy. The CO must visually inspect the tamper-evident seals for tears, rips, dissolved adhesive, and other signs of malice. If evidence of tampering is found during periodic inspection, the Crypto-Officer must zeroize the keys and re-image the module before bringing it back into operation. To request additional seals, the Crypto-Officer can contact McAfee Customer Service via email at service@mcafee.com. The Crypto-Officer must be sure to include contact information and the shipping address, as well as the appliance serial number. 3.1.6 Monitoring Status The Crypto-Officer must monitor the module’s status regularly for Approved mode of operation and active bypass mode. The “show status” service to determine the current mode of operation involves examining the Admin Console’s FIPS mode checkbox, shown in Figure 29. This can also be done via the following CLI command: cf fips query When correctly configured, the module will display the following message: fips set enabled=yes The “show status” service as it pertains to bypass is shown in the GUI under VPN Definitions and the module column. For the CLI, the Crypto-Officer may enter “cf ipsec policydump” to display the active VPNs, while “cf ipsec q type=bypass” will display get a listing of the existing bypass rules. If any irregular activity is noticed or the module is consistently reporting errors, then McAfee customer support should be contacted. 3.1.7 Zeroization It is the Crypto Officer’s responsibility to zeroize the module’s keys when necessary. In order to zeroize the module of all keys and CSPs, it is necessary to first rebuild the module’s image, essentially wiping out all data from the module. Once a factory reset has been performed, default keys and CSPs must be set up as part of the renewal process. These keys must be recreated as per the instructions found in section Error! Reference source not found.. Failure to recreate these keys will result in a non-compliant module. For more information about resetting the module to a factory default, please consult the documentation that shipped with the module. McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 42 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 3.2 User Guidance When using key establishment protocols (RSA and DH) in the Approved mode, the User is responsible for selecting a key size that provides the appropriate level of key strength for the key being transported. 3.3 Non-Approved Mode of Operation When configured according to the Crypto-Officer guidance in this Security Policy, the module does not support a non-Approved mode of operation. McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 43 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 4 Acronyms This section describes the acronyms used throughout the document. Table 10 – Acronyms Acronym Definition AES Advanced Encryption Standard ANSI American National Standards Institute BIOS Basic Input/Output System CAC Common Access Card CAST Carlisle Adams and Stafford Tavares CBC Cipher-Block Chaining CD Compact Disc CD-ROM Compact Disc – Read-Only Memory CFB Cipher Feedback CLI Command Line Interface CLSOS Cryptographic Library for SecureOS CMVP Cryptographic Module Validation Program CO Crypto-Officer CRNGT Continuous Random Number Generator Test CSEC Communications Security Establishment Canada CSP Critical Security Parameter CTR Counter CVL Component Validation List DES Digital Encryption Standard DH Diffie-Hellman DoS Denial of Service DRBG Deterministic Random Bit Generator DSA Digital Signature Algorithm DTLS Datagram Transport Layer Security ECB Electronic Codebook ECDSA Elliptic Curve Digital Signature Algorithm EMC Electromagnetic Compatibility EMI Electromagnetic Interference ESD Electrostatic Discharge FIPS Federal Information Processing Standard McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 44 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Acronym Definition GUI Graphical User Interface HA High Availability HMAC (Keyed-) Hash Message Authentication Code HTTP Hypertext Transfer Protocol HTTPS Hypertext Transfer Protocol Secure iDRAC6 Integrated Dell™ Remote Access Controller 6 IG Implementation Guidance IKE Internet Key Exchange IP Internet Protocol IPsec Internet Protocol Security KAT Known Answer Test KCLSOS Kernel Cryptographic Library for SecureOS LCD Liquid Crystal Display LDAP Lightweight Directory Access Protocol LED Light Emitting Diode MAC Message Authentication Code MD Message Digest MIB Management Information Base NAT Network Address Translation NIC Network Interface Card NIST National Institute of Standards and Technology NMI Non-Maskable Interrupt NMS Network Management System OFB Output Feedback OS Operating System PCIe Peripheral Component Interconnect Express PKCS Public Key Cryptography Standard PRNG Pseudo Random Number Generator RADIUS Remote Authentication Dial-In User Service RC Rivest Cipher RNG Random Number Generator RSA Rivest Shamir and Adleman SHA Secure Hash Algorithm SNMP Simple Network Management Protocol McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 45 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 0.4 July 16, 2014 Acronym Definition SQL Structured Query Language SSH Secure Shell SSL Secure Sockets Layer TLS Transport Layer Security USB Universal Serial Bus UTM Unified Threat Management VGA Video Graphics Array VPN Virtual Private Network McAfee Firewall Enterprise 1100F, 2150F, and 4150F Page 46 of 47 © 2014 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Prepared by: Corsec Security, Inc. 13135 Lee Jackson Memorial Highway, Suite 220 Fairfax, Virginia 22033 United States of America Phone: +1 703 267 6050 Email: info@corsec.com http://www.corsec.com