PA-200, PA-500, PA-2000 Series, PA-3000 Series, PA-4000 Series, and PA-5000 Series Firewalls Non-Proprietary Security Policy             Version: L Palo Alto Networks Revision Date: 8/4/2014 www.paloaltonetworks.com © 2014 Palo Alto Networks. May be reproduced only in its original entirety (without revision). Palo Alto Networks, PAN-OS, and Panorama are trademarks of Palo Alto Networks, Inc. All other trademarks are the property of their respective owners. P/N 880-000018-00L Palo Alto Networks 880-000018-00L Change Record Table 1 - Change Record Revision Date Author Description of Change A 8/23/2010 N. Campagna Initial authoring Added detail to the identity and authentication of B 1/24/2011 N. Campagna IPSec endpoints. C 5/31/2011 N. Campagna Added FW Version 3.1.7-h1 Added PA-5000 Series and updated firmware D 6/15/2011 N. Campagna version Updates related to FW Version 4.0.10, TLS, E 3/9/2012 Jake Bajic SSHv2, IPSec/IKEv1 and RSA F 4/20/2012 Jake Bajic Updated algorithms certificate numbers G 6/7/2012 Jake Bajic Minor updates H 1/2/2013 Jake Bajic Addressing CMVP comments I 7/29/13 Jake Bajic Updated with new production part numbers Updates related to PAN-OS 5.0.8, added PA-200 J 9/17/13 Jake Bajic and PA-3000 Series K 1/15/14 Jake Bajic Updates PAN-OS 5.0.11 Added additional PA-200 and PA-3000 Series L 8/4/2014 Richard Bishop information and minor edits Palo Alto Networks Firewall Security Policy Page 2 of 72 Palo Alto Networks 880-000018-00L Contents 1 Module Overview ............................................................................................................................................ 6 2 Security Level ................................................................................................................................................ 18 3 Modes of Operation ....................................................................................................................................... 19 3.1 FIPS Approved Mode of Operation...................................................................................................................... 19 3.2 Approved and Allowed Algorithms....................................................................................................................... 20 3.3 Non-Approved, Non-Allowed Algorithms ............................................................................................................. 21 4 Ports and Interfaces ........................................................................................................................................ 22 5 Identification and Authentication Policy ....................................................................................................... 26 5.1 Assumption of Roles ............................................................................................................................................. 26 6 Access Control Policy .................................................................................................................................... 28 6.1 Roles and Services................................................................................................................................................ 28 6.2 Unauthenticated Services ..................................................................................................................................... 29 6.3 Definition of Critical Security Parameters (CSPs) .............................................................................................. 29 6.4 Definition of Public Keys ..................................................................................................................................... 31 6.5 Definition of CSPs Modes of Access .................................................................................................................... 32 7 Operational Environment ............................................................................................................................... 33 8 Security Rules ................................................................................................................................................ 33 9 Physical Security Policy ................................................................................................................................ 35 9.1 Physical Security Mechanisms ............................................................................................................................. 35 9.2 Operator Required Actions .................................................................................................................................. 45 10 Mitigation of Other Attacks Policy ................................................................................................................ 46 11 References...................................................................................................................................................... 46 12 Definitions and Acronyms ............................................................................................................................. 46 13 Appendix A - PA-200 - FIPS Accessories/Tamper Seal Installation (5 Seals) ............................................. 48 14 Appendix B - PA-500 - FIPS Accessories/Tamper Seal Installation (12 Seals)............................................ 51 15 Appendix C - PA-2000 Series - FIPS Accessories/Tamper Seal Installation (10 Seals) ............................... 58 16 Appendix D - PA-3000 Series - FIPS Accessories/Tamper Seal Installation (7 Seals) ................................. 62 17 Appendix E - PA-4000 Series – FIPS Accessories/Tamper Seal Installation (10 Seals) .............................. 65 18 Appendix F - PA-5000 Series - FIPS Accessories/Tamper Seal Installation (17 Seals) ............................... 70 Palo Alto Networks Firewall Security Policy Page 3 of 72 Palo Alto Networks 880-000018-00L Tables Table 1 - Change Record ......................................................................................................................................... 2 Table 2 - Validated Version Information ............................................................................................................... 16 Table 3 - Module Security Level Specification ..................................................................................................... 18 Table 4 - FIPS Approved Algorithms Used in Current Module ............................................................................ 20 Table 5 - FIPS Allowed Algorithms Used in Current Module .............................................................................. 20 Table 6 - Supported Protocols in FIPS Approved Mode ....................................................................................... 20 Table 7 - Non-Approved, Non-Allowed Algorithms Used in Current Module ..................................................... 21 Table 8 - PA-200 FIPS 140-2 Ports and Interfaces ................................................................................................ 22 Table 9 - PA-500 FIPS 140-2 Ports and Interfaces ................................................................................................ 22 Table 10 - PA-2000 Series FIPS 140-2 Ports and Interfaces ................................................................................. 23 Table 11 - PA-3000 Series FIPS 140-2 Ports and Interfaces ................................................................................. 23 Table 12 - PA-4000 Series FIPS 140-2 Ports and Interfaces ................................................................................. 24 Table 13 - PA-5000 Series FIPS 140-2 Ports and Interfaces ................................................................................. 24 Table 14 - Roles and Required Identification and Authentication ......................................................................... 26 Table 15 - Strengths of Authentication Mechanisms ............................................................................................. 27 Table 16 - Authenticated Service Descriptions ...................................................................................................... 28 Table 17 - Authenticated Services ......................................................................................................................... 28 Table 18 - Unauthenticated Services ..................................................................................................................... 29 Table 19 - Private Keys and CSPs ......................................................................................................................... 29 Table 20 - Public Keys ........................................................................................................................................... 31 Table 21 - CSP Access Rights within Roles & Services ....................................................................................... 32 Table 22 - Inspection/Testing of Physical Security Mechanisms .......................................................................... 45 Figures Figure 1 - PA-200 Front Image ................................................................................................................................ 8 Figure 2 - PA-200 Back Image ................................................................................................................................ 8 Figure 3 - PA-200 with Front Opacity Shield and Cage Enclosure ......................................................................... 8 Figure 4 - PA-500 Front Image ................................................................................................................................ 9 Figure 5 - PA-500 Back Image ................................................................................................................................ 9 Figure 6 - PA-500 with Front Opacity Shield .......................................................................................................... 9 Figure 7 - PA-500 with Side Opacity Shield ........................................................................................................... 9 Figure 8 - PA-2020 / PA-2050 Front Images ......................................................................................................... 10 Figure 9 - PA-2020 / PA-2050 Back Image ........................................................................................................... 10 Figure 10 - PA-2020 / PA-2050 Front Opacity Shield .......................................................................................... 11 Figure 11 - PA-2020 / PA-2050 with Side Opacity Shield .................................................................................... 11 Figure 12 - PA-3020 / PA-3050 Front Images ....................................................................................................... 11 Figure 13 - PA-3020 / PA-3050 Back Image ......................................................................................................... 12 Figure 14 - PA-3020 / PA-3050 Opacity Shield .................................................................................................... 12 Palo Alto Networks Firewall Security Policy Page 4 of 72 Palo Alto Networks 880-000018-00L Figure 15 - PA-3020 / PA-3050 side with Opacity Shield..................................................................................... 12 Figure 16 - PA-4020 / PA-4050 Front Image ........................................................................................................ 13 Figure 17 - PA-4060 Front Image .......................................................................................................................... 13 Figure 18 - PA-4020 / PA-4050 / PA-4060 Back Image ....................................................................................... 13 Figure 19 - PA-4020 / PA-4050 / PA-4060 Left Side with Opacity Shield ........................................................... 14 Figure 20 - PA-5020 Front Image .......................................................................................................................... 14 Figure 21 - PA-5050/PA-5060 Front Image .......................................................................................................... 14 Figure 22 - PA-5000 Series Back Image ............................................................................................................... 15 Figure 23 - PA-5000 Series Left Side with front Opacity Shield .......................................................................... 15 Figure 24 - Logical Diagram .................................................................................................................................. 17 Figure 25 - PA-200 Left Side and Top Tamper Seal Placement (3) ...................................................................... 36 Figure 26 - PA-200 Right Side Tamper Seal Placement (2) .................................................................................. 36 Figure 27 - PA-500 Front Tamper Seal Placement (1) .......................................................................................... 37 Figure 28 - PA-500 Left Side Tamper Seal Placement (3) .................................................................................... 37 Figure 29 - PA-500 Right Side Tamper Seal Placement (2) .................................................................................. 37 Figure 30 - PA-500 Rear Tamper Seal Placement (6) ........................................................................................... 38 Figure 31 - PA-2000 Series Front Tamper Seal Placement (1).............................................................................. 38 Figure 32 - PA-2000 Series Left Side Tamper Seal Placement (3) ....................................................................... 39 Figure 33 - PA-2000 Series Right Side Tamper Seal Placement (3) ..................................................................... 39 Figure 34 - PA-2000 Series Rear Tamper Seal Placement (3)............................................................................... 39 Figure 35 - PA-3000 Series Tamper Seal Placement (3) ....................................................................................... 40 Figure 36 - PA-3000 Series Tamper Seal Placement (2) ....................................................................................... 40 Figure 37 - PA-3000 Series Tamper Seal Placement (2) ....................................................................................... 41 Figure 38 - PA-4000 Series Rear Tamper Seal Placement – From Top (4)........................................................... 41 Figure 39 - PA-4000 Series Rear Side Tamper Seal Placement – From Underside (4)......................................... 41 Figure 40 - PA-4000 Series Right Side Tamper Seal Placement (1) ..................................................................... 42 Figure 41 - PA-4000 Series Left Side Tamper Seal Placement (1) ....................................................................... 42 Figure 42 - PA-5000 Series Rear Tamper Seal Placement (9)............................................................................... 43 Figure 43 - PA-5000 Series Right Side Tamper Seal Placement (4) ..................................................................... 43 Figure 44 - PA-5000 Series Left Side Tamper Seal Placement (4) ....................................................................... 44 Palo Alto Networks Firewall Security Policy Page 5 of 72 Palo Alto Networks 880-000018-00L 1 Module Overview Palo Alto Networks offers a full line of next-generation security appliances that range from the PA-200, designed for enterprise remote offices, to the PA-5000 series, which are designed for high-speed datacenters. Our platform architecture is based on our single-pass software, PAN-OS, for networking, security, threat prevention, and management functionality that is consistent across all platforms. The platforms differ only in capacities, performance, and physical configuration. The Palo Alto Networks PA-200, PA-500, PA-2000 Series, PA-3000 Series, PA-4000 Series, and PA- 5000 Series firewalls (hereafter referred to as the modules) are multi-chip standalone modules that provide network security by enabling enterprises to see and control applications, users, and content – not just ports, IP addresses, and packets – using three unique identification technologies: App- ID, User-ID, and Content-ID. These identification technologies, found in Palo Alto Networks' enterprise firewalls, enable enterprises to create business-relevant security policies – safely enabling organizations to adopt new applications, instead of the traditional “all-or-nothing” approach offered by traditional port-blocking firewalls used in many security infrastructures. Features and Benefits  Application visibility and control: Accurate identification of the applications traversing the network enables policy-based control over application usage at the firewall, the strategic center of the security infrastructure.  Visualization tools: Graphical visibility tools, customizable reporting and logging enables administrators to make a more informed decision on how to treat the applications traversing the network.  Application browser: Helps administrators quickly research what the application is, its’ behavioral characteristics and underlying technology resulting in a more informed decision making process on how to treat the application. User-based visibility and control: Seamless integration with enterprise directory services (Active  Directory, LDAP, eDirectory) facilitates application visibility and policy creation based on user and group information, not just IP address. In Citrix and terminal services environments, the identity of users sitting behind Citrix or terminal services can be used to enable policy-based visibility and control over applications, users and content. An XML API enables integration with other, 3rd party user repositories.  Real-time threat prevention: Detects and blocks application vulnerabilities, viruses, spyware, and worms; controls web activity; all in real-time, dramatically improving performance and accuracy.  File and data filtering: Taking full advantage of the in-depth application inspection being performed by App-ID, administrators can implement several different types of policies that reduce the risk associated with unauthorized file and data transfer.  Legacy firewall support: Support for traditional inbound and outbound port-based firewall rules mixed with application-based rules smooth the transition to a Palo Alto Networks next generation firewall. Networking architecture: Support for dynamic routing (OSPF, RIP, BGP), virtual wire mode and  layer 2/layer 3 modes facilitates deployment in nearly any networking environment. Palo Alto Networks Firewall Security Policy Page 6 of 72 Palo Alto Networks 880-000018-00L Policy-based Forwarding: Forward traffic based on policy defined by application, source  zone/interface, source/destination address, source user/group, and service. Virtual Systems: Create multiple virtual “firewalls” within a single device as a means of supporting  specific departments or customers. Each virtual system can include dedicated administrative accounts, interfaces, networking configuration, security zones, and policies for the associated network traffic.  VPN connectivity: Secure site-to-site connectivity is enabled through standards-based IPSec VPN support while remote user access is delivered via SSL VPN connectivity. Quality of Service (QoS): Deploy traffic shaping policies (guaranteed, maximum and priority) to  enable positive policy controls over bandwidth intensive, non-work related applications such as streaming media while preserving the performance of business applications. Real-time bandwidth monitor: View real-time bandwidth and session consumption for applications  and users within a selected QoS class. Purpose-built platform: combines single pass software with parallel processing hardware to deliver  the multi-Gbps performance necessary to protect today’s high speed networks. Palo Alto Networks Firewall Security Policy Page 7 of 72 Palo Alto Networks 880-000018-00L Note: Modules are shown in figures with no opacity shields included to demonstrate module interfaces and other physical characteristics. Pictures are also included of each chassis with the opacity shields in place. Figure 1 - PA-200 Front Image Figure 2 - PA-200 Back Image Figure 3 - PA-200 with Front Opacity Shield and Cage Enclosure Palo Alto Networks Firewall Security Policy Page 8 of 72 Palo Alto Networks 880-000018-00L Figure 4 - PA-500 Front Image Figure 5 - PA-500 Back Image Figure 6 - PA-500 with Front Opacity Shield Figure 7 - PA-500 with Side Opacity Shield Palo Alto Networks Firewall Security Policy Page 9 of 72 Palo Alto Networks 880-000018-00L Figure 8 - PA-2020 / PA-2050 Front Images Figure 9 - PA-2020 / PA-2050 Back Image Palo Alto Networks Firewall Security Policy Page 10 of 72 Palo Alto Networks 880-000018-00L Figure 10 - PA-2020 / PA-2050 Front Opacity Shield Figure 11 - PA-2020 / PA-2050 with Side Opacity Shield Figure 12 - PA-3020 / PA-3050 Front Images Palo Alto Networks Firewall Security Policy Page 11 of 72 Palo Alto Networks 880-000018-00L Figure 13 - PA-3020 / PA-3050 Back Image Figure 14 - PA-3020 / PA-3050 Opacity Shield Figure 15 - PA-3020 / PA-3050 side with Opacity Shield Palo Alto Networks Firewall Security Policy Page 12 of 72 Palo Alto Networks 880-000018-00L Figure 16 - PA-4020 / PA-4050 Front Image Figure 17 - PA-4060 Front Image Figure 18 - PA-4020 / PA-4050 / PA-4060 Back Image Palo Alto Networks Firewall Security Policy Page 13 of 72 Palo Alto Networks 880-000018-00L Figure 19 - PA-4020 / PA-4050 / PA-4060 Left Side with Opacity Shield Figure 20 - PA-5020 Front Image Figure 21 - PA-5050/PA-5060 Front Image Palo Alto Networks Firewall Security Policy Page 14 of 72 Palo Alto Networks 880-000018-00L Figure 22 - PA-5000 Series Back Image Figure 23 - PA-5000 Series Left Side with front Opacity Shield Palo Alto Networks Firewall Security Policy Page 15 of 72 Palo Alto Networks 880-000018-00L The configurations for this validation are: Table 2 - Validated Version Information Module Part Number Hardware FIPS Kit Part FIPS Kit Firmware Version Number Hardware Version Version PA-200 910-000015-00E Rev. E 920-000084-00A Rev. A 5.0.11 PA-500 910-000006-00O Rev. O 920-000005-00A Rev. A 5.0.11 PA-500-2GB 910-000094-00O Rev. O 920-000005-00A Rev. A 5.0.11 PA-2020 910-000004-00Z Rev. Z 920-000004-00A Rev. A 5.0.11 PA-2050 910-000003-00Z Rev. Z 920-000004-00A Rev. A 5.0.11 PA-3020 910-000017-00J Rev. J 920-000081-00A Rev. A 5.0.11 PA-3050 910-000016-00J Rev. J 920-000081-00A Rev. A 5.0.11 PA-4020 910-000002-00AB Rev. AB 920-000003-00A Rev. A 5.0.11 PA-4050 910-000001-00AB Rev. AB 920-000003-00A Rev. A 5.0.11 PA-4060 910-000005-00S Rev. S 920-000003-00A Rev. A 5.0.11 PA-5020 910-000010-00F Rev. F 920-000037-00A Rev. A 5.0.11 PA-5050 910-000009-00F Rev. F 920-000037-00A Rev. A 5.0.11 PA-5060 910-000008-00F Rev. F 920-000037-00A Rev. A 5.0.11 Palo Alto Networks Firewall Security Policy Page 16 of 72 Palo Alto Networks 880-000018-00L Figure 24 depicts the logical block diagram for the modules. The cryptographic boundary includes all of the logical components of the modules and the boundary is the physical enclosure of the firewall. Figure 24 - Logical Diagram Palo Alto Networks Firewall Security Policy Page 17 of 72 Palo Alto Networks 880-000018-00L 2 Security Level The cryptographic modules meet the overall requirements applicable to Level 2 security of FIPS 140-2. Table 3 - Module Security Level Specification Security Requirements Section Level Cryptographic Module Specification 3 Module Ports and Interfaces 2 Roles, Services and Authentication 3 Finite State Model 2 Physical Security 2 Operational Environment N/A Cryptographic Key Management 2 EMI/EMC 2 Self-Tests 2 Design Assurance 3 Mitigation of Other Attacks N/A Palo Alto Networks Firewall Security Policy Page 18 of 72 Palo Alto Networks 880-000018-00L 3 Modes of Operation 3.1 FIPS Approved Mode of Operation The modules support both a CC mode (FIPS mode) and a non-CC mode. The following procedure will put the modules into the FIPS-approved mode of operation:  Install FIPS kit opacity shields and tamper evidence seals according to Section 9.  The tamper evidence seals and opacity shields shall be installed for the module to operate in a FIPS Approved mode of operation.  During initial boot up, break the boot sequence via the console port connection (by pressing the maint button when instructed to do so) to access the main menu.  Select “Continue.”  Select the “Set CCEAL4 Mode” option to enter CC mode.  Select “Enable CCEAL4 Mode”.  When prompted, select “Reboot” and the module will re-initialize and continue into CC mode (FIPS mode).  The module will reboot.  In CC mode, the console port is available only as a status output port. The module will automatically indicate the FIPS Approved mode of operation in the following manner:  Status output interface will indicate “**** CCEAL4 MODE ENABLED ****” via the CLI session.  Status output interface will indicate “CCEAL4 mode enabled successfully” via the console port.  The module will display “CC” at all times in the status bar at the bottom of the web interface. Should one or more power-up self-tests fail, the FIPS Approved mode of operation will not be achieved. Feedback will consist of:  The module will output “CC EAL4 failure”  The module will reboot and enter a state in which the reason for the reboot can be determined.  To determine which self-test caused the system to reboot into the error state, connect the console cable and follow the on-screen instructions to view the self-test output. Palo Alto Networks Firewall Security Policy Page 19 of 72 Palo Alto Networks 880-000018-00L 3.2 Approved and Allowed Algorithms The cryptographic modules support the following FIPS Approved algorithms. Table 4 - FIPS Approved Algorithms Used in Current Module FIPS Approved Algorithm CAVP Cert. # AES: 2728 - ECB, CBC, CFB, OFB modes; Encrypt/Decrypt; 128, 192 and 256-bit - CTR mode; 128-bit FIPS 186-4 RSA: 1420 - Key Generation: 2048 and 3072-bit - Signature Generation: 2048 and 3072-bit - Signature Verification: 1024, 2048 and 3072-bit HMAC-SHA-1, HMAC-SHA-256 1707 SHA-1, SHA-256, SHA-384, SHA-512 2298 ANSI X9.31 RNG 1263 SP 800-135 KDF – TLS, SNMP, SSH, IKEv1 227 (CVL) The cryptographic modules support the following non-FIPS Approved algorithms that are allowed for use in CC (FIPS) mode. Table 5 - FIPS Allowed Algorithms Used in Current Module FIPS Allowed Algorithm Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength) RSA (key wrapping, key establishment methodology provides 112 bits of encryption strength) NDRNG (used to seed ANSI X9.31 RNG) MD5 (within TLS) Table 6 - Supported Protocols in FIPS Approved Mode Supported Protocols TLS SSHv2 IPSec/IKEv1 SNMP Palo Alto Networks Firewall Security Policy Page 20 of 72 Palo Alto Networks 880-000018-00L 3.3 Non-Approved, Non-Allowed Algorithms The cryptographic modules support the following non-Approved algorithms. No security claim is made in the current modules for any of the following non-Approved algorithms. Table 7 - Non-Approved, Non-Allowed Algorithms Used in Current Module Non-FIPS Allowed Algorithms in Non-FIPS Mode MD5 – used for hashing of non-security relevant data; in CHAP authentication with RADIUS servers; in authentication for OSPF, RIP, and BGP dynamic routing protocols; for password hashing on Data Leakage Protection and Administrator passwords; and to integrity check URL filtering database downloads (note this is in addition to HMAC-SHA-1 authentication/integrity check). MD5 is also used to authenticate communications with the security module. MD5 is also used to hash administrator passwords. RC4 – used to encrypt SSL communications with the security module. Camellia - used to encrypt SSL communications with the security module. RC2 - used to encrypt SSL communications with the security module. SEED - used to encrypt SSL communications with the security module. DES - used to encrypt SSL communications with the security module. Palo Alto Networks Firewall Security Policy Page 21 of 72 Palo Alto Networks 880-000018-00L 4 Ports and Interfaces The modules are multi-chip standalone modules with ports and interfaces as shown below. Table 8 - PA-200 FIPS 140-2 Ports and Interfaces Interface PA-200 FIPS 140-2 Designation Name and Description Qty RJ45 1 Data input, control input, data Console port output, status output RJ45 1 Data input, control input, data Out of band management output, status output RJ45 4 Data input, control input, data 10/100/1000 Ethernet interface output, status output DC-12V 1 Power input Power interface LEDs 6 Status output Status indicators USB 1 Disabled except for power Used in manufacturing Table 9 - PA-500 FIPS 140-2 Ports and Interfaces Interface PA-500 FIPS 140-2 Designation Name and Description Qty RJ45 1 Data input, control input, data Console port output, status output RJ45 1 Data input, control input, data Out of band management output, status output RJ45 8 Data input, control input, data 10/100/1000 Ethernet interface output, status output 100-240 1 Power input Power interface Vcc LEDs 6 Status output Status indicators USB 1 Disabled except for power Used in manufacturing Palo Alto Networks Firewall Security Policy Page 22 of 72 Palo Alto Networks 880-000018-00L Table 10 - PA-2000 Series FIPS 140-2 Ports and Interfaces Interface PA-2050 PA-2020 FIPS 140-2 Designation Name and Description Qty Qty RJ45 1 1 Data input, control input, Console port data output, status output RJ45 1 1 Data input, control input, Out of band management data output, status output SFP 4 2 Data input, control input, Ethernet optical gigabit interface data output, status output RJ45 16 12 Data input, control input, 10/100/1000 Ethernet interface data output, status output 100-240 1 1 Power input Power interface Vcc LEDs 6 6 Status output Status indicators USB 1 1 Disabled except for Used in manufacturing power Table 11 - PA-3000 Series FIPS 140-2 Ports and Interfaces Interface PA-3050 PA3020 FIPS 140-2 Designation Name and Description Qty Qty RJ45 1 1 Data input, control input, Console port data output, status output RJ45 1 1 Data input, control input, Out of band management data output, status output RJ45 2 2 Data input, control input, 10/100/1000 HA Ethernet interface data output, status output SFP 8 8 Data input, control input, Ethernet optical gigabit interface data output, status output RJ45 12 12 Data input, control input, 10/100/1000 Ethernet interface data output, status output 100-240 1 1 Power input Power interface Vcc LEDs 6 6 Status output Status indicators USB 1 1 Disabled except for power Used in manufacturing Palo Alto Networks Firewall Security Policy Page 23 of 72 Palo Alto Networks 880-000018-00L Table 12 - PA-4000 Series FIPS 140-2 Ports and Interfaces Interface PA-4060 PA-4050 PA-4020 FIPS 140-2 Designation Name and Qty Qty Qty Description DB9 1 1 1 Data input, control input, Console port data output, status output RJ45 1 1 1 Data input, control input, Out of band data output, status output management XFP 4 0 0 Data input, control input, Ethernet optical 10- data output, status output gigabit interface SFP 4 8 8 Data input, control input, Ethernet optical data output, status output gigabit interfaces RJ45 2 2 2 Data input, control input, 10/100/1000 HA data output, status output Ethernet interface RJ45 0 16 16 Data input, control input, 10/100/1000 Ethernet data output, status output Interfaces 100-240 2 2 2 Power input Power interface Vcc LEDs 8 8 8 Status output Status indicators USB 2 2 2 Disabled except for power Used in manufacturing Table 13 - PA-5000 Series FIPS 140-2 Ports and Interfaces Interface PA-5060 PA-5050 PA-5020 FIPS 140-2 Designation Name and Qty Qty Qty Description RJ45 1 1 1 Data input, control input, Console port data output, status output RJ45 1 1 1 Data input, control input, Out of band data output, status output management SFP+ 4 4 0 Data input, control input, Ethernet optical 10- data output, status output gigabit interface SFP 8 8 8 Data input, control input, Ethernet optical data output, status output gigabit interfaces RJ45 2 2 2 Data input, control input, 10/100/1000 HA data output, status output Ethernet interface RJ45 12 12 12 Data input, control input, 10/100/1000 Ethernet data output, status output Interfaces Palo Alto Networks Firewall Security Policy Page 24 of 72 Palo Alto Networks 880-000018-00L Interface PA-5060 PA-5050 PA-5020 FIPS 140-2 Designation Name and Qty Qty Qty Description 100-240 2 2 2 Power input Power interface Vcc LEDs 8 8 8 Status output Status indicators USB 2 2 2 Disabled except for power Used in manufacturing Palo Alto Networks Firewall Security Policy Page 25 of 72 Palo Alto Networks 880-000018-00L 5 Identification and Authentication Policy 5.1 Assumption of Roles The modules support four distinct operator roles, User and Cryptographic Officer (CO), Remote Access VPN, and Site-to-site VPN. The cryptographic modules enforce the separation of roles using unique authentication credentials associated with operator accounts. The modules support concurrent operators. The modules do not provide a maintenance role or bypass capability. Table 14 - Roles and Required Identification and Authentication Authentication Role Description Authentication Data Type CO This role has access to all Identity-based Username and password configuration, show status and operator (optional certificate update services offered by the authentication based authentication can modules. Within the PAN-OS be added in addition to software, this role maps to the username and password) “Superuser” administrator role. User This role has limited access to Identity-based Username and password services offered by the modules. operator (optional certificate This role does not have access to authentication based authentication can modify or view the passwords be added in addition to associated with other administrator username and password) accounts, it may not view or alter CSPs of any type stored on the module. Within the PAN-OS software, this role maps to the “Superuser (read-only)” administrator role (also referred to as “Superreader”). Remote Remote user accessing the network Identity-based Username and password Access via VPN. operator (optional certificate VPN authentication based authentication can (RA be added in addition to VPN) username and password) Site-to- Remote VPN device establishing a Identity-based IKE/IPSec Pre-shared site VPN VPN session to facilitate access to operator keys - Identification (S-S the network. authentication with the IP Address and VPN) authentication with the Pre-Shared Key. Palo Alto Networks Firewall Security Policy Page 26 of 72 Palo Alto Networks 880-000018-00L Table 15 - Strengths of Authentication Mechanisms Authentication Mechanism Strength of Mechanism Username and Password Minimum length is 6 characters (95 possible characters). The probability that a random attempt will succeed or a false acceptance will occur is 1/(956 ) which is less than 1/1,000,000. The probability of successfully authenticating to the module within one minute is 10/(956), which is less than 1/100,000. The firewall’s configuration supports at most ten attempts to authenticate in a one- minute period. Certificate based The security modules support certificate-based authentication using authentication 2048 bit RSA keys. Such keys possess an equivalent strength of 112 bits. The probability that a random attempt will succeed is 1/(2112) which is less than 1/1,000,000. The probability of successfully authenticating to the module within a one minute period is 3,600,000/(2112), which is less than 1/100,000. The firewall supports at most 60,000 new sessions per second to authenticate in a one-minute period. The 160 bit key length supports 2160 different combinations. The IKE/IPSec pre-shared keys probability of successfully authenticating to the module is 1/(2160), which is less than 1/1,000,000. The number of authentication attempts is limited by the number of new connections per second supported (120,000) on the fastest platform of the Palo Alto Networks firewalls. The probability of successfully authenticating to the module within a one minute period is 7,200,000/(2160), which is less than 1/100,000. Palo Alto Networks Firewall Security Policy Page 27 of 72 Palo Alto Networks 880-000018-00L 6 Access Control Policy 6.1 Roles and Services Table 16 - Authenticated Service Descriptions Service Description Security Configuring and managing cryptographic parameters and Configuration setting/modifying security policy, including creating User accounts and Management additional CO accounts. Other Configuration Networking parameter configuration, logging configuration, and other non-security relevant configuration. View Other Read-only of non-security relevant configuration (see above). Configuration Show Status View status via the web interface or command line interface. VPN Provide network access for remote users or site-to-site connections. Firmware update Provides a method to update the firmware on the firewall. Note: Additional information on the services the module provides can be found at https://live.paloaltonetworks.com/community/documentation Table 17 - Authenticated Services Crypto Service User RA VPN S-S VPN Officer Security Configuration Y N N N Management Other Configuration Y N N N View Other Configuration Y Y N N Show Status Y Y Y Y VPN N N Y Y Firmware update Y N N N Palo Alto Networks Firewall Security Policy Page 28 of 72 Palo Alto Networks 880-000018-00L 6.2 Unauthenticated Services The cryptographic module supports the following unauthenticated services: Table 18 - Unauthenticated Services Service Description Zeroize The device will overwrite all CSPs. Self-Tests Run power up self-tests on demand by power cycling the module. Show Status (LEDs) View status of the module via the LEDs. Zeroize The zeroization procedure is invoked when the operator exits CC (FIPS) mode. The procedure consists of overwriting the Master Key used to encrypt all CSPs. The operator must be in control of the module during the entire procedure to ensure that it has successfully completed. During the zeroization procedure, no other services are available. 6.3 Definition of Critical Security Parameters (CSPs) The modules contain the following CSPs: Table 19 - Private Keys and CSPs CSP # Key Name Type Description 1 Web interface private RSA Decrypts TLS session key and provides authentication key services (admin web interface, captive portal, SSL VPN portal) 2 TLS PreMaster Secret TLS Secret value used to derive the TLS session keys Secret 3 TLS DH Private DH Diffie Hellman (Group 14) 2048 bit private component Components used in key establishment 4 TLS-HMAC HMAC- Authentication keys used in all https connections to the SHA-1 security module’s web interface. 5 TLS session keys AES Used in all https connections to the security module’s web interface. 6 SSH-Firewall private RSA Used to identify the security appliance in SSH. The key security modules support 512, 1024, and 2048 bit keys and only 2048 bit keys are supported in CC (FIPS) mode. 7 SSH-HMAC HMAC- Authentication keys used in all SSH connections to the SHA-1 security module’s command line interface. Palo Alto Networks Firewall Security Policy Page 29 of 72 Palo Alto Networks 880-000018-00L CSP # Key Name Type Description 8 SSH session keys AES Used in all SSH connections to the security module’s command line interface. 9 SSH DH Private DH Diffie Hellman (Group 14) 2048 bit private component Components used in key establishment 10 S-S VPN IPSec/IKEv1 HMAC- Used to authenticate the peer in an IKE/IPSec tunnel authentication SHA-1 connection. 11 S-S VPN IPSec/IKEv1 AES Used to encrypt IKE/IPSec data. These are AES (128 session key bit, 192 bit, 256 bit) keys. 12 S-S VPN IPSec/IKEv1 DH Diffie Hellman (Group 14) 2048 bit private component Diffie Hellman Private used in key establishment Components 13 S-S VPN IPSEC pre- Part of Entered manually by an administrator in the CO role. shared keys HMAC Used in authentication. 14 RA VPN IPSec session AES-128 Used to encrypt remote access sessions utilizing IPSec. key 15 RA VPN IPSec HMAC- Used in authentication of remote access IPSec data. authentication HMAC SHA-1 16 Firmware code HMAC- Used to check the integrity of crypto-related code. integrity check SHA-256 17 Firmware Content AES-256 Used to decrypt firmware, software, and content. encryption key 18 CO, User, RA VPN Password Entered by the Operator. Password 19 Master Key AES-256 Used to encrypt crypto-related files on the firewall. 20 RNG seed key AES Seed key used in RNG. 21 RNG seed value Seed used to initialize RNG. 22 DLP Private key RSA Used to encrypt DLP data. Only 2048 bit keys are supported. Note: The CSPs in Volatile memory locations are zeroized by overwrite with a pseudo random pattern followed by read-verify. Intermediate plaintext key material (CSP) is zeroized when it is copied from one to another memory location. All keys (CSPs) are zeroized when they expire. Session keys (CSPs) are zeroized as soon as the associated session has ended/timed out/ or been closed. Private keys (CSPs) are zeroized when their corresponding public keys (certificates) expire. Palo Alto Networks Firewall Security Policy Page 30 of 72 Palo Alto Networks 880-000018-00L 6.4 Definition of Public Keys The modules contain the following public keys: Table 20 - Public Keys Key Name Type Description Web interface certificates RSA-2048 Used to establish TLS sessions between firewall and user for web interface (management), captive portal, and remote access SSL VPN portal CA certificate RSA-2048 Used to trust a CA for SSL decryption sessions Client CA certificate RSA-2048 Used to verify client certificates for firewall administrators Client OCSP verify CA RSA-2048 Used for certificate validation via OCSP certificate TLS peer public key RSA-2048 Cert coming in from web server in outbound TLS decryption - used to encrypt the session key for client session with web server TLS DH public components DH – 2048 Used in key agreement (Group 14) SSH DH public components DH – 2048 Used in key agreement (Group 14) SSH – Firewall public key RSA-2048 Used firewall in authentication process S-S VPN - IPSec/IKEv1 DH – 2048 Used in key agreement Diffie Hellman public (Group 14) component Public key for firmware RSA-2048 Used to authenticate firmware and content to be content load test installed on the firewall DLP public key RSA-2048 Used to encrypt data loss prevention data Client public key RSA-2048 Used to authenticate User, CO, or remote access VPN users Palo Alto Networks Firewall Security Policy Page 31 of 72 Palo Alto Networks 880-000018-00L 6.5 Definition of CSPs Modes of Access Table 21 defines the relationship between access to CSPs and the different module services. The modes of access shown in the table are defined as:  R = Read: The module reads the CSP. The read access is typically performed before the module uses the CSP.  W = Write: The module writes the CSP. The write access is typically performed after a CSP is imported into the module, or the module generates a CSP, or the module overwrites an existing CSP.  Z = Zeroize: The module zeroizes the CSP. Table 21 - CSP Access Rights within Roles & Services Cryptographic Key or CSP Role Authorized Service Mode (as numbered in Table 19) CO Security Configuration RW 1, 2, 3, 4, 5, 6, 7, 8, 9, 16, 17, Management 18, 19, 20, 21, 22 CO Other Configuration RW 1, 2, 3, 4, 5, 6, 7, 8, 9 User, CO Show Status R 1, 2, 3, 4, 5, 6, 7, 8, 9 Unauthenticated Zeroize Z All CSPs are zeroized. S-S VPN VPN R 10, 11, 12, 13 RA VPN VPN R 1, 2, 3, 4, 5, 14, 15 CO Firmware Update RW 17 Unauthenticated Self-Tests W N/A Unauthenticated Show Status (LEDs) N/A N/A Palo Alto Networks Firewall Security Policy Page 32 of 72 Palo Alto Networks 880-000018-00L 7 Operational Environment The FIPS 140-2 Area 6 Operational Environment requirements are not applicable because the PA- 200, PA-500, PA-2000 Series, PA-3000 Series, PA-4000 Series, and PA-5000 Series Firewalls do not contain modifiable operational environments. 8 Security Rules The module design corresponds to the module security rules. This section documents the security rules enforced by the cryptographic module to implement the security requirements of this FIPS 140-2 Level 2 module. 1. The cryptographic module shall provide four distinct operator roles. These are the User role, Remote Access VPN role, Site-to-site VPN role, and the Cryptographic Officer role. 2. The cryptographic module shall provide identity-based authentication. 3. The cryptographic module shall clear previous authentications on power cycle. 4. When the module has not been placed in a valid role, the operator shall not have access to any cryptographic services. 5. The cryptographic module shall perform the following tests A. Power up Self-Tests 1. Cryptographic algorithm tests a. AES Encrypt and Decrypt Known Answer Tests b. RSA Sign and Verify Known Answer Tests c. HMAC-SHA-1 Known Answer Test d. HMAC-SHA-256 Known Answer Test e. SHA-1, SHA-256, SHA-384, SHA-512 Known Answer Test f. RNG Known Answer Test g. DH Parameter Test h. DH Known Answer Test i. Monobit RNG Test j. Poker RNG Test k. Runs RNG Test l. Long runs RNG Test 2. The tests, g-l, are run on power up but are not FIPS required tests. B. Firmware Integrity Test – A 128 bit EDC (using MD5) is calculated on non-security related code. Security related code is verified with HMAC-SHA-256. C. Critical Functions Tests 1. N/A D. Conditional Self-Tests 1. Continuous Random Number Generator (RNG) test – performed on NDRNG and RNG, 128 bits 2. RSA Pairwise Consistency Test (when a key generation fails, the error message displayed is “Cannot verify key and certificate. Maybe the passphrase is incorrect.”) 3. Firmware Load Test – Verify RSA 2048 signature on firmware at time of load Palo Alto Networks Firewall Security Policy Page 33 of 72 Palo Alto Networks 880-000018-00L 4. If any conditional test fails, the module will output ‘CC EAL4 failure’ and the specific test that failed. 6. The module will output a status of “fail” if any of the power up self-tests do not pass. 7. The operator shall be capable of commanding the module to perform the power-up self-test by cycling power of the module. 8. Power-up self-tests do not require any operator action. 9. Data output shall be inhibited during key generation, self-tests, zeroization, and error states. 10. Status information does not contain CSPs or sensitive data that if misused could lead to a compromise of the module. 11. The module ensures that the seed and seed key inputs to the Approved RNG are not equal. 12. There are no restrictions on which keys or CSPs are zeroized by the zeroization service. 13. The module maintains separation between concurrent operators. 14. The module does not support a maintenance interface or role. 15. The module does not have any external input/output devices used for entry/output of data. 16. The module does not enter or output plaintext CSPs. 17. The module does not output intermediate key generation values. Vendor imposed security rules: 1. The module does not support the update of the logical serial number or vendor ID. 2. The module does not provide access to revenue related data structures while plaintext CSPs are present. 3. If the cryptographic module remains inactive in any valid role for the administrator specified time interval, the module automatically logs out the operator. 4. The module enforces a timed access protection mechanism that supports at most ten authentication attempts per minute. After the administrator specified number of consecutive unsuccessful Password validation attempts have occurred, the cryptographic module shall enforce a wait period of at least 1 minute before any more login attempts can be attempted. This wait period shall be enforced even if the module power is momentarily removed. Palo Alto Networks Firewall Security Policy Page 34 of 72 Palo Alto Networks 880-000018-00L 9 Physical Security Policy 9.1 Physical Security Mechanisms The multi-chip standalone modules are production quality containing standard passivation. Chip components are protected by an opaque enclosure. There are tamper evident seals that are applied on the modules by the Crypto-Officer. The seals prevent removal of the opaque enclosure without evidence. The Crypto-Officer is responsible for controlling all unused seals and removing and re- installing the tamper evident seals or opacity shields when necessary. The Crypto-Officer must perform the following steps when applying the tamper evident seals: 1. Ensure that the module surface is clean and dry. 2. Press the tamper evident seals firmly onto the adhering surfaces during installation. 3. Permit 24 hours of cure time for all tamper evident seals. The tamper evident seals and opacity shields shall be installed for the module to operate in a FIPS Approved mode. The Crypto-Officer should inspect the seals and shields for evidence of tamper every 30 days. If the seals show evidence of tamper, the Crypto-Officer should assume that the modules have been compromised and contact Customer Support. Note: For ordering information, see Table 2 for FIPS kit part numbers and versions. Opacity shields are included in the FIPS kits. Refer to Appendix A for instructions on installation of the tamper seals and opacity shields. The locations of the five (5) tamper evident seals implemented on the PA-200 are shown in Figure 25 through Figure 26 [1] [3] [2] Palo Alto Networks Firewall Security Policy Page 35 of 72 Palo Alto Networks 880-000018-00L Figure 25 - PA-200 Left Side and Top Tamper Seal Placement (3) [5] [4] Figure 26 - PA-200 Right Side Tamper Seal Placement (2) Refer to Appendix B for instructions on installation of the tamper seals and opacity shields. The locations of the twelve (12) tamper evident seals implemented on the PA-500 are shown in Figure 27 through Figure 30 Palo Alto Networks Firewall Security Policy Page 36 of 72 Palo Alto Networks 880-000018-00L [1] Figure 27 - PA-500 Front Tamper Seal Placement (1) [3] [4] [2] Figure 28 - PA-500 Left Side Tamper Seal Placement (3) [6] [5] Figure 29 - PA-500 Right Side Tamper Seal Placement (2) Palo Alto Networks Firewall Security Policy Page 37 of 72 Palo Alto Networks 880-000018-00L [7] [9] [11] [8] [12] [10] Figure 30 - PA-500 Rear Tamper Seal Placement (6) Refer to Appendix C for instructions on installation of the tamper seals and opacity shields. The locations of the ten (10) tamper evident seals on the PA-2000 Series modules are shown in Figure 31 through Figure 34 [1] Figure 31 - PA-2000 Series Front Tamper Seal Placement (1) Palo Alto Networks Firewall Security Policy Page 38 of 72 Palo Alto Networks 880-000018-00L [2] [4] [3] Figure 32 - PA-2000 Series Left Side Tamper Seal Placement (3) [7] [5] [6] Figure 33 - PA-2000 Series Right Side Tamper Seal Placement (3) [9] [10] [8] Figure 34 - PA-2000 Series Rear Tamper Seal Placement (3) Palo Alto Networks Firewall Security Policy Page 39 of 72 Palo Alto Networks 880-000018-00L Refer to Appendix D for instructions on installation of the tamper seals and opacity shields. The locations of the seven (7) tamper evident seals on the PA-3000 Series modules are shown in Figure 35 through Figure 37 [2] [3] [1] Figure 35 - PA-3000 Series Tamper Seal Placement (3) [4] [5] Figure 36 - PA-3000 Series Tamper Seal Placement (2) Palo Alto Networks Firewall Security Policy Page 40 of 72 Palo Alto Networks 880-000018-00L [7] [6] Figure 37 - PA-3000 Series Tamper Seal Placement (2) Refer to Appendix E for instructions on installation of the tamper seals and opacity shields. The locations of the ten (10) tamper evident seals implemented on the PA-4000 Series modules are shown in Figure 38 through Figure 41 below. [1] [2] [3] [4] Figure 38 - PA-4000 Series Rear Tamper Seal Placement – From Top (4) [5] [6] [7] [8] Figure 39 - PA-4000 Series Rear Side Tamper Seal Placement – From Underside (4) Palo Alto Networks Firewall Security Policy Page 41 of 72 Palo Alto Networks 880-000018-00L [9] Figure 40 - PA-4000 Series Right Side Tamper Seal Placement (1) [10] Figure 41 - PA-4000 Series Left Side Tamper Seal Placement (1) Refer to Appendix F for instructions on installation of the tamper seals and opacity shields. The locations of the seventeen (17) tamper evident seals implemented on the PA-5000 Series modules are shown in Figure 42 through Figure 44 below Palo Alto Networks Firewall Security Policy Page 42 of 72 Palo Alto Networks 880-000018-00L [2] [4] [6] [1] [3] [5] [7] [8] [9] Figure 42 - PA-5000 Series Rear Tamper Seal Placement (9) [10] [12] [11] [13] Figure 43 - PA-5000 Series Right Side Tamper Seal Placement (4) Palo Alto Networks Firewall Security Policy Page 43 of 72 Palo Alto Networks 880-000018-00L [16] [15] [17] [14] Figure 44 - PA-5000 Series Left Side Tamper Seal Placement (4) Palo Alto Networks Firewall Security Policy Page 44 of 72 Palo Alto Networks 880-000018-00L 9.2 Operator Required Actions Table 22 - Inspection/Testing of Physical Security Mechanisms Physical Recommended Model Security Frequency of Inspection/Test Guidance Details Mechanisms Inspection/Test PA-5060, PA-5050, Tamper 30 days Verify integrity of tamper evident PA-5020, PA-4060, Evident Seals seals in the locations identified in PA-4050, PA-4020, the FIPS Kit Installation Guide PA-3050, PA-3020, PA-2050, PA-2020, PA-500, PA 200 PA-5060, PA-5050, Front Cover 30 days Verify that front cover and side PA-5020, PA-3050, and Side opacity shields have not been PA-3020, PA-2050, Opacity deformed from their original shape, PA-2020, PA-500 Shields thereby reducing their effectiveness PA-4020, PA-4050, Front Cover 30 days Verify that front cover has not been PA-4060 deformed from its original shape thereby reducing its effectiveness PA-200 Front cover 30 days Verify that front cover and cage and Cage enclosure have not been deformed Enclosure from their original shape, thereby reducing their effectiveness Palo Alto Networks Firewall Security Policy Page 45 of 72 Palo Alto Networks 880-000018-00L 10 Mitigation of Other Attacks Policy The module has not been designed to mitigate any specific attacks outside of the scope of FIPS 140-2, so these requirements are not applicable. 11 References [FIPS 140-2] FIPS Publication 140-2 Security Requirements for Cryptographic Modules 12 Definitions and Acronyms API – Application Programming Interface App-ID – Application Identification - Palo Alto Networks’ ability to identify applications and apply security policy based on the ID rather than the typical port and protocol-based classification. BGP – Border Gateway protocol – Dynamic routing protocol CA – Certificate authority Content-ID – Content Identification – Palo Alto Networks’ threat prevention features including Antivirus, Antispyware, and Intrusion Prevention. CO – Cryptographic Officer DB9 – Console port connector DLP – Data loss prevention Gbps – Gigabits per second HA – High Availability IKE – Internet Key Exchange IP – Internet Protocol IPSec – Internet Protocol Security LDAP – Lightweight Directory Access Protocol LED – Light Emitting Diode NDRNG – Non-deterministic random number generator OCSP – Online Certificate Status Protocol OSPF – Open Shortest Path First – Dynamic routing protocol PAN-OS – Palo Alto Networks’ Operating System QoS – Quality of Service RA VPN – Remote Access Virtual Private Network Palo Alto Networks Firewall Security Policy Page 46 of 72 Palo Alto Networks 880-000018-00L RIP – Routing Information Protocol – Dynamic routing protocol RJ45 – Networking Connector RNG –Random number generator S-S VPN – Site to site Virtual Private Network SFP – Small Form-factor Pluggable Transceiver SSL – Secure Sockets Layer TLS – Transport Layer Security USB – Universal Serial Bus User-ID – User Identification – Palo Alto Networks’ ability to apply security policy based on who initiates the traffic rather than the typical IP-based approach. VPN – Virtual Private Network XFP – 10 Gigabit Small Form Factor Pluggable Transceiver XML – Extensible Markup Language Palo Alto Networks Firewall Security Policy Page 47 of 72 Palo Alto Networks 880-000018-00L 13 Appendix A - PA-200 - FIPS Accessories/Tamper Seal Installation (5 Seals) 1. Insert the PA-200 unit into the cage. 2. Secure right side of the PA-200 unit to the cage with (2x) 4-40x1/2” screws provided in the kit. Repeat for the left side of the cage. Palo Alto Networks Firewall Security Policy Page 48 of 72 Palo Alto Networks 880-000018-00L 3. Install the front panel with the curve side up to the front cage. 4. Secure the front panel to the cage with (5x) 4-40x3/16” screws. Palo Alto Networks Firewall Security Policy Page 49 of 72 Palo Alto Networks 880-000018-00L 5. Affix a tamper seal on the top middle of the front panel screw. 6. Affix two tamper seals over both screw mounting holes on the cage and right side screw on the front panel. Repeat for the left side Palo Alto Networks Firewall Security Policy Page 50 of 72 Palo Alto Networks 880-000018-00L 14 Appendix B - PA-500 - FIPS Accessories/Tamper Seal Installation (12 Seals) 1. Remove the right side cover screws. Repeat for the left side cover screws. 2. Install the right side FIPS opacity shield and secure with 2x #4-40x1/4” SEMS screws provided in the kit. Repeat for the left side. Palo Alto Networks Firewall Security Policy Page 51 of 72 Palo Alto Networks 880-000018-00L 3. Install the front FIPS panel with the curve side up and align with the ear mounting screw holes. 4. Sandwich the right side mounting ear between the front panel and the opacity shield. Repeat with the left side of the chassis. Palo Alto Networks Firewall Security Policy Page 52 of 72 Palo Alto Networks 880-000018-00L 5. Install and secure the right side mounting ear with (2x) #6-32x1/2” Truss screws provided in the kit. Repeat on the left side. 6. Remove 1x upper-right fan screw. Palo Alto Networks Firewall Security Policy Page 53 of 72 Palo Alto Networks 880-000018-00L 7. Install and partially tighten the screw on one of the fan guard mounting holes. 8. Remove the other 3x fan screws. Palo Alto Networks Firewall Security Policy Page 54 of 72 Palo Alto Networks 880-000018-00L 10. Align the fan guard and secure with 3x screws as shown. Repeat the installation steps for the other fan. Caution: The fan guard may crack if you over-tighten the screws. 11. Affix one tamper seal over top cover/rear left chassis. Affix one tamper seal over the upper PSU screw. Affix four tamper seals over the fan cover screws. Palo Alto Networks Firewall Security Policy Page 55 of 72 Palo Alto Networks 880-000018-00L 12 Affix a tamper seal over both screw access holes on the left side opacity shield. Affix a tamper seal over the bottom ear screw on the left side of the chassis. Affix a tamper seal on top of the opacity shield/cover on the left side of the chassis. 13. Affix a tamper seal over the bottom ear screw on the right side of the chassis. Affix a tamper seal on top of the opacity shield/cover on the right side of the chassis. Palo Alto Networks Firewall Security Policy Page 56 of 72 Palo Alto Networks 880-000018-00L 14. Affix a tamper seal on the top of the cover and panel. Palo Alto Networks Firewall Security Policy Page 57 of 72 Palo Alto Networks 880-000018-00L 15 Appendix C - PA-2000 Series - FIPS Accessories/Tamper Seal Installation (10 Seals) Install the front panel with the curve side up and line it up to the left and right side ear mounting holes. Install and secure the right side mounting ear with (2x) 6-32x1/2” screws provided in the kit. Repeat the same step on the left side of the chassis. Palo Alto Networks Firewall Security Policy Page 58 of 72 Palo Alto Networks 880-000018-00L Remove the right side cover screws. Repeat the same steps for the left side cover screws. Install the right side FIPS opacity shield and secure with 3x #4-40x1/4” SEM screws provided by the kit. Repeat the same steps for the left side. Palo Alto Networks Firewall Security Policy Page 59 of 72 Palo Alto Networks 880-000018-00L Affix a tamper seal to cover the right Affix a tamper seal at right side of the chassis between side bottom ear mounting bracket the top cover and the FIPS opacity shield. Affix another screw. Repeat the same steps for the tamper seal between the bottom chassis and the FIPS left side. opacity shield. Repeat the same steps for the left side. Affix tamper seals evenly spaced between the top cover mounting screws. Palo Alto Networks Firewall Security Policy Page 60 of 72 Palo Alto Networks 880-000018-00L Affix a tamper seal on top of the cover/panel. Palo Alto Networks Firewall Security Policy Page 61 of 72 Palo Alto Networks 880-000018-00L 16 Appendix D - PA-3000 Series - FIPS Accessories/Tamper Seal Installation (7 Seals) 1. Install the front panel with the curve side up and line it up to the left and right side ear mounting holes. 2. Install and secure the right side mounting ear and (2x) 6-32x1/2” screws provided in the kit. Repeat the same step on the left side of the chassis. Palo Alto Networks Firewall Security Policy Page 62 of 72 Palo Alto Networks 880-000018-00L 3. Install the right side FIPS plenum and secure with (4x) #6-32x1” SEM screws provided by the kit. Repeat the same steps for the left side. 4. Affix a tamper seal to cover the right side bottom ear mounting bracket screw. Repeat the same steps for the left side. Affix a tamper seal at right side of the chassis between the top cover and the FIPS plenum. Affix another tamper seal between the bottom of the chassis and the FIPS plenum. Repeat the same steps for the left side. Palo Alto Networks Firewall Security Policy Page 63 of 72 Palo Alto Networks 880-000018-00L 5. Affix a tamper seal on top of the cover / panel. Palo Alto Networks Firewall Security Policy Page 64 of 72 Palo Alto Networks 880-000018-00L 17 Appendix E - PA-4000 Series – FIPS Accessories/Tamper Seal Installation (10 Seals) Install the front panel FIPS opacity shield as shown. Install right mounting bracket and secure with (2x) 8-32x3/8” screws provided by the kit. Repeat the same steps for the right mounting bracket. Palo Alto Networks Firewall Security Policy Page 65 of 72 Palo Alto Networks 880-000018-00L Remove 1x upper-left fan screw. Install and secure the fan guard with the fan screw to one of the fan guard mounting holes as shown. Palo Alto Networks Firewall Security Policy Page 66 of 72 Palo Alto Networks 880-000018-00L Remove the other 3x fan screws Align the fan guard and secure with 3x screws as shown. Repeat above installation steps for the other fans. Warning: Over tighten the screw will result cracking the fan guard. Palo Alto Networks Firewall Security Policy Page 67 of 72 Palo Alto Networks 880-000018-00L Install the fan filter and clip on the fan guard cover onto the fan guard as shown. Affix a tamper proof seal over screw on the lower right side mounting bracket. Repeat the same step for left side bracket. Palo Alto Networks Firewall Security Policy Page 68 of 72 Palo Alto Networks 880-000018-00L Affix four tamper proof seals between the top cover/fan guards and top cover/PSU where as shown. Affix four tamper proof seals between the bottom chassis/fan guards and bottom chassis/PSU where as shown. Palo Alto Networks Firewall Security Policy Page 69 of 72 Palo Alto Networks 880-000018-00L 18 Appendix F - PA-5000 Series - FIPS Accessories/Tamper Seal Installation (17 Seals) 6. Install the front panel. 7. Install the right FIPS mounting bracket and secure with (2x) #8-32x3/8” screws provided in the original accessory kit. Repeat for the left mounting bracket. 8. Install the side panel on the right side of the chassis and secure with (4x) #8-32x1.00”L screws. Place the leading edge towards front of the chassis. Repeat for the left side of the chassis. Leading Edge Palo Alto Networks Firewall Security Policy Page 70 of 72 Palo Alto Networks 880-000018-00L 9. Affix two tamper evident labels over both upper and lower screws on the FIPS mounting bracket. Repeat for the left side panel. 10. Affix two tamper evident labels over front upper and rear lower of the right side panel screws. Repeat for the left side panel. 11. Affix three tamper evident labels on the top cover /rear chassis. Ensure the top cover screws are covered by the labels. Palo Alto Networks Firewall Security Policy Page 71 of 72 Palo Alto Networks 880-000018-00L 12. Affix a tamper evident label on the top cover/fan access panel. Affix another tamper evident label on the bottom chassis/fan access panel. 13. Affix a tamper evident label on upper HDD access panel/rear chassis. Affix a tamper evident label on lower HDD access panel/rear chassis. 14. Affix a tamper evident label on the upper left PSU/rear chassis. Affix a tamper evident label on the upper right PSU/rear chassis. Palo Alto Networks Firewall Security Policy Page 72 of 72