McAfee, Inc. McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Hardware Models: WBG-5000-C, WBG-5500-C; Firmware Version: 7.3.2.3.4 FIPS 140-2 Non-Proprietary Security Policy FIPS Security Level: 1 Document Version: 1.5 Prepared for: Prepared by: McAfee, Inc. Headquarters Corsec Security, Inc. 2821 Mission College Blvd. 13921 Park Center Road, Suite 460 Santa Clara, CA 95054 Herndon, VA 20171 United States of America United States of America Phone: +1 (888) 847-8766 Phone: +1 (703) 267-6050 http://www.mcafee.com http://www.corsec.com Security Policy, Version 1.5 December 17, 2015 Table of Contents 1 INTRODUCTION ................................................................................................................... 4 1.1 PURPOSE ................................................................................................................................................................ 4 1.2 REFERENCES .......................................................................................................................................................... 4 1.3 DOCUMENT ORGANIZATION ............................................................................................................................ 4 2 MCAFEE WEB GATEWAY WBG-5000-C AND WBG-5500-C APPLIANCES ................. 5 2.1 OVERVIEW ............................................................................................................................................................. 5 2.2 MODULE SPECIFICATION..................................................................................................................................... 8 2.3 MODULE INTERFACES .......................................................................................................................................... 9 2.4 ROLES AND SERVICES .........................................................................................................................................12 2.4.1 Cryptographic Officer Role ............................................................................................................................... 12 2.4.2 User Role ................................................................................................................................................................ 12 2.4.3 Services ................................................................................................................................................................... 12 2.4.4 Non-Security Relevant Services ....................................................................................................................... 15 2.4.5 Authentication Mechanisms ............................................................................................................................. 15 2.5 PHYSICAL SECURITY ...........................................................................................................................................16 2.6 OPERATIONAL ENVIRONMENT.........................................................................................................................17 2.7 CRYPTOGRAPHIC KEY MANAGEMENT ............................................................................................................17 2.8 EMI/EMC ............................................................................................................................................................23 2.9 SELF-TESTS ..........................................................................................................................................................23 2.9.1 Power-Up Self-Tests ............................................................................................................................................ 23 2.9.2 Conditional Self-Tests ......................................................................................................................................... 23 2.10 MITIGATION OF OTHER ATTACKS ..................................................................................................................24 3 SECURE OPERATION ......................................................................................................... 25 3.1 INITIAL SETUP......................................................................................................................................................25 3.1.1 Setting FIPS Environment .................................................................................................................................. 25 3.2 CRYPTO-OFFICER GUIDANCE ..........................................................................................................................25 3.2.1 Management ........................................................................................................................................................ 26 3.2.2 Zeroization ............................................................................................................................................................ 26 3.3 USER GUIDANCE ................................................................................................................................................26 4 ACRONYMS .......................................................................................................................... 27 Table of Figures FIGURE 1 ­ MCAFEE WEB GATEWAY WBG-5000-C .........................................................................................................5 FIGURE 2 ­ MCAFEE WEB GATEWAY WBG-5500-C .........................................................................................................5 FIGURE 3 ­ TYPICAL DEPLOYMENT SCENARIO .....................................................................................................................7 FIGURE 4 ­ BLOCK DIAGRAM FOR THE WBG-5000-C AND WBG-5500-C ..................................................................8 FIGURE 5 ­ MCAFEE WEB GATEWAY WBG-5000-C (FRONT VIEW) ..............................................................................9 FIGURE 6 ­ MCAFEE WEB GATEWAY WBG-5500-C (FRONT VIEW) ..............................................................................9 FIGURE 7 ­ MCAFEE WEB GATEWAY WBG-5000-C (REAR VIEW) .................................................................................9 FIGURE 8 ­ MCAFEE WEB GATEWAY WBG-5500-C (REAR VIEW) .............................................................................. 10 List of Tables TABLE 1 ­ MCAFEE WEB GATEWAY MODEL SPECIFICATIONS ...........................................................................................7 TABLE 2 ­ SECURITY LEVEL PER FIPS 140-2 SECTION .........................................................................................................7 TABLE 3 ­ MCAFEE WEB GATEWAY PORTS AND INTERFACES ....................................................................................... 10 TABLE 4 ­ FIPS 140-2 LOGICAL INTERFACE MAPPINGS ................................................................................................... 10 TABLE 5 ­ LED DESCRIPTIONS............................................................................................................................................. 11 TABLE 6 ­ MCAFEE WEB GATEWAY SERVICES .................................................................................................................. 12 McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 2 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 TABLE 7 ­ AUTHENTICATION MECHANISMS EMPLOYED BY THE MODULE .................................................................... 16 TABLE 8 ­ ALGORITHM CERTIFICATE NUMBERS FOR CRYPTOGRAPHIC LIBRARIES....................................................... 17 TABLE 9 ­ NETWORK PROTOCOL COMPONENT VALIDATION ...................................................................................... 18 TABLE 10 ­ CRYPTOGRAPHIC KEYS, CRYPTOGRAPHIC KEY COMPONENTS, AND CSPS ............................................ 19 TABLE 11 ­ ACRONYMS ........................................................................................................................................................ 27 McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 3 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 1 Introduction 1.1 Purpose This is a non-proprietary Cryptographic Module Security Policy for the McAfee Web Gateway WBG- 5000-C and WBG-5500-C Appliances from McAfee, Inc. This Security Policy describes how the McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances 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 (CSE) Cryptographic Module Validation Program (CMVP) website at http://csrc.nist.gov/groups/STM/cmvp. This policy was prepared as part of the Level 1 FIPS 140-2 validation of the module. The McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances are referred to in this document collectively as the McAfee Web Gateway, the appliance, 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 Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 4 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 2 McAfee Web Gateway WBG-5000- C and WBG-5500-C 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 Web Gateway is a high-performance, enterprise-strength proxy appliance family that provides the caching, authentication, administration, and authorization controls required by today's most demanding enterprises. With multiple appliance models to choose from, the McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances deliver deployment flexibility and performance, along with scalability to easily support hundreds of thousands of users in a single environment. McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances deliver comprehensive security for all aspects of Web 2.0 traffic. A view of the Model WBG-5000-C and WBG-5500-C is shown in Figure 1 and Figure 2 below. Figure 1 ­ McAfee Web Gateway WBG-5000-C Figure 2 ­ McAfee Web Gateway WBG-5500-C The McAfee Web Gateway ensures comprehensive web security for networks. It protects networks against threats arising from the web, such as viruses and other malware, inappropriate content, data leaks, and related issues. It also ensures regulatory compliance and a productive work environment. The appliance is installed as a gateway that connects a network to the web. Following the implemented web security rules, it filters the requests that users send to the web from within the network. Responses sent back from the web and embedded objects sent with requests or responses are also filtered. Malicious and inappropriate content is blocked, while useful content is allowed to pass through. Web filtering is accomplished via the following appliance processes: McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 5 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 Intercepting web traffic: this is achieved by the gateway functions of the appliance, using different network protocols and services such as HTTP1, HTTPS2, FTP3, Yahoo, ICQ, Windows Live Messenger, and others. As a gateway, the appliance can run in explicit proxy mode or in transparent bridge or router mode. Filtering web objects: special anti-virus and anti-malware functions on the appliance scan and filter web traffic and block objects when they are infected. Other functions filter requested URLs4, using information from the global TrustedSource intelligence system, or do media type and HTML5 filtering. They are supported by functions that do not filter themselves, but do jobs such as counting user requests or indicating the progress made in downloading web objects. Filtering users: this is done by the authentication mechanisms provided by the appliance, using information from internal and external databases and methods such as NTLM 6,7,8, LDAP9, RADIUS10, Kerberos, and others. In addition to filtering normal users, the appliance also provides control over administrator rights and responsibilities. Monitoring the filtering process: the monitoring functions of the appliance allow administrators a continuous overview of the filtering process. The monitoring functions include a dashboard, which provides information on web usage, filtering activities, and system behavior as the dashboard also provides logging and tracing functions and options to forward data to an ePolicy Orchestrator. Event monitoring is provided by an SNMP11 agent. For user-initiated web requests, the McAfee Web Gateway first enforces an organization's internet use policy. For all allowed traffic, it then uses local and global techniques to analyze the nature and intent of all content and active code entering the network via the requested web pages, providing immediate protection against malware and other hidden threats. Additionally, the SSL12 Scanner feature of the McAfee Web Gateway can examine TLS13 traffic to provide in-depth protection against malicious code that might otherwise be disguised through encryption. To secure outbound traffic, the McAfee Web Gateway scans user-generated content on all key web protocols, including HTTP, HTTPS, and FTP. As part of a fully-integrated McAfee data loss prevention solution, the McAfee Web Gateway protects against loss of confidential information and other threats leaking from the organization through blogs, wikis, and online productivity tools such as organizers and calendars. The McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances also provide administrators with the ability to monitor and troubleshoot the appliance. The McAfee Web Gateway combines and integrates numerous protections that would otherwise require multiple stand-alone products. Web filtering, anti-virus, anti-spyware, SSL scanning, and content control filtering capabilities are combined into a single appliance. A simplified management footprint means that a single compliance policy can be shared across protections and protocols. Figure 3 shows a typical deployment scenario for the McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances. 1 HTTP ­ Hypertext Transfer Protocol 2 HTTPS ­ Secure Hypertext Transfer Protocol 3 FTP ­ File Transfer Protocol 4 URL ­ Uniform Resource Locator 5 HTML ­ Hypertext Markup Language 6 NTLM ­ Microsoft Windows NT LAN Manager 7 NT ­ New Technology 8 LAN ­ Local Area Network 9 LDAP ­ Lightweight Directory Access Protocol 10 RADIUS ­ Remote Authentication Dial-up User Service 11 SNMP ­ Simple Network Management Protocol 12 SSL ­ Secure Sockets Layer 13 TLS ­ Transport Layer Security McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 6 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 Figure 3 ­ Typical Deployment Scenario Table 1 below provides general specification for the McAfee Web Gateway WBG-5000-C and WBG-5500- C Appliances. Table 1 ­ McAfee Web Gateway Model Specifications WBG-5000-C WBG-5500-C Form Factor 1U rack-mount 1U rack-mount Processor Intel Xeon E5-2430 Intel Xeon E5-2680V2 (1x 6-core) (2x 10-core) Memory 16 GB 16 GB Interfaces 4 x 10/100/1000 4 x 10/100/1000 RAID14 RAID 1/10 RAID 1/10 Hard Disk Available: 8 x SAS Available: 8 x SAS Installed : 2 x 600 GB SAS Installed : 6 x 300 GB SAS Power Supply Redundant Redundant The McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances are validated at the FIPS 140-2 Section levels shown in Table 2 below. Table 2 ­ Security Level Per FIPS 140-2 Section Section Section Title Level 1 Cryptographic Module Specification 1 2 Cryptographic Module Ports and Interfaces 1 3 Roles, Services, and Authentication 2 4 Finite State Model 1 5 Physical Security 1 6 Operational Environment 1 7 Cryptographic Key Management 1 15 8 EMI/EMC 1 14 RAID ­ Redundant Array of Inexpensive Disks McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 7 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 Section Section Title Level 9 Self-tests 1 10 Design Assurance 3 11 Mitigation of Other Attacks N/A16 2.2 Module Specification The McAfee Web Gateway is a multi-chip standalone cryptographic hardware module that meets overall Level 1 FIPS 140-2 requirements. The cryptographic boundary of the module is defined by the hard metal chassis, which surrounds all the hardware and firmware components. Figure 4 depicts the block diagram and the cryptographic boundary of the module, which is indicated using the red dotted line. Please note that the anti-virus and URL categorization modules are excluded from the cryptographic boundary. Hardware Network DVD RAM Management Interface HDD Clock SCSI/SATA Generator Controller LEDs/LCD CPU(s) Serial I/O Hub Audio Cache PCI/PCIe Slots USB BIOS Power Graphics PCI/PCIe Interface Controller Slots External Power Supply KEY: Plaintext data BIOS ­ Basic Input/Output System PCIe ­ PCI express Encrypted data CPU ­ Central Processing Unit HDD ­ Hard Disk Drive Control input SATA ­ Serial Advanced Technology Attachment DVD ­ Digital Video Disc Status output SCSI ­ Small Computer System Interface USB ­ Universal Serial Bus Crypto boundary PCI ­ Peripheral Component Interconnect RAM ­ Random Access Memory LED ­ Light Emitting Diode LCD ­ Liquid Crystal Display I/O ­ Input/Output Figure 4 ­ Block Diagram for the WBG-5000-C and WBG-5500-C17 15 EMI/EMC ­ Electromagnetic Interference / Electromagnetic Compatibility 16 N/A ­ Not Applicable McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 8 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 2.3 Module Interfaces The McAfee Web Gateway is a multi-chip standalone cryptographic module that meets overall Level 1 FIPS 140-2 requirements. 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 All ports and interfaces are located at the back side of the hardware module. The front of the chassis is populated with the power/sleep, reset, ID18, and NMI19 buttons, a USB port, and several LEDs20; please note that some of these are covered by the security bezel. The front and rear view of the appliances are shown in the figures below. Figure 5 ­ McAfee Web Gateway WBG-5000-C (Front View) Figure 6 ­ McAfee Web Gateway WBG-5500-C (Front View) Figure 7 ­ McAfee Web Gateway WBG-5000-C (Rear View) 17 It should be noted that either the serial port or the Graphics Controller (VGA) port is used for status output but not both at the same time. 18 ID ­ Identification 19 NMI ­ Non-Maskable Interrupt 20 LED ­ Light-Emitting Diode McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 9 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 Figure 8 ­ McAfee Web Gateway WBG-5500-C (Rear View) Table 3 below describes the ports and interfaces found on the two models of the cryptographic module. Table 3 ­ McAfee Web Gateway Ports and Interfaces Model Physical Ports Web Gateway WBG-5000-C CD-ROM Drive (covered by bezel) Four (4) gigabit Ethernet ports Four (4) USB ports Two (2) USB ports (covered by bezel) One (1) Intel RMM421 NIC22 Port One (1) serial port One (1) Video Graphics Array (VGA) port LEDs ­ System ID, System Status, Power, NIC (x4), Hard Disk One (1) Intel® I/O module Two (2) power connectors Web Gateway WBG-5500-C Four (4) gigabit Ethernet ports Three (3) Universal Serial Bus (USB) ports One (1) Intel RMM4 NIC Port One (1) serial ports One (1) Video Graphics Array (VGA) port LEDs ­ NIC (x4), Power, System Status, System ID, Hard Disk One (1) Intel I/O module Two (2) power connectors Once the module has been mounted by the Crypto-Officer (CO), all physical ports marked with "(covered by bezel)" will not be accessible unless the bezel is removed by the Crypto-Officer. The Crypto-Officer role is defined in Section 2.4.1. The module's ports and interfaces are mapped to logical interfaces in Table 4 below. All of these physical interfaces are separated into logical interfaces defined by FIPS 140-2, as described in Table 4. Table 4 ­ FIPS 140-2 Logical Interface Mappings FIPS 140-2 Interface McAfee Web Gateway WBG-5000-C and WBG-5500- C Appliances Physical Ports Data Input Ethernet ports 21 RMM ­ Remote Management Module 22 NIC ­ Network Interface Card McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 10 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 FIPS 140-2 Interface McAfee Web Gateway WBG-5000-C and WBG-5500- C Appliances Physical Ports Data Output Ethernet ports Control Input Ethernet ports Status Output Ethernet ports, serial port, VGA port, LEDs Power Power connectors Status output will be provided via the serial port or the VGA port, dependant on the option selected during installation of the v7.3.2.3.4 firmware. The USB and RMM4 ports are disabled once the module is configured. Table 5 below provides a description of the LEDs visible on the WBG-5000-C and WBG-5500-C appliances with the bezels attached. Table 5 ­ LED Descriptions LED Color Condition Description On System on Green Power/Sleep Blink23,24 Sleep Off Off System off On NIC link NIC 1-4 Green Blink NIC activity Green On Running/ Normal Operation 25 Blink Degraded System Status (on standby Amber On Critical or non-recoverable condition power) Blink Non-critical condition Off Off POST26/System Stop Green Random blink Provides an indicator for disk activity Disk Activity 27 Off Off No hard disk activity System Blue On Identify active via command or button Identification Off Off No identification 23 Blink rate is ~1Hz at 50% duty cycle 24 The power LED sleep indication is maintained on standby by the chipset. If the system is powered down without going through the BIOS, the LED state that is in effect at the time of power-off is restored when the system is powered on until the BIOS clears it. If the system is not powered down normally, it is possible that the power LED is blinking while the system status LED is off. This is due to a failure or configuration change that prevents the BIOS from running. 25 The amber status takes precedence over the green status. When the amber LED is on or blinking, the green LED is off. 26 POST ­ Power-On Self-Test 27 Off when the system is powered off or in a sleep state McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 11 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 2.4 Roles and Services The module supports role-based authentication. There are two authorized roles in the module that an operator may assume: a Cryptographic Officer (Crypto-Officer, CO) role and a User role. 2.4.1 Cryptographic Officer Role The Crypto-Officer role performs administrative services on the module, such as initialization, configuration, and monitoring of the module. Before accessing the module for any administrative service, the operator must authenticate to the module. The module offers the following management interfaces: MWGUI28 SNMPv3 2.4.2 User Role A User of the module is any one of a set of clustered modules that share configuration information of the master McAfee Web Gateway appliance. Users have to authenticate to the module with a valid certificate before they can access any of the user services. 2.4.3 Services Services provided to authenticated operators are provided in Table 6 below. Please note that the keys and Critical Security Parameters (CSPs) listed indicate the type of access required: Read (R) : The CSP is read Write (W): The CSP is established, generated, modified, or zeroized Execute (X): The CSP is used within an Approved or Allowed security function or authentication mechanism Table 6 ­ McAfee Web Gateway Services OperatorApproved Service Description Algorithms Type of Access CO User Accessed Perform initial Configure the X N/A None configuration primary network interface, IP29 address, host name, and DNS30 server 28 MWGUI ­ McAfee Web Gateway Graphical User Interface 29 IP ­ Internet Protocol 30 DNS ­ Domain Name System McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 12 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 OperatorApproved Service Description Algorithms Type of Access CO User Accessed CO Login Crypto-Officer X AES, Triple- DH31 Establishment Public Key ­ login DES, RSA, RX; SHA, HMAC, DH Establishment Private Key ­ SP 800-90A RX; DRBG RSA32 Establishment Public Key ­ WRX; RSA Establishment Private Key ­ WRX; TLS Session Key ­ RWX; MWGUI Public Key ­ RX; MWGUI Private Key ­ RX; CO Password ­ RX Implement/mod Create/modify web X RSA Root CA33 Private Key ­ RW; ify a web security policy using Root CA Public Key ­ RW; security policy* rules and filter lists RADIUS Shared Secret ­ WX; LDAP Account Password ­ WX; NTLM Account Password ­ WX Import a Import a license X N/A None license* Modify Modify appliance X RSA MWGUI Public Key ­ WX; configuration configuration MWGUI Private Key ­ WX; settings* settings Cluster CA Public Key ­ WX; Cluster Server Key ­ WX; Cluster Client Key ­ WX; WCCP34 Authentication Key ­ WX; SNMP v3 Password ­ WX; NTLM Account Password ­ WX SWPS Key ­ WX; Manage Set up account for X N/A CO Password ­ WX; administrator administrator RADIUS Shared Secret ­ WX; account* NTLM Account Password ­ WX; SNMP v3 Password ­ WX; Backup Store the X RSA CO Password ­ X; appliance appliance's SNMP v3 Password ­ X; configuration* configuration RADIUS Shared Secret ­ X; information LDAP Account Password ­ X; (including rules, MWGUI Public Key ­ X; lists, settings, and MWGUI Private Key ­ X; administrator Root CA Private Key ­ RW; accounts) in a Root CA Public Key ­ RW; backup file WCCP Key ­ R 31 DH ­ Diffie Hellman 32 RSA ­ Rivest, Shamir, and Adleman 33 CA ­ Certificate Authority 34 WCCP ­ Web Cache Communication Protocol McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 13 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 OperatorApproved Service Description Algorithms Type of Access CO User Accessed Restore Restore the X RSA CO Password, SNMP v3 Password, appliance appliance's RADIUS Shared Secret, LDAP configuration* configuration Account Password, MWGUI Public information from a Key, backup file MWGUI Private Key, Root CA Private Key, Root CA Public Keys, WCCP Key ­ WX Monitor system Monitor how the X N/A None functions* appliance executes its filtering functions Monitor status Monitors non X N/A SNMP v3 Password ­ RX on SNMP security relevant status of the module via SNMPv3 Perform self- Run self-tests on X N/A None tests* demand (via MWGUI) Perform self- Run self-tests on X N/A None tests demand (via power cycle) Show status* Allows Crypto- X N/A None Officer to check module status Zeroize Zeroizes the X N/A All Keys and CSPs ­ W module to the factory default state Configure Services required X RSA Cluster CA Public Key ­ W; cluster CA* to communicate Cluster Server Key ­ W; with each other in Cluster Client Key ­ W multi-appliance configurations Management Shutdown or X N/A CO Password ­ X over REST35 * restart the appliance; view log files; flush the cache; create configuration backup Note: The `*' above indicates the `CO Login' service is required. 35 REST ­ Representational State Transfer McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 14 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 OperatorApproved Service Description Algorithms Type of Access CO User Accessed Configuration Clustered instances X AES, Triple- DH Establishment Public Key ­ sharing share the DES, RSA, RWX; configuration SHA, HMAC, DH Establishment Private Key ­ information of the SP 800-90A RWX; McAfee Web DRBG Cluster CA Public Key ­ RX; Gateway master Cluster Server Key ­ RX; Cluster Client Key ­ RX; TLS Session Key ­ WX; CO Password, SNMP v3 Password, RADIUS Shared Secret, LDAP Account Password, MWGUI Public Key, MWGUI Private Key , Root CA Private Key, Root CA Public Key, WCCP ­ WR (depending on originator) 2.4.4 Non-Security Relevant Services In addition to the services listed in Table 6, the modules provide non-security relavent services. The non- security relevant services provided by the modules are provided in the modules' product guide: McAfee Web Gateway 7.3.2: Product Guide; Revision A (2013). The document is publicly available for download at: https://kc.mcafee.com/resources/sites/MCAFEE/content/live/PRODUCT_DOCUMENTATION/24000/PD 24502/en_US/mwg_732_pg_product_a_en-us.pdf. 2.4.5 Authentication Mechanisms Crypto-Officers may authenticate to the module over the MWGUI with a combination of username and password or with a client certificate. Users may authenticate to the module using one of the following configurable methods: NTLM NTLM-Agent LDAP RADIUS SWPS36 Kerberos The modules supports role-based authentication. An operator explicitly assumes either a Crypto-Officer role or a User role based on the authentication credentials. Please refer to the Table 7 for the authentication methods used by operators to authenticate the module and assume an authorized role. 36 SWPS ­ Secure Web Protection Service McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 15 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 Table 7 ­ 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 module firmware. The maximum password length is 1,000 characters. The password must contain the following: At least one lower case letter. At least one upper case letter. At least one numeric or special character. Starting with all 8-character strings: 958 Then remove all passwords with no lowercase (698), all passwords with no uppercase (698), and all passwords with no digits/specials (528). But then you removed some passwords twice. You must add back all passwords with: no lowercase and no uppercase: 438 no lowercase and no digits/specials: 268 no uppercase and no digits/specials: 268 958 -698 -698 -528 +438 +268 +268 = 5,565,253,689,908,6405.565×1015 passwords The chance of a random attempt falsely succeeding is 1: 5.565x1015 Crypto-Officer/ RSA Public Key Certificate The module supports RSA digital certificate User authentication during TLS sessions. Using conservative estimates and equating a 2048-bit RSA key to an 112-bit symmetric key, the probability for a random attempt to succeed is 1:2112. Crypto-Officer One Time Password When enabled, a one-time password is sent to the CO after successfully authenticating with an RSA digital certificate. The CO must type in the received password in order to authenticate to the module. The use of a one-time password acts as a two-factor authentication method, which greatly increases the overall strength of CO's password. 2.5 Physical Security The McAfee Web Gateway 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 1 physical security requirements. McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 16 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 2.6 Operational Environment The operational environment of the the McAfee Web Gateway consists of the module's firmware (v7.3.2.3.4) executing on a non-modifiable version of McAfee's Linux Operating System (MLOS v2.2.3). The OS has a limited operational environment, and only the module's custom-written image can be run on the system. 2.7 Cryptographic Key Management The module's cryptographic functionality is provided by a firmware library (McAfee Linux OpenSSL library) that offers secure networking protocols and cryptographic functionalities. This firmware library is integrated as part of the underlying operating system. Security functions offered by the module map to the certificates listed in Table 8. Table 8 ­ Algorithm Certificate Numbers for Cryptographic Libraries Approved Security Function Certificate Number Symmetric Key Algorithm AES37: 128-, 192-, 256-bit in CBC38 mode 3116 Triple-DES39 : 168-bit in CBC mode 1787 Secure Hashing Algorithm (SHA) SHA-1, SHA-224, SHA-256, SHA-384, and SHA-512 2572 Message Authentication Code (MAC) Function HMAC40 using SHA-1, SHA-224, SHA-256, SHA-384, and SHA-512 1953 Deterministic Random Bit Generator (DRBG) SP800-90A CTR_DRBG 627 Asymmetric Key Algorithm RSA41 Key Pair Generation (FIPS 186-4) with 2048-bit keys 1587 RSA PKCS42 #1 v1.5 Signature Generation (FIPS 186-4) with 2048-bit keys 1587 RSA PKCS #1 v1.5 Signature Verification (FIPS 186-2) with 1024-, 1536-, 2048-, 1587 3072-, 4096-bit keys Digital Signature Algorithm (DSA) Signature Verification: 1024-bit keys 900 Additional information concerning SHA-1 and RSA key signatures and specific guidance on transitions to the use of stronger cryptographic keys and more robust algorithms is contained in NIST Special Publication 800-131A. 37 AES ­ Advanced Encryption Standard 38 CBC ­ Cipher-Block Chaining 39 DES ­ Data Encryption Standard 40 HMAC ­ (Keyed-) Hash Message Authentication Code 41 RSA ­ Rivest Shamir, Adleman 42 PKCS ­ Public Key Cryptography Standards McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 17 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 The cryptographic module implements the TLS and SNMP secure networking protocols. Each protocol implements a Key Derivation Function (KDF) listed in NIST SP 800-135rev1 and has been validated by the CMVP. There certificate numbers are provided in Table 9. The complete protocol implementations have not been reviewed or tested by the CAVP 43 and CMVP. Table 9 ­ Network Protocol Component Validation CVL44 Certificate Algorithm Number TLS 1.0/1.1 and TLS 1.2 KDF45 using SHA 256 and SHA 384 378 SNMP KDF using SHA-1 378 The module implements the following non-compliant key establishment methodologies: Diffie-Hellman: 2048-bit key (key agreement; key establishment methodology provides 112 bits of encryption strength) RSA: 2048-bit keys (key wrapping; key establishment methodology provides 112 bits of encryption strength) The module employs a non-Approved Non-Deterministic Random Number Generator (NDRNG), which is used as an entropy source for seeding the Approved DRBG listed in Table 8. Its use is allowed per FIPS 140-2 Implementation Guidance 7.11. 43 CAVP ­ Cryptographic Algorithm Validation Program 44 CVL ­ Component Validation List 45 KDF ­ Key Derivation Function McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 18 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 The module supports the CSPs listed below in Table 10. Table 10 ­ Cryptographic Keys, Cryptographic Key Components, and CSPs Key/CSP Key/CSP Generation / Input Output Storage Zeroization Use Type Crypto-Officer Password Set via MWGUIor Configuration sharing or Stored as SHA256 hash Overwritten by another Authentication of Password imported backup - encrypted in the configuration on password or when administrators hard disk appliance is re-imaged (Crypto-Officers) SNMP v3 Password Set via MWGUI or Configuration sharing or Stored as USM46 hash Overwritten by another Used with SHA-1 and Password imported backup - encrypted (rfc3414) in the password or when AES for authentication configuration on hard appliance is re-imaged of SNMP requests disk RADIUS Shared Password Set via MWGUI or Configuration sharing or Stored in plain text in Overwritten by another Authenticate RADIUS Secret imported backup - encrypted the configuration on password or when messages hard disk appliance is re-imaged NTLM Account Password Internally generated Never leaves the module Stored on hard disk in Overwritten by another Authenticate at Password by FIPS approved plain text password or when Domain DRBG appliance is re-imaged LDAP Account Password Set via MWGUI or Configuration sharing or Stored on hard disk in Overwritten by another Authenticate at LDAP Password imported backup - encrypted plain text in the password or when configuration appliance is re-imaged Kerberos Password Set via MWGUI or Configuration sharing or Stored in plain text in Overwritten by another Authenticate Kerberos Password imported backup - encrypted the configuration on password or when messages hard disk appliance is re-imaged Cluster CA X509 / RSA >= Preinstalled and later Leaves the module in Stored on hard disk in Overwritten via MWGUI Verification of other Public Key 2048 bits changed via MWGUI plaintext plain text or when appliance is re- cluster member and imaged issuing of a cluster client certificate 46 USM ­ User-based Security Model McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 19 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 Key/CSP Key/CSP Generation / Input Output Storage Zeroization Use Type SWPS Key Pre-shared key Set via MWGUI or Configuration sharing or Stored in plain text in Overwritten via MWGUI End User imported backup ­ encrypted the configuration on or when appliance is re- authentication over hard disk imaged encrypted channel Cluster RSA private Internally generated Private key will not leave Stored on hard disk in Appliance re-image or Client / Server Communication key with 2048 by following FIPS the module plain text reissuing due to Cluster authentication for Private Key bits 186-4 CA change Transport Layer Security cluster communication Cluster X509 / RSA Internally generated Leaves the module in Stored on hard disk in Appliance re-image or Client / Server Communication public key with by following FIPS plaintext plain text reissuing due to Cluster authentication for TLS Public Key 2048 bits 186-4 CA change cluster communication MWGUI Private RSA private Set via MWGUI or Configuration sharing or Stored in plain text in Overwritten via MWGUI Serve TLS connection Key key with 2048 imported backup ­ encrypted the configuration on or when appliance is re- to the MWGUI bits hard disk imaged MWGUI Public X509, RSA Set via MWGUI or Configuration sharing or Stored in plain text in Overwritten via MWGUI Serve TLS connection Key public key with imported backup ­ encrypted; the configuration on or when appliance is re- to the MWGUI 2048 bits Leaves the module in hard disk imaged plaintext Root CA RSA private Set via MWGUI or Configuration sharing or Stored in plain text in Overwritten via MWGUI SSL-Scanner: Issuing Private Key key with 2048 imported backup - encrypted the configuration file on or when appliance is re- server certificates bits hard disk imaged Root CA Public X509, RSA Set via MWGUI or Configuration sharing or Stored in plain text in Overwritten via MWGUI SSL-Scanner: Key public key with imported backup ­ encrypted; the configuration on or when appliance is re- Verification of TLS 2048 bits Leaves the module in hard disk imaged connections plaintext DH Diffie-Hellman Internally generated Never leaves the module Stored in plain text on By power cycle or session TLS connections for Establishment private key by FIPS approved hard disk termination cluster communication, Private Key 224-bit DRBG configuration, signature updates and SSL Scanner functions McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 20 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 Key/CSP Key/CSP Generation / Input Output Storage Zeroization Use Type DH Diffie-Hellman Generated internally Leaves the module in Stored in plain text on By power cycle or session TLS connections for Establishment Public key plaintext hard disk termination cluster communication, Public Key 2048-bit configuration, signature updates and SSL Scanner functions RSA Key RSA private Internally generated Never leaves the module Stored in plain text on By power cycle or session TLS connections for Establishment key 2048 bit by following FIPS hard disk termination MWGUI or SSL Private Key 186-4 Scanner RSA Key RSA public key Internally generated Leaves the module in Stored in plain text on By power cycle or session TLS connections for Establishment 2048 bit by following FIPS plaintext hard disk termination MWGUI or SSL Public Key 186-4 Scanner TLS Session Key Triple-DES, Internally generated Output in encrypted Volatile memory in By power cycle or session TLS connections for AES 128, AES by the TLS KDF form during TLS plain text termination cluster communication, 256 handshake Configuration, signature updates and SSL Scanner functions DRBG Seed Random data Internally Generated Never Not persistently stored By power cycle; Seeding material for SP by the module DRBG uninstantiation 800-90A DRBG DRBG Entropy Random data Internally Generated Never Not persistently stored By power cycle; Entropy material for SP (512 -75203 by the module DRBG uninstantiation 800-90A DRBG Bytes) DRBG `V' Value Internal state Internally Generated Never Not persistently stored By power cycle; Secret, internal value value by the module DRBG uninstantiation for the CTR_DRBG DRBG `Key' Internal state Internally Generated Never Not persistently stored By power cycle; Key used for Value value by the module DRBG uninstantiation generating random material by the CTR_DRBG McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 21 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 Key/CSP Key/CSP Generation / Input Output Storage Zeroization Use Type WCCP Password Set via MWGUI or Configuration sharing or Stored in plain text in Overwritten by another Authentication (MD5) Authentication imported backup - encrypted the configuration on password or when for WCCP UDP47 Key hard disk appliance is re-imaged control packets 47 UDP ­ User Datagram Protocol McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 22 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 2.8 EMI/EMC The McAfee Web Gateway system 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). 2.9 Self-Tests The McAfee Web Gateway performs power-up and conditional self-tests as stated in the sections below. 2.9.1 Power-Up Self-Tests The McAfee Web Gateway performs the following self-tests at power-up: Firmware integrity check using HMAC SHA-256 Known Answer Tests (KAT) o AES Encrypt KAT o AES Decrypt KAT o Triple-DES Encrypt KAT o Triple-DES Decrypt KAT o SHA-1 KAT o HMAC KAT with SHA-1, SHA-224, SHA-256, SHA-384, and SHA-512 o RSA Signature Generation KAT o RSA Signature Verification KAT o RSA Key Wrap KAT o RSA Key Unwrap KAT o SP 800-90A CTR_DRBG KAT DSA Pairwise Consistency Test (verify operation) If any of the tests listed above fails, the module enters into a critical error state where all cryptographic operations and output of any data is prohibited. The module indicates that it is in an error state when the status output indicating an error is provided via the management port. An example output is as follows: Firmware integrity test failure message: "FIPS Self Test failed: RPM verify failed System halted" Cryptographic algorithm test failure message: "FIPS Self Test failed: : () : System halted" Operators can reboot or power-cycle the module, to try to clear the error and resume normal operation. 2.9.2 Conditional Self-Tests The module performs the following conditional self-tests: Continuous Random Number Generator Test (CRNGT) for SP 800-90A CTR_DRBG Continuous RNG Tests for NDRNG RSA Pairwise Consistency Test (sign and verify operations) McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 23 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 If any of the tests listed above fails, the module enters into the critical error state where all cryptographic operations and output of any data is prohibited. Operators can reboot or power-cycle the module, to try to clear the error and resume normal operation. 2.10 Mitigation of Other Attacks This section is not applicable. The module does not claim to mitigate any attacks beyond the FIPS 140-2 Level 1 requirements for this validation. McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 24 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 3 Secure Operation The McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances meet Level 1 requirements for FIPS 140-2. The sections below describe how to place and keep the module operation. 3.1 Initial Setup The following sections provide the necessary step-by-step instructions necessary to configure the module for operation. McAfee delivers the module via trusted delivery services (FedEx, Expeditors International, and Airgroup Express). For any questions or issues that arise at any point during the installation and configuration of the appliance, contact the McAfee support team at http://www.mcafee.com/us/support.aspx. 3.1.1 Setting FIPS Environment In order to setup the appliance in its validated configuration, the following steps shall be performed by an authorized individual: 1. Obtain version 7.3.2.3.4 installation image from McAfee's Content & Cloud Security Portal. 2. Write 7.3.2.3.4 image to a USB or CD-ROM media. NOTE: From this point onwards, until the appliance is sealed, the appliance must not be left unattended by the operator. 3. Attach keyboard/monitor or serial console to appliance and boot to BIOS. Reset the BIOS setting to their Default settings. Change boot settings to add USB or CD to top of boot order. 4. Reboot with media inserted. 5. Select the FIPS 140-2 Level 1 installation mode and serial or keyboard/video as installation operator interface. 6. Wait for disk reformat, install, and reboot. 7. Follow the procedures included in the module's Product Guide to complete installation using the installation wizard. 8. Follow the instructions in Section 3.2 to ensure that the appliance is completely configured for operation. Change the BIOS boot to be hard drive only and add an administrator password to enter the BIOS. 9. Install the front bezel. The appliance is now considered to be in its validated configuration. This installation procedure disables logon to the appliance using SSH48 or from a direct-connected console and implements other features required for FIPS compliance. Once the module is in its validated configuration, the following needs to be done to maintain compliance: 1. The module shall only boot from the hard drive. 2. The Intel Remote Management Console on the module is disabled by default and shall remain so. 3. The log file encryption and/or anonymization feature shall remain turned off. 3.2 Crypto-Officer Guidance The Crypto-Officer is responsible for initializing, performing security-relevant configuration, and monitoring the module. The Crypto-Officer is required to set a BIOS password to prevent unauthorized individuals from changing the module's settings. During initial set up, the CO shall change the default admin password, MWGUI server certificate, and the cluster CA. Additionally, the CO shall ensure that the log file encryption and/or anonymization feature is turned off when the module is being operated. 48 SSH ­ Secure Shell McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 25 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 The Crypto-Officer can initiate the execution of self-tests, and can access the module's status reporting capability. Self-tests can be initiated at any time by power cycling the module. 3.2.1 Management The Crypto-Officer is responsible for maintaining and monitoring the status of the module. Please refer to Section 3.1 above for guidance that the Crypto-Officer must follow. To obtain the current FIPS status of the module, the CO should access the module via the MWGUI. On the upper, left-hand corner of the GUI, the CO will see "FIPS 140-2" when the module has been properly configured. For details regarding the management of the modules, please refer to the McAfee Web Gateway Installation Guide. 3.2.2 Zeroization Session keys are zeroized at the termination of the session, and are also cleared when the module is power- cycled. Zeroizartion also includes the SP 800-90A CTR_DRBG seed, entropy, and key values. All other CSPs may be zeroized by reimaging the appliance. The Crypto-Officer must wait until the module has successfully rebooted in order to verify that zeroization has completed. 3.3 User Guidance The User does not have the ability to configure sensitive information on the module. McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 26 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 4 Acronyms Table 11 in this section describes the acronyms used throughout the document. Table 11 ­ Acronyms Acronym Definition AC Alternating Current AES Advanced Encryption Standard CAVP Cryptographic Algorithm Validation Program CBC Cipher-Block Chaining CLI Command Line Interface CMVP Cryptographic Module Validation Program CO Crypto-Officer CRNGT Continuous Random Number Generator Test CSE Communications Security Establishment CSP Critical Security Parameter CVL Component Validation List DB-9 D-subminiature 9-pin connector DES Digital Encryption Standard DNS Domain Name System DSA Digital Signature Algorithm ECB Electronic Codebook EDC Error Detection Code EMC Electromagnetic Compatibility EMI Electromagnetic Interference FIPS Federal Information Processing Standard FTP File Transfer Protocol GUI Graphical User Interface HMAC (Keyed-) Hash Message Authentication Code HTML Hypertext Markup Language HTTP Hypertext Transfer Protocol HTTPS Secure Hypertext Transfer Protocol ID Identification I/O Input/Output IP Internet Protocol KAT Known Answer Test McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 27 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Security Policy, Version 1.5 December 17, 2015 Acronym Definition LDAP Lightweight Directory Access Protocol LED Light Emitting Diode MD Message Digest MLOS McAfee Linux Operating System MWGUI McAfee Web Gateway Graphical User Interface NDRNG Non-Deterministic Random Number Generator NIC Network Interface Card NIST National Institute of Standards and Technology NTLM Microsoft Windows NT LAN Manager NMI Non-Maskable interrupt OS Operating System PCI Peripheral Component Interconnect PCIe Peripheral Component Interconnect Express PKCS Public Key Cryptography Standard POST Power-On Self-Test RADIUS Remote Authentication Dial-In User Service RAID Redundant Array of Inexpensive Disks RC Rivest Cipher RSA Rivest Shamir and Adleman SHA Secure Hash Algorithm SNMP Simple Network Management Protocol SSH Secure Shell SSL Secure Sockets Layer SWPS Secure Web Protection Service TLS Transport Layer Security UDP User Datagram Protocol URL Uniform Resource Locator USB Universal Serial Bus USM User-based Security Model UTF Unicode Transformation Format UUID Universally Unique Identifier VGA Video Graphics Array WCCP Web Cache Communication Protocol McAfee Web Gateway WBG-5000-C and WBG-5500-C Appliances Page 28 of 29 © 2015 McAfee, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. Prepared by: Corsec Security, Inc. 13921 Park Center Road, Suite 460 Herndon, VA 20171 United States of America Phone: +1 (703) 267-6050 Email: info@corsec.com http://www.corsec.com