> 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/features-introduced-before-2026/2025-releases/release-28-february-2025.md).

# Release 2.8 (February 2025)

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

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

| Feature                                                     | Description                                                                                                                                                                                                                                                                                |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Simplified Self-Service Asset Management                    | The new bulk asset management features enable you to proactively add/remove assets, such as IP address ranges, paid-level domains, and subdomains, across your attack surface.                                                                                                             |
| Expanded coverage for automated exposure remediation        | The newly added support for Kubernetes Control Plane Component, LDAP Server, NetBIOS Name Server, NFS Rpcbind Server, Rpcbind Server, and SMB Server, enable you to save time and reduce manual work across a broader set of attack surface exposures.                                     |
| Dozens of new Attack Surface Rules and Attack Surface Tests | The new rules and tests expand detection coverage for existing and new KEV vulnerabilities. You can also discover over 100 unique OT/IoT devices, providing unmatched visibility across industrial and connected device environments.                                                      |
| Attack Surface Rules to identify malicious domain takeover  | Cortex Xpanse has released two attack surface rules to help identify malicious domain takeover of customer-owned domains. These policies detect malicious redirects and content injection for gambling sites, hacktivism, and extortion sites. These new rules will be enabled by default. |
| Dynamic Protocol Detection                                  | For a subset of our protocols and ports, Cortex Xpanse can dyamically detect 60+ server protocols. For details, reach out to your customer success contact.                                                                                                                                |
| New API capabilities                                        | These enhancements introduce new APIs to configure IdP and SSO authentication settings, enabling administrators greater control and efficiency in enforcing and managing access control.                                                                                                   |


---

# 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/features-introduced-before-2026/2025-releases/release-28-february-2025.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.