Blue Coat Systems, Inc. ProxySG 600 Series Models: SG600-10, SG600-20, SG600-35 Hardware Version: 090-02911, 090-02912, 090-02913, 090-02914, 090-02915, 090-02916 Firmware Version: 6.5.1.103 FIPS 140-2 Non-Proprietary Security Policy FIPS Security Level: 2 Document Version: 0.7 Prepared for: Prepared by: Blue Coat Systems, Inc. Corsec Security, Inc. 420 N. Mary Avenue 13135 Lee Jackson Memorial Highway, Suite 220 Sunnyvale, CA 94085 Fairfax, VA 22033 United States of America United States of America Phone: +1 866 30 BCOAT (22628) Phone: +1 703 267 6050 Email: usinfo@bluecoat.com Email: info@corsec.com http://www.bluecoat.com http://www.corsec.com ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Table of Contents 1 INTRODUCTION ................................................................................................................... 4 1.1 PURPOSE ................................................................................................................................................................ 4 1.2 REFERENCES .......................................................................................................................................................... 4 1.3 DOCUMENT ORGANIZATION ............................................................................................................................ 4 2 PROXYSG 600 SERIES ........................................................................................................... 5 2.1 OVERVIEW ............................................................................................................................................................. 5 2.2 MODULE SPECIFICATION..................................................................................................................................... 8 2.3 MODULE INTERFACES .......................................................................................................................................... 9 2.4 ROLES AND SERVICES .........................................................................................................................................11 2.4.1 Crypto-Officer Role.............................................................................................................................................. 12 2.4.2 User Role ................................................................................................................................................................ 14 2.4.3 Additional Services............................................................................................................................................... 15 2.4.4 Authentication Mechanism ............................................................................................................................... 15 2.5 PHYSICAL SECURITY ...........................................................................................................................................18 2.6 OPERATIONAL ENVIRONMENT.........................................................................................................................18 2.7 CRYPTOGRAPHIC KEY MANAGEMENT ............................................................................................................18 2.8 SELF-TESTS ..........................................................................................................................................................25 2.8.1 Power-Up Self-Tests ............................................................................................................................................ 25 2.8.2 Conditional Self-Tests ......................................................................................................................................... 25 2.8.3 Critical Function Tests ........................................................................................................................................ 26 2.9 MITIGATION OF OTHER ATTACKS ..................................................................................................................27 3 SECURE OPERATION ......................................................................................................... 28 3.1 INITIAL SETUP......................................................................................................................................................28 3.1.1 Label and Baffle Installation Instructions ..................................................................................................... 28 3.2 SECURE MANAGEMENT .....................................................................................................................................32 3.2.1 Initialization ........................................................................................................................................................... 32 3.2.2 Management ........................................................................................................................................................ 33 3.2.3 Zeroization ............................................................................................................................................................ 34 3.3 USER GUIDANCE ................................................................................................................................................35 3.4 NON-APPROVED MODE ...................................................................................................................................35 4 ACRONYMS .......................................................................................................................... 36 List of Figures FIGURE 1 TYPICAL DEPLOYMENT OF A PROXYSG 600 SERIES APPLIANCE ......................................................................5 FIGURE 2 SG600 (FRONT VIEW) ...........................................................................................................................................8 FIGURE 3 CONNECTION PORTS AT THE REAR OF THE SG600 ...................................................................................... 10 FIGURE 4 FIPS SECURITY KIT CONTENTS .......................................................................................................................... 28 FIGURE 5 REAR BAFFLE INSTALLATION............................................................................................................................... 29 FIGURE 6 PCI COVER INSTALLATION ................................................................................................................................. 30 FIGURE 7 LABEL SHOWING TAMPER EVIDENCE ................................................................................................................ 30 FIGURE 8 TAMPER-EVIDENT LABEL PLACEMENT OVER THE PCI COVER ........................................................................ 31 FIGURE 9 TAMPER-EVIDENT LABEL PLACEMENT ON LEFT REAR OF APPLIANCE ........................................................... 31 FIGURE 10 KEYRING CREATION MANAGEMENT CONSOLE DIALOGUE BOX ............................................................... 34 FIGURE 11 KEYRING CREATION CLI COMMANDS ........................................................................................................... 34 List of Tables TABLE 1 MACH5 VS PROXY EDITION CAPABILITY DIFFERENCES .....................................................................................6 TABLE 2 SECURITY LEVEL PER FIPS 140-2 SECTION............................................................................................................7 Blue Coat ProxySG 600 Series Page 2 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 TABLE 3 SG600 APPLIANCE CONFIGURATIONS ..................................................................................................................8 TABLE 4 FIPS 140-2 LOGICAL INTERFACE MAPPINGS FOR THE FRONT OF THE SG600.................................................9 TABLE 5 FRONT PANEL LED STATUS INDICATIONS FOR THE SG600 ..............................................................................9 TABLE 6 FIPS 140-2 LOGICAL INTERFACE MAPPINGS FOR THE REAR OF THE SG600 ................................................. 10 TABLE 7 REAR PANEL LED STATUS INDICATIONS FOR THE SG600 .............................................................................. 10 TABLE 8 FIPS AND SG600 ROLES....................................................................................................................................... 12 TABLE 9 CRYPTO OFFICER ROLE SERVICES AND CSP ACCESS ....................................................................................... 13 TABLE 10 USER SERVICES AND CSP ACCESS ..................................................................................................................... 15 TABLE 11 AUTHENTICATION MECHANISMS USED BY THE MODULE ............................................................................. 17 TABLE 12 FIPS-APPROVED ALGORITHM IMPLEMENTATIONS .......................................................................................... 19 TABLE 13 LIST OF CRYPTOGRAPHIC KEYS, CRYPTOGRAPHIC KEY COMPONENTS, AND CSPS................................. 20 TABLE 14 SG600 CONDITIONAL SELF-TESTS ................................................................................................................... 26 TABLE 15 LIST OF CRITICAL FUNCTION TESTS ................................................................................................................. 27 TABLE 16 RS-232 PARAMETERS .......................................................................................................................................... 32 TABLE 17 ACRONYMS .......................................................................................................................................................... 36 Blue Coat ProxySG 600 Series Page 3 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 1 Introduction 1.1 Purpose This is a non-proprietary Cryptographic Module Security Policy for the ProxySG 600 Series (Models: SG600-10, SG600-20, SG600-35; Firmware Version: 6.5.1.103) from Blue Coat Systems, Inc.. This Security Policy describes how the ProxySG 600 Series 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 document also describes how to run the appliance in the Approved mode of operation. This policy was prepared as part of the Level 2 FIPS 140-2 validation of the module. The ProxySG 600 Series (SG600-10, SG600-20, SG600-35) is referred to in this document as theSG600, crypto module, or 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 Blue Coat website (www.bluecoat.com) contains information on the full line of products from Blue Coat.  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  Other supporting documentation as additional references This Security Policy and the other validation submission documentation were produced by Corsec Security, Inc. under contract to Blue Coat. With the exception of this Non-Proprietary Security Policy, the FIPS 140-2 Submission Package is proprietary to Blue Coat and is releasable only under appropriate non- disclosure agreements. For access to these documents, please contact Blue Coat. Blue Coat ProxySG 600 Series Page 4 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 2 ProxySG 600 Series 2.1 Overview The foundation of Blue Coat’s application delivery infrastructure, the Blue Coat ProxySG 600 Series appliances establish points of control that accelerate and secure business applications for users across the distributed organization. The ProxySG 600 Series appliances serve as an Internet proxy and wide area network (WAN) optimizer. The purpose of the appliances is to provide a layer of security between an Internal and External Network (typically an office network and the Internet), and to provide acceleration and compression of transmitted data. As the world’s leading proxy appliance, the Blue Coat SG600 is a powerful yet flexible tool for improving both application performance and security, removing the need for compromise:  Performance – Blue Coat’s patented “MACH5” acceleration technology combines five different capabilities onto one box. Together, they optimize application performance and help ensure delivery of critical applications. User and application fluent, MACH5 improves the user experience no matter where the application is located, internally or externally on the Internet.  Security – Blue Coat’s industry leading security architecture addresses a wide range of requirements, including filtering Web content, preventing spyware and other malicious mobile code, scanning for viruses, inspecting encrypted Secure Sockets Layer (SSL) traffic, and controlling instant messaging (IM), Voice-over-IP (VoIP), peer-to-peer (P2P), and streaming traffic.  Control – Blue Coat’s patented Policy Processing Engine empowers administrators to make intelligent decisions. Using a wide range of attributes such as user, application, content and others, organizations can effectively align security and performance policies with corporate priorities. See Figure 1 below for a typical deployment scenario for the ProxySG 600 Series appliances. Figure 1 Typical Deployment of a ProxySG 600 Series Appliance The security provided by the SG600 can be used to control, protect, and monitor the Internal Network’s use of controlled protocols on the External Network. The SG600 appliances offer a choice of two “editions” via licensing: MACH5 and Proxy. The controlled protocols implemented in the evaluated configurations are: Blue Coat ProxySG 600 Series Page 5 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Table 1 MACH5 vs Proxy Edition Capability Differences Licensing Edition Capability MACH5 Proxy Common Internet File System (CIFS) Acceleration Yes Yes Windows Media Optimization (Microsoft Media Streaming (MMS)) Yes Yes Microsoft Smooth Streaming Optimization Yes Yes Real Media Optimization Yes Yes Real-Time Streaming Protocol (RTSP) Optimization Yes Yes Real-Time Messaging Protocol (RTMP) Optimization Yes Yes QuickTime Optimization (Apple HTTP Live Streaming) Yes Yes Adobe Flash Optimization (Adobe HTTP Dynamic Streaming) Optional Optional Bandwidth Management Yes Yes DNS proxy Yes Yes Advanced DNS Access Policy No Yes Hypertext Transfer Protocol (HTTP)/ Secure Hypertext Transfer Protocol (HTTPS) Acceleration Yes Yes File Transfer Protocol (FTP) Acceleration Yes Yes Secure Sockets Layer (SSL) Acceleration Yes Yes IMAP1 Acceleration Yes Yes TCP2 tunneling protocols (Secure Shell (SSH)) Yes Yes POP3 Acceleration Yes Yes SMTP4 Acceleration Yes Yes Messaging Application Programming Interface (MAPI) Acceleration Yes Yes Secure Shell Yes Yes Telnet Proxy No Yes ICAP Services No Yes CA eTrust SiteMinder No Yes IMAP – Internet Message Access Protocol 1 2 TCP – Transmission Control Protocol POP3 – Post Office Protocol version 3 3 SMTP – Simple Mail Transfer Protocol 4 Blue Coat ProxySG 600 Series Page 6 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Licensing Edition Capability MACH5 Proxy Oblix COREid No Yes Peer-To-Peer No Yes User Authentication Yes Yes Onbox Content Filtering (3rd Party or BCWF5) No Yes Instant Messaging (AOL6, Yahoo, MSN7) No Yes 8 SOCKS No Yes SSL Termination/Proxy Yes Yes Access control is achieved by enforcing configurable policies on controlled protocol traffic to and from the Internal Network users. The policy may include authentication, authorization, content filtering, and auditing. In addition, the SG600provides optimization of data transfer between SG600 nodes on a WAN using its Application Delivery Network (ADN) technology. Optimization is achieved by enforcing a configurable policy on traffic traversing the WAN. Additionally, the SG600 offers network traffic acceleration by using hardware implementations of cryptographic services provided by on-board hardware accelerator cards (HAC) produced by Cavium Networks. The SG600 is validated at the following FIPS 140-2 Section levels in Table 2. Table 2 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 8 Electromagnetic Interference/Electromagnetic Compatibility 2 9 Self-tests 2 10 Design Assurance 2 11 Mitigation of Other Attacks N/A 5 BCWF – Blue Coat Web Filter AOL – America Online 6 MSN – The Microsoft Network 7 SOCKS – SOCKet Secure 8 Blue Coat ProxySG 600 Series Page 7 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 2.2 Module Specification For the FIPS 140-2 validation, the crypto module was tested on the following SG600 appliance configurations: Table 3 SG600 Appliance Configurations Hardware Version Model Proxy Edition MACH5 Edition SG600-10 090-02912 090-02911 SG600-20 090-02914 090-02913 SG600-35 090-02916 090-02915 The Proxy edition and MACH5 edition hardware version numbers represent licensing options available. The MACH5 and Proxy editions run on the exact same hardware and firmware and are exactly the same from a cryptographic functionality and boundary perspective. The MACH5 and Proxy editions vary in only data processing capabilities; the Crypto Officer and User services of the module are identical for both licensing editions. Table 1 above provides a mapping between the capabilities and the licensing edition. The SG600 offers an affordable rack-mountable appliance solution for small enterprises and branch offices that have direct access to the Internet. The front panel, as shown in Figure 2 below, has 1 Liquid Crystal Display (LCD), 2 Light Emitting Diodes (LEDs), and 6 control buttons (NOTE: the front panel control buttons are disabled when configured for Approved mode of operation). Connection ports are at the rear, as shown in Figure 3. Figure 2 SG600 (Front View) For the FIPS 140-2 validation, the module was tested on the following SG600 appliance configurations:  SG600 (SG600-10, SG600-20, SG600-35) with a Cavium CN501 PCI-e9 SSL HAC The SG600 is a module with a multi-chip standalone embodiment. The overall security level of the module is 2. The cryptographic boundary of the SG600 is defined by the appliance chassis, which surrounds all the hardware and firmware. The module firmware, version 6.5.1.1, contains the SGOS 6.5 Cryptographic Library version 3.1.1. PCI-e – Peripheral Component Interconnect Express 9 Blue Coat ProxySG 600 Series Page 8 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 2.3 Module Interfaces The front panel of the SG600 (as shown in Figure 2) has an LCD interface, 2 LEDs, and six control buttons. The control buttons on the front panel are disabled once the module is configured for its Approved mode of operation. The type and quantity of all ports present in the front panel of the SG600 are given in Table 4. Table 4 FIPS 140-2 Logical Interface Mappings for the front of the SG600 FIPS 140-2 Physical Port/Interface Quantity Interface  Status Output LEDs 2  Status Output LCD 1 The status indications provided by the LEDs on the SG600 is described in Table 5. Table 5 Front Panel LED Status Indications for the SG600 LED Color Definition Power LED OFF The SG600 is powered off. AMBER The OS has loaded but has not been loaded. FLASHING GREEN The OS has been loaded but has not TO AMBER been configured. GREEN The OS has loaded and is properly configured. System LED OFF The appliance has not determined the system status. GREEN Healthy. AMBER Warning. FLASHING AMBER Critical Warning. BLUE Diagnostic mode. The rear of the SG600 is shown in Figure 3. Blue Coat ProxySG 600 Series Page 9 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Figure 3 Connection Ports at the Rear of the SG600 The rear side of the SG600 (shown in Figure 3) contains all the connecting ports. Those ports are:  An AC power connector.  A serial port to connect to a Personal Computer (PC) for management.  Two 10/100/1000 Base T Ethernet adapter ports.  One 10/100/1000 Base T Ethernet adapter port for management.  An expansion slot for: o An optional Four port 1000 Base-F (quad GigE Fiber SX) NIC o An optional Four port 1000 Base-T (quad GigE with bypass) NIC The type and quantity of all ports present in rear panel of the SG600 are given in Table 6. Table 6 FIPS 140-2 Logical Interface Mappings for the rear of the SG600 FIPS 140-2 Physical Port/Interface Quantity Interface  Ethernet ports 3 Data Input  Data Output  Control Input  Status Output  Control Input Serial ports 1  Status Output  Status Output Ethernet Interface – Speed LEDs 3  Status Output Ethernet Interface – Activity LEDs 3  Power Input AC power 1  Control Input Power Switch 1 The status indications provided by the LEDs on the rear of the SG600 are described in Table 7. Table 7 Rear Panel LED Status Indications for the SG600 LED Color Definition Ethernet Interface – OFF No link is present. Activity LEDs GREEN Link is present. Blue Coat ProxySG 600 Series Page 10 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 LED Color Definition FLASHING GREEN Link activity. Ethernet Interface – OFF 10 Mbps speed connection is present. Activity LEDs GREEN 100 Mbps speed connection is present. AMBER 1000 Mbps speed connection is present. 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 Crypto-Officer (CO) role and a User role. Before accessing the modules for any administrative services, COs and Users must authenticate to the module according to the methods specified in Table 11. The modules offer two management interfaces:  Command Line Interface (CLI) – accessible locally via the serial port (provides access to the Setup Console portion of the CLI which requires the additional “Setup” password to gain access) or remotely using SSH. This interface is used for management of the modules. This interface must be accessed locally via the serial port to perform the initial module configurations (IP address, DNS server, gateway, and subnet mask) and placing the modules into the Approved mode. When the module has been properly configured, this interface can be accessed via SSH. management of the module may take place via SSH or locally via the serial port. Authentication is required before any functionality will be available through the CLI.  Management Console – a graphical user interface accessible remotely with a web browser that supports TLS10. This interface is used for management of the modules. Authentication is required before any functionality will be available through the Management Console. When managing the module over the CLI, COs and Users both log into the modules with administrator accounts entering the “standard”, or “unprivileged” mode on the SG600. Unlike Users, COs have the ability to enter the “enabled”, or “privileged” mode after initial authentication to the CLI by supplying the “enabled” mode password. Additionally, COs can only enter the “configuration” mode from the “enabled” mode via the CLI, which grants privileges to make configuration level changes. Going from the “enabled” mode to the “configuration” mode does not require additional credentials. The details of these modes of operation are found below in Table 8. TLS – Transport Layer Security 10 Blue Coat ProxySG 600 Series Page 11 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Table 8 FIPS and SG600 Roles FIPS Roles SG600 Roles and Privileges CO The CO is an administrator of the module that has been granted “enabled” mode access while using the CLI and “read/write” access while using the Management Console. When the CO is using the CLI, and while in the “enabled” mode of operation, COs may put the module in its Approved mode, reset to the factory state (local serial port only) and query if the module is in Approved mode. In addition, COs may do all the services available to Users while not in “enabled” mode. Once the CO has entered the “enabled” mode, the CO may then enter the “configuration” mode via the CLI. The “configuration” mode provides the CO management capabilities to perform tasks such as account management and key management. When the CO is administering the module over the Management Console, they can perform all the same services available in CLI (equivalent to being in the “configuration” mode in the CLI) except the CO is unable to put the module into Approved mode. The CO may monitor the health and status of the modules using SNMPv3. SNMPv3 privacy and authentication keys are assigned to a CO and are not tied to the CO’s CLI and Management Console credentials. User The User is an administrator of the module that operates only in the “standard” or “unprivileged” mode and has not been granted access to the “enabled” mode in the CLI and has been given “read-only” privileges when using the Management Console. The User will access the CLI and Management Console interfaces for management of the module. When the User is administering the module over the Management Console, they perform all the same services available in CLI (“standard” mode only services). The User may monitor the health and status of the modules using SNMPv3. SNMPv3 privacy and authentication keys are assigned to a User and are not tied to the User’s CLI and Management Console credentials. Descriptions of the services available to a Crypto Officer and User are described below in Table 9 and Table 10 respectively. For each service listed below, COs and Users are assumed to already have authenticated prior to attempting to execute the service. Please note that the keys and CSPs listed in the table indicate the type of access required using the following notation:  R – The CSP is read  W – The CSP is established, generated, modified, or zeroized  X – Execute: The CSP is used within an Approved or Allowed security function or authentication mechanism. 2.4.1 Crypto-Officer Role Descriptions of the services available to the Crypto-Officer role are provided in the table below. Blue Coat ProxySG 600 Series Page 12 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Table 9 Crypto Officer Role Services and CSP Access Service Description CSP and Access Required Set up the module Set up the first-time network CO Password – W configuration, CO username and “Enabled” mode password – W password, and enable the module “Setup” Password – W in the Approved mode of operation. For more information, see section 3.2.1 in the Security Policy. Enter the “enabled” mode Manage the module in the Enabled” mode password – RX “enabled” mode of operation, granting access to higher privileged commands * Enter the “configuration” mode Manage the module in the None “configuration” mode of operation, allowing permanent system modifications to be made * Disable FIPS mode Re-initializes the module to a MAK – W factory state (accessible only via SSH Session Key – W the serial port) SSH Authentication Key – W TLS Session Key – W TLS Authentication Key – W All CTR_DRBG CSPs – W ** Firmware Load Loads new external firmware and Integrity Test public key – performs an integrity test using WRX an RSA digital signature. Create remote management session Manage the module through the RSA public key – RX (CLI) CLI (SSH) remotely via Ethernet RSA private key – RX port. SSH Session Key – WRX SSH Authentication Key – WRX All CTR_DRBG CSPs – RW Create remote management session Manage the module through the RSA public key – RX (Management Console) Management Console (TLS) RSA private key – RX remotely via Ethernet port, with TLS Session Key – WRX optional CAC authentication TLS Authentication Key – enabled. WRX All CTR_DRBG CSPs – RW ** Create, edit, and delete operator Create, edit and delete operator None groups groups; define common sets of operator permissions. ** Create, edit, and delete operators Create, edit and delete operators Crypto-Officer Password – W (these may be COs or Users); User Password – W define operator’s accounts, SNMP Privacy Key – W change password, and assign SNMP Authentication Key – W permissions. ** Create filter rules (CLI) Create filters that are applied to None user data streams. Create filter rules (Management Create filters that are applied to None Console) user data streams. Blue Coat ProxySG 600 Series Page 13 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Service Description CSP and Access Required Show FIPS-mode status (CLI) The CO logs in to the module None using the CLI. Entering the command “show version” will display if the module is configured in Approved mode. Show FIPS-mode status (Management The CO logs in to the module None Console) using the Management Console and navigates to the “Configuration” tab that will display if the module is configured in Approved mode. ** Manage module configuration Backup or restore the module RSA public key – WRX configuration RSA private key – WRX SNMP Privacy Key – WRX SNMP Authentication Key – WRX CO Password – WRX User Password – WRX “Enabled” mode password – WRX * Zeroize keys Zeroize keys by re-initializing the MAK – W module to a factory state SSH Session Key – W (accessible only via the serial SSH Authentication Key – W port). This will zeroize all CSPs. TLS Session Key – W The zeroization occurs while the TLS Authentication Key – W module is still in Approved-mode. All CTR_DRBG CSPs – W ** Change password Change Crypto-Officer password Crypto-Officer Password – W * Perform self-test Perform self-test on demand by SSH Session Key – W rebooting the machine SSH Authentication Key – W TLS Session Key – W TLS Authentication Key – W All CTR_DRBG CSPs – W * Reboot the module Reboot the module. SSH Session Key – W SSH Authentication Key – W TLS Session Key – W TLS Authentication Key – W All CTR_DRBG CSPs – W Create SNMPv3 session Monitor the module using SNMP Privacy Key – RX SNMPv3 SNMP Authentication Key – RX * - Indicates services that are only available once the CO has entered the “enabled” mode of operation. ** - Indicates services that are only available once the CO has entered the “enabled” mode followed by the “configuration” mode of operation. 2.4.2 User Role Descriptions of the services available to the User role are provided in the table below. Blue Coat ProxySG 600 Series Page 14 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Table 10 User Services and CSP Access Service Description CSP and Access Required Create remote management session Manage the module through the RSA public key – RX (CLI) CLI (SSH) remotely via Ethernet RSA private key – RX port. SSH Session Key –WRX SSH Authentication Key – WRX All CTR_DRBG CSPs – RW Create remote management session Manage the module through the RSA public key – RX (Management Console) Management Console (TLS) RSA private key – RX remotely via Ethernet port, with TLS Session Key – WRX optional CAC authentication TLS Authentication Key – enabled. WRX All CTR_DRBG CSPs – RW Create SNMPv3 session Monitor the health of the module SNMP Privacy Key – RX using SNMPv3 SNMP Authentication Key – RX Show FIPS-mode status (Management The User logs in to the module None Console) using the Management Console and navigates to the “Configuration” which will display if the module is configured in Approved mode. Show FIPS-mode status (CLI) The User logs in to the module None using the CLI. Entering the command “show version” will display if the module is configured in Approved mode. 2.4.3 Additional Services The module also offers proxying and termination services for the protocols listed in section 2.1. For more information on the non security relevant services of the module, please refer to the Blue Coat® Systems SGOS Administration Guide. 2.4.4 Authentication Mechanism COs and Users must authenticate using a user ID and password, SSH client key (SSH only), or certificates associated with the correct protocol in order to set up the secure session. Secure sessions that authenticate for User services have no interface available to access other services (i.e. Crypto Officer services). Each CO or User SSH session remains active (logged in) and secured until the operator logs out. Each CO and User Management Console sessions remain active until the operator logs out or inactivity for a configurable amount of time has elapsed. Modules used by the United States Department of Defense (DoD) must meet Homeland Security Presidential Directive (HSPD)-12 requirements regarding the use of FIPS 201 validated Common Access Card (CAC) authentication for COs and Users connecting to management functionality of the module. Additionally, other agencies may require FIPS 201 validated PIV11 II card authentication. PIV – Personal Identity Verification II 11 Blue Coat ProxySG 600 Series Page 15 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 When the module is configured to use CAC authentication, the module will implement specially configured CPL during administrator authentication in order to facilitate TLS mutual authentication. This is accomplished by modifying the HTTPS-Console service so that it can be configured to validate a client certificate against a chosen certificate authority (CA) list. CAC authentication will take place against a Certificate realm, and CO and User authorization takes place against an LDAP realm. The authentication procedure leverages 3rd party middleware on the management workstation in order to facilitate two factor authentication of the user to their CAC using a Personal Identification Number (PIN). This process enables the module to retrieve the X.509 certificate from the microprocessor smart card. The process is as follows: 1. On the management workstation the CO or User opens a browser and establishes a clear-text HTTP connection with the module. 2. Using CPL similar to the VPM NotifyUser action, the CO or User is presented with a DoD warning banner which they must positively acknowledge and accept. 3. NotifyUser redirects the browser to an HTTPS connection with the module that requires mutual authentication. This is made possible by CPL that puts the module in reverse-proxy mode at this point. 4. The TLS handshakes begin. The reverse-proxy service on the module requires a certificate to complete the handshake (i.e. the verify-peer setting has been enabled in the reverse-proxy service). 5. The browser presents the CO or User with a dialog box prompting which certificate to select. 6. The CO or User selects the X.509 certificate on the CAC. 7. The middleware on the management workstation prompts the CO or User for the PIN to unlock the certificate. The CO or User enters the PIN and the certificate is transmitted to the module. 8. The module authenticates the certificate against the CA list that has been configured on the reverse proxy service using local CRLs and OCSP to check for certificate revocation. 9. The CO or User reviews and accepts the certificate issued to the web browser by the module. A mutually authenticated TLS session is now in use. 10. The module extracts the subject name (of the CO or User) from the subjectAltNames extension of the X.509 certificate according to configuration of the certificate realms, Within the subjectAltNames extension is the CO or User’s userPrincipleName (UPN) (When PIV cards are used in place of CACs, the CommonName (CN) field is extracted from the certificate instead). The UPN/CN is what ties the CAC identity to the Principle Name (PN) field of a CO or User record in Active Directory (AD), the LDAP server. 11. The certificate realm is configured to use an LDAP realm for authorization. The LDAP user is determined by LDAP search using the following filter: (userPrincipleName=$(user.name)). The CO or User is granted access to the Management Console if the UPN/CN is found in the LDAP directory. The exchanges with the LDAP server are secured using TLS. Conditions like group= and ldap.attribute may also be used to authorize the CO or User and to specify if the CO or User should have read-only or read-write access. The authentication mechanisms used in the module are listed below in Table 11. Blue Coat ProxySG 600 Series Page 16 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Table 11 Authentication Mechanisms Used by the Module Role Type of Authentication Authentication Strength Crypto-Officer Password The modules support password authentication internally. For password authentication done by the modules, passwords are required to be at least 8 characters in length and maximum of 64 bytes (number of characters is dependent on the character set used by system). An 8-character password allowing all printable American Standard Code for Information Interchange (ASCII) characters (95) with repetition equates to a 1: (958), or 1: 6,634,204,312,890,625 chance of false acceptance. The Crypto-Officer may connect locally using the serial port or remotely after establishing a TLS or SSH session. Password (“Enabled” Mode) The modules support password authentication internally. For password authentication done by the modules, passwords are required to be at least 8 characters in length and maximum of 64 bytes (number of characters is dependent on the character set used by system). An 8-character password allowing all printable American Standard Code for Information Interchange (ASCII) characters (95) with repetition equates to a 1: (958), or 1: 6,634,204,312,890,625 chance of false acceptance. This password is entered by the Crypto- Officer to enter the “enabled” mode; this is entered locally through the serial port or remotely after establishing an SSH session. Password (“Setup”) The modules support password authentication internally. For password authentication done by the modules, passwords are required to be at least 4 characters in length and maximum of 64 bytes (number of characters is dependent on the character set used by system). A 4-character password allowing all printable American Standard Code for Information Interchange (ASCII) characters (95) with repetition equates to a 1: (954), or 1: 81,450,625 chance of false acceptance. This password is entered by the Crypto-Officer and is required when using the serial port to access the Setup Console portion of the CLI. Public keys The module supports using RSA keys for authentication of Crypto-Officers during TLS (when CAC authentication is configured with a local Certificate Realm) or SSH. Using conservative estimates and equating a 2048-bit RSA key to a 112-bit symmetric key, the probability for a random attempt to succeed is 1:2112 or 1: 5.19 x 1033. Blue Coat ProxySG 600 Series Page 17 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Role Type of Authentication Authentication Strength User Password The modules support password authentication internally. For password authentication done by the modules, passwords are required to be at least 8 characters in length and maximum of 64 bytes (number of characters is dependent on the character set used by system). An 8-character password allowing all printable American Standard Code for Information Interchange (ASCII) characters (95) with repetition equates to a 1: (958), or 1: 6,634,204,312,890,625 chance of false acceptance. The User may connect remotely after establishing a TLS or SSH session. Public keys The module supports using RSA keys for authentication of Users during TLS (when CAC authentication is configured with a local Certificate Realm) or SSH. Using conservative estimates and equating a 2048-bit RSA key to a 112-bit symmetric key, the probability for a random attempt to succeed is 1:2112 or 1: 5.19 x 1033. 2.5 Physical Security The SG600 is a multi-chip standalone cryptographic module and is enclosed in a hard, opaque metal case that completely encloses all of its internal components. There are only a limited set of vent holes provided in the case, and these holes obscure the view of the internal components of the module. Tamper-evident labels are applied to the case to provide physical evidence of attempts to remove the case of the module. The Crypto-Officer is responsible for the placement of tamper-evident labels and baffles and guidance can be found in Section 3.1.1.2. The labels and baffles are part of the FIPS Security Kit (Part Number: 085- 02762). All of the module’s components are production grade. The SG600 was 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.6 Operational Environment The operational environment requirements do not apply to theSG600. The module does not provide a general purpose operating system nor does it allow operators the ability to load untrusted firmware. The operating system run by the cryptographic module is referred to as Secure Gateway Operating System (SGOS). SGOS is a proprietary real-time embedded operating system. 2.7 Cryptographic Key Management The module implements the FIPS-Approved algorithms listed in Table 12 below. Blue Coat ProxySG 600 Series Page 18 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Table 12 FIPS-Approved Algorithm Implementations CN501 SSL HAC Firmware Implementation Algorithm Implementation Certificate Certificate Number Number Symmetric Key Algorithms AES: ECB , CBC , OFB , CFB -128 bit mode for 128-, 192-, 12 13 14 15 #2560 #105 and 256-bit key sizes 3DES16: ECB, CBC, CFB-64, OFB mode for keying option 1 (3 #1549 #217 different keys) Asymmetric Key Algorithms RSA (ANSI X9.31) Key Generation – 2048, 3072, 4096-bit #1312 N/A RSA PKCS #1 signature generation – 2048, 3072, and 4096-bit 17 RSA PKCS#1 signature verification – 1024, 1536, 2048, 3072, and #1312 N/A 4096-bit Hashing Functions #2159 N/A SHA18-1 SHA-2 (SHA-224, SHA-256, SHA-384, SHA-512) #2159 N/A Message Authentication Code (MAC) Functions #1580 N/A HMAC19 with SHA-120 HMAC with SHA-224, SHA-256, SHA-384, SHA-512 #1580 N/A Deterministic Random Bit Generator (DRBG) SP21 800-90 CTR_DRBG (AES-256) #386 N/A NOTE: As of December 31, 2010, the following algorithm listed in the table above is considered “legacy-use” only.  Digital signature verification using RSA key sizes of 1024 and 1536-bits are approved for legacy use only. RSA Signature Verfication using 1536-bits is present only in the firmware implementation The module utilizes the following non-FIPS-Approved algorithms:  RSA PKCS#1 wrap/unwrap (key-wrapping) – 2048, 3072, and 4096–bit sizes providing 112, 130, and 150-bits of security.  Diffie-Hellman for key agreement during TLS and SSH: 2048-bit keys (provides 112 bits of security).  Non-Deterministic RNG (NDRNG) for seeding the FIPS-Approved RNG (SP 800-90 CTR_DRBG) Caveat: The module implements MD5 22 for use with SSL3.1/TLS1.0, which is allowed in the FIPS- Approved mode of operation. Any other use of this function is prohibited. ECB – Electronic Codebook 12 CBC – Cipher Block Chaining 13 OFB – Output Feedback 14 CFB – Cipher Feedback 15 16 3DES – Triple Data Encryption Standard PKCS – Public Key Cryptography Standard 17 SHA – Secure Hash Algorithm 18 HMAC – Hash-Based Message Authentication Code 19 20 HMAC-SHA-1 uses keys of at least 112-bits of security strength. SP – Special Publication 21 MD5 – Message Digest v5 22 Blue Coat ProxySG 600 Series Page 19 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 The module supports the CSPs listed below in Table 13. Table 13 List of Cryptographic Keys, Cryptographic Key Components, and CSPs Key Key Type Generation / Input Output Storage Zeroization Use Master Appliance AES CBC 256-bit Internally generated Never exits the Stored in plaintext By disabling the FIPS- Encrypting Crypto- Key (MAK) key via FIPS-Approved module on non-volatile Approved mode of Officer password, DRBG. memory operation SNMP localized key, RSA private key Integrity Test Public RSA public key 2048 Externally generated, Never exits the Stored in plaintext Overwritten after Verifying the Key bits Imported in encrypted module on non-volatile upgrade by the key in integrity of the form via a secure TLS memory the newly signed system image during or SSH session image. upgrade or downgrade. 204823, 3072, and RSA Public Key Modules’ public key is Output during Modules’ public key Modules’ public key is Negotiating TLS or 4096-bits internally generated TLS/SSH negotiation is stored on non- deleted by command. SSH sessions via FIPS-Approved in plaintext. volatile memory. DRBG. Output during TLS Modules’ public key negotiation for CAC can be imported from authentication a back-up configuration. Exits in encrypted format when performing a module configuration backup. 23 There are separate RSA keypairs used for negotiating SSH and TLS sessions. TLS session negotiations can use 2048, 3072, and 4096-bit RSA keypairs; SSH session negotiations can only use 2048- bit RSA keypairs. Blue Coat ProxySG 600 Series Page 20 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Key Key Type Generation / Input Output Storage Zeroization Use 1024, 1536, 2048, Other entities’ public Never output Other entities’ public Other entities’ public 3072, and 4096-bits keys are sent to the keys reside on keys are cleared by module in plaintext. volatile memory. power cycle. Can be sent to the module as part of an X.509 certificate during CAC authentication. RSA Private Key 2048, 3072, and Internally generated Exits in encrypted Stored in encrypted Inaccessible by Negotiating TLS or 4096-bits via FIPS-Approved format when form on non-volatile zeroizing encrypting SSH sessions DRBG. performing a module memory MAK configuration Imported in encrypted backup. form via a secure TLS or SSH session Imported in plaintext via a directly attached cable to the serial port DH public key 2048-bits The module’s Public The module’s Public Stored in plaintext Rebooting the Negotiating TLS or key is internally key exits the module on volatile memory modules; Remove SSH sessions generated via FIPS- in plaintext. Power Approved DRBG; while public key of a peer enters the module in plaintext. DH private key 224-bits Internally generated Never exits the Stored in plaintext Rebooting the Negotiating TLS or via FIPS-Approved module on volatile memory modules; Remove SSH sessions DRBG Power Blue Coat ProxySG 600 Series Page 21 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Key Key Type Generation / Input Output Storage Zeroization Use TLS or SSH Session AES CBC 128-, or Internally generated Output in encrypted Stored in plaintext Rebooting the Encrypting TLS or Key 256-bit key via FIPS-Approved form during TLS or on volatile memory modules; Remove SSH data DRBG. SSH protocol Power 3DES CBC keying handshake option 1 (3 different keys) TLS or SSH Session HMAC SHA-1 key Internally generated Never exits the Resides in volatile Rebooting the Data authentication Authentication Key module memory in plaintext modules; Remove for TLS or SSH Power sessions Crypto-Officer Minimum of eight Externally generated. Exits in encrypted Stored in encrypted Inaccessible by Locally Password (8) and maximum of Enters the module in form via a secure form on non-volatile zeroizing the authenticating a CO 64 bytes long encrypted form via a TLS session for memory. encrypting MAK or User for User Password printable character secure TLS or SSH external Management string session authentication. Console or CLI Enters the module in Exits in encrypted plaintext via a directly format when attached cable to the performing a module serial port configuration backup. “Enabled” mode Minimum of eight Enters the module in Exits in encrypted Stored in encrypted Inaccessible by Used by the CO to password (8) and maximum of encrypted form via a form via a secure form on non-volatile zeroizing the enter the 64 bytes long secure SSH session. TLS session for memory. encrypting MAK. “privileged” or printable character external “enabled” mode string Enters the module in authentication. when using the CLI. plaintext via a directly attached cable to the Exits in encrypted serial port. format when performing a module configuration backup. Blue Coat ProxySG 600 Series Page 22 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Key Key Type Generation / Input Output Storage Zeroization Use “Setup” Password Minimum of four (4) Enters the module in Never exits the Stored in encrypted Inaccessible by Used by the CO to and maximum of 64 plaintext via a directly module. form on non-volatile zeroizing the secure access to the bytes long printable attached cable to the memory. encrypting MAK. CLI when accessed character string. serial port. over the serial port. SNMP Privacy Key AES CFB 128 -bit Externally generated, Exits the module Stored in encrypted Inaccessible by Encrypting SNMPv3 key Imported in encrypted encrypted over TLS form on non-volatile zeroizing the packets. form via a secure TLS or encrypted during memory encrypting MAK or SSH session a configuration backup. Imported in plaintext via a directly attached cable to the serial port SNMP HMAC-SHA-1-96 – Externally generated, Exits the module Stored in encrypted Inaccessible by Authenticating Authentication Key bit key Imported in encrypted encrypted over TLS form on non-volatile zeroizing the SNMPv3 packets. form via a secure TLS or encrypted during memory encrypting MAK or SSH session a configuration backup. Imported in plaintext via a directly attached cable to the serial port Blue Coat ProxySG 600 Series Page 23 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Key Key Type Generation / Input Output Storage Zeroization Use SP 800-90A 384-bit random Internally generated Never exits the Plaintext in volatile Rebooting the Seeding material for CTR_DRBG Seed number module memory modules; Remove the SP800-90A Power CTR_DRBG SP 800-90A 256-bit random Internally generated Never exits the Plaintext in volatile Rebooting the Entropy material for CTR_DRBG number with module memory modules; Remove the SP800-90A Entropy24 derivation function Power CTR_DRBG 384-bit random number without derivation function SP 800-90A Internal state value Internally generated Never Plaintext in volatile Rebooting the Used for the SP 800- CTR_DRBG key memory modules; Remove 90A CTR_DRBG value Power SP 800-90A Internal state value Internally generated Never exits the Plaintext in volatile Rebooting the Used for the SP 800- CTR_DRBG V value module memory modules; Remove 90A CTR_DRBG Power NOTE: that some algorithms may be classified as deprecated, restricted, or legacy-use. Please consult NIST SP 800-131A for details. Keys and passwords that exit the module during a configuration backup are encrypted using a FIPS-Approved encryption algorithm. During the backup process, the CO must select the encryption algorithm to use: AES-128 CBC mode, or AES-256 CBC mode. 24 The Entropy required by the FIPS-Approved SP 800-90 CTR_DRBG (with AES-256) is supplied by the NDRNG Blue Coat ProxySG 600 Series Page 24 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 2.8 Self-Tests If any of the hardware accelerator cards self-tests fail, then the module forces the corresponding card to enter an error state, logs the error to a file, and shuts down the card. The modules will only use the cryptographic implementations found in the firmware. If any of the firmware self-tests fail, an error is printed to the CLI (when being accessed via the serial port). When this error occurs, the modules halt operation and provide no functionality. The only way to clear the error and resume normal operation is for the Crypto-Officer to reboot the modules. The status output provided below is shown only over the CLI (when being accessed via the serial port). ********************** SYSTEM ERROR *********************** The SG Appliance has failed the FIPS Self test. System startup cannot continue. ****************** SYSTEM STARTUP HALTED ***************** E)xit FIPS mode and reinitialize system R)estart and retry FIPS self-test Selection: The sections below describe the self-tests performed by the module. 2.8.1 Power-Up Self-Tests The SG600 performs the following self-tests using the OpenSSL firmware implementation at power-up:  Firmware integrity check using an EDC (32-bit CRC)  Known Answer Tests (KATs) o AES encrypt and decrypt KAT o 3DES encrypt and decrypt KAT o RSA digital signature generation KAT o RSA digital signature verification KAT o RSA wrap/unwrap KAT o SHA-1, SHA-224, SHA-256, SHA-384, and SHA-512 KATs o HMAC KAT with SHA-1, SHA-224, SHA-256, SHA-384, and SHA-512 KATs o DRBG KAT Upon successful completion of the firmware implementation self-tests, the SG600 performs the following self-tests on the hardware accelerator card:  AES-CBC KAT  3DES-CBC KAT If the hardware accelerator card self-tests pass, further execution of these algorithms will take place in the hardware implementation. If the hardware accelerator card self-tests fail, all algorithm execution will occur exclusively in the firmware implementation. No data output occurs via the data output interface until all power-up self tests including the hardware accelerator card power-up self-tests have completed. 2.8.2 Conditional Self-Tests The SG600 performs the conditional self-tests in Table 14 (only on its firmware implementation of OpenSSL). Blue Coat ProxySG 600 Series Page 25 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Table 14 SG600 Conditional Self-Tests Conditional Self-Test Occurrence Firmware load (RSA sign/verify) test This test is run when the firmware is loaded. An RSA digital signature verification is performed over the firmware. If the verification succeeds, the test succeeds; otherwise it fails. RSA pairwise consistency test This test is run upon generation of an RSA key pair for key transport. The public key is used to wrap a block of data, and the resultant ciphertext is compared with the original data. If they are the same, the test fails. If they differ, then the private key is used to unwrap the ciphertext, and the resultant plaintext is compared to the original data. If they are the same, the test passes. Otherwise, it is failed. Continuous RNG Test (CRNGT) for the This test is run upon generation of FIPS-Approved DRBG random data by the DRBG to detect failure to a constant value. CRNGT for the non-Approved NDRNG This test is run when the DRBG is requesting entropy. When entropy has been gathered, this test compares the collected entropy with the previously collected entropy. If they are equal, the test fails. If they differ, the newly collected entropy is returned to be used by the DRBG. 2.8.3 Critical Function Tests The SG600 performs the SP800-90A DRBG Critical Function tests in Table 15 (only on its firmware implementation of OpenSSL). Blue Coat ProxySG 600 Series Page 26 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Table 15 List of Critical Function Tests Conditional Test Occurrence SP 800-90A DRBG Instantiate Test Done before the instantiation of a new DRBG. The DRBG instantiation algorithm is sent fixed values of entropy, nonce, and personalization string. The output is compared with the value that was expected. If the values match, the test passes. Otherwise, it fails. Error testing is done by forcing an error upon the algorithm. If the algorithm handles the error as expected, the test passes. Otherwise, it fails SP 800-90A DRBG Generate Test Done before the first use of the DRBG. The DRBG Generate function tests both the Instantiate and Reseed algorithms. KATs are performed for each security strength supported and for each prediction resistance (if supported). The number of bits requested, additional input (if supported), working internal state, are supplied to the Generate function. If the values used during the test produce the expected results and the errors are handled as expected, the test passes. Otherwise, it fails. SP 800-90A DRBG Reseed Test Done before reseeding the DRBG instantiation function (w/o prediction resistance) or before the generation of a new random number (w/ prediction resistance). The DRBG reseed algorithm is sent fixed values of entropy and the internal state value, V. The output is compared with the value that was expected. If the values match, the test passes. Otherwise, it fails. Error testing is done by forcing an error upon the algorithm. If the algorithm handles the error as expected, the test passes. Otherwise, it fails SP 800-90A DRBG Uninstantiate Test This test is performed whenever the Instantiate, Generate, or Reseed tests are executed. It demonstrates that error handling is performed correctly and zeroizes the internal state 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. Blue Coat ProxySG 600 Series Page 27 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 3 Secure Operation The SG600 meets Level 2 requirements for FIPS 140-2. The sections below describe how to place and keep the module in Approved mode of operation. 3.1 Initial Setup Before powering-up the module, the CO must ensure that the required tamper-evident labels (included in the FIPS security kit) are correctly applied to the enclosure. The FIPS security kit (Part Number: 085- 02762) consists of the following items as shown below in Figure 4. Figure 4 FIPS Security Kit Contents Note: There are six (6) ‘Short Labels’ included; however, only three (3) are required for FIPS compliance. There are three additional labels provided. A hard copy of the guidance found below in section 3.1.1.2 is also included in the kit in a documents titled ProxySG 600 Series, FIPS Compliance Guide: Tamper Evident Panel and Label Installation, Rev B.0. 3.1.1 Label and Baffle Installation Instructions The Crypto-Officer is responsible for installing the baffle (security panel) and applying the tamper-evident labels at the client’s deployment site to ensure full FIPS 140-2 compliance. Once the seals have been applied, the Crypto Officer must develop an inspection schedule to verify that the external enclosure of the module and the tamper seals have not been damaged or tampered with in any way. If the Crypto-Officer detects evidence of tampering or damage to the labels, the Crypto-Officer must return to the module to the uninitialized factory state, remove and reapply all labels per section 3.1.1.2, and must complete the first- time configuration in order to operate in its FIPS-Approved mode as detailed in section 3.2.1. The Crypto- Officer is responsible for securing and having control at all times of any unused labels. The Crypto-Officer is responsible for the direct control and observation of any changes to the module such as reconfigurations where the tamper-evident labels or security appliances are removed or installed to ensure the security of the module is maintained during such changes and the module is returned to a FIPS Approved state. Crypto-Officers must adhere to the following when applying the tamper-evident labels:  The minimum temperature of the environment must be 35-degrees Fahrenheit. After application, the labels’ acceptable temperature in the operational environment is -5-degrees to 158-degrees Fahrenheit. Blue Coat ProxySG 600 Series Page 28 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014  Do not touch the adhesive side of the label. This disrupts the integrity of the adhesive. If a label is removed from a surface, the image is destroyed and the label leaves tamper-evident text as evidence. If you accidently touch the adhesive side, discard that label and apply another one.  Label application tips: o Apply skin moisturizer on your fingers before handling. o Use a rubber finger tip to partially remove the label from its backing.  After applying the labels, allow at least 24 hours for the label adhesive to cure. 3.1.1.1 Baffle Installation 1. The rear baffle and PCI cover (ProxySG 600 Security Panel and ProxySG 600 PCI Cover Security Panel respectively as shown in Figure 4) are designed to prevent unauthorized access to key system components by shielding the rear ventilation outlets. 2. To install the rear baffle, align the security panel mounting points against the screw locations shown below in Figure 5 with seven (7) flat-head screws. Figure 5 Rear Baffle Installation 3. Install the PCI cover as shown in Figure 6. To install the PCI cover, you must: Blue Coat ProxySG 600 Series Page 29 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Figure 6 PCI Cover Installation a. Remove the chassis cover from the appliance b. Remove the PCI slot plate by supporting it using one hand and removing both screws. c. Align the PCI slot plate against the chassis interior and install the PCI cover using two screws. d. Reinstall the appliance cover. 3.1.1.2 Label Installation The tamper-evident labels are applied over key areas of the chassis to provide tamper-evident security. If the labels are removed after being affixed to a surface, the image self-destructs and leaves a text pattern on the label. Figure 7 below illustrates the tamper-evident features of the label. Figure 7 Label Showing Tamper Evidence 1. Use alcohol swabs to clean the label location surface using Isopropyl Alcohol (99%); this ensures complete adhesion. Verify that all the surfaces are dry before applying the labels. 2. Set the appliance on a flat, slip-proof work space and make sure you have access to all sides of the appliance. 3. Apply one (1) label vertically over a section of the rear baffle, across the center of the PCI cover, and over the top edge of the appliance as shown below in Figure 8. Blue Coat ProxySG 600 Series Page 30 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Figure 8 Tamper-Evident Label Placement over the PCI Cover 4. Apply two (2) labels to the rear baffle on the left side of the appliance as shown below in Figure 9.  Apply one (1) label vertically over the upper-left (when looking from the rear of the appliance) flush mount hexagonal insert and the rear baffle. Make sure the label does not interfere with any of the vents; the remaining label material crosses over the top edge of the appliance.  Apply one (1) label vertically over the lower-left corner of the rear baffle. The label should cover the bottom 2 rows, across two columns of ventilation holes. The remaining label material crosses over the bottom edge of the appliance Figure 9 Tamper-Evident Label Placement on Left Rear of Appliance 5. Rack mount the appliance being cautious not to damage the labels during the mounting process. Blue Coat ProxySG 600 Series Page 31 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 6. Reinstall the power cables. 7. Reinstall the network cables 8. Power-on the appliance. 3.2 Secure Management 3.2.1 Initialization The module is delivered in an uninitialized factory state, and requires minimal first-time configuration in order to operate in its FIPS-Approved mode and be accessed by a web browser. Physical access to the module shall be limited to the Crypto-Officer, and the CO shall be responsible for putting the module into the Approved mode. The process of establishing the initial configuration via a secure serial port is described below. Connect a serial cable to a serial port on a PC and to the module’s serial port. Open a terminal 1. emulator (such as HyperTerminal) on the PC, and connect to the serial port to which you attached the cable. Create and name a new connection (either a COM or TCP/IP), using the port parameters provided in Table 16. Table 16 RS-232 Parameters RS-232C Parameter Parameter Setting Baud rate 9600 bps Data bits 8 Parity None Stop bits 1 Flow control None 2. Power on the module and wait for the system to finish booting. Press three times. When the “Welcome to the SG Appliance Setup Console” prompt appears, 3. the system is ready for the first-time network configuration. 4. Set up the first time configuration by entering the interface number, IP address, IP subnet mask, IP gateway, DNS server parameters, username, and password. Press to confirm the configuration when the “Successful Configuration Setup” prompt 5. appears. 6. Repeat step 3. 7. Selection option #1 for the Command Line Interface. This option takes you immediately to the Admin prompt. Blue Coat ProxySG 600 Series Page 32 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 The Crypto-Officer shall enter the “enabled” mode on the CLI by typing the ‘enable’ command 8. followed by the ‘enable’ password. The prompt will change from ‘>’ to ‘#’ signifying the Crypto-Officer is in the ‘enabled’ mode. Type 9. the command ‘fips-mode enable.’ When prompted for confirmation, elect ‘y’ to confirm. Once the reinitialization is complete, the module will display the prompt “The system is in FIPS mode.”  NOTE 1: The entry of the “fips-mode enable” command causes the device to power cycle, zeroizing the Master Appliance Key and returning the configuration values set in steps 1 and 2 to their factory state.  NOTE 2: This command is only accepted via the CLI when accessed over the serial port. 10. Wait for the system to finish rebooting. Repeat step 3. 11. Repeat step 4. 12. The module will prompt for the ‘enabled’ mode password: You must configure the console user account now. Enter console username: Enter console password: Enter enable password: 13. Configure the setup password to secure the serial port which must be configured while in FIPS mode. The module will prompt the following: The serial port must be secured and a setup password must be configured. Enter setup password: 14. The module will prompt to restrict workstation access. Choose “Yes” or “No.” 15. Finally, select the licensing mode. The module will prompt with the following options: M)ACH5 Edition P)roxy Edition Upon completion of these initialization steps, the module is considered to be operating in its Approved mode of operation. 3.2.2 Management The Crypto-Officer is able to monitor and configure the module via the Management Console (HTTPS over TLS) and the CLI (serial port or SSH). The Crypto-Officer should monitor the module’s status regularly. If any irregular activity is noticed or the module is consistently reporting errors, customers should consult Blue Coat Systems Blue Touch Online (BTO) and the administrative guidance documents to resolve the issues. If the problems cannot be resolved through these resources, Blue Coat Systems customer support should be contacted. Blue Coat ProxySG 600 Series Page 33 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 The CO must ensure that localized keys used for SNMPv3 authentication and privacy match the key type requirements specified in Table 13. Key sizes less than what is specified shall not be used. The CO password and “enabled” mode password must be at least 8 characters in length. The “Setup” password must be at least 4 characters in length. When creating or importing key pairs, such as during the restoration of an archived SG600 configuration, the CO must ensure that the “Do not show key pair” option is selected in the Management Console as shown in Figure 10, or the “no-show” argument is passed over the CLI as shown in Figure 11. Please see Section E: Preparing Archives for Restoration on New Devices in the Blue Coat Systems SGOS Administration Guide, Version 6.5 for further reference. Figure 10 Keyring Creation Management Console Dialogue Box Figure 11 Keyring Creation CLI Commands 3.2.3 Zeroization The CO can return the module to its factory state by entering the “enabled” mode on the CLI, followed by the “fips-mode disable” command. This command will automatically reboot the module and zeroize the MAK. The RSA private key, Crypto-Officer password, User password, “Enabled” mode password, “Setup” password, SNMP Privacy key, and the SNMP Authentication key are all stored encrypted by the MAK. Once the MAK is zeroized, decryption involving the MAK becomes impossible, making these CSPs unobtainable by an attacker. In addition, rebooting the module causes all temporary keys stored in volatile memory (SSH Session key, TLS session key, DRBG entropy values, and NDRNG entropy values) to be zeroized. The Crypto-Officer must wait until the module has successfully rebooted in order to verify that zeroization has completed. Blue Coat ProxySG 600 Series Page 34 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 3.3 User Guidance The User is only able to access the module remotely via SSH (CLI) or HTTPS (Management Console). The User must change his or her password at the initial login. The User must be diligent to pick strong passwords (alphanumeric with minimum 8 characters) that will not be easily guessed, and must not reveal their password to anyone. Additionally, the User should be careful to protect any secret/private keys in their possession, such as TLS or SSH session keys. The User should report to the Crypto-Officer if any irregular activity is noticed. 3.4 Non-Approved Mode When initialized and configured according to the Crypto-Officer guidance in this Security Policy, the module does not support a non-Approved mode of operation. Blue Coat ProxySG 600 Series Page 35 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 4 Acronyms This section describes the acronyms used throughout this document. Table 17 Acronyms Acronym Definition AD Active Directory AES Advanced Encryption Standard BTO BlueTouch Online CA Certificate Authority CAC Common Access Card CBC Cipher Block Chaining CFB Cipher Feedback CIFS Common Internet File System CLI Command Line Interface CMVP Cryptographic Module Validation Program CN Common Name CO Crypto-Officer CRNGT Continuous Random Number Generator Test CSE Communications Security Establishment CSP Critical Security Parameter CX4 Four pairs of twin-axial copper wiring DES Data Encryption Standard DNS Domain Name System DoD Department of Defense DRBG Deterministic Random Bit Generator ECB Electronic Codebook EDC Error Detection Code EMC Electromagnetic Compatibility EMI Electromagnetic Interference FIPS Federal Information Processing Standard FTP File Transfer Protocol HAC Hardware Accelerator Card HDS HTTP Dynamic Streaming HLS HTTP Live Streaming Blue Coat ProxySG 600 Series Page 36 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Acronym Definition HMAC Hash-Based Message Authentication Code HSPD Homeland Security Presidential Directive HTTP Hypertext Transfer Protocol HTTPS Secure Hypertext Transfer Protocol IM Instant Messaging IMAP Internet Message Access Protocol IP Internet Protocol KAT Known Answer Test LCD Liquid Crystal Display LED Light Emitting Diode MAC Message Authentication Code MD5 Message Digest v5 NIC Network Interface Card NIST National Institute of Standards and Technology OFB Output Feedback OS Operating System P2P Peer-to-Peer PC Personal Computer PCI-e Peripheral Component Interconnect Express PIN Personal Identification Number PIV Personal Identity Verification PN Principle Name POP3 Post Office Protocol version 3 RS-232 Recommended Standard 232 RSA Rivest Shamir Adleman RTMP Real-Time Messaging Protocol RTSP Real-Time Streaming Protocol SFTP Secure File Transfer Protocol SGOS Secure Gateway Operating System SHA Secure Hash Algorithm SMTP Simple Mail Transfer Protocol SNMP Simple Network Management Protocol SOCKS SOCKet Secure SSH Secure Shell Blue Coat ProxySG 600 Series Page 37 of 39 © 2014 Blue Coat Systems, Inc. This document may be freely reproduced and distributed whole and intact including this copyright notice. ProxySG 600 Series Security Policy, Version 0.7 May 29, 2014 Acronym Definition SSL Secure Sockets Layer TCP Transmission Control Protocol TLS Transport Layer Security UPN User Principle Name USB Universal Serial Bus VoIP Voice Over Internet Protocol WAN Wide Area Network Blue Coat ProxySG 600 Series Page 38 of 39 © 2014 Blue Coat Systems, 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, VA 22033 United States of America Phone: +1 703 267 6050 Email: info@corsec.com http://www.corsec.com