## Palo Alto Networks Cortex XSOAR Server 6.14 Security Target Version: 0.3 Date: September 16, 2026 Cortex SOAR Server 6.14 Security Target Palo Alto Networks ####### Palo Alto Networks, Inc. © 2026 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. ####### [www.paloaltonetworks.com](http://www.paloaltonetworks.com/) Page 2 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ### Table of Contents | 1. SECURITY TARGET INTRODUCTION ............................................................................................................... 4 | 1. SECURITY TARGET INTRODUCTION ............................................................................................................... 4 | 1. SECURITY TARGET INTRODUCTION ............................................................................................................... 4 | 1. SECURITY TARGET INTRODUCTION ............................................................................................................... 4 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| | 1.1 S ECURITY TARGET , TOE AND CC I DENTIFICATION ......................................................................................... | 1.1 S ECURITY TARGET , TOE AND CC I DENTIFICATION ......................................................................................... | 1.1 S ECURITY TARGET , TOE AND CC I DENTIFICATION ......................................................................................... | 4 | | 1.2 CONFORMANCE CLAIMS ................................................................................................................................. | 1.2 CONFORMANCE CLAIMS ................................................................................................................................. | 1.2 CONFORMANCE CLAIMS ................................................................................................................................. | 5 | | 1.3 CONVENTIONS ................................................................................................................................................ | 1.3 CONVENTIONS ................................................................................................................................................ | 1.3 CONVENTIONS ................................................................................................................................................ | 5 | | 1.3.1 Terminology ......................................................................................................................................... | 1.3.1 Terminology ......................................................................................................................................... | 1.3.1 Terminology ......................................................................................................................................... | 6 | | 1.3.2 Acronyms .............................................................................................................................................. | 1.3.2 Acronyms .............................................................................................................................................. | 1.3.2 Acronyms .............................................................................................................................................. | 6 | | 2. PRODUCT DESCRIPTION ............................................................................................................................. | 2. PRODUCT DESCRIPTION ............................................................................................................................. | 2. PRODUCT DESCRIPTION ............................................................................................................................. | 8 | | 2.1 TOE OVERVIEW ............................................................................................................................................. | 2.1 TOE OVERVIEW ............................................................................................................................................. | 2.1 TOE OVERVIEW ............................................................................................................................................. | 8 | | 2.2 TOE ARCHITECTURE ....................................................................................................................................... | 2.2 TOE ARCHITECTURE ....................................................................................................................................... | 2.2 TOE ARCHITECTURE ....................................................................................................................................... | 9 | | 2.2.1 Physical Boundaries ............................................................................................................................ | 2.2.1 Physical Boundaries ............................................................................................................................ | 2.2.1 Physical Boundaries ............................................................................................................................ | 9 | | 2.2.2 Logical Boundaries ............................................................................................................................ | 2.2.2 Logical Boundaries ............................................................................................................................ | 2.2.2 Logical Boundaries ............................................................................................................................ | 10 | | 2.3 TOE DOCUMENTATION ............................................................................................................................... | 2.3 TOE DOCUMENTATION ............................................................................................................................... | 2.3 TOE DOCUMENTATION ............................................................................................................................... | 11 | | 3. | SECURITY PROBLEM DEFINITION ........................................................................................................... | SECURITY PROBLEM DEFINITION ........................................................................................................... | 12 | | 4. | SECURITY OBJECTIVES .............................................................................................................................. | SECURITY OBJECTIVES .............................................................................................................................. | 13 | | 4.1 S ECURITY OBJECTIVES FOR THE TOE ........................................................................................................... | 4.1 S ECURITY OBJECTIVES FOR THE TOE ........................................................................................................... | 4.1 S ECURITY OBJECTIVES FOR THE TOE ........................................................................................................... | 13 | | 4.2 S ECURITY OBJECTIVES FOR THE OPERATIONAL ENVIRONMENT .................................................................... | 4.2 S ECURITY OBJECTIVES FOR THE OPERATIONAL ENVIRONMENT .................................................................... | 4.2 S ECURITY OBJECTIVES FOR THE OPERATIONAL ENVIRONMENT .................................................................... | 13 | | 5. IT SECURITY REQUIREMENTS .................................................................................................................. | 5. IT SECURITY REQUIREMENTS .................................................................................................................. | 5. IT SECURITY REQUIREMENTS .................................................................................................................. | 14 | | 5.1 EXTENDED REQUIREMENTS .......................................................................................................................... | 5.1 EXTENDED REQUIREMENTS .......................................................................................................................... | 5.1 EXTENDED REQUIREMENTS .......................................................................................................................... | 14 | | 5.2 TOE S ECURITY F UNCTIONAL REQUIREMENTS .............................................................................................. | 5.2 TOE S ECURITY F UNCTIONAL REQUIREMENTS .............................................................................................. | 5.2 TOE S ECURITY F UNCTIONAL REQUIREMENTS .............................................................................................. | 14 | | 5.2.1 Cryptographic Support (FCS) ........................................................................................................... | 5.2.1 Cryptographic Support (FCS) ........................................................................................................... | 5.2.1 Cryptographic Support (FCS) ........................................................................................................... | 16 | | 5.2.2 User Data Protection (FDP) ............................................................................................................. | 5.2.2 User Data Protection (FDP) ............................................................................................................. | 5.2.2 User Data Protection (FDP) ............................................................................................................. | 21 | | 5.2.3 Identification and Authentication (FIA) ........................................................................................... | 5.2.3 Identification and Authentication (FIA) ........................................................................................... | 5.2.3 Identification and Authentication (FIA) ........................................................................................... | 22 | | 5.2.4 Security Management (FMT) ............................................................................................................ | 5.2.4 Security Management (FMT) ............................................................................................................ | 5.2.4 Security Management (FMT) ............................................................................................................ | 25 | | 5.2.5 Privacy (FPR) ...................................................................................................................................... | 5.2.5 Privacy (FPR) ...................................................................................................................................... | 5.2.5 Privacy (FPR) ...................................................................................................................................... | 25 | | 5.2.6 Protection of the TSF (FPT) .............................................................................................................. | 5.2.6 Protection of the TSF (FPT) .............................................................................................................. | 5.2.6 Protection of the TSF (FPT) .............................................................................................................. | 26 | | 5.2.7 Trusted Path/Channel (FTP) ............................................................................................................ | 5.2.7 Trusted Path/Channel (FTP) ............................................................................................................ | 5.2.7 Trusted Path/Channel (FTP) ............................................................................................................ | 27 | | 5.3 TOE S ECURITY ASSURANCE REQUIREMENTS ...................................................................................................... | 5.3 TOE S ECURITY ASSURANCE REQUIREMENTS ...................................................................................................... | 5.3 TOE S ECURITY ASSURANCE REQUIREMENTS ...................................................................................................... | 29 | | 6. | 6. | 6. | 30 | | | TOE SUMMARY SPECIFICATION ............................................................................................................. CRYPTOGRAPHIC S | UPPORT | ........................................................................................................................... 30 | | 6.1 6.2 | 6.1 6.2 | USER DATA PROTECTION ............................................................................................................................. | 32 | | 6.3 I DENTIFICATION AND AUTHENTICATION ....................................................................................................... | 6.3 I DENTIFICATION AND AUTHENTICATION ....................................................................................................... | 6.3 I DENTIFICATION AND AUTHENTICATION ....................................................................................................... | 33 | | 6.4 S ECURITY MANAGEMENT ............................................................................................................................. | 6.4 S ECURITY MANAGEMENT ............................................................................................................................. | 6.4 S ECURITY MANAGEMENT ............................................................................................................................. | 35 | | 6.5 PRIVACY ....................................................................................................................................................... | 6.5 PRIVACY ....................................................................................................................................................... | 6.5 PRIVACY ....................................................................................................................................................... | 35 | | 6.6 PROTECTION OF THE TSF ............................................................................................................................. | 6.6 PROTECTION OF THE TSF ............................................................................................................................. | 6.6 PROTECTION OF THE TSF ............................................................................................................................. | 35 | | 6.7 TRUSTED PATH /C HANNEL ............................................................................................................................ | 6.7 TRUSTED PATH /C HANNEL ............................................................................................................................ | 6.7 TRUSTED PATH /C HANNEL ............................................................................................................................ | 37 | | 7. PROTECTION PROFILE CLAIMS ............................................................................................................... | 7. PROTECTION PROFILE CLAIMS ............................................................................................................... | 7. PROTECTION PROFILE CLAIMS ............................................................................................................... | 38 | | 8. RATIONALE ................................................................................................................................................... | 8. RATIONALE ................................................................................................................................................... | 8. RATIONALE ................................................................................................................................................... | 39 | Page 3 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks LIST OF FIGURES | Figure 1: TOE Deployment | 8 | |-------------------------------------------------------|-----| | Figure 2: TOE Architecture | 9 | | LIST OF TABLES | | | Table 1 TOE Security Functional Components | 14 | | Table 2 Assurance Components | 29 | | Table 3 Cryptographic Functions and CAVP Certificates | 31 | ## 1. Security Target Introduction This section identifies the Security Target (ST) and Target of Evaluation (TOE) identification, ST conventions, ST conformance claims, and the ST organization. The TOE is the Cortex XSOAR Server version 6.14. The Palo Alto Networks Cortex XSOAR (eXtended Security Orchestration, Automation and Response) combines security orchestration, threat intel and incident management, and automated investigation. The focus on this evaluation is on the TOE functionality supporting the claims in the Protection Profile for Application Software. The Security Target contains the following additional sections: - Product Description (Section 2) - Security Problem Definition (Section 3) - Security Objectives (Section 4) - IT Security Requirements (Section 5) - TOE Summary Specification (Section 6) - Protection Profile Claims (Section 7) - Rationale (Section 8). ### 1.1 Security Target, TOE and CC Identification ST Title - Palo Alto Networks Cortex XSOAR Server 6.14 Security Target ST Version - Version 0.3 ST Date - September 16, 2026 ####### TOE Identification - - Cortex XSOAR Server 6.14.0 running on Ubuntu 24.04 1 . TOE Developer - Palo Alto Networks, Inc. 1 While the TOE was tested on Ubuntu 24.04, additional Linux environments such as RHEL 8/9/10, Ubuntu (20.04, 22.04), Oracle Linux 8.9/9.3/9.4, Amazon Linux 2/2023, and Rocky Linux 9.5/9.6 are supported as well. This is vendor affirmed with CAVP algorithm testing. The minimum hardware requirements on those systems are 16 CPU cores, 32 GB of memory, and 1 TB SSD hard disk. Page 4 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks Evaluation Sponsor - Palo Alto Networks, Inc. CC Identification - Common Criteria for Information Technology Security Evaluation, Common Criteria CC:2022, Revision 1 ### 1.2 Conformance Claims This ST and the TOE it describes are conformant to the following CC specifications: This ST is conformant to: - Protection Profile for Application Software, Version 2.0, June 16, 2025 [APPSW]. - Functional Package for Transport Layer Security (TLS), Version 2.1, August 25, 2015 [PKGTLS] - Functional Package for X.509, Version 1.0, October 21, 2024 [PKGX509] This TOE and ST are conformant to Parts 2 (extended) and 3 (extended) of Common Criteria CC:2022, Revision 1. The following NIAP Technical Decision(s) apply to this APPSW, and have been accounted for in the ST development: - TD0994 Addition of FCS_COP.1/XOF to PP_APP_V2.0 - TD1026 Clarifications to FMT_MEC_EXT.1 Windows Test - TD1003 Adding MOD_EDR V2.0 and MOD_HA to the Conformance Claims for PP_APP_V2.0 - TD1050 Clarification to App Note for FPT_LIB_EXT.1.1 The TOE and ST are package-name conformant to [PKGTLS and PKGX509]. The following NIAP Technical Decision(s) apply to PKGTLS or PKGX509, and have been accounted for in the ST development: - TD0969 Correction to Session Resumption Test - TD0977 Removal of Deplicative Test Case in FIA_X509_EXT.1 - TD0970 Clarification to Selections in FIA_X509_EXT.1.4 - TD0979 Correction to Section 1.3 FCS_RBG.1 Entry - TD0981 Correction to Test FCS_TLSS_EXT.1.1:5.3.5 - TD0980 Correction to FCS_(D)TLSS_EXT.1.4 and FCS_(D)TLSC_EXT.1.4 - TD0989 Correction to FCS_TLSC_EXT.1.1:8.1 in PKCS_TLS_V2.1 - TD1008 (D)TLS(C/S) Corrections - TD0993 Administrative Corrections for PKG_X509_V1.0 - TD1025 Restriction to CNSA-Compliant Algorithms for (D)TLS Servers - TD1057 Clarification RE Signing in FIA_X509_EXT.1.1 - TD1038 Corrections to Application Notes Regarding Extended Master Secret Extension ### 1.3 Conventions The following conventions have been applied in this document: - Security Functional Requirements - Part 2 of the CC defines the approved set of operations that may be applied to functional requirements: iteration, assignment, selection, and refinement. Page 5 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks - o Iteration: allows a component to be used more than once with varying operations. In the ST, iteration is indicated by a number in parentheses placed at the end of the component. For example, FDP_ACC.1 (1) and FDP_ACC.1 (2) indicate that the ST includes two iterations of the FDP_ACC.1 requirement, (1) and (2). - o Assignment: allows the specification of an identified parameter. Assignments are indicated using italicized and are surrounded by brackets (e.g., [ assignment ]). Note that an assignment within a selection would be identified in italics and with embedded bold brackets (e.g., [ [selected-assignment] ]). - o Selection: allows the specification of one or more elements from a list. Selections are indicated using bold and are surrounded by brackets (e.g., [ selection ]). - o Refinement: allows the addition of details. Refinements are indicated using bold, for additions, and strikethrough, for deletions (e.g., '… all objects …' or '… some big things …'). Note that 'cases' that are not applicable in a given SFR have simply been removed without any explicit identification. - Other sections of the ST - Other sections of the ST use bolding to highlight text of special interest, such as captions. - The ST does not highlight operations that have been completed by the PP and EP authors. #### 1.3.1 Terminology The following terms and abbreviations are used in this ST: Playbooks Playbooks are at the heart of the Cortex XSOAR system. They enable you to automate many of your security processes, including, but not limited to handling your investigations and managing your tickets. #### 1.3.2 Acronyms | AES | Advanced Encryption Standard | |-------|-------------------------------------------------------------------| | CBC | Cipher-Block Chaining | | CC | Common Criteria for Information Technology Security Evaluation | | CEM | Common Evaluation Methodology for Information Technology Security | | CM | Configuration Management | | CLI | Command Line Interface | | DH | Diffie-Hellman | | DRBG | Deterministic Random Bit Generator | | FIPS | Federal Information Processing Standard | | FSP | Functional Specification | | GCM | Galois/Counter Mode | | GUI | Graphical User Interface | | HMAC | Hashed Message Authentication Code | | HTTPS | Hypertext Transfer Protocol Secure | | IP | Internet Protocol | | IPv4 | Internet Protocol version 4 | | Ipv6 | Internet Protocol version 6 | | NIST | National Institute of Standards and Technology | | PP | Protection Profile | | RHEL | Red Hat Enterprise Linux | Page 6 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks | RSA | Rivest, Shamir and Adleman (algorithm for public-key cryptography) | |-------|----------------------------------------------------------------------| | SAR | Security Assurance Requirement | | SFR | Security Functional Requirement | | SHA | Secure Hash Algorithm | | SOAR | Security Orchestration, Automation and Response | | SOC | Security Operation Center | | SSH | Secure Shell | | SSL | Secure Socket Layer | | ST | Security Target | | TLS | Transport Layer Security | | TOE | Target of Evaluation | | TSF | TOE Security Functions | | URL | Uniform Resource Locator | | VM | Virtual Machine | Page 7 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ## 2. Product Description The Target of Evaluation (TOE) is the Palo Alto Networks Cortex 2 XSOAR Server 6.14. Cortex XSOAR combines security orchestration, incident management, and interactive investigation into a seamless experience. The orchestration component is designed to automate security product tasks and weave in human analyst tasks and workflows. ### 2.1 ### TOE Overview The TOE is a software application that runs on various Linux environments (server/workstation) to provide SOC team with detection and automatic response capabilities 3 . The Server provides UI functionality and playbook detection/response functionality, while TLS Client (e.g., Engine) in the operational environment is used to efficiently share the workload (e.g., load-balancing), thereby speeding up execution time. The Server provides security management functions and interface via web UI protected by HTTPS and communicates with the Client(s) through TLSv1.2 protected channels. The Server implements TLS server functionality while the Client, which is in the operational environment, implements TLS client functionality. The TOE and Client can be deployed on the same workstation/server, or they can be deployed on separate devices. TOE Page 8 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ####### FIPS-CC Mode of Operation The FIPS-CC Version of Cortex XSOAR are, by default, compliant with all FIPS and CC Approved algorithms, protocols, and key sizes requirements. The FIPS-CC mode is enabled by default and cannot be disabled. Additional configurations must be performed to enable X509v3 certification validation, revocation checking, and mutual authentication. All configuration steps are fully documented in the CC Evaluated Configuration Guide (also known as the AGD). ### 2.2 TOE Architecture The TOE is a software solution that is comprised of the items noted in Section 2.2.1 and 2.2.2. The software is available for download from the Palo Alto Networks support site. The following diagram depicts the software architecture of the TOE. Figure 2: TOE Architecture #### 2.2.1 Physical Boundaries The physical boundary of the TOE is the application installed and running on a supported platform (i.e., Linux operating systems). ##### 2.2.1.1 Software Requirements The TOE runs on an operating system that includes RHEL 8/9/10, Ubuntu (20.04, 22.04, 24.04), Oracle Linux 8.9/9.3/9.4, Amazon Linux 2/2023, or Rocky Linux 9.5/9.6. ##### 2.2.1.2 Hardware Requirements The TOE must be installed on the server system with the minimum hardware requirements specified below. Minimum hardware: 16 CPU (minimum); 32 GB RAM (minimum); 1 TB of disk space (minimum) Page 9 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks The TOE was installed and tested on the following platforms: - Ubuntu 24.04 - Processor: Intel Xeon Gold 6248 (Cascade Lake) #### 2.2.2 Logical Boundaries This section summarizes the security functions provided by the TOE: ##### Cryptographic Support ##### Identification and Authentication ##### User Data Protection ##### Security Management ##### Protection of the TSF ##### Privacy ##### Trusted Path/Channels ### 2.2.2.1 Cryptographic Support The TOE implements CAVP validated cryptographic algorithms that provide key management, random bit generation, encryption/decryption, digital signature and cryptographic hashing and keyed-hash message authentication features in support of cryptographic protocols such as TLS. ### 2.2.2.2 User Data Protection The TOE provides no access to hardware resources or sensitive information repositories. The TOE restricts network communication to application-initiated communication between the TOE and Client(s), and remotely user-initiated communication from administrators. All sensitive application data (e.g., API keys, passphrase) are stored encrypted using AES-256 in CBC mode. ### 2.2.2.3 Identification and Authentication The TOE authenticates all users using password-based or X509v3 certificate-based methods. This is configurable and by default, password-based method is used. ### 2.2.2.4 Security Management The TOE provides access to the security management functions via the web UI. Identification and authentication are required before accessing the UI. In addition, the operating system can provide some configuration options for the TOE. In that case, the operating system I&A method and privileges will be used and enforced. ### 2.2.2.5 Privacy The TOE does not transmit PII over the network. ### 2.2.2.6 Protection of the TSF The TOE implements a number of functions to ensure that it is protected against tampering and corruption. These mechanisms include utilizing platform APIs, memory mapping, and stack-based buffer overflow protection. The TOE is implemented in Golang which is designed as a memory safe language. This includes automatic bounds checking, garbage collection, and type safety check. Palo Alto Networks provides customers with a means of updating their TOE using trusted updates. These trusted updates (signed DEB package) are securely delivered over HTTPS website and verified using approved digital signature methods. All of these updates are properly signedand are verified by the operating system mechanism. In addition, the TOE image is protected with FIPS Software integrity test at power-up (e.g., when the application is started or is reloaded). Page 10 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ##### 2.2.2.7 Trusted Path/Channels The TOE protects interactive communication with remote administrators using HTTP over TLS (HTTPS). TLS ensures both integrity and disclosure protection. TLS also protects communication between the Server and its Client(s). ### 2.3 TOE Documentation Palo Alto Networks Inc. offers a series of documents that describe the installation of Palo Alto Networks Cortex XSOAR as well as guidance for subsequent use and administration of the applicable security features. For Cortex XSOAR v6.14, these documents include: - Palo Alto Networks Common Criteria Evaluated Configuration Guide (CCECG) for Cortex XSOAR Server and Engine 6.14, 07/15/2026 Page 11 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ## 3. Security Problem Definition This security target includes by reference the Security Problem Definition (composed of organizational policies, threat statements, and assumption) from [APPSW]. In general, the [APPSW] has presented a Security Problem Definition appropriate for software applications, and as such, is applicable to the TOE. The following threats are directly from the [APPSW]: | T. NETWORK_ATTACK | An attacker is positioned on a communications channel or elsewhere on the network infrastructure. Attackers may engage in communications with the application software or alter communications between the application software and other endpoints in order to compromise it. | |---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | T.NETWORK_EAVESDROP | An attacker is positioned on a communications channel or elsewhere on the network infrastructure. Attackers may monitor and gain access to data exchanged between the application and other endpoints. | | T.LOCAL_ATTACK | An attacker can act through unprivileged software on the same computing platform on which the application executes. Attackers may provide maliciously formatted input to the application in the form of files or other local communications. | | T.PHYSICAL_ACCESS | An attacker may try to access sensitive data at rest. | The following assumptions are made as drawn directly from the [APPSW]: | A. PLATFORM | The TOE relies upon a trustworthy computing platform with a reliable time clock for its execution. This includes the underlying platform and whatever runtime environment it provides to the TOE. | |-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | A. PROPER_USER | The user of the application software is not willfully negligent or hostile, and uses the software in compliance with the applied enterprise security policy. | | A. PROPER_ADMIN | The administrator of the application software is not careless, willfully negligent or hostile, and administers the software in compliance with the applied enterprise security policy. | . Page 12 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ## 4. Security Objectives The sections below identify the security objectives for the TOE and for the operational environment. These security objectives identify the responsibilities of the TOE and the operational environment in meeting security needs. ### 4.1 Security Objectives for the TOE See Section 4 of [APPSW]. ### 4.2 Security Objectives for the Operational Environment | OE.PLATFORM | The TOE relies upon a trustworthy computing platform for its execution. This includes the underlying operating system and any discrete execution environment provided to the TOE. | |-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | OE.PROPER_USER | The user of the application software is not willfully negligent or hostile, and uses the software within compliance of the applied enterprise security policy. | | OE.PROPER_ADMIN | The administrator of the application software is not careless, willfully negligent or hostile, and administers the software within compliance of the applied enterprise security policy. | Page 13 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ## 5. IT Security Requirements This section defines the Security Functional Requirements (SFRs) and Security Assurance Requirements (SARs) that serve to represent the security functional claims for the Target of Evaluation (TOE) and to scope the evaluation effort. The SFRs have all been drawn from the following Protection Profiles (PP): - Protection Profile for Application Software, Version 2.0, 16 June 2025 [APPSW], - Functional Package for X.509, Version 1.0, 21 October 2024 [PKGX509] - Functional Package for Transport Layer Security (TLS), Version 2.1, 25 August 2025 [PKGTLS], The SARs are the set of SARs specified in [APPSW]. ### 5.1 Extended Requirements All extended requirements in this ST have been drawn from the [APPSW], [PKGTLS], and [PKGX509]. The [APPSW], [PKGTLS], and [PKGX509] define all the extended SFRs (*_EXT.1) and since they are not redefined in this ST, the [APPSW], [PKGSTLS], and [PKGX509] should be consulted for more information in regard to those CC extensions. ### 5.2 TOE Security Functional Requirements The following table identifies the SFRs that are satisfied by the Palo Alto TOE. Table 1 TOE Security Functional Components | Requirement Class | Requirement Component | |----------------------------|---------------------------------------------------------------------------------| | FCS: Cryptographic Support | FCS_CKM_EXT.1 Cryptographic Key Generation Services | | FCS: Cryptographic Support | FCS_CKM.1/AK Cryptographic Asymmetric Key Generation | | FCS: Cryptographic Support | FCS_CKM.1/SK Cryptographic Symmetric Key Generation | | FCS: Cryptographic Support | FCS_CKM.2 Cryptographic Key Establishment | | FCS: Cryptographic Support | FCS_COP.1/SKC Cryptographic Operation - Encryption/Decryption | | FCS: Cryptographic Support | FCS_COP.1/Hash Cryptographic Operation - Hashing | | FCS: Cryptographic Support | FCS_COP.1/KeyedHash Cryptographic Operation - Keyed-Hash Message Authentication | | FCS: Cryptographic Support | FCS_COP.1/SigGen Cryptographic Operation - Signing Generation | | FCS: Cryptographic Support | FCS_COP.1/SigVer Cryptographic Operation - Signing Verification | | FCS: Cryptographic Support | FCS_HTTPS_EXT.1 HTTPS Protocol | | FCS: Cryptographic Support | FCS_HTTPS_EXT.2 HTTPS Support for Authentication | | FCS: Cryptographic Support | FCS_RBG_EXT.1 Random Bit Generation Services | | FCS: Cryptographic Support | FCS_RBG.1 Random Bit Generation (RBG) | | FCS: Cryptographic Support | FCS_RBG.2 Random Bit Generation (External Seeding) | | FCS: Cryptographic Support | FCS_STO_EXT.1 Storage of Credentials | | FCS: Cryptographic Support | FCS_TLS_EXT.1 TLS Protocol | Page 14 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks | Requirement Class | Requirement Component | |----------------------------------------|------------------------------------------------------------------------------------| | | FCS_TLSS_EXT.1 TLS Server Protocol | | | FCS_TLSS_EXT.2 TLS Server Support for Mutual Authentication | | | FCS_TLSS_EXT.4 TLS Server Support for Renegotiation | | | FCS_TLSS_EXT.5 TLS Server Support for Session Resumption | | FDP: User Data Protection | FDP_DEC_EXT.1 Access to Platform Resources | | | FDP_NET_EXT.1 Network Communications | | | FDP_DAR_EXT.1 Encryption of Sensitive Application Data | | FIA: Identification and Authentication | FIA_X509_EXT.1 X.509 Certificate Validation | | | FIA_X509_EXT.2 X.509 Certificate Support for Functions | | | FIA_X509_EXT.3 X.509 Certificate Requests | | | FIA_XCU_EXT.1 Implementation of X.509 Functions | | | FIA_XCU_EXT.2 X.509 Certificate Acquisition | | FMT: Security Management | FMT_MEC_EXT.1 Supported Configuration Mechanism | | | FMT_CFG_EXT.1 Secure by Default Configuration | | | FMT_SMF.1 Specification of Management Functions | | FPR: Privacy | FPR_ANO_EXT.1 User Consent for Transmission of Personally Identifiable Information | | FPT: Protection of the TSF | FPT_API_EXT.1 Use of Supported Services and APIs | | | FPT_AEX_EXT.1 Anti-Exploitation Capabilities | | | FPT_FLS.1 Failure with Preservation of Secure State | | | FPT_TST.1 TSF Self-Testing | | | FPT_TUD_EXT.1 Support for Trusted Updates | | | FPT_TUD_EXT.2 Integrity for Installation and Update | | | FPT_LIB_EXT.1 Use of Third Party Libraries | | FTP: Trusted Path/Channel | FTP_DIT_EXT.1 Protection of Data in Transit | Page 15 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks #### 5.2.1 Cryptographic Support (FCS) ####### FCS_CKM_EXT.1 - Cryptographic Key Generation Services FCS_CKM_EXT.1.1 The application shall [ - implement asymmetric key generation ]. ####### FCS_CKM.1/AK - Cryptographic Asymmetric Key Generation FCS_CKM.1.1/AK The application shall [ - implement functionality ] to generate asymmetric cryptographic keys in accordance with a specified cryptographic key generation algorithm [ - CNSA 1.0 Compliant Algorithms: - o [ECC schemes] using ['NIST curves' P -384 and [P-521] that meet the following: [FIPS PUB 1865, 'Digital Signature Standard (DSS)', Appendix A.2] ]. ####### FCS_CKM.1/SK - Cryptographic Symmetric Key Generation ####### FCS_CKM.1.1/SK The application shall [ implement functionality ] to generate symmetric cryptographic key using a Random Bit Generator as specified in FCS_RBG_EXT.1 and specified cryptographic key sizes 256-bit ####### FCS_CKM.2 - Cryptographic Key Establishment ####### FCS_CKM.2.1 The application shall [ implement functionality ] to perform cryptographic key establishment in accordance with a specified cryptographic key establishment method: [ ]. ####### FCS_COP.1/SKC - Cryptographic Operation - Encryption/Decryption FCS_COP.1.1/SKC The application shall [ perform ] [ encryption/decryption ] in accordance with a specified cryptographic algorithm [ - AES-CBC (as defined in NIST SP 800-38A) mode, - CNSA 1.0 Compliant Algorithms: - o [Elliptical curve-based key establishment schemes ] that meets the following: [NIST Special Publication 80056A, 'Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography'] Page 16 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks - AES-GCM (as defined in NIST SP 800-38D) mode ] and cryptographic key sizes [ 256-bits ] . ####### FCS_COP.1/Hash - Cryptographic Operation - Hashing FCS_COP.1.1/Hash The application shall perform [ cryptographic hashing services ] in accordance with a specified cryptographic algorithm [ - SHA-384 - SHA-512 ] and message digest sizes [ - 384 - 512 ] bits that meet the following: [ FIPS Pub 1804, 'Secure Hash Standard' ]. ####### FCS_COP.1/KeyedHash - Cryptographic Operation - Keyed-Hash Message Authentication FCS_COP.1.1/KeyedHash The application shall perform [ keyed-hash message authentication ] in accordance with a specified cryptographic algorithm [ - HMAC-SHA-384, - HMAC-SHA-512 ] ] with key sizes [ 384, 512 ] and message digest sizes [ 384, 512 ] bits that meet the following: [ FIPS Pub 1981, 'The Keyed - Hash Message Authentication Code,' and FIPS Pub 1804, 'Secure Hash Standard' ] . ####### FCS_COP.1/SigGen - Cryptographic Operation - Signing Generation FCS_COP.1.1/SigGen The application shall perform [ cryptographic signature services (generation) ] in accordance with a specified cryptographic algorithm [ - CNSA 1.0 Compliant Algorithms: [ - o RSA schemes using cryptographic key sizes of [3072-bit or greater] that meet the following: [FIPS PUB 1865, 'Digital Signature Standard (DSS)', Section 5] - o ECDSA schemes using 'NIST curves' [ P-384, P-521 ] that meet the following: [FIPS PUB 1865, 'Digital Signature Standard (DSS)', Section 6] ] Page 17 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ]. ####### FCS_COP.1/SigVer - Cryptographic Operation - Signing Verification FCS_COP.1.1/SigVer The application shall perform [ cryptographic signature services (verification) ] in accordance with a specified cryptographic algorithm [ - CNSA 1.0 Compliant Algorithms: [ - o RSA schemes using cryptographic key sizes of [3072-bit or greater] that meet the following: [FIPS PUB 1865, 'Digital Signature Standard (DSS)', Section 5] - o ECDSA schemes using 'NIST curves' [ P-384, P-521 ] that meet the following: [FIPS PUB 1865, 'Digital Signature Standard (DSS)', Section 6] ]. ####### FCS_HTTPS_EXT.1 - HTTPS Protocol ####### FCS_HTTPS_EXT.1.1 ####### FCS_HTTPS_EXT.1.2 The application shall implement the HTTPS protocol as a [ server with mutual authentication ] that complies with RFC 2818. The application shall implement HTTPS using TLS as defined in the Functional Package for TLS. ####### FCS_HTTPS_EXT.2 - HTTPS Support forAuthentication ####### FCS_HTTPS_EXT.2.1 The application shall [ establish or not establish the connection based on an administrative or user setting ] if the peer certificate is deemed invalid when attempting to establish a HTTPS connection. ####### FCS_RBG_EXT.1 - Random Bit Generation Services FCS_RBG_EXT.1.1 The application shall [ - implement DRBG functionality ] for its cryptographic operations. ####### FCS_RBG.1 - Random Bit Generation (RBG) | FCS_RBG.1.1 | The TSF shall perform deterministic random bit generation services using [ ● CTR_DRBG (AES) ]in accordance with [ NIST SP 800-90A ] after initialization with a seed. | |---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | FCS_RBG.1.2 | The TSFshall use a [ TSF interface for seeding ] for initialized seeding. | | FCS_RBG.1.3 | The TSF shall update the RBG state by [ reseeding ] using a [ TSF interface for seeding ] in the following situations: [ | ] Page 18 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ] ####### FCS_STO_EXT.1 - Storage of Credentials FCS_STO_EXT.1.1 The application shall [ - Implement functionality to securely store [API keys, passphrase] according to [FCS_COP.1/SKC] ] to non-volatile memory. ####### FCS_TLS_EXT.1 - TLS Protocol FCS_TLS_EXT.1 The TSF shall implement [ - TLS as a server ]. ####### FCS_TLSS_EXT.1 - TLS Server Protocol FCS_TLSS_EXT.1.1 FCS_TLSS_EXT.1.2 The TSF shall implement [ TLS 1.2 (RFC 5246) ] as a server that supports additional functionality for session renegotiation protection and [ - mutual authentication - session resumption ] and shall reject connection attempts from clients supporting only TLS 1.1, TLS 1.0, or SSL versions. The TSF shall be able to support the following [ - TLS 1.2 ciphersuites: [ - CNSA 1.0 compliant [ - on the condition: [platform is rebooted or every 4096 calls to RAND_bytes] ] in accordance with [ FIPS 140-3 and SP 800-90A ]. ####### FCS_RBG.2 - Random Bit Generation (External Seeding) FCS_RBG.2.1 The TSF shall be able to accept a minimum input of [ 384 bits ] from a TSF interface for the purpose of seeding. ####### FCS_SNI_EXT.1 - Cryptographic Operation (Salt, Nonce, and Initialization Vector Generation) FCS_SNI_EXT.1.1 FCS_SNI_EXT.1.2 The application shall [ use no salts ] The application shall use [ no nonces ] FCS_SNI_EXT.1.3 The application shall [ - create IVs in the following manner [ - CBC: IVs shall be non-repeating and unpredictable ] Page 19 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ] , and [ ]. FCS_TLSS_EXT.1.5 The TSF shall perform key establishment for TLS using [ - RSA with [ - CNSA 1.0 compliant size [3072, 4096] ] ####### and no other TLS 1.2 ciphersuites, ] using a preference order based on [ ClientHello ordering ]. FCS_TLSS_EXT.1.3 The TSF shall not establish a connection with a client that does not indicate support for at least one of the supported cryptographic parameter sets. FCS_TLSS_EXT.1.4 The TSF shall be able to support the following TLS ClientHello message extensions: - signature_algorithms extension (RFC 8446) indicating support for CNSA 1.0 compliant [ - ecdsa_secp384r1_sha384 (RFC 8446) - rsa_pkcs1_sha384 (RFC 8446) ], and [ - CNSA 1.0 compliant [ - rsa_pss_pss_sha384 (RFC 8446) - rsa_pss_rsae_sha384 (RFC 8446) - [rsa_pss_rsae_sha512, rsa_pkcs1_sha512, ecdsa_secp521r1_sha512] ] - ■ TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289 and RFC 8422 - ■ TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289 and RFC 8422 - supported_groups extension indicating support for [ - CNSA 1.0 compliant [ ■ secp384r1 (RFC 8446) ] ○ and [ ■ secp521r1 (RFC 8446) - extended_master_secret extension (RFC7627) enforcing server support, and [no other enforcement mode] ``` ] ``` Page 20 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ]. ####### FCS_TLSS_EXT.2 - TLS Server Support for Mutual Authentication FCS_TLSS_EXT.2.1 FCS_TLSS_EXT.2.2 FCS_TLSS_EXT.2.3 The TSF shall support authentication of TLS clients using X.509v3 certificates during the TLS handshake and [ at no other time ] using the certificate types indicated in the client's signature_algorithms and [ no other ] extension. The TSF shall support authentication of TLS clients using X.509v3 certificates in accordance with FIA_X509_EXT.1. The TSF shall be able to reject the establishment of a trusted channel if the requested client certificate is invalid and [ - no other processing options for missing or invalid client certificates ] Application Note : The TOE only verifies the SAN in the X509v3 certificate. The certificate must have a SAN field or the connection will be terminated. ####### FCS_TLSS_EXT.4 - TLS Server Support for Renegotiation FCS_TLSS_EXT.4.1 The TSF shall support secure TLS renegotiation through the use of [ not allowing session renegotiation ]. FCS_TLSS_EXT.4.2 The TSF shall [ not allow renegotiation ]. FCS_TLSS_EXT.4.3 The TSF shall terminate the session if an unexpected ClientHello is received during an active TLS session. ####### FCS_TLSS_EXT.5 - TLS Server Support for Session Resumption FCS_TLSS_EXT.5.1 The TSF shall support session resumption as a TLS server via the use of [ tickets in accordance with RFC 5077 ]. #### 5.2.2 User Data Protection (FDP) ####### FDP_DEC_EXT.1 - Access to Platform Resources FDP_DEC_EXT.1.1 The application shall restrict its access to [ - network connectivity ]. ] - ECDHE parameters with [ - CNSA 1.0 compliant elliptic curves [secp384r1, secp521r1] ] and no other curves, consistent with the client's supported_groups extension and [no other] extension and using non-compressed formatting for points FDP_DEC_EXT.1.2 The application shall restrict its access to [ Page 21 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks - no sensitive information repositories ]. Application Note : The TOE is not designed to be installed on a mobile device (such as a phone or tablet). | FDP_NET_EXT.1 - Network Communications | |------------------------------------------| FDP_NET_EXT.1.1 The application shall restrict network communication to [ - respond to [Web UI users-initiated HTTPS connection], - [communication with Client] ]. | FDP_DAR_EXT.1 - Encryption of Sensitive Application Data | |------------------------------------------------------------| ####### FDP_DAR_EXT.1.1 The application shall [ - protect sensitive data in accordance with FCS_STO_EXT.1 ] in non-volatile memory. #### 5.2.3 Identification and Authentication (FIA) | FIA_X509_EXT.1 - X.509 Certificate Validation | |-------------------------------------------------| FIA_X509_EXT.1.1 The TSF shall [ implement functionality ] to validate certificates in accordance with the following rules: - Certification path validation meets requirements of RFC 5280 for certificate paths of [ unlimited path length ] and certificate paths exceeding the maximum path length are invalid. - The current time is within the notBefore and notAfter values of all certificates in the certification path. - The certification path shall terminate at a trust anchor element appropriate for the supported function. - Certificates containing subjectUniqueID and issuerUniqueID fields are considered invalid. - Certificates are signed using cryptographic signatures and hashes in accordance with RFC 8603, and [ - o no other algorithms ####### ] and certificates signed using other cryptographic algorithms are considered invalid. - [ ] ● - o no other algorithm constraints Page 22 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks FIA_X509_EXT.1.2 The TSF shall [ implement ] processing of the extensions indicated in RFC 5280, section 4.2, - Authority Key Identifier, - Subject Key Identifier - keyUsage and [ - basicConstraints - authorityInformationAccess - Subject alternative name containing any of the following name types [ ] FIA_X509_EXT.1.4 The TSF shall [ - implement functionality ] to obtain supported revocation status information via [ - Network connection to [OSCP responder] ] FIA_X509_EXT.1.5 The TSF shall [ implement functionality ] to validate that the context of the certificate path and trust store element is consistent with the supported function use via [ - processing [ - extendedKeyUsage (EKU) field constraints in the leaf certificate including: [ - ■ Client certificates presented for TLS shall have the Client Authentication purpose (id-kp 2 with OID 1.3.6.1.5.5.7.3.2), - ■ Server certificates presented for TLS shall have the Server Authentication purpose (id-kp 1 with OID 1.3.6.1.5.5.7.3.1), ]. FIA_X509_EXT.1.6 The TSF shall [ use platform-managed trust stores ] used for all certification path validation. ]. FIA_X509_EXT.1.3 The TSF shall [ implement functionality ] to validate revocation status of the certificate using [ - The Online Certificate Status Protocol (OCSP) as specified in RFC 6960 ○ ■ dNSName - ■ iPAddress ] extendedKeyUsage ] ] and rejects the certificate if the context requirements are not met, Page 23 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ####### FIA_X509_EXT.2 - X.509 Certificate Support for Functions FIA_X509_EXT.2.1 FIA_X509_EXT.2.2 ] For each function indicated in FIA_X509_EXT.2.1, the TSF shall [ determine ] whether the [ administrator is allowed to configure certificate acceptance ] when valid certificate revocation status information cannot be obtained from a source indicated in FIA_X509_EXT.1.3. ####### FIA_X509_EXT.3 - X.509 Certificate Requests FIA_X509_EXT.3.1 The TSF shall [ invoke the TOE platform to generate ] Certificate Requests as specified by [ - RFC 2986 (PKCS-10) ] and be able to provide the following information in the request: public key, [ ``` ● Subject DN consisting of values for [ ○ O ○ OU ○ CN ○ [State] ] ● one or more of the following SAN types [ ○ dNSName ○ iPAddress ○ [no other types] ] ● and [ ○ no other information. ] ``` The TSF shall [ validate ] X.509v3 certificates in accordance with FIA_X509_EXT.1 to support [ authentication of sessions ] using [ - [TLS] ``` ] ``` FIA_X509_EXT.3.2 The TSF shall [ invoke platform-provided functionality ] to validate the certificate path in accordance with FIA_X509_EXT.1 upon receiving the CA Certificate Response, and validate that the certificate path of the response is consistent with the intended usage. ####### FIA_XCU_EXT.1 - Implementation of X.509 Functions FIA_XCU_EXT.1.1 The TSF shall [verify, assert] identities included in X.509 certificates. ####### FIA_XCU_EXT.2 - X.509 Certificate Acquisition ``` FIA_XCU_EXT.2.1 ``` The TSF shall [ Page 24 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ] #### 5.2.4 Security Management (FMT) ####### FMT_MEC_EXT.1 - Supported Configuration Mechanism FMT_MEC_EXT.1.1 The application shall [ - invoke the mechanisms recommended by the platform vendor for storing and setting configuration options. ]. ####### FMT_CFG_EXT.1 - Secure by Default Configuration FMT_CFG_EXT.1.1 FMT_CFG_EXT.1.2 The application shall [ provide only enough functionality to set new credentials when configured with default credentials or no credentials for application provided credentials ]. The application shall be configured by default with file permissions which protect the application binaries and data files from modification by normal unprivileged users. ####### FMT_SMF.1 - Specification of Management Functions ####### FMT_SMF.1.1 The TSF shall be capable of performing the following management functions [ - [User management - Password complexity management - Password change - TLS/X509 configuration - Encrypting API keys and passphrase in the database] - Querying the current version of the TOE ] #### 5.2.5 Privacy (FPR) ####### FPR_ANO_EXT.1 - User Consent for Transmission of Personally Identifiable Information FPR_ANO_EXT.1.1 The application shall [ - not transmit PII over a network ]. - request certificates from an [external] CA ] to represent [itself for TLS authentication] for [ - TLS Page 25 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks #### 5.2.6 Protection of the TSF (FPT) ####### FPT_API_EXT.1 - Use of Supported Services and APIs FPT_API_EXT.1.1 The application shall use only documented platform APIs. | FPT_AEX_EXT.1 - Anti-Exploitation Capabilities | FPT_AEX_EXT.1 - Anti-Exploitation Capabilities | |--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| | FPT_AEX_EXT.1.1 | The application shall not request to map memory at an explicit address except for [ no exceptions ]. | | FPT_AEX_EXT.1.2 | The application shall [ ● not allocate any memory region with both write and execute permissions ]. | | FPT_AEX_EXT.1.3 | The application shall be compatible with security features provided by the platform vendor. | | FPT_AEX_EXT.1.4 | The application shall not write user-modifiable files to directories that contain executable files unless explicitly directed by the user to do so. | | FPT_AEX_EXT.1.5 | The application shall be compiled with stack-based buffer overflow protection enabled. | ####### FPT_FLS.1 - Failure with Preservation of Secure State ####### FPT_FLS.1.1 The TSF shall preserve a secure state when the following type of failures occur: [ DRBG self-test failure ]. | FPT_TST.1 - TSF Self-Testing | FPT_TST.1 - TSF Self-Testing | |--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| | FPT_TST.1.1 | The TSF shall run a suite of the following self-tests [ during initial start-up ] to demonstrate the correct operation of [ TSF DRBG specified in FCS_RBG.1 ]. | | FPT_TST.1.2 | The TSF shall provide authorized users with the capability to verify the integrity of [ [DRBG seed/output data] ]. | | FPT_TST.1.3 | The TSF shall provide authorized users with the capability to verify the integrity of [ [TSF DRBG specified in FCS_RBG.1] ]. | ####### FPT_TUD_EXT.1 - Support for Trust Updates | FPT_TUD_EXT.1.1 | The application shall [ use platform-provided services ] to check for updates and patches to the application software. | |-------------------|--------------------------------------------------------------------------------------------------------------------------| | FPT_TUD_EXT.1.2 | The application shall [ provide the ability ] to query the current version of the application software. | Page 26 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks | FPT_TUD_EXT.1.3 | The application shall [ ● not download, modify, replace or update its own binary code ]. | |-------------------|-------------------------------------------------------------------------------------------------------------------------------------------| | FPT_TUD_EXT.1.4 | Application updates shall be digitally signed such that the application platform can cryptographically verify them prior to installation. | | FPT_TUD_EXT.1.5 | The application is distributed [ as an additional software package to the platform OS ]. | ####### FPT_TUD_EXT.2 - Integrity for Installation and Update | FPT_TUD_EXT.2.1 | The application shall be distributed using the [ format of the platform-supported package manager ]. | |-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | FPT_TUD_EXT.2.2 | The application shall be packaged such that its removal results in the deletion of all traces of the application, with the exception of configuration settings, output files, and audit/log events. | | FPT_TUD_EXT.2.3 | The application installation package shall be digitally signed such that its platform can cryptographically verify them prior to installation. | ####### FPT_LIB_EXT.1 - Use of Third Party Libraries FPT_LIB_EXT.1.1 The application shall be packaged with only [ libraries identified in vendor-provided SBOM ] #### 5.2.7 Trusted Path/Channel (FTP) ####### FTP_DIT_EXT.1 - Protection of Data in Transit ####### FTP_DIT_EXT.1.1 The application shall [ - encrypt all transmitted [data] with [ - o HTTPS as a server with support for mutual authentication in accordance with FCS_HTTPS_EXT.1 and FCS_HTTPS_EXT.2 - o TLS as a server as defined in the Functional Package for Tranport Security Layer (TLS), version 2.1 and also supports functionality for [mutual authentication] ] for [protocols authentication] using certificates as defined in the Functional Package for X.509 ] between itself and another trusted IT product. Page 27 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks Page 28 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ### 5.3 TOE Security Assurance Requirements The security assurance requirements for the TOE are included by reference to [APPSW]. Table 2 Assurance Components | Requirement Class | Requirement Component | |-------------------------------|---------------------------------------------| | ASE: Security Target | ASE_CCL.1 Conformance claims | | ASE: Security Target | ASE_ECD.1 Extended components definition | | ASE: Security Target | ASE_INT.1 ST introduction | | ASE: Security Target | ASE_OBJ.1 Security objectives | | ASE: Security Target | ASE_REQ.1 Security requirements | | ASE: Security Target | ASE_SPD.1 Security problem definition | | ASE: Security Target | ASE_TSS.1 TOE summary specification | | ADV: Development | ADV_FSP.1 Basic functional specification | | AGD: Guidance Documents | AGD_OPE.1: Operational user guidance | | AGD: Guidance Documents | AGD_PRE.1: Preparative procedures | | ALC: Life-Cycle Support | ALC_CMC.1 Labelling of the TOE | | ALC: Life-Cycle Support | ALC_CMS.1 TOE CM coverage | | ALC: Life-Cycle Support | ALC_FLR.3 Systematic flaw remediation | | ALC: Life-Cycle Support | ALC_TSU_EXT.1 Timely security updates | | ATE: Tests | ATE_IND.1 Independent testing - conformance | | AVA: Vulnerability Assessment | AVA_VAN.1 Vulnerability survey | Page 29 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ## 6. TOE Summary Specification This chapter describes the security functions: - Cryptographic Support - Identification and Authentication - User Data Protection - Security Management - Protection of the TSF - Privacy ### Trusted Path/Channel ### 6.1 Cryptographic Support | FCS_CKM_EXT.1 FCS_CKM.1/AK FCS_CKM.1/SK | The TOE does not provide users with the capability to generate certificates 4 . Platform Administrators can set/load client or server certificates into the certificate store of the platform (i.e., keypair generated on the platform) that the TOE is running on. During a TLS handshake, the TOE utilizes ECC scheme to generate asymmetric keys with NIST curves that include P-384 and P-521 that adhere to the NIST Special Publication 186-5. For details regarding the algorithms supported and their CAVP certificates, see table below. | |-------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | FCS_CKM.2 | The TOE implements key establishment methods using elliptical curve key establishment scheme (ECDHE). The curves utilized by the TOE include P-384 and P-521 as defined in NIST SP 800-56A (revision 3). | | FCS_COP.1/SKC | The TOE can encrypt/decrypt using AES-CBC mode (as defined in NIST SP 800- 38A) and AES-GCM mode (as defined in NIST SP 800-38D) with key sizes 256- bits. Corresponding CAVP certificates for these algorithms are present in the table below. | | FCS_COP.1/Hash | The TOE uses hash functions that include SHA-384 and SHA-512 as defined in FIPS 180-4. The digest sizes include 256-bits, 384-bits, and 512-bits that are compliant with FIPS 180-4. The hashing capabilities are utilized for digital signature verification and generation and software integrity checks. The TOE uses SHA-384 hashing as part of generating digital signatures. SHA-512 is used as part of the software integrity power-up test. Corresponding CAVP certificates for these algorithms are present in the table below. | | FCS_COP.1/KeyedHash | The TOE supports the use of a Keyed-Hash Message Authentication algorithms that include HMAC-SHA-384, and HMAC-SHA-512. They include key sizes of 384-bits and 512-bits respectively. The HMAC-SHA functions are used as part of the TOE's integrity check (HMAC -SHA-512) to ensure that it has not been tampered and is additionally used as part of the TLS handshake (HMAC-SHA- 384). Corresponding CAVP certificates for these algorithms are present in the table below. | | FCS_COP.1/SigGen | Both RSA and ECDSA schemes are used for TLS functions with Approved key sizes. This includes RSA 3072-bits. For ECDSA, they include the curve sizes P- | Page 30 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks | FCS_COP.1/SigVer | 384 and P-521. During TLS handshakes, these certificates are used for peer authentication to verify the server's identity (and/or client, if configured). These certificates are also used by the TOE to present its identity to the peer. Corresponding CAVP certificates and the relevant schemes for these algorithms are present in the table below. | |-------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | FCS_HTTPS_EXT.1 FCS_HTTPS_EXT.2 | The TOE provides a web UI protected by HTTPS (complies with RFC 2818) to the administrators. The TOE acts as an HTTPS server and waits for client connections on TCP port 443. The TOE's HTTPS server supports TLSv1.2 only and will deny connection requests from TLS clients with lower versions. By default, mutual authentication is not enabled. In the evaluated configuration, the administrator must enable mutual authentication. The TLS implementation that protects the HTTP connection is the same implementation as described below. The verification of the peer certification (server or client) is configurable. | | FCS_RBG_EXT.1 FCS_RBG.1 FCS_RBG.2 | The TOE implements DRBG functionality using the CTR_DRBG in AES-256 mode. The DRBG is seeded using the platform's entropy source (outside of TOE's boundary), which provides a minimum of 256 bits of entropy. The entropy design source description is described in a separate document proprietary to the platform vendor. | | FCS_STO_EXT.1 FCS_SNI_EXT.1 | The TOE uses AES-CBC (256-bits keys) and IVs generated by Approved DRBG to protect sensitive data such as API keys or passphrases in the TOE database on the non-volatile memory. API keys are used for authentication during API calls. The passphrase is used to encrypt the private key. Restrictive access and permissions to the database are, in addition, enforced by Linux. | | FCS_TLSS_EXT.1 FCS_TLSS_EXT.2 FCS_TLSS_EXT.4 FCS_TLSS_EXT.5 | All data that is transmitted between the Server and the web users and Client in the operational environment are encrypted using TLSv1.2. When the TOE is establishing a TLS session, it checks the reference identifier that has been specified by the administrators. These reference identifiers can include FQDN or IP address (not recommended) and are checked by looking at the Subject Alternative Name (SAN). The certificate must have a SAN field, or the TLS connection will be terminated. The TOE does not support wildcards if a certificate is presented with one in it. Certificate pinning is also not supported but session tickets are supported for session resumption based on RFC 5077 and session renegotiation is not allowed. The extended_master_secret extension is also supported. CA certificates are stored in the Linux trust anchor or key store. The TOE will also only support the same four cipher suites below. TLS version 1.2 is the only version of TLS supported by the TOE. ● TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ● TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 The server supports secp384r1 and secp521r1 NIST curves and signature_algorithms identified in the SFR above. During the negotiation of the TLS handshake, X.509v3 certificates are used to verify the client's identity (if configured for mutual authentication). | Page 31 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks Table 3 Cryptographic Functions and CAVP Certificates | Algorithm Name and Capabilities | Algorithm Description | Certificate | |----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------| | Asymmetric key generation (FCS_CKM.1 and FCS_CKM.1/AK) | Asymmetric key generation (FCS_CKM.1 and FCS_CKM.1/AK) | Asymmetric key generation (FCS_CKM.1 and FCS_CKM.1/AK) | | ECDSA KeyGen and KeyVer (P-384, P-521 curves) | FIPS PUB 186-5 , 'Digital Signature Standard (DSS)', Appendix A.2 | #A8208 | | Cryptographic key establishment (FCS_CKM.2) | Cryptographic key establishment (FCS_CKM.2) | Cryptographic key establishment (FCS_CKM.2) | | Elliptic Curve Diffie-Hellman with NIST Curves P-384 and P-521 | NIST Special Publication 800-56A Revision 3, 'Recommendation for Pair -Wise Key Establishment Schemes Using Discrete Logarithm Cryptography' | #A8208 | | Symmetric encryption/decryption (FCS_COP.1/SKC) | Symmetric encryption/decryption (FCS_COP.1/SKC) | Symmetric encryption/decryption (FCS_COP.1/SKC) | | AES-CBC (256 bits) AES-GCM (256 bits) | Advanced Encryption Standard (FIPS PUB 197) CBC as defined in NIST SP 800-38A GCM as defined in NIST SP 800-38D | #A8208 | | Cryptographic hashing (FCS_COP.1/Hash) | Cryptographic hashing (FCS_COP.1/Hash) | Cryptographic hashing (FCS_COP.1/Hash) | | SHA-384 SHA-512 | Secure Hashing Algorithm (FIPS PUB 180-4) | #A8208 | | Cryptographic signature services (FCS_COP.1/Sig) | Cryptographic signature services (FCS_COP.1/Sig) | Cryptographic signature services (FCS_COP.1/Sig) | | RSA SigGen and SigVer with 3072- bit modulus | Rivest - Shamir - Adleman (FIPS PUB 186-5) | #A8208 | | ECDSA SigGen and SigVer with NIST Curves P-384 and P-521 | Elliptical Curve Digital Signature Algorithm (FIPS PUB 186-5) | #A8208 | | Keyed-hash message authentication (FCS_COP.1/KeyedHash) | Keyed-hash message authentication (FCS_COP.1/KeyedHash) | Keyed-hash message authentication (FCS_COP.1/KeyedHash) | | HMAC-SHA-384 HMAC-SHA-512 | Hash-based Message Authentication Code FIPS PUB 198-1 FIPS PUB 180-4 | #A8208 | | Deterministic random bit generation (FCS_RBG.1) | Deterministic random bit generation (FCS_RBG.1) | Deterministic random bit generation (FCS_RBG.1) | | Counter DRBG (AES-256) | Deterministric Random Bit Generator NIST SP 800-90A | #A8208 | ### 6.2 User Data Protection | FDP_DEC_EXT.1 | The TOE accesses the network connectivity of its platform as identified by the SFR. The TOE does not access any sensitive information repositories. | |-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| | FDP_NET_EXT.1 | The TOE can respond to user-initiated HTTPS connection sessions or TLS connection with TLS client in the operational environment. | Page 32 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks | FDP_DAR_EXT.1 | The TOE protects sensitive data (such as API keys) in accordance with FCS_STO_EXT.1. Please see FCS_STO_EXT.1 for more details. | |-----------------|-----------------------------------------------------------------------------------------------------------------------------------| ### 6.3 Identification and Authentication | FIA_X509_EXT.1 | The TOE implements the ability to perform certificate path validation on the certificate chain that is presented to it by the peer. The certificate path validation begins with the identity certificate presented by the peer, and then proceeds in checking the intermediate CA certificate(s) until it reaches the trusted CA certificate stored in the platform OS trust store. If no trusted CA certificate is found (i.e., the TOE cannot choose to use any certificate for path validation), the session will terminate. The following steps are performed for each certificate in the path: ● The public key algorithm/parameters are checked (i.e., RSA/ECDSA key sizes meet requirements of 2048 bits or greater for RSA and 256 bits or greater for ECDSA) ● The certificate is checked to make sure it is not expired (i.e., validity period of the certificate must be proper) ● The certificate is checked to make sure it is not revoked using OCSP ● The issuer name is checked to ensure that it matches the subject name of the previous certificate in the chain ● The certificate is checked that it terminates with a trusted CA certificate and that all CA certificate have the basicConstraints extension present (and set to TRUE) ● The extendedKeyUsage field is checked such that OCSP certificates and server/client certificates contain the correct OID (e.g., OCSP Signing purpose and Server/Client Authentication purpose) ● The key usage extension of the certificate is checked to make sure that it is allowed to sign certificates Certificates that are presented to the TOE must meet the x509v3 requirements as defined in RFC 5280 for TLS. If there are any issues with the certificate presented (as noted above), the TOE will not accept the certificate and reject the connection. A log message will be generated, and an administrator will be required to address the problem noted for the connection to succeed. The TOE also supports revocation checking of the certificate presented using OCSP as specified in RFC 2560. In the event that the certificate is revoked following a check of its status, the TOE will terminate the connection. If the OCSP responder can't b e reached, the administrator can configure if the connection is established or terminated prior to the event occurring. As the TOE is a software application, it depends on the platform to generate the CSR (Certificate Signing Request) using PKCS-10 format and path validation consistent with intended usage. The CSR may include Organization name (O), Department (OU), State (S), but Common Name (CN), Subject Alternative Name (SAN), and public key are required. In addition, the SAN types DNS and/or IP addresses are supported. For the purpose of the functions, only these two SAN types are applicable in the | |-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | FIA_X509_EXT.2 FIA_X509_EXT.3 | | Page 33 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks | | evaluated configuration. Peer certificates must contain SAN or the TLS session will not be established. | |-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | FIA_XCU_EXT.1 FIA_XCU_EXT.2 | The TOE will verify the peer certification for TLS authentication. In addition, the TOE supports mutual authentication and will assert its own identity as well. For its own X.509 certificate, the TOE requests a certificate from an external CA via the platform. | Page 34 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ### 6.4 Security Management | FMT_MEC_EXT.1 | The TOE stores its configuration settings and logs in Linux recommended directories. | |-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | FMT_CFG_EXT.1 | The TOE is shipped with default credentials. However, one of the first things the administrator must do is to create new secure credentials. Otherwise, the administrator cannot proceed with the installation and setup. By default, the TOE includes file permissions that protect the TOE's binary and data files from modification from normal unprivileged users. The TOE also includes an integrity check for itself to ensure that no malicious activity occurs. | | FMT_SMF.1 | The TOE provides several management functions that include the following: ▪ User management ▪ Password change ▪ Password complexity management ▪ TLS/X509 configuration ▪ Querying the current version of the TOE ▪ Encrypting API keys and passphrase in database | ### 6.5 Privacy | FPR_ANO_EXT.1 | The TOE does not transmit or store any personally identifiable information about an individual. | |-----------------|---------------------------------------------------------------------------------------------------| ### 6.6 Protection of the TSF | FPT_API_EXT.1 | The TOE includes the use of documented Linux system APIs (kernel version 2.6.26 or later). System function calls includes functionality such as ● Driver, ● Data type, ● C library functions, ● Kernel functions, ● Memory management, ● Kernel IPC, ● Hardware, and ● Firmware. | |-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | FPT_AEX_EXT.1 | The TOE automatically enables ASLR when the application is compiled (with -pie build flag), and stack-based buffer overflow protection is enabled via Golang language. The TOE does not request any memory mapping at an explicit address. The TOE does not allocate any memory region with both write and execute permissions; | Page 35 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks | | users shall also not write user-modifiable files to directories that contain executable files unless they are explicitly told to do so. The TOE is designed to be compatible with the security features that are provided by the platform (SELinux or AppArmor) vendor that is it installed on. | |-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | FPT_FLS.1 FPT_TST.1 | The DRBG self-test and failure detection and description are described in a separate document proprietary to the platform vendor. If any of the self-tests fails, the TOE will not start up (i.e., in FIPS error state). Please reboot the system or re-install the TOE if the failure is persistent. | | FPT_TUD_EXT.1 FPT_TUD_EXT.2 | The TOE has specific versions, which can be queried by the user via the TOE's interface. New versions of the TOE are created by Palo Alto Networks, which an administrator can retrieve to update the current version of the TOE. During the installation process, a digital signature verification check can be performed by the platform to verify that the signed installer has not been modified. All versions of the installer are digitally signed by Palo Alto Networks. Customer Support will send verified customers an email with a download link. They also send license key and instructions in the email. The link is only valid for a limited number of downloads and time. The image is securely retrieved from the download server (https://download.demisto.com) The TOE cannot update its own binary code - it relies on the administrator to download and install the new version available. Registered users are emailed when a security update has been published and available on the download server. Customers with support account in the Customer Support Portal (https://support.paloaltonetworks.com/) will also get notifications as well. Based on the Linux distribution, the package can be RPM (e.g., Redhat) or DEB (e.g., Ubuntu). | | FPT_LIB_EXT.1 | The TOE utilizes Golang (version 1.25) for its TLS functions and Go Crypto module (version 1.0.0 5 ) for its crypto functions. | Page 36 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ### 6.7 Trusted Path/Channel | FTP_DIT_EXT.1 | All data transmitted between the Server and the web users and TLS clients (in the operational environment) are encrypted using TLSv1.2. For more details, please see the FCS_HTTPS* and FCS_TLS* requirements above. | |-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| Page 37 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ## 7. Protection Profile Claims This ST is conformant to the [APPSW]. Page 38 of iv Cortex SOAR Server 6.14 Security Target Palo Alto Networks ## 8. Rationale This Security Target includes by reference the [APPSW] Security Problem Definition, Security Objectives, and Security Assurance Requirements. The security target makes no additions to the [APPSW] assumptions. Security functional requirements have been reproduced verbatim with the protection profile operations completed. Operations on the security requirements follow [APPSW] application notes and assurance activities. The security target did not add or remove any security requirements. Consequently, [APPSW] rationale applies and is complete. Page 39 of iv