> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.12/learn-about-cortex-xsoar/get-started-in-cortex-xsoar/fips-version.md). # FIPS Version Use the vendor-affirmed FIPS version in Cortex XSOAR 6.12 with FIPS 140-3 validated cryptography. Palo Alto Networks offers a vendor-affirmed FIPS version of Cortex XSOAR. The vendor affirmed FIPS version, starting from version 6.2, uses a third-party software library, [BoringCrypto](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4735), as a crypto module. The BoringCrypto module has been validated against FIPS 140-3, a U.S. and Canadian government standard used to approve cryptographic modules. The vendor-affirmed FIPS version of Cortex XSOAR can be used for single server deployments, multi-tenant deployments, and high availability deployments (single server or multi-tenant). The vendor-affirmed FIPS version of Cortex XSOAR has similar functionality and supports the same [operating systems](/xsoar-6-administrator-guide/6.12/onboard-cortex-xsoar/single-server-deployment/system-requirements.md) as the non-FIPS version of Cortex XSOAR. Cortex XSOAR will, by default, install the standard version of Docker or Podman for your operating system. If you require the FIPS version of Docker or Podman instead, it must be installed before installing the vendor-affirmed FIPS version of Cortex XSOAR. The vendor-affirmed FIPS version of Cortex XSOAR has the following limitations: * Upgrades between FIPS and non-FIPS certified versions are not supported, including database migrations, backups, and restores. * The FIPS version supports only engines installed on the Linux operating system --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.12/learn-about-cortex-xsoar/get-started-in-cortex-xsoar/fips-version.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.