> 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-expander-rn/2026-releases/february-2026.md).

# Release 2.12 (February 2026)

The table below describes the features and enhancements introduced in the Cortex Xpanse Expander 2.12 (February 2026) release.

Cortex Xpanse typically upgrades customers over a three-week time frame. Contact customer success to find out your specific upgrade date.

#### Attack Surface Management

| FEATURE                                           | DESCRIPTION                                                                                                                                                                                                                                                                                       |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Improved asset attribution evidence               | See exactly why assets link to your organization. We expanded attribution logic to expose determinations made by analysts and machine learning models, helping you validate assets faster.                                                                                                        |
| CPE information in Services API                   | Accelerate vulnerability workflows. You can now ingest Common Platform Enumeration (CPE) data via the Services API to directly correlate services with CVEs and track versions accurately.                                                                                                        |
| RADAR service classifications                     | <p>RADAR service classifications have moved from 2.12 to a future release.</p><p>Scan data is now enriched with RADAR details, including port, protocol, product, and version information. This enhanced data can be searched and filtered and provides better visibility into more services.</p> |
| Cloud observation processing logic update         | Reduce false positives. Expander decreases the threshold for new observations to limit attribution after a cloud resource is released or modified. Applies to Prisma Cloud, AWS, GCP, and Azure.                                                                                                  |
| Dangerous API misconfiguration validation testing | Newly added, more intrusive Attack Surface Tests (AST) offer the ability to validate dangerous misconfigurations in API frameworks such as Spring Boot.                                                                                                                                           |


---

# 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-expander-rn/2026-releases/february-2026.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.