## National Information Assurance Partnership ## Common Criteria Evaluation and Validation Scheme ## Validation Report ## Palo Alto Networks Cortex XSOAR Server 6.14 Report Number: Dated: CCEVS-VR-VID11715-2026 October 26, 2026 Version: 0.2 National Institute of Standards and Technology Information Technology Laboratory 100 Bureau Drive Gaithersburg, MD 20899 Department of Defense ATTN: NIAP, Suite 6982 9800 Savage Road Fort Meade, MD 20755-6982 Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 ###### ACKNOWLEDGEMENTS ####### Validation Team Jerome Myers Marybeth Panock Seada Mohammed The Aerospace Corporation ####### Common Criteria Testing Laboratory John Messiha Gossamer Security Solutions, Inc. Columbia, MD ii Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 ## Table of Contents | 1 | Executive Summary ................................................................................................................ | 1 | |-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------| | 2 | Identification ........................................................................................................................... | 1 | | 3 | Architectural Information ....................................................................................................... | 3 | | 3.1 | TOE Description ............................................................................................................. | 3 | | 3.2 | TOE Evaluated Platforms ............................................................................................... | 3 | | 3.3 | TOE Architecture ............................................................................................................ | 3 | | | 3.4 Physical Boundaries ........................................................................................................ | 4 | | 4 | Security Policy ........................................................................................................................ | 4 | | | 4.1 Cryptographic support .................................................................................................... | 4 | | 4.2 | User data protection ........................................................................................................ | 4 | | | 4.3 Identification and authentication..................................................................................... | 5 | | 4.4 | Security management ...................................................................................................... | 5 | | 4.5 | Privacy ............................................................................................................................ | 5 | | 4.6 | Protection of the TSF ...................................................................................................... | 5 | | 4.7 | Trusted path/channels ..................................................................................................... | 5 | | 5 | | 5 | | | Assumptions & Clarification of Scope ................................................................................... | | | 6 | Documentation ........................................................................................................................ | 6 7 | | 7 | IT Product Testing .................................................................................................................. | 7 | | 7.1 7.2 | Developer Testing ........................................................................................................... Evaluation Team Independent Testing ........................................................................... | 7 | | 8 | | 7 | | 9 | Evaluated Configuration ......................................................................................................... | | | | Results of the Evaluation ........................................................................................................ | 7 | | 9.2 Evaluation of the Development | 9.1 Evaluation of the Security Target (ASE) ........................................................................ | 7 (ADV) .......................................................................... 8 | | 9.3 Evaluation of the Guidance | | Documents (AGD) ............................................................. 8 | | 9.4 | Evaluation of the Life Cycle Support Activities (ALC) ................................................. | 8 | | | Evaluation of the Test Documentation and the Test Activity (ATE) ............................. | | | 9.5 | | 8 | | 9.6 | Vulnerability Assessment Activity (VAN) ..................................................................... | 9 | | 9.7 | Summary of Evaluation Results...................................................................................... | 9 | | 10 | Validator Comments/Recommendations ............................................................................ | 9 | | 11 | Annexes............................................................................................................................. | 10 | | 12 | Security Target .................................................................................................................. | 10 | | 13 | Glossary ............................................................................................................................ | 10 | | 14 | Bibliography ..................................................................................................................... | 11 | iii Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 ## 1 Executive Summary This report documents the assessment of the National Information Assurance Partnership (NIAP) validation team of the evaluation of Palo Alto Networks Cortex XSOAR Server 6.14 solution provided by Palo Alto Networks, Inc. It presents the evaluation results, their justifications, and the conformance results. This Validation Report is not an endorsement of the Target of Evaluation by any agency of the U.S. government, and no warranty is either expressed or implied. The evaluation was performed by the Gossamer Security Solutions (Gossamer) Common Criteria Testing Laboratory (CCTL) in Columbia, MD, United States of America, and was completed in September 2026. The information in this report is largely derived from the Evaluation Technical Report (ETR) and associated test reports, all written by Gossamer Security Solutions. The evaluation determined that the product is both Common Criteria Part 2 Extended and Part 3 Extended, and meets the assurance requirements of the Protection Profile for Application Software, Version 2.0, 16 June 2025 (ASPP20) with the Functional Package for Transport Layer Security (TLS), Version 2.1, 25 August 2025 (TLS21) and the Functional Package for X.509, version 1.0, 21 October 2024 (X50910). The Target of Evaluation (TOE) is the Palo Alto Networks Cortex XSOAR Server 6.14. The Target of Evaluation (TOE) identified in this Validation Report has been evaluated at a NIAP approved Common Criteria Testing Laboratory using the Common Methodology for IT Security Evaluation (Version 2022, Rev 1) for conformance to the Common Criteria for IT Security Evaluation (Version 2022, Rev 1). This Validation Report applies only to the specific version of the TOE as evaluated. The evaluation has been conducted in accordance with the provisions of the NIAP Common Criteria Evaluation and Validation Scheme and the conclusions of the testing laboratory in the evaluation technical report are consistent with the evidence provided. The validation team monitored the activities of the evaluation team, provided guidance on technical issues and evaluation processes, and reviewed the individual work units and successive versions of the ETR. The validation team found that the evaluation showed that the product satisfies all of the functional requirements and assurance requirements stated in the Security Target (ST). Therefore the validation team concludes that the testing laboratory's findings are accurate, the conclusions justified, and the conformance results are correct. The conclusions of the testing laboratory in the evaluation technical report are consistent with the evidence produced. The technical information included in this report was obtained from the Palo Alto Networks Cortex XSOAR Server 6.14 Security Target, version 0.3, September 16, 2026 and analysis performed by the Validation Team. ## 2 Identification The CCEVS is a joint National Security Agency (NSA) and National Institute of Standards and Technology (NIST) effort to establish commercial facilities to perform trusted product evaluations. Under this program, security evaluations are conducted by commercial testing laboratories called Common Criteria Testing Laboratories (CCTLs) using the Common Evaluation Methodology 1 Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 (CEM) in accordance with National Voluntary Laboratory Assessment Program (NVLAP) accreditation. The NIAP Validation Body assigns Validators to monitor the CCTLs to ensure quality and consistency across evaluations. Developers of information technology products desiring a security evaluation contract with a CCTL and pay a fee for their product's evalu ation. Upon successful completion of the evaluation, the product is added to NIAP's Validated Products List. Table 1 provides information needed to completely identify the product, including: - The Target of Evaluation (TOE): the fully qualified identifier of the product as evaluated. - The Security Target (ST), describing the security features, claims, and assurances of the product. - The conformance result of the evaluation. - The Protection Profile to which the product is conformant. - The organizations and individuals participating in the evaluation. Table 1: Evaluation Identifiers | Item | Identifier | |------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Evaluation Scheme | United States NIAP Common Criteria Evaluation and Validation Scheme | | TOE | Palo Alto Networks Cortex XSOAR Server 6.14 (Specific models identified in Section 8) | | Protection Profile | Protection Profile for Application Software, Version 2.0, 16 June 2025 (ASPP20) with the Functional Package for Transport Layer Security (TLS), Version 2.1, 25 August 2025 (TLS21) and the Functional Package for X.509, version 1.0, 21 October 2024 (X50910) | | ST | Palo Alto Networks Cortex XSOAR Server 6.14 Security Target, version 0.3, September 16, 2026 | | Evaluation Technical Report | Evaluation Technical Report for Palo Alto Networks Cortex XSOAR Server 6.14, version 0.2, October 26, 2026 | | CC Version | Common Criteria for Information Technology Security Evaluation, Version 2022, rev 1 | | Conformance Result | CC Part 2 extended, CC Part 3 extended | | Sponsor | Palo Alto Networks, Inc. | | Developer | Palo Alto Networks, Inc. | | Common Criteria Testing Lab (CCTL) | Gossamer Security Solutions, Inc. Columbia, MD | | CCEVS Validators | Jerome Myers, Marybeth Panock, Seada Mohammed | 2 Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 ## 3 Architectural Information Note: The following architectural description is based on the description presented in the Security Target. The TOE is a software application that runs on various Linux environments (server/workstation) to provide SOC team with detection and automatic response capabilities1. 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. ### 3.1 TOE 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. ### 3.2 TOE Evaluated Platforms Detail regarding the evaluated configuration is provided in Section 8 below. ### 3.3 TOE Architecture The TOE is a software solution that is comprised of items listed in Section 2.2.1 of the ST. The software is available for download from the Palo Alto Networks support site. The following diagram depicts the software architecture of the TOE. 3 Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 ### 3.4 Physical Boundaries The physical boundary of the TOE is the application installed and running on a supported platform (i.e., Linux operating systems). ##### ● 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. ##### ● Hardware Requirements The TOE must be installed on the system with the minimum hardware requirements specified below. Minimum hardware: 16 CPU (minimum); 32 GB RAM (minimum); 1 TB of disk space (minimum) The TOE was installed and tested on the following platforms: - Ubuntu 24.04 - Processor: Intel Xeon Gold 6248 (Cascade Lake) ## 4 Security Policy This section summaries the security functionality of the TOE: ### Cryptographic support ### User data protection ### Identification and authentication ### Security management ### Privacy ### Protection of the TSF ### Trusted path/channels ## 4.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. ## 4.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. 4 Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 ## 4.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. ## 4.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. ## 4.5 Privacy The TOE does not transmit PII over the network. ## 4.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 signed and 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). ## 4.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). ## 5 Assumptions & Clarification of Scope ####### Assumptions The Security Problem Definition, including the assumptions, may be found in the following documents: - Protection Profile for Application Software, Version 2.0, 16 June 2025 (ASPP20) - Functional Package for Transport Layer Security (TLS), Version 2.1, 25 August 2025 (TLS21) - Functional Package for X.509, version 1.0, 21 October 2024 (X50910) That information has not been reproduced here and the ASPP20/TLS21/X50910 should be consulted if there is interest in that material . 5 Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 The scope of this evaluation was limited to the functionality and assurances covered in the ASPP20/TLS21/X50910 as described for this TOE in the Security Target. Other functionality included in the product was not assessed as part of this evaluation. All other functionality provided by the devices needs to be assessed separately, and no further conclusions can be drawn about their effectiveness . ####### Clarification of scope All evaluations (and all products) have limitations, as well as potential misconceptions that need clarification. This text covers some of the more important limitations and clarifications of this evaluation. Note that: - As with any evaluation, this evaluation only shows that the evaluated configuration meets the security claims made with a certain level of assurance (the assurance activities specified in the Application Software Protection Profile with the TLS and X509 Packages and performed by the evaluation team). - This evaluation covers only the specific device models and software as identified in this document, and not any earlier or later versions released or in process. - Apart from the Admin Guide, additional customer documentation for the specific Software Application models was not included in the scope of the evaluation and therefore should not to be relied upon when configuring or operating the device as evaluated. - This evaluation did not specifically search for, nor attempt to exploit, vulnerabilities that were not 'obvious' or vulnerabilities to objectives not claimed in the ST. The CEM defines an 'obvious' vulnerability as one that is easily exploited with a minim um of understanding of the TOE, technical sophistication and resources. - The functionality evaluated is scoped exclusively to the security functional requirements specified in the ASPP20/TLS21/X50910 and applicable Technical Decisions. Any additional security related functional capabilities of the TOE were not covered by this evaluation. ## 6 Documentation The following documents were available with the TOE for evaluation: - Palo Alto Networks Common Criteria Evaluated Configuration Guide (CCECG) Cortex XSOAR Server and Engine 6.14, Version 0.1, July 15, 2026 Any additional customer documentation provided with the product, or that is available online was not included in the scope of the evaluation and therefore should not to be relied upon when configuring or operating the device as evaluated. To use the product in the evaluated configuration, the product must be configured as specified in the Guidance Documentation listed above. Consumers are encouraged to download the configuration guides from the NIAP website to ensure the device is configured as evaluated. 6 Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 ## 7 IT Product Testing This section describes the testing efforts of the developer and the Evaluation Team. It is derived from information contained in the proprietary Detailed Test Report for Palo Alto Networks Cortex XSOAR Server 6.14, Version 0.2, October 26, 2026 (DTR), as summarized in the evaluation Assurance Activity Report (AAR). ### 7.1 Developer Testing No evidence of developer testing is required in the assurance activities for this product. ### 7.2 Evaluation Team Independent Testing The evaluation team verified the product according to a Common Criteria Certification document and ran the tests specified in the ASPP20/TLS21/X50910 including the tests associated with optional requirements. The AAR, in sections 1.1 lists the tested devices, provides a list of test tools, and has diagrams of the test environment. ## 8 Evaluated Configuration The evaluated configuration is the Cortex XSOAR Server 6.14. The TOE was tested on Ubuntu 24.04 - Processor: Intel Xeon Gold 6248 (Cascade Lake). ## 9 Results of the Evaluation The results of the assurance requirements are generally described in this section and are presented in detail in the proprietary ETR. The reader of this document can assume that all assurance activities and work units received a passing verdict. A verdict for an assurance component is determined by the resulting verdicts assigned to the corresponding evaluator action elements. The evaluation was conducted based upon CC version 2022 rev 1 and CEM version 2022 rev 1. The evaluation determined the Palo Alto Networks Cortex XSOAR Server 6.14 TOE to be Part 2 extended, and to meet the SARs contained in the ASPP20/TLS21/X50910. ### 9.1 Evaluation of the Security Target (ASE) The evaluation team applied each ASE CEM work unit. The ST evaluation ensured the ST contains a description of the environment in terms of policies and assumptions, a statement of security requirements claimed to be met by the Palo Alto Networks Cortex XSOAR Server 6.14 products that are consistent with the Common Criteria, and product security function descriptions that support the requirements. The validator reviewed the work of the evaluation team, and found that sufficient evidence and justification was provided by the evaluation team to confirm that the evaluation was conducted in accordance with the requirements of the CEM, and that the conclusion reached by the evaluation team was justified. 7 Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 ### 9.2 Evaluation of the Development (ADV) The evaluation team applied each ADV CEM work unit. The evaluation team assessed the design documentation and found it adequate to aid in understanding how the TSF provides the security functions. The design documentation consists of a functional specification contained in the Security Target and Guidance documents. Additionally the evaluator performed the assurance activities specified in the ASPP20/TLS21/X50910 related to the examination of the information contained in the TSS. The validator reviewed the work of the evaluation team, and found that sufficient evidence and justification was provided by the evaluation team to confirm that the evaluation was conducted in accordance with the requirements of the CEM, and that the conclusion reached by the evaluation team was justified. ### 9.3 Evaluation of the Guidance Documents (AGD) The evaluation team applied each AGD CEM work unit. The evaluation team ensured the adequacy of the user guidance in describing how to use the operational TOE. Additionally, the evaluation team ensured the adequacy of the administrator guidance in describing how to securely administer the TOE. All of the guides were assessed during the design and testing phases of the evaluation to ensure they were complete. The validator reviewed the work of the evaluation team, and found that sufficient evidence and justification was provided by the evaluation team to confirm that the evaluation was conducted in accordance with the requirements of the CEM, and that the conclusion reached by the evaluation team was justified. ### 9.4 Evaluation of the Life Cycle Support Activities (ALC) The evaluation team applied each ALC CEM work unit. The evaluation team found that the TOE was identified. The validator reviewed the work of the evaluation team, and found that sufficient evidence and justification was provided by the evaluation team to confirm that the evaluation was conducted in accordance with the requirements of the CEM, and that the conclusion reached by the evaluation team was justified. ### 9.5 Evaluation of the Test Documentation and the Test Activity (ATE) The evaluation team applied each ATE CEM work unit. The evaluation team ran the set of tests specified by the assurance activities in the ASPP20/TLS21/X50910 and recorded the results in a Test Report, summarized in the AAR. The validator reviewed the work of the evaluation team, and found that sufficient evidence and justification was provided by the evaluation team to confirm that the evaluation was conducted in accordance with the requirements of the CEM, and that the conclusion reached by the evaluation team was justified. 8 Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 ### 9.6 Vulnerability Assessment Activity (VAN) The evaluation team applied each AVA CEM work unit. The vulnerability analysis is in the Detailed Test Report (DTR) prepared by the evaluator. The vulnerability analysis includes a public search for vulnerabilities. The public search for vulnerabilities did not uncover any residual vulnerability. The evaluator searched the National Vulnerability Database (https://web.nvd.nist.gov/view/vuln/search) and Vulnerability Notes Database (http://www.kb.cert.org/vuls/) on 10/26/2026 (from 6/1/2025) with the following search terms: with the following search terms: ' Palo Alto Networks ', ' XSOAR ', ' Cortex XSOAR ', ' Cortex XSOAR Server ', ' Intel Xeon Gold 6248 ', ' Ubuntu 24.04 ', ' Golang 1.2 5', and ' Go Crypto 1.0.0 '. The validator reviewed the work of the evaluation team, and found that sufficient evidence and justification was provided by the evaluation team to confirm that the evaluation was conducted in accordance with the requirements of the CEM, and that the conclusion reached by the evaluation team was justified. ### 9.7 Summary of Evaluation Results The evaluation team's assessment of the evaluation evidence demonstrates that the claims in the ST are met. Additionally, the evaluation team's testing also demonstrated the accuracy of the claims in the ST. The validation team's assessment of the evidence provided by the evaluation team is that it demonstrates that the evaluation team followed the procedures defined in the CEM, and correctly verified that the product meets the claims in the ST. ## 10 Validator Comments/Recommendations The validation team notes that the evaluated configuration is dependent upon the TOE being configured per the evaluated configuration instructions in the Palo Alto Networks Common Criteria Evaluated Configuration Guide (CCECG) Cortex XSOAR Server and Engine 6.14 , Version 0.1, July 15, 2026. No versions of the TOE, either earlier or later, are covered by the scope of this evaluation. The scope of this evaluation was limited to the functionality and assurances covered in the ASPP20/TLS21/X50910 as described for this TOE in the Security Target. The product includes playbook detection and automatic response capabilities for use by the SOC team along with security management functions. These features are out of the evaluation scope and described in the Security Target for informational purposes only, as indicated by a footnote in ST Section 2.1 TOE Overview. 9 Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 Other functionality included in the product was not assessed as part of this evaluation. All other functionality provided by the application needs to be assessed separately, and no further conclusions can be drawn about its effectiveness. All other items and scope issues have been sufficiently addressed elsewhere in this document. ## 11 Annexes Not applicable ## 12 Security Target The Security Target is identified as: Palo Alto Networks Cortex XSOAR Server 6.14 Security Target, Version 0.3, September 16, 2026 . ## 13 Glossary The following definitions are used throughout this document: - Common Criteria Testing Laboratory (CCTL) . An IT security evaluation facility accredited by the National Voluntary Laboratory Accreditation Program (NVLAP) and approved by the CCEVS Validation Body to conduct Common Criteria-based evaluations. - Conformance . The ability to demonstrate in an unambiguous way that a given implementation is correct with respect to the formal model. - Evaluation . The assessment of an IT product against the Common Criteria using the Common Criteria Evaluation Methodology to determine whether or not the claims made are justified; or the assessment of a protection profile against the Common Criteria using the Common Evaluation Methodology to determine if the Profile is complete, consistent, technically sound and hence suitable for use as a statement of requirements for one or more TOEs that may be evaluated. - Evaluation Evidence . Any tangible resource (information) required from the sponsor or developer by the evaluator to perform one or more evaluation activities. - Feature. Part of a product that is either included with the product or can be ordered separately. - Target of Evaluation (TOE) . A group of IT products configured as an IT system, or an IT product, and associated documentation that is the subject of a security evaluation under the CC. - Validation . The process carried out by the CCEVS Validation Body leading to the issue of a Common Criteria certificate. - Validation Body . A governmental organization responsible for carrying out validation and for overseeing the day-to-day operation of the NIAP Common Criteria Evaluation and Validation Scheme. 10 Palo Alto Networks Cortex XSOAR Server 6.14 Validation Report Version 0.2, October 26, 2026 ## 14 Bibliography The Validation Team used the following documents to produce this Validation Report: - [1] Common Criteria for Information Technology Security Evaluation: Part 1: Introduction and General Model, Version 2022, Revision 1, April 2017. - [2] Common Criteria for Information Technology Security Evaluation Part 2: Security functional components, Version 2022, Revision 1, April 2017. - [3] Common Criteria for Information Technology Security Evaluation Part 3: Security assurance components, Version 2022 Revision 1, April 2017. - [4] Protection Profile for Application Software, Version 2.0, 16 June 2025 (ASPP20). - [5] Functional Package for Transport Layer Security (TLS), Version 2.1, 25 August 2025 (TLS21). - [6] Functional Package for X.509, version 1.0, 21 October 2024 (X50910). - [7] Palo Alto Networks Cortex XSOAR Server 6.14 Security Target, Version 0.3, September 16, 2026 (ST). - [8] Assurance Activity Report for Palo Alto Networks Cortex XSOAR Server 6.14, Version 0.2, October 26, 2026 (AAR). - [9] Detailed Test Report for Palo Alto Networks Cortex XSOAR Server 6.14, Version 0.2, October 26, 2026 (DTR). - [10] Evaluation Technical Report for Palo Alto Networks Cortex XSOAR Server 6.14, Version 0.2, October 26, 2026 (ETR). 11