Palo Alto Networks, Inc.
www.paloaltonetworks.com
© 2022 Palo Alto Networks, Inc. Palo Alto Networks is a registered trademark of Palo Alto Networks. A list of our
trademarks can be found at https://www.paloaltonetworks.com/company/trademarks.html. All other marks
mentioned herein may be trademarks of their respective companies.
This document may be freely reproduced and distributed whole and intact including this copyright notice.
Palo Alto Networks
Panorama 9.0 M-100, M-200, M-500
and M-600
FIPS 140-2 Non-Proprietary Security Policy
Version: 1.2
Revision Date: June 29, 2022
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 2
Table of Contents
1. Module Overview ...............................................................................................................................6
2. Security Levels.................................................................................................................................. 12
3. Modes of Operation ........................................................................................................................ 13
4. Ports and Interfaces......................................................................................................................... 19
5. Roles, Services, and Authentication ............................................................................................. 26
6. Operational Environment............................................................................................................... 34
7. Self-Tests / Security Rules ............................................................................................................. 35
8. Physical Security............................................................................................................................... 37
9. Mitigation of Other Attacks........................................................................................................... 38
10. References......................................................................................................................................... 38
11. Definitions and Acronyms.............................................................................................................. 38
Appendix A – M-100 FIPS Tamper Seal Installation (28 Seals)........................................................ 39
Appendix B – M-200 FIPS Tamper Seal Installation (15 Seals)........................................................ 43
Appendix C – M-500 FIPS Tamper Seal Installation (12 Seals)........................................................ 47
Appendix D – M-600 FIPS Tamper Seal Installation (21 Seals) ....................................................... 54
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 3
Table 1 - Validated Version Information .....................................................................................................................................................7
Table 2 - Module Security Level Specification........................................................................................................................................ 12
Table 3 - CAVP Certificates for FIPS Approved Algorithms ................................................................................................................ 15
Table 4 - FIPS Allowed Algorithms Used in the Approved Mode ....................................................................................................... 17
Table 5 - Supported Protocols in the Approved Mode ......................................................................................................................... 18
Table 6 – Non-Approved, Non-Allowed Algorithms.............................................................................................................................. 18
Table 7 – M-100 Ports and Interfaces...................................................................................................................................................... 19
Table 8 – M-200 Front Panel Ports and Interfaces................................................................................................................................ 20
Table 9 – M-200 Back Panel Ports and Interfaces................................................................................................................................. 21
Table 10 – M-500 Ports and Interfaces ................................................................................................................................................... 22
Table 11 – M-600 Front Panel Ports and Interfaces ............................................................................................................................. 24
Table 12 – M-600 Back Panel Ports and Interfaces .............................................................................................................................. 25
Table 13 – Panorama and Management-Only modes - Roles and Authentication ......................................................................... 26
Table 14 – Log Collector mode - Roles and Authentication ................................................................................................................ 26
Table 15 – PAN-DB mode - Roles and Authentication......................................................................................................................... 26
Table 16 - Strength of Authentication Mechanisms.............................................................................................................................. 26
Table 17 - Private Keys and CSPs.............................................................................................................................................................. 27
Table 18 - Public Keys.................................................................................................................................................................................. 28
Table 19 - Authenticated Services – Panorama or Management-Only Mode ................................................................................. 30
Table 20 - Authenticated Services – Log Collector Mode.................................................................................................................... 32
Table 21 - Authenticated Services – PAN-DB Mode (M-500/M-600 Only).................................................................................... 33
Table 22 - Unauthenticated Services........................................................................................................................................................ 33
Table 23 - Inspection/Testing of Physical Security Mechanisms........................................................................................................ 37
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 4
Figure 1 – Front of M-100 .............................................................................................................................................................................7
Figure 2 – Front of M-100 with FIPS Kit ....................................................................................................................................................7
Figure 3 – Rear of M-100 with FIPS Kit ......................................................................................................................................................8
Figure 4 – Front of M-200 .............................................................................................................................................................................8
Figure 5 – Front of M-200 with FIPS Kit ........................................................................................................................................................8
Figure 6 – Rear of M-200 with FIPS Kit ......................................................................................................................................................8
Figure 7 –Front of M-500 ..............................................................................................................................................................................9
Figure 8 – Front of M-500 with FIPS Kit ....................................................................................................................................................9
Figure 9 – Rear of M-500 with FIPS Kit ......................................................................................................................................................9
Figure 10 – Right Side of M-500 with FIPS Kit....................................................................................................................................... 10
Figure 11 – Left Side of M-500 with FIPS Kit......................................................................................................................................... 10
Figure 12 –Front of M-600......................................................................................................................................................................... 10
Figure 13– Front of M-600 with FIPS Kit ................................................................................................................................................ 11
Figure 14 – Rear of M-600 with FIPS Kit................................................................................................................................................. 11
Figure 15 – Right Side of M-600 with FIPS Kit....................................................................................................................................... 11
Figure 16 – Left Side of M-600 with FIPS Kit......................................................................................................................................... 11
Figure 17 – M-100 Ports and Interfaces (Front and Back)................................................................................................................... 19
Figure 18 – M-200 Front Panel Ports and Interfaces............................................................................................................................ 20
Figure 19 – M-200 Back Panel Ports and Interfaces............................................................................................................................. 21
Figure 20 – M-500 Front Panel Ports and Interfaces............................................................................................................................ 22
Figure 21 – M-500 Back Panel Ports and Interfaces............................................................................................................................. 22
Figure 22 – M-600 Front Panel Ports and Interfaces............................................................................................................................ 24
Figure 23 – M-600 Back Panel Ports and Interfaces............................................................................................................................. 25
Figure 24 – M-100: Remove Screws on Rear Side................................................................................................................................. 39
Figure 25 – M-100: Attach Rear Opacity Shield .................................................................................................................................... 39
Figure 26 – M-100: Apply Tamper Seals and Vent Overlays............................................................................................................... 40
Figure 27 – M-100: Apply Rail Kit............................................................................................................................................................. 40
Figure 28 – M-100: Remove Front Plastic Bracket Covers and Screws............................................................................................ 41
Figure 29 – M-100: Install Front Opacity Shield .................................................................................................................................... 41
Figure 30 – M-100: Install Outer Rails ..................................................................................................................................................... 42
Figure 31 – M-200: Top Cover Replacement.......................................................................................................................................... 43
Figure 32 – M-200: Side View Before Rail Installation ......................................................................................................................... 44
Figure 33 – M-200: Inner Rack Mount Rail Brackets ............................................................................................................................ 44
Figure 34 – M-200: Replacing Front Rack-Mount Brackets ................................................................................................................ 45
Figure 35 – M-200: Attach FIPS Front Cover......................................................................................................................................... 45
Figure 36 – M-200: Seal locations on Top and Right Side ................................................................................................................... 46
Figure 37 – M-200: Seal Locations on Left Side and Rear ................................................................................................................... 46
Figure 38 – M-500: Remove Front Handles and Modules................................................................................................................... 47
Figure 39 – M-500: Secure the Front Brackets ...................................................................................................................................... 48
Figure 40 – M-500: Attach Pull Handles and Front Modules.............................................................................................................. 48
Figure 41 – M-500: Install Front Opacity Shield .................................................................................................................................... 49
Figure 42 – M-500: Front Opacity Shield Installed................................................................................................................................ 49
Figure 43 – M-500: Install Rear Opacity Shield Tray............................................................................................................................. 50
Figure 44 – M-500: Install Rear Opacity Shield...................................................................................................................................... 50
Figure 45 – M-500: Apply Vent Overlays................................................................................................................................................ 51
Figure 46 – M-500: Apply Tamper Seals on Vent Overlays and Side Opening ............................................................................... 51
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 5
Figure 47 – M-500: Install Rail Kit............................................................................................................................................................. 52
Figure 48 – M-500: Apply Tamper Seals on the Bottom of the Appliance....................................................................................... 52
Figure 49 – M-500: Apply Tamper Seals on the Top and Sides of the Appliance........................................................................... 53
Figure 50 – M-600: Top Cover Replacement.......................................................................................................................................... 54
Figure 51 – M-600: Front Cover Bracket ................................................................................................................................................ 55
Figure 52 – M-600: FIPS Front Cover ...................................................................................................................................................... 55
Figure 53 – M-600: Tamper Seal Locations (Top and Rear)................................................................................................................. 56
Figure 54 – M-600: Tamper Seal Locations (Top and Front) ............................................................................................................... 57
Figure 55 – M-600: Tamper Seals Location for Side Rails.................................................................................................................... 57
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 6
1. Module Overview
Panorama 9.0 M-100, M-200, M-500 and M-600 module management appliances provide centralized management and
visibility of Palo Alto Networks next generation firewalls. From a central location, you can gain insight into applications,
users, and content traversing the firewalls. The knowledge of what is on the network, in conjunction with safe application
enablement policies, maximizes protection and control while minimizing administrative effort. Your security team can
centrally perform analysis, reporting, and forensics with the aggregated data over time, or on data stored on the local
firewall.
The Panorama management appliances’ individual management and logging components can be separated in a distributed
manner to accommodate large volumes of log data. Panorama management appliances can be deployed in the following
ways:
• Centralized: In this scenario, all Panorama management and logging functions are combined into a single device.
• Distributed: you can separate the management and logging functions across multiple devices, splitting the
functions between managers and log collectors.
o Panorama: The Panorama manager is responsible for handling the tasks associated with policy and device
configuration across all managed devices. The manager analyzes the data stored in managed log collectors
for centralized reporting.
o Management-Only: Providing the ability to perform all functions of Panorama with the exception of
logging.
o Log Collector: Organizations with high logging volume and retention requirements can deploy dedicated
Panorama log collector devices that will aggregate log information from multiple managed firewalls.
• Panorama on the M-500 and M-600 supports an additional mode, the PAN-DB private cloud. The PAN-DB private
cloud is an on-premise solution that is suitable for organizations that prohibit or restrict the use of the PAN-DB
public cloud service. With this on-premise solution, you can deploy one or more M-500/M-600 appliances as
PAN-DB servers within your network or data center.
The Palo Alto Networks Panorama management appliances are multi-chip standalone modules and are shown in the figures
below. The M-100 is demonstrated in Figure 1 through Figure 3, M-200 is demonstrated in Figure 4 through Figure 6, the
M-500 is demonstrated in Figure 7 through Figure 11, and M-600 is demonstrated in Figure 12 through Figure 16. The
cryptographic boundary is defined by the external perimeter of the appliance including the FIPS kit.
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 7
Table 1 - Validated Version Information
Module Part Number Hardware
Version
FIPS Kit Part Number FIPS Kit
Hardware
Version
Firmware
Version
Panorama M-100
1TB RAID: 2 x 1TB RAID Certified
HDD for 1TB of RAID Storage
910-000030 00D 920-000140 00A 9.0.9
Panorama M-100
4TB RAID: 8 x 1TB RAID Certified
HDD for 4TB of RAID Storage
910-000092 00D 920-000140 00A 9.0.9
Panorama M-200 910-000176 00A 920-000208 00A 9.0.9
Panorama M-500 910-000073 00D 920-000145 00A 9.0.9
Panorama M-600 910-000175 00A 920-000209 00A 9.0.9
M-100
Figure 1 – Front of M-100
Figure 2 – Front of M-100 with FIPS Kit
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 8
Figure 3 – Rear of M-100 with FIPS Kit
M-200
Figure 4 – Front of M-200
Figure 5 – Front of M-200 with FIPS Kit
Figure 6 – Rear of M-200 with FIPS Kit
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 9
M-500
Figure 7 –Front of M-500
Figure 8 – Front of M-500 with FIPS Kit
Figure 9 – Rear of M-500 with FIPS Kit
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 10
Figure 10 – Right Side of M-500 with FIPS Kit
Figure 11 – Left Side of M-500 with FIPS Kit
M-600
Figure 12 –Front of M-600
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 11
Figure 13– Front of M-600 with FIPS Kit Figure 14 – Rear of M-600 with FIPS Kit
Figure 15 – Right Side of M-600 with FIPS Kit
Figure 16 – Left Side of M-600 with FIPS Kit
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 12
2. Security Levels
The cryptographic module meets the overall requirements applicable to Level 2 security of FIPS 140-2.
Table 2 - Module Security Level Specification
Security Requirements Section Level
Cryptographic Module Specification 2
Module Ports and Interfaces 2
Roles, Services, 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
When initialized in Panorama, Management-Only, or
PAN-DB system mode, the module supports Level 3,
identity-based authentication.
Security Requirements Section Level
Cryptographic Module Specification 2
Module Ports and Interfaces 2
Roles, Services, Authentication 2
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
When initialized in Panorama Log Collector system
mode, the module supports Level 2 role-based
authentication.
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 13
3. Modes of Operation
The module provides both a FIPS 140-2 Approved (FIPS-CC Mode) and non-Approved (Normal Mode) mode of operation.
This module is configured during initialization to operate only in an Approved or non-Approved mode of operation when in
the operational state. The module cannot alternate service by service between Approved and non-Approved modes of
operation.
FIPS 140-2 Approved Mode of Operation
The module provides both FIPS 140-2 Approved and non-Approved modes of operation. The module is configured during
initialization to operate only in an Approved or non-Approved mode of operation when in the operational state. The
module cannot alternate service by service between Approved and non-Approved modes of operation.
The following procedure will configure the Approved mode of operation:
• The tamper-evident seals and opacity shields must be installed as per Appendices (based on the model). The FIPS
kit must be correctly installed to operate in the Approved mode of operation.
• During initial boot up, break the boot sequence via the console port connection (by entering ‘maint’ when
instructed to do so) to access the main menu.
• Select “Continue.”
• Select the “Set FIPS-CC Mode” option to enter the Approved mode.
• Select “Enable FIPS-CC Mode”.
• When prompted, select “Reboot” and the module will re-initialize and continue into the Approved mode.
• The module will reboot.
• In the Approved mode, the console port is available only as a status output port.
The module will automatically indicate the Approved mode of operation in the following manner:
• Status output interface will indicate “**** FIPS-CC MODE ENABLED ****” via the CLI session.
• Status output interface will indicate “FIPS-CC mode enabled successfully” via the console port.
• The module will display “FIPS-CC” at all times in the status bar at the bottom of the web interface.
Selecting Panorama, Management-Only, and PAN-DB System Modes
Panorama appliances support multiple configurations that provide varying services. The Cryptographic Officer can initialize
the module into different system modes. The primary and default system mode is the Panorama mode. The Management-
Only system mode is the same as Panorama mode except there is no log collecting service. The Log Collector system mode
is a secondary mode that provides a focused log collecting and forwarding capability. Directions to convert the appliance
into the Log Collector mode are discussed below. The M-500 and M-600 provide a fourth system mode, PAN-DB Private
Cloud server.
Convert the M-100/M-200/M-500/M-600 appliance from Panorama mode to the Management-Only mode:
• Log into the CLI via SSH
• Enter “request system system-mode management-only”
• Enter “Y” to confirm the change to Management-Only mode.
• The system will reboot and perform the required power on self-tests.
Convert the M-100/M-200/M-500/M-600 appliance from Management-Only mode to the Panorama mode:
• Log into the CLI via SSH
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 14
• Enter “request system system-mode panorama”
• Enter “Y” to confirm the change to Panorama mode.
• The system will reboot and perform the required power on self-tests.
Convert the M-500/M-600 appliance from Panorama Manager mode to the dedicated PAN-DB Private Cloud mode:
• Log into the CLI via SSH
• Enter “request system system-mode panurldb”
• Enter “Y” to confirm the change to PAN-DB Private Cloud mode.
• The system will reboot and perform the required power on self-tests.
Convert the M-500/M-600 appliance from PAN-DB mode to the Panorama Manager mode:
• Log into the CLI via SSH
• Enter “request system system-mode panorama”
• Enter “Y” to confirm the change to Panorama mode.
• The system will reboot and perform the required power on self-tests.
Selecting Panorama Log Collector System Mode
Convert the M-100/M-200/M-500/M-600 appliance from Panorama mode to the dedicated Panorama Log Collector
mode:
• Log into the CLI via SSH
• Enter “request system system-mode logger”
• Enter “Y” to confirm the change to Panorama Log Collector mode.
• The system will reboot and perform the required power on self-tests.
Convert the M-100/M-200/M-500/M-600 appliance from Panorama Log Collector mode to the Panorama mode:
• Log into the CLI via SSH
• Enter “request system system-mode panorama”
• Enter “Y” to confirm the change to Panorama mode.
• The system will reboot and perform the required power on self-tests.
NOTE: Changing the System Mode does not change the FIPS-CC Mode. To change the FIPS-CC Mode back to Normal
Mode, follow the instructions below.
Non-Approved Mode of Operation
The following procedure will put the modules into the non-Approved mode of operation:
• During initial boot up, break the boot sequence via the console port connection (by entering ‘maint’ when
instructed to do so) to access the main menu.
• Select “Continue.”
• Select the “Set FIPS-CC Mode” option to enter the Approved mode.
• Select “Disable FIPS-CC Mode”.
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 15
• When prompted, select “Reboot” and the module will re-initialize and continue into the non-Approved mode.
The module will reboot.
Approved and Allowed Algorithms
The cryptographic module has the following CAVP certificates:
Table 3 - CAVP Certificates for FIPS Approved Algorithms
FIPS Approved Algorithm CAVP Cert. #
AES [FIPS 197, SP800-38A]:
- ECB, CBC, CTR modes; Encrypt/Decrypt; 128, 192 and 256 bits
- CFB128 mode; Encrypt/Decrypt:
Note: AES-OFB (128, 192, 256 bit), AES-CFB1 (128, 192, 256 bit), AES-
CFB8 (128, 192, 256 bit) and AES-CFB128 (192, 256 bit) were also
tested but are not available for use.
C1005
AES-CCM [SP800-38C]: Encrypt and Decrypt, 128-bit
Note: AES-CCM was tested but is not used by the module except for the self-
test.
C1005
AES-GCM [SP800-38D]: Encrypt and Decrypt, 128 and 256-bit
Note 1: GCM IV handling is compliant with FIPS IG A.5 and SP800-38D.**
Note 2: GCM 192-bit was tested but is not used by the module.
Note 3: GMAC was tested but not used by the module.
C1005
CKG:
Function: Key Generation
Method 1: Asymmetric Key Generation; SP800-133 §6, seed results from an
unmodified DRBG output
Method 2: Symmetric Key Generation; SP800-133 §7.1 (symmetric key results
from an unmodified DRBG output), §7.2, and §7.3
Vendor Affirmed
CVL: ECDSA Signature Generation
• P-256 SHA: SHA-224, SHA-256, SHA-384, SHA-512
• P-384 SHA: SHA-224, SHA-256, SHA-384, SHA-512
• P-521 SHA: SHA-224, SHA-256, SHA-384, SHA-512
Note: ECDSA Signature Generation Component was tested, but not used by the
module
C1005
CVL: KDF, Application Specific [SP800-135]
-TLS 1.0/1.1/1.2 KDF
-SNMPv3 KDF
-SSHv2 KDF
Note: - IKE v1/v2 KDF were tested but are not used by the module.
C1005
CVL: RSA [SP800-56B] C1005
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 16
Function: Key Unwrap/wrap
-RSADP
Note: Tested, but not used
DRBG [SP800-90A]
-CTR DRBG with AES-256
Derivation function enabled is supported.
No derivation function enabled is also supported.
C1005
DSA [FIPS 186-4]
-Key Generation: 2048 bits
-Prerequisite to CVL #C1005
C1005
ECDSA [FIPS 186-4]
- Key Pair Generation P-256, P-384 and P-521
- PKV P-256, P-384, and P-521
- Signature Generation P-256, P-384 and P-521; with all SHA-2 sizes*
- Signature Verification P-256, P-384 and P-521; with SHA-1 and all SHA-2
sizes*
Note: P-521 was tested, but the module does not generate this keypair.
*Does not include the “short SHA-512” sizes SHA-512/224 or SHA-512/256
C1005
HMAC [FIPS 198]
- HMAC-SHA-1 with λ=96, 160
- HMAC-SHA-256 with λ=256
- HMAC-SHA-384 with λ=384
- HMAC-SHA-512 with λ=512
C1005
KAS-SSC: SP 800-56A Rev.3 Elliptic Curve Diffie-Hellman Exchange (key
agreement; key establishment methodology provides between 128 and 256 bits
of encryption strength) and Diffie-Hellman Exchange (key agreement; key
establishment methodology provides 112 bits of encryption strength)
A2670
KAS (KAS-SSC Cert. #A2670, CVL Cert. #C1005): SP 800-56A Rev3 compliant
key agreement scheme, where testing was performed separately for the shared
secret computation and for a TLS, SSH, and IKE KDF compliant with SP 800-135
Rev1
KAS-SSC Cert. A2670
CVL Cert. C1005
KTS [SP800-38F §3.1]:
- AES-GCM (128 or 256 bits)
(Key wrapping; key establishment methodology provides 128 bits or 256 bits of
encryption strength)
C1005
KTS [SP800-38F §3.1]:
- AES-CBC (128/192/256 bits) plus HMAC
- AES-CTR (128/192/256 bit) plus HMAC
(Key wrapping; key establishment methodology provides between 128 bits and
256 bits of encryption strength)
C1005
RSA [FIPS 186-4]
- Key Pair Generation: 2048 and 3072
C1005
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 17
** The module is compliant to IG A.5: GCM is used in the context of TLS and SSH:
• For TLS, The GCM implementation meets Scenario 1 of IG A.5: it is used in a manner compliant with SP
800-52 and in accordance with Section 4 of RFC 5288 for TLS key establishment, and ensures when
the nonce_explicit part of the IV exhausts all possible values for a given session key, that a new TLS
handshake is initiated per sections 7.4.1.1 and 7.4.1.2 of RFC 5246. (From this RFC 5288, the GCM
cipher suites in use are TLS_RSA_WITH_AES_128_GCM_SHA256,
TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, and
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384.) During operational testing, the module was tested
against an independent version of TLS and found to behave correctly.
• For SSH, the module meets Scenario 4 of IG A.5. The fixed field is 32 bits in length and is derived using
the SSH KDF; this ensures the fixed field is unique for any given GCM session. The invocation field is
64 bits in length and is incremented for each invocation of GCM; this prevents the IV from repeating
until the entire invocation field space of 264
is exhausted which can take hundreds of years. (In FIPS-CC
Mode, SSH rekey is automatically configured at 1 GB of data or 1 hour, whichever comes first.)
In all the above cases, the nonce_explicit is always generated deterministically. AES GCM keys are zeroized when
the module is power cycled. For each new TLS or SSH session, a new AES GCM keys is established.
The cryptographic module supports the following non-FIPS Approved algorithms that are allowed for use in FIPS-CC mode
in Approved mode.
Table 4 - FIPS Allowed Algorithms Used in the Approved Mode
- Signature Generation (ANSI X9.31, RSASSA-PKCS1_v1-5, RSASSA-PSS): 2048,
3072, and 4096-bit (per IG A.14) with hashes (SHA-1+
/256/384/512)
- Signature Verification (ANSI X9.31, RSASSA-PKCS1_v1-5, RSASSA-PSS):
1024++
, 2048, 3072, 4096-bit (per IG A.14) with hashes (SHA-
1/224+++
/256/384/512)
+
: Only used for signature generation in SSH in the Approved Mode
++
: This size is not supported for RSASSA-PKCS1_v1-5
+++
: This Hash algorithm is not supported for ANSI X9.31
Note: FIPS 186-2 SigGen was tested, but not used by the module.
Safe Primes Key Generation and Verification using MODP-2048 A2670
SHA-1 and SHA-2 [FIPS 180-4]
SHA-1, SHA-224, SHA-256, SHA-384, SHA-512
Functions: Digital Signature Generation, Digital Signature Verification, non-
Digital Signature Applications
Note: SHA-224 was tested but is not used by the module.
C1005
FIPS Allowed Algorithms
CMAC - A self-test is performed for this algorithm, but it is not used by the module.
MD5 (within TLS)
NDRNG (seeding source) This provides a minimum of 256 bits of entropy.
RSA wrap, non-compliant to SP800-56B RSA (key wrapping; key establishment methodology provides 112 or 128 bits
of encryption strength)
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 18
Table 5 - Supported Protocols in the Approved Mode
*Note: these protocols were not reviewed or tested by the CMVP or CAVP.
Non-Approved, Non-Allowed Algorithms
The cryptographic module supports the following non-Approved algorithms. No security claim is made in the current
module for any of the following non-Approved algorithms.
Table 6 – Non-Approved, Non-Allowed Algorithms
1
See vendor-imposed security rule #4 in “Security Rules” section.
Supported Protocols
TLS v1.01
, v1.1 and 1.2
SSHv2
SNMPv3
Non-FIPS Algorithms in Non-Approved Mode
Digital Signatures (non-Approved strengths, non-compliant):
RSA Key Generation: 512, 1024, and 4096
RSA signature generation: Modulus bit length less than 2048 or greater than 4096 bits; up to 16384 bits
RSA signature verification: Modulus bit length less than 1024 or greater than 4096 bits; up to 16384 bits
ECDSA: B, K, P curves not equal to P-256, P-384 or P-521
DSA: 768 to 4096 bits
Encrypt/Decrypt: Camellia, SEED, Triple-DES (non-compliant), Blowfish, CAST, RC4, DES
Hashing: RIPEMD, MD5
Key Exchange (non-Approved strengths):
Elliptic Curve Diffie-Hellman: B, K, P curves not equal to P-256, P-384 or P-521
Diffie-Hellman: 768, 1024 and 1536-bit modulus
RSA: Less than 2048-bit modulus
Message Authentication: UMAC, HMAC-MD5, HMAC-RIPEMD
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 19
4. Ports and Interfaces
The M-100 module provides the following ports and interfaces.
Figure 17 – M-100 Ports and Interfaces (Front and Back)
Table 7 – M-100 Ports and Interfaces
Interface Quantity FIPS 140-2
Designation
Name and Description
1 DB9 1 Status output Console port
2 RJ45 1 Data input, Control
input, Data output,
Status output
Management and data communication (MGT)
3 RJ45 2 Data input, Control
input, Data output,
Status output
Port 1 (Front) and Port 2 (Rear)
10/100/1000 Ethernet
4 RJ45 1 Data input, Control
input, Data output,
Status output
Port 3 (Rear) 10/100/1000 Ethernet
5 Front LEDs 3 Status output System Health, Internal HDD activity, LAN Activity
6 UID button
with LED
(Front and
Back)
2 Control input, Status
output
Button that activates a flashing LED on front and back
of chassis to help identify physical location
7 Power Button
with LED
1 Control input, status
output
Power on and shut down device
8 NMI Button 1 Disabled Disabled
9 USB 4 Disabled Disabled
10 Power Port 1 Power input Power interface
Note: The slots A1/A2, B1/B2, C1/C2, D1/D2 are hard drive bays, which are depicted as populated in Figure 17. The
1TB model, P/N: 910-000030, will have two slots populated, while the 4TB model, P/N: 910-000092, will have all
eight slots populated.
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 20
The M-200 module provides the following ports and interfaces.
Figure 18 – M-200 Front Panel Ports and Interfaces
Table 8 – M-200 Front Panel Ports and Interfaces
Interface Quantity FIPS 140-2
Designation
Name and Description
1 NA 1 NA System drive used for operating system
2 Unique
Identification
(UID) button
1 Control input Button that activates a flashing LED on front and back
of chassis to help identify physical location
3 System Info
LED
1 Status output Indicate system information such as overheat condition,
fan or power failures
4 Network
actvitiy LEDs
2 Status output Blinking green indicates network activity
5 Hard disk
LED
1 Status output Blinking yellow indicates activity
6 Power LED 1 Status output Solid green indicates power is on
7 Reset button 1 Control input Button to reboot the appliance
8 Power
button
1 Control input Power on and shut down appliance
9 NA 4 NA Hard disks used for log storage
10 Hard disk
LEDs
2 Status output Indicate disk activity or failure
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 21
Figure 19 – M-200 Back Panel Ports and Interfaces
Table 9 – M-200 Back Panel Ports and Interfaces
Interface Quantity FIPS 140-2
Designation
Name and Description
1 Power 2 Power In Power supplies
2 RJ45 4 Data input,
Control input,
Data output,
Status output
Management and 10/100/1000 Ethernet Ports
3 USB 2 Disabled Disabled
4 IPMI 1 Disabled Disabled
5 DB9 1 Status output Console port
6 Unique
Identification
(UID) LED
1 Status output UID LED that illuminates bright blue when you push the
UID button on the front of the appliance
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 22
The M-500 module provides the following ports and interfaces.
Figure 20 – M-500 Front Panel Ports and Interfaces
Figure 21 – M-500 Back Panel Ports and Interfaces
Table 10 – M-500 Ports and Interfaces
Interface Quantity FIPS 140-2
Designation
Name and Description
1 Power
Button
and Reset
2 Control input Reboot or shut down device
2 Front LED
Panel
4 Status output Power, Power failure, HDD, Overheat/Fan failure
3 Drives
LEDs
48 Status output Left LED—drive failure
Right LED—activity
4 Power 2 Power In Power supplies
5 DB9 1 Status Output Console
6 USB 4 Disabled USB (Reserved for future use)
7 RJ45 1 Data input,
Control input,
Data output,
Status output
MGT Ethernet 10/100/1000
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 23
8 NMI
Button
3 Data input,
Control input,
Data output,
Status Output
Ethernet 1, 2, 3
9 VGA 1 Disabled Graphic port (Reserved for future use)
10 UID
button
with LED
1 Control input,
Status output
Button that activates LED on front and back of chassis to
help identify physical location
Note: By default, the M-500 appliance ships with Qty. Eight (8) 1TB drives installed in drive bays A1 – D2. Qty. Eight
(8) additional drives can be installed in drive bays E1 – H2. Drive bays I1 – L2 can be utilized for adding additional
drives.
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 24
The M-600 module provides the following ports and interfaces.
Figure 22 – M-600 Front Panel Ports and Interfaces
Table 11 – M-600 Front Panel Ports and Interfaces
Interface Quantity FIPS 140-2
Designation
Name and Description
1 Power
button
1 Control input Power on and shut down appliance
2 Reset
button
1 Control input Button to reboot the appliance
3 Power
LED
1 Status output Solid green indicates power is on
4 Power
failure LED
1 Status output Solid red indicates power supply failed or no power
source
5 Hard disk
LED
1 Status output Blinking yellow indicates activity
6 System
Info LED
1 Status output Indicate system information such as overheat condition,
fan or power failures
7 NA 4 NA Hard disks used for log storage
8 Hard disk
LEDs
2 Status output Indicate disk activity or failure
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 25
Figure 23 – M-600 Back Panel Ports and Interfaces
Table 12 – M-600 Back Panel Ports and Interfaces
Interface Quantity FIPS 140-2
Designation
Name and Description
1 NA 1 NA System drive used for operating system
2 Power 2 Power In Power supplies
3 RJ45 4 Data input,
Control input,
Data output,
Status output
Management and 10/100/1000 Ethernet Ports
4 USB 2 Disabled Disabled
5 IPMI 1 Disabled Disabled
6 DB9 1 Status output Console port
7 UID
button
with LED
(Front and
Back)
2 Control input,
Status output
Button that activates a flashing LED on front and back of
chassis to help identify physical location
8 SFP Ports 2 Data input,
Control input,
Data output,
Status output
10 Gigabit Ethernet enhanced Small Form-Factor
Pluggable (SFP+) ports
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 26
5. Roles, Services, and Authentication
Assumption of Roles
The module supports distinct operator roles. The cryptographic module in Panorama mode, Management-Only mode, or
PAN-DB mode enforces the separation of roles using unique authentication credentials associated with operator accounts.
The Log Collector mode only supports one role, the Crypto-Officer (CO) role.
The module supports concurrent operators.
The module does not provide a maintenance role or bypass capability.
Table 13 – Panorama and Management-Only modes - Roles and Authentication
Role Description Authentication Type Authentication Data
CO
This role has administrative capabilities
for Panorama Manager services. The CO
has the ability to create other CO and
User accounts that have limited service
access.
Identity-based
operator
authentication
Username and password
and/or certificate/public key-
based authentication.
User
This User role has read-only access
defined for a set of configuration and
status information
Identity-based
operator
authentication
Username and password
and/or certificate/public key-
based authentication.
Table 14 – Log Collector mode - Roles and Authentication
Role Description Authentication Type Authentication Data
CO
This role has administrative capabilities
for Log Collector services.
Role-based operator
authentication
Username and Password
and/or public key based
authentication
Table 15 – PAN-DB mode - Roles and Authentication
Role Description Authentication Type Authentication Data
CO
This role has administrative capabilities
for PAN-DB services.
Identity-based
operator
authentication
Username and Password
User
This User role has read-only access
defined for a set of configuration and
status information.
Identity-based
operator
authentication
Username and Password
Table 16 - Strength of Authentication Mechanisms
Authentication
Mechanism
Strength of Mechanism
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 27
Username and
Password
The minimum password length is six (6) characters2
(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 Panorama’s configuration supports at
most ten attempts to authenticate in a one-minute period.
Certificate/public key
based authentication
The security modules support certificate-based authentication using RSA 2048,
RSA 3072, RSA 4096, ECDSA P-256, ECDSA P-384 or ECDSA P-521.
The minimum equivalent strength supported is 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 device supports at
most 60,000 new sessions per second to authenticate in a one-minute period.
Security Parameters
The module contains the following keys and critical security parameters (CSP):
Table 17 - Private Keys and CSPs
Key/CSP Description
ECDSA Private Keys
Supports establishment of TLS session keys, SSH host authentication, and
certificate signing keys
(ECDSA P-256, P-384, P-521)
RSA Private Keys
Supports establishment of TLS session keys, SSH host authentication, and
certificate signing keys
(RSA 2048, 3072 or 4096 bits)
TLS DHE Private Components
Diffie-Hellman Ephemeral private component used in TLS connections (DH
Group 14, L = 2048, N >=224)
TLS ECDHE Private Components
EC Diffie-Hellman Ephemeral private component used in TLS connections
(ECDHE P-256, P-384, P-521)
TLS Pre-Master Secret
Secret value used to derive the TLS Master Secret along with client and
server random nonces
TLS Master Secret Secret value used to derive the TLS session keys
TLS Encryption Keys AES session keys used in TLS connections (128 or 256 bits; CBC or GCM)
TLS HMAC Keys HMAC-SHA-1/256/384 session keys used in TLS connections
2
In FIPS-CC Mode, the module checks and enforces the minimum password length of six (6) characters.
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 28
SSH DH private components Diffie-Hellman private component
(DH Group 14, L=2048, N >=224)
SSH ECDH Private Components EC Diffie-Hellman private component
(ECDH P-256, ECDH P-384, ECDH P-521)
SSH Session Encryption Key AES session key used in SSH connections
(128, 192, 256 bits: CBC or CTR)
(128 or 256 bits: GCM)
SSH Session Authentication Key Session key used in SSH connections
(HMAC-SHA-1, HMAC-SHA2-256, HMAC-SHA2-512)
CO, User Passwords Password for operator authentication
DRBG seed/state/input string DRBG seed and input string coming from the NDRNG and AES 256 CTR
DRBG state used in the generation of a random values
SNMPv3 Authentication Secret SNMPv3 Authentication Secret
SNMPv3 Privacy Secret SNMPv3 Privacy Secret
SNMPv3 Authentication Key HMAC- SHA-1 Authentication key
SNMPv3 Session Key AES CFB Privacy Encryption key
RADIUS Secret Authentication key for RADIUS server (must be minimum of six (6)
characters)
Master Key AES-256 CBC key used to protect private keys and CSPs
Note: All CSP and keys defined may be accessed by the Manager and Log-Collector modes while the PAN-DB
mode only supports some of the CSP/keys defined. For details regarding what CSPs are supported in each
mode, please see Tables 17 – 21. The CSPs and keys may be shared between the Approved modes of
operation.
Table 18 - Public Keys
Key Name Description
CA Certificates RSA and/or ECDSA keys used to extend trust for certificates.
RSA Public Keys
RSA Public keys managed as certificates for the verification of signatures,
establishment of TLS, operator authentication and peer authentication.
(RSA 2048, 3072, or 4096 bits)
ECDSA Public Keys
ECDSA public keys managed as certificates for the verification of
signatures, establishment of TLS, operator authentication and peer
authentication (ECDSA P-256, P-384, P-521)
Client Authentication Public Key
Used to authenticate the end user (ECDSA P-256, P-384, P-521; RSA
2048, 3072, 4096 bits)
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 29
TLS DHE Public Components Used in key agreement (DH Group 14)
TLS ECDHE Public Components Used in key agreement (ECDHE P-256, P-384, P-521)
SSH DH Public Components Used in key agreement (DH Group 14)
SSH ECDH Public Components Used in key agreement (P-256, P-384, P-521)
SSH Host RSA Public Key Used in SSH public key authentication process
(RSA 2048, 3072, or 4096 bits)
SSH Host ECDSA Public Key Used in SSH public key authentication process
(ECDSA P-256, P-384, P-521)
SSH Client RSA Public Key Used in SSH public key authentication process
(RSA 2048, 3072, or 4096 bits)
Firmware Authentication Key RSA key used to authenticate firmware (2048 bits)
Firmware Integrity Check Key
Used to check the integrity of crypto-related code
(HMAC-SHA-256* and ECDSA P-256)
*Keys used to perform power-up self-tests are not CSPs as per IG 7.4
Note: All keys defined may be accessed by the Manager and Log-Collector modes while PAN-DB mode only
supports some of the keys defined. For details regarding what CSPs are supported in each mode, please see
Tables 17 – 21. The keys may be shared between the Approved modes of operation.
Access Control Policy
The Approved and non-Approved mode of operation provide identical services. While in the Approved mode of operation
all authenticated services and CSPs are accessed via authenticated SSH or TLS sessions. Access is restricted to
authenticated operators only and no interface is provided to modify the public or private key.
For all authenticated services the following CSPs and public keys may be executed:
• TLS Management Access
o ECDSA Private Keys/Public Keys
o RSA Private Keys/Public Keys
o TLS DHE Private/Public Components
o TLS ECDHE Private/Public Components
o TLS Pre-master Secret
o TLS Master Secret
o TLS Encryption keys
o TLS HMAC keys
• SSH Management Access
o SSH DH public components
o SSH ECDH public components
o SSH Host RSA public key
o SSH Host ECDSA public key
o SSH Client RSA public key (Manager Mode only)
SNMPv3 authentication is supported but is not a method of module administration and does not allow read/write access
of CSPs. Approved and allowed algorithms, relevant CSP and public keys related to these protocols are used to access the
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 30
following services. CSP access by services is further described in the following tables. Additional service information and
administrator guidance for Panorama can be found at https://www.paloaltonetworks.com/documentation.html
The Crypto-Officer may access all services, and through the “management of administrative access” service may define
multiple Crypto-Officer roles with limited services. The User role provides read-only access to the System Audit service.
When configured in the default mode, Panorama Manager provides services via web-browser based interface and a
command line interface (CLI). For the Panorama Log Collector mode and PAN-DB mode, only the CLI is available for
management.
The services listed below are also available in the non-Approved mode. In the non-Approved mode, non-Approved
algorithms and non-Approved algorithm strengths are used to access these services.
Table 19 - Authenticated Services – Panorama or Management-Only Mode
CO Services Description CSP/Key Access
System Provisioning Perform panorama licensing, diagnostics, debug
functions, manage Panorama support
information and switch between Panorama
Management-only, Logger, and PAN-DB
modes.
N/A
Panorama Firmware
Update
Download and install firmware updates
Signature verification with RSA public key
Panorama Manager
Setup
Presents configuration options for management
interfaces and communication for peer services
(e.g., SNMP, RADIUS).
Import, Export, Save, Load, revert and validate
Panorama configurations and state
Import or Export RSA/ECDSA
Private/Public Keys
Import SNMPv3 Authentication and
Privacy Secrets
Execute/Read SNMPv3 keys
Creation RADIUS Secret
Execute/Read/Write Master key
Manage Panorama
Administrative Access
Define access control methods via admin role
profiles, configure administrators and password
profiles
Configure local user database, authentication
profiles, sequence of methods and access
domains
Import, modify, or delete operator
passwords
Import, modify, or delete SSH Client RSA
public keys
Modify SSH Host RSA public key and SSH
Host ECDSA public key
Configure High
Availability
Configure High Availability communication
settings
Import or export SSH RSA/ECDSA public
keys
Panorama Certificate
Management
Manage RSA/ECDSA certificates and private
keys, certificate profiles, revocation status, and
usage; show status.
Import or export RSA /ECDSA
private/public keys
Generate RSA/ECDSA private/public keys
Sign RSA/ECDSA private keys
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 31
Execute/Read/Write DRBG seed and
state
Execute/Read/Write Master key
Panorama Log settings
Configure log forwarding N/A
Panorama Server
Profiles
Configure communication parameters and
information for peer servers such as Syslog,
SNMP trap servers, email servers and
authentication servers
Import SNMPv3 Secrets
Execute/Read SNMPv3 keys
Execute/Read Master key
Setup Managed Devices
and Deployment
Set-up and define managed devices, device
groups for firewalls
Configure device deployment applications and
licenses
View current deployment information on the
managed firewalls. It also allows you to manage
firmware versions and schedule updates on the
managed firewalls and managed log collectors.
N/A
Configure managed
Device Templates
Define and manage common base configuration
templates for managed firewalls. Template
configurations define settings that are required
for the management of the firewalls on the
network.
Import or export RSA/ECDSA
private/public keys
Signature generation with RSA/ECDSA
private keys
Generate RSA/ECDSA private/public keys
Execute/Read/Write DRBG seed and
state
Execute/Read/Write Master key
Configure Managed
Device Groups
Define and manage common base of policies
and data objects for managed firewalls in
configured device groups
N/A
Configure managed Log
Collectors
Setup and manage other Log Collector
management, communication and storage
settings
View current deployment information on the
managed Log Collectors. It also allows you to
manage firmware versions and schedule
updates on managed log collectors.
Modify operator passwords
Monitor system status
and logs
Review system status via the panorama system
CLI, dashboard and logs; show status.
N/A
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 32
Monitor network
activity
Review aggregated information across all
managed firewalls and show status. The
aggregated view provides actionable
information on trends in user activity, traffic
patterns, and potential threats across your
entire network.
N/A
Switch Context Browses a managed firewall’s web based user
interface.
N/A
System Audit Allows review of limited configuration and
system status via SNMPv3, logs, dashboard,
show status, and configuration screens.
N/A
User Services Description
System Audit Allows review of limited configuration and
system status via SNMPv3, logs, dashboard,
show status, and configuration screens.
Provides no configuration commit capability.
N/A
Monitor system status
and logs
Review system status via the panorama system
CLI, dashboard and logs; show status.
N/A
Table 20 - Authenticated Services – Log Collector Mode
CO Services Description CSP/Key Access
Panorama Log Collector
Setup
Presents configuration options for management
interfaces and communication for peer services
Import, Export, Save, Load, revert and validate
Panorama configurations and state
Import or Export RSA/ECDSA
Private/Public Keys
Execute/Read Master key
Panorama Firmware
Update
Download and install firmware updates.
Signature verification with RSA public key
Manage Panorama
Administrative Access
Update Administrator password Import or modify operator passwords
Panorama Certificate
Management
Manage RSA/ECDSA certificates and private
keys, certificate profiles, revocation status, and
usage; show status.
Import or export RSA/ECDSA
private/public keys
Generate RSA/ECDSA private/public keys
Sign with RSA/ECDSA private keys
Execute/Read/Write DRBG seed and
state
Execute/Read/Write Master key
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 33
Table 21 - Authenticated Services – PAN-DB Mode (M-500/M-600 Only)
CO Services Description CSP/Key Access
Pan-DB Setup
Presents configuration options for management
interfaces and communication for peer services
Import, Export, Save, Load, revert and validate
Panorama configurations and state
N/A
Panorama Firmware
Update
Download and install firmware updates Signature verification with RSA public key
Manage PAN-DB
Administrative Access
Define access control methods via admin role
profiles
Import or modify operator passwords
System Audit Allows review of limited configuration and
system status via SNMPv3, logs, dashboard,
show status, and configuration screens.
N/A
User Services Description
System Audit Allows review of limited configuration and
system status via SNMPv3, logs, show status,
and configuration screens. Provides no
configuration commit capability.
N/A
Table 22 - Unauthenticated Services
Unauthenticated Services Description
Zeroize
The device will overwrite all CSPs. The zeroization procedure is invoked when the operator
performs a factory reset. The operator must be present to observe the method has
completed successfully or in control via a remote management session. During the
zeroization procedure, no other services are available.
Procedures to perform zeroization:
• During initial boot up, break the boot sequence via the console port connection
(by entering ‘maint’ when instructed to do so) to access the main menu.
• Select “Continue.”
• Select the “Factory Reset” option.
• Select “Factory Reset”.
• When prompted, select “Reboot” and the module will re-initialize and continue.
The module will reboot.
Self-Tests
Run power up self-tests on demand by power cycling the module. Execute/Read access to
FW integrity Check key.
Show Status (LEDs) View hardware status (on/off) of the module via the LEDs.
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 34
6. Operational Environment
The FIPS 140-2 Area 6 Operational Environment requirements are not applicable because the module contains a non-
modifiable operational environment. The operational environment is limited since the module includes a firmware load
service to support necessary updates. New firmware versions within the scope of this validation must be validated through
the FIPS 140-2 CMVP. Any other firmware loaded into this module is out of the scope of this validation and require a
separate FIPS 140-2 validation.
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 35
7. Self-Tests / 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 provides distinct operator roles. When the module has not been placed in a valid
role, the operator does not have access to any cryptographic services.
2. The Panorama M-100, M-200, M-500 and M-600 cryptographic modules supports initialization as a Log
Collector in an Approved mode of operation with Level 2 role-based authentication or support initialization as
a Panorama Manager or PAN-DB (M-500 and M-600 only) in an Approved mode of operation with Level 3
identity-based authentication.
3. The cryptographic module clears previous authentications on power cycle.
4. The cryptographic module performs the following tests for all Approved modes:
A. Power up Self-Tests
1. Cryptographic algorithm tests
a. AES ECB Encrypt Known Answer Test
b. AES ECB Decrypt Known Answer Test
c. AES CMAC Known Answer Test
d. AES GCM Encrypt Known Answer Test
e. AES GCM Decrypt Known Answer Test
f. AES CCM Encrypt Known Answer Test
g. AES CCM Decrypt Known Answer Test
h. ECDSA Sign Known Answer Test
i. ECDSA Verify Known Answer Test
j. RSA Sign Known Answer Test
k. RSA Verify Known Answer Test
l. RSA Encrypt Known Answer Test
m. RSA Decrypt Known Answer Test
n. HMAC-SHA-1 Known Answer Test
o. HMAC-SHA-256 Known Answer Test
p. HMAC-SHA-384 Known Answer Test
q. HMAC-SHA-512 known Answer Test
r. SHA-1 Known Answer Test
s. SHA-256 Known Answer Test
t. SHA-384 Known Answer Test
u. SHA-512 Known Answer Test
v. DRBG Known Answer Test
w. ECDH Known Answer Test
x. DH Known Answer Test
y. SP800-90A Section 11.3 Health Tests
B. Firmware Integrity Test – HMAC-SHA-256 and ECDSA P-256.
C. Conditional Self-Tests
1. Continuous Random Number Generator (RNG) test – performed on NDRNG and DRBG
2. ECDSA Pairwise Consistency Test Sign/Verify
3. RSA Pairwise Consistency Test Sign/Verify and Encrypt/Decrypt
4. Firmware Load Test – Verify RSA 2048 with SHA-256 signature on firmware at time of
load
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 36
D. If any conditional test fails, the module will output ‘FIPS-CC failure’ and the specific test that
failed.
5. The operator is capable of commanding the module to perform the power-up self-test by cycling power of the
module.
6. Upon re-configuration to/from the Log Collector mode or PAN-DB mode of operation from/to the
Panorama/Management-only mode, the cryptographic module reboots and perform all power-up self-tests.
7. Power-up self-tests do not require any operator action.
8. Data output is inhibited during power-up self-tests and error states.
9. Processes performing key generation and zeroization processes are logically isolated from the logical data
output paths.
10. The module does not output intermediate key generation values.
11. Status information output from the module does not contain CSPs or sensitive data that if misused could lead
to a compromise of the module.
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.
Vendor imposed security rules:
1. When configured, the module automatically logs out the operator when the cryptographic module remains
inactive in any valid role for the administrator specified time interval.
2. When configured, 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 has occurred, the cryptographic module shall enforce a wait period of at
least one (1) minute before any more login attempts can be attempted. This wait period shall be enforced
even if the module power is momentarily removed.
3. When FIPS-CC mode is enabled, the operator shall not install plugins. If a plugin is installed, the module
shall be configured in non-Approved mode of operation.
4. When FIPS-CC mode is enabled, TLSv1.0 is disabled. The operator should not re-enable TLSv1.0. TLSv1.0
can be used in an Approved mode of operation (Approved TLS KDF algorithm); however, TLS v1.0
protocol is no longer considered as secure because of the Cipher Block Chaining IV attack, a client of the
module could use a vulnerable implementation.
5. When FIPS-CC mode is enabled, the operator shall not use TACACS+. RADIUS may be used but must be
protected by TLS protocol. If TACACS+ or RADIUS without TLS protocol are set, the module shall be
configured in non-Approved mode of operation.
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 37
8. Physical Security
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. There are
twenty-eight (28) tamper-evident seals for the M-100, fifteen (15) for the M-200, twelve (12) for the M-500, and twenty-
one (21) for the M-600. All unused seals are to be controlled by the Crypto-Officer. The seals prevent removal of the
opaque enclosure without evidence. The Crypto-Officer must ensure that the module surface is clean and dry. Tamper
evident seals must be pressed firmly onto the adhering surfaces during installation and once applied, the Crypto-Officer
shall permit 24 hours of cure time for all tamper evident seals. The seals prevent removal of the opaque enclosure without
evidence. 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 support.
Note: For ordering information, see Table 1 for FIPS kit part numbers and versions. Opacity shields are included in the
FIPS kits.
Refer to Appendix A to D for instructions on installation and placement of the tamper seals and opacity shields. The
locations of the tamper-evident seals implemented on the M-100, M-200, M-500, and M-600 are shown in Appendix A to
Appendix D, respectively.
Operator Required Actions
The following table provides information regarding the various physical security mechanisms, and their recommended
frequency of inspection/test.
Table 23 - Inspection/Testing of Physical Security Mechanisms
Model Physical Security
Mechanism
Recommended
Frequency of
Inspection/Test
Inspection/Test Guidance Details
M-100
M-200
Tamper Evident
Seals
30 days Verify integrity of tamper-evident seals in the
locations identified in Appendix A and C of this
Security Policy.
M-100
M-200
Front and Rear
Opacity Shields
Side Rails
30 days Verify that opacity shields and side rails have
not been loosened or deformed from their
original shape, thereby reducing their
effectiveness.
M-100
Top Overlays 30 days Verify top overlays have not been removed or
deformed. All edges should maintain strong
adhesion characteristics.
M-500
M-600
Tamper Evident
Seals
30 days Verify integrity of tamper-evident seals in the
locations specified in Appendix B and D.
M-500
M-600
Front and Rear
Opacity Shields
30 days Verify that the front and rear opacity shields
have not been deformed from their original
shape, thereby reducing their effectiveness.
M-500
M-600
Vent Overlays 30 days Verify that the vent overlays have not been
removed or deformed. All edges should
maintain strong adhesion characteristics.
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 38
9. Mitigation of Other Attacks
The module is not designed to mitigate any specific attacks outside the scope of FIPS 140-2. These requirements are not
applicable.
10. References
[FIPS 140-2] FIPS Publication 140-2 Security Requirements for Cryptographic Modules
11. Definitions and Acronyms
AES – Advanced Encryption Standard
CA – Certificate Authority
CLI – Command Line Interface
CO – Crypto-Officer
CSP – Critical Security Parameter
CVL – Component Validation List
DB9 – D-sub series, E size, 9 pins
DES – Data Encryption Standard
DH – Diffie-Hellman
DRBG – Deterministic Random Bit Generator
EDC – Error Detection Code
ECDH – Elliptical Curve Diffie-Hellman
ECDSA – Elliptical Curve Digital Signature Algorithm
FIPS – Federal Information Processing Standard
HMAC – (Keyed) Hashed Message Authentication Code
KDF – Key Derivation Function
LED – Light Emitting Diode
NDRNG – Non-Deterministic Random Number Generator
RJ45 – Networking Connector
RNG –Random number generator
RSA – Algorithm developed by Rivest, Shamir and Adleman
SHA – Secure Hash Algorithm
SNMP – Simple Network Management Protocol
SSH – Secure Shell
TLS – Transport Layer Security
USB – Universal Serial Bus
VGA – Video Graphics Array
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 39
Appendix A – M-100 FIPS Tamper Seal Installation (28 Seals)
Step 1: From the rear of the module, remove the six (6) screws and port cover, as shown. Retain screws and port
cover for the Step 2.
Figure 24 – M-100: Remove Screws on Rear Side
Step 2: Attach the rear opacity shields.
A. Using two (2) #6 - #32 3/8” screws, attach the lower rear cover bracket. Replace the port cover and secure
with the four (4) screws that you removed in Step 1.
B. Use four (4) #4 - #40 1/4” screws to attach the rear cover to the bracket.
Figure 25 – M-100: Attach Rear Opacity Shield
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 40
Step 3: Apply tamper-evident seals (two (2) seals) to the seam of the rear cover and rear outer edges of the
appliance (seals #1 and #2 in the illustration below). Apply tamper-evident seals to the left and right sides covering
the side holes (two (2) seals #3 and #4). Apply top air vent overlay covers and tamper-evident seals (sixteen (16)
seals, #5 - #10 and #11 - #20).
Figure 26 – M-100: Apply Tamper Seals and Vent Overlays
Step 4: Place side inner rails to each side of the module and attach using rail kit screws.
Figure 27 – M-100: Apply Rail Kit
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 41
Step 5: Remove the two (2) front plastic bracket covers and screws. Remove and retain the two (2) captive screws
from the plastic covers.
Figure 28 – M-100: Remove Front Plastic Bracket Covers and Screws
Step 6: Install front opacity shield and attach to brackets using four (4) 4-40 x 0.25-inch screws and thread a
captive screw through each side of the front cover bracket, as shown. Affix four (4) tamper seals on top and bottom
of module as shown.
Figure 29 – M-100: Install Front Opacity Shield
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 42
Step 7: Slide module into outer rails and attach outer rails and apply four (4) seals overlapping the rack mount
bracket and the module sides.
Figure 30 – M-100: Install Outer Rails
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 43
Appendix B – M-200 FIPS Tamper Seal Installation (15 Seals)
1. Replace the top cover with the FIPS top cover.
a. Remove the VOID WARRANTY label and cover screws (replacement label included in the kit).
M-200 appliance—Remove the Void Warranty label that covers the left top cover screw then use a
Phillips-head screwdriver to remove both screws as indicated in the illustration.
b. Simultaneously depress the two (2) release buttons on top of the cover and slide the cover toward the
back of the appliance to remove it.
c. Slide the FIPS top cover (does not have vents) on the appliance until the release buttons click. Reinsert
and slide cover into position and secure with the two (2) screws.
Figure 31 – M-200: Top Cover Replacement
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 44
2. On the left side of the M-200, firmly apply seven (7) tamper-evident seals as indicated in the illustration.
Figure 32 – M-200: Side View Before Rail Installation
Install the inner rack mount rail brackets as described in the “M-200 and M-600 Appliance Hardware
Reference”. The front rack bracket that you replace in the next step is located on the front inner rails.
Figure 33 – M-200: Inner Rack Mount Rail Brackets
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 45
3. Attach the FIPS front cover brackets.
Replace the front rack-mount brackets (one bracket on each side) that are part of the inner-rack rails with the
FIPS rack-mount brackets by removing and then reinstalling two screws on each bracket. The FIPS handles
have standoffs that are used to secure the front cover.
Figure 34 – M-200: Replacing Front Rack-Mount Brackets
4. Attach the FIPS front cover to the front of the appliance.
Slide the M-200 FIPS front cover over the FIPS brackets and secure the cover by turning the thumb screws
clockwise (one thumb screw on each side).
Figure 35 – M-200: Attach FIPS Front Cover
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 46
5. Attach the FIPS back cover to the back of the appliance.
Slide the back cover onto the back of the appliance, insert two M4 x 0.7 x 8mm (one (1) screw on each side),
and turn the screws clockwise to secure the cover.
6. Apply a tamper-evident seal to each location shown in the following M-200 illustrations. Ensure you apply two
(2) tamper-evident seals on the power supplies (see seals #14 and #15 on the rear illustration).
Before you apply the tamper-evident seals, ensure that the appliance and FIPS kit surfaces are clean and dry.
Firmly press one (1) seal on to each of the locations shown in the illustrations. Avoid touching the seals for at
least 24 hours to allow time for the seals to properly adhere to the appliance and FIPS kit surfaces.
Figure 36 – M-200: Seal locations on Top and Right Side
Figure 37 – M-200: Seal Locations on Left Side and Rear
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 47
Appendix C – M-500 FIPS Tamper Seal Installation (12 Seals)
Step 1:
Remove the two pull handles and front modules on the left and right side of the appliance by removing the three (3)
screws located behind each handle/module. There is no need to disconnect the LED circuit board attached to the
end of the ribbon cable. Retain these screws for Step 2.
Figure 38 – M-500: Remove Front Handles and Modules
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 48
Step 2:
Attach the left and right front cover brackets to the appliance using the six (6) screws that you removed in Step 1.
First attach the brackets using the bottom screws (one on each side) as shown in Figure 39, ensuring that you feed
the ribbon cable and LED circuit board through the left bracket. Replace the front modules and secure them using
the middle and top screws on each side as shown in Figure 40.
Figure 39 – M-500: Secure the Front Brackets
Figure 40 – M-500: Attach Pull Handles and Front Modules
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 49
Step 3:
Secure the front opacity shield to the right and left front brackets that you installed in Step 2. Use two (2) screws
(provided) on each side.
Figure 41 – M-500: Install Front Opacity Shield
Figure 42 – M-500: Front Opacity Shield Installed
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 50
Step 4:
Attach the rear opacity shield tray to the appliance. First, remove the two (2) screws (shown in Figure 43) from the
appliance and use these screws to secure the rear opacity shield tray.
Note: Install the back cables (power cords and network/management cables) because you will not be able to access
these ports after the next step.
Figure 43 – M-500: Install Rear Opacity Shield Tray
Step 5:
Place the rear opacity shield on top of the rear opacity shield tray ensuring that you run the cables through the
opening at the bottom. Secure the opacity shields with two (2) screws (provided) on each side.
Figure 44 – M-500: Install Rear Opacity Shield
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 51
Step 6:
Cover the vent openings as shown in Figure 45 by applying one (1) overlay sticker over the left side vent and one (1)
overlay sticker over the right side vent. Each overlay requires two (2) tamper seals as shown in Figure 46 (A). Also
apply one (1) additional tamper seal as shown in Figure 46 (B) #5.
Figure 45 – M-500: Apply Vent Overlays
Figure 46 – M-500: Apply Tamper Seals on Vent Overlays and Side Opening
A
B
[ 1 ]
[ 2 ]
[ 3 ]
[ 4 ]
[ 5 ]
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 52
Step 7:
Re-attach the rail kit to the appliance as shown in Figure 47 and then add three (3) tamper seals to the bottom of
the appliance as shown in Figure 48. One (1) tamper seal prevents tampering of the front opacity shield connected
to the bottom of the appliance and two (2) tamper seals wrap around the upper and lower rear opacity shields to
prevent tampering of the rear opacity shields.
Figure 47 – M-500: Install Rail Kit
Figure 48 – M-500: Apply Tamper Seals on the Bottom of the Appliance
[ 6 ]
[ 7 ]
[ 8 ]
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 53
Step 8:
Place four (4) tamper seals on the top of the appliance. Two (2) tamper seals (#9 and #11) prevent tampering of the
top front and rear opacity shields and two (2) tamper seals (#10 and #12) prevents someone from attempting to
access the vent overlays by sliding the rail kit. This completes the FIPS kit installation.
Figure 49 – M-500: Apply Tamper Seals on the Top and Sides of the Appliance
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 54
Appendix D – M-600 FIPS Tamper Seal Installation (21 Seals)
1. Replace the top cover with the FIPS top cover.
a. Remove the VOID WARRANTY label and cover screws (replacement label included in the kit).
Remove the Void Warranty label that covers the left side cover screw then use a Phillips-head
screwdriver to remove both screws as indicated in the illustration.
b. Simultaneously depress the two (2) release buttons on top of the cover and slide the cover toward the
back of the appliance to remove it.
c. Slide the FIPS top cover (does not have vents) on the appliance until the release buttons click. Replace
the two screws that you removed from the old cover
Figure 50 – M-600: Top Cover Replacement
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 55
2. Attach the FIPS front cover brackets.
Remove the front pull handles by removing two (2) screws from each handle (one (1) handle on each side),
insert the M-600 FIPS front-cover brackets under each handle, and then replace the handles and secure them
using the screws that you removed. The FIPS handles have standoffs that are used to secure the front cover.
Figure 51 – M-600: Front Cover Bracket
3. Attach the FIPS front cover to the front of the appliance.
Slide the M-600 FIPS front cover over the FIPS pull handle brackets and secure the cover by turning the
thumb screws clockwise (one thumb screw on each side).
Figure 52 – M-600: FIPS Front Cover
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 56
4. Install a tamper-evident seal on the back of the appliance. This is seal #13 in the M-600 Figure 53. You need to
install this seal before you install the M-600 FIPS back cover.
5. Attach the FIPS back cover to the back of the appliance.
a. Slide the back cover onto the back of the appliance and turn the two (2) thumb screws clockwise
until tight (one (1) screw on each side) to secure the cover.
Apply a tamper-evident seal to each location shown in the following M-600 illustrations below.
Also install the overlay stickers to cover vent openings (two (2) stickers on each side). You then install tamper-
evident seals over the overlay stickers. Apply two (2) tamper-evident seals on the back side of the right rack
handle (see seals #18 and #19 on the left side in
6. Figure 54). Apply two (2) tamper-evident seals on the power supplies (see seals #11 and #12 with rear inset of
Figure 53).
Before you apply the tamper-evident seals, ensure that the appliance and FIPS kit surfaces are
clean and dry. Firmly press one (1) seal on to each of the locations shown in the illustrations.
Avoid touching the seals for at least 24 hours to allow time for the seals to properly adhere to the
appliance and FIPS kit surfaces.
M-600 Seal Placement (21 Seals)
Figure 53 – M-600: Tamper Seal Locations (Top and Rear)
© 2022 Palo Alto Networks, Inc. Panorama 9.0 Security Policy 57
Figure 54 – M-600: Tamper Seal Locations (Top and Front)
Figure 55 – M-600: Tamper Seals Location for Side Rails