> 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-8-opp-release-notes/8.8/features-introduced-in-this-release/marketplace-content-changes.md).

# Marketplace Content Changes

## Marketplace Content Changes

This section describes the changes in content (integrations, playbooks, and indicators) from Cortex 8.7 to 8.8.

| Content                                                           | Description                                                                                                                                                                                                                                                                                                                 | Change Type |
| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
| Symantec Email Security Cloud integration                         | Introduced a new integration to enhance email filtering and blocking capabilities directly from Cortex XSOAR. For more information, see [Symantec Email Security Cloud](https://xsoar.pan.dev/docs/reference/integrations/symantec-email-security-cloud).                                                                   | New         |
| Command and Scripting Interpreter playbook for Crowdstrike Falcon | Introduced a new playbook to handle alerts based on the T1059 technique, which addresses potential threats that an attacker may exploit to execute commands, scripts, and binaries. For more information, see [CrowdStrike Falcon](https://cortex.marketplace.pan.dev/marketplace/details/CrowdStrikeFalcon/).              | New         |
| Splunk PY integration                                             | Added multiple events support to the `splunk-submit-event-hec` command, which improves performance for high-volume event collection and leverages batch submission supported by Splunk HEC API. For more information, see [Splunk-PY](https://xsoar.pan.dev/docs/reference/integrations/splunk-py#splunk-submit-event-hec). | Update      |
| Prisma Cloud Compute Integration                                  | Added the `prisma-cloud-compute-custom-feeds-ip-remove` integration, which removes a list of IP addresses from the system's block list. For more information, see [Palo Alto Networks - Prisma Cloud Compute](https://xsoar.pan.dev/docs/reference/integrations/palo-alto-networks-prisma-cloud-compute).                   | Update      |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-8-opp-release-notes/8.8/features-introduced-in-this-release/marketplace-content-changes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.