> 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/cortex-xpanse/reference/cortex-xpanse-product-policies/cortex-xpanse-product-security.md).

# Cortex Xpanse Product Security

Cortex Xpanse product security

Cortex Xpanse defines your public internet attack surface and tells you what you need to do to minimize risk. You’ll know what to do first, how to fix it, and what it means to your organization. To keep your information safe, Cortex Xpanse is designed with multiple layers of protection, distributed across a scalable, secure infrastructure.

These layers of protection include:

* Cortex Xpanse data at rest are encrypted using 256-bit Advanced Encryption Standard (AES). Cortex Xpanse data is stored in a combination of Amazon Web Services (AWS) and Google Cloud Platform (GCP).
* Cortex Xpanse uses Secure Sockets Layer (SSL)/Transport Layer Security (TLS) to protect data in transit between Cortex Xpanse application and Cortex Xpanse servers.
* SSL/TSL creates a secure tunnel protected by 128-bit or higher Advanced Encryption Standard (AES) encryption.
* Two-factor authorization (2FA) and Single sign-on (SSO) is available for an extra layer of security at login.
* Cortex Xpanse applications and infrastructure are regularly tested for security vulnerabilities and hardened to enhance security and protect against attacks.


---

# 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/cortex-xpanse/reference/cortex-xpanse-product-policies/cortex-xpanse-product-security.md?ask=<question>&goal=<user_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.