> 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-xsiam/cloud-security/overview/secure-your-api-landscape.md).

# Secure your API landscape

Secure APIs in Cortex XSIAM through gateway integration, risk assessment, threat monitoring, specification validation, and workload protection.

Integrate Cortex Cloud with your API Gateway (AWS, Azure, GCP, Kong or F5 BIG-IP LTM) to scan traffic and analyze logs. With Cortex Cloud, use the API security features to monitor, manage, and enforce security policies across the integrated API gateways. In addition, the API specification can validate live traffic against specifications and alert on surface deviations, undocumented endpoints, or security gaps.

Refer to the relevant section for more information:

* [Gain visibility and assess risk of API endpoints](/cortex-xsiam/cloud-security/overview/secure-your-api-landscape/gain-visibility-and-assess-risk-of-api-endpoints.md)
* [Monitor and investigate API threats](/cortex-xsiam/cloud-security/overview/secure-your-api-landscape/monitor-and-investigate-api-threats.md)
* [Configure API security from end to end](/cortex-xsiam/cloud-security/overview/secure-your-api-landscape/configure-api-security-from-end-to-end.md)
* [API specification inventory](/cortex-xsiam/cloud-security/overview/secure-your-api-landscape/api-specification-inventory.md)


---

# 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-xsiam/cloud-security/overview/secure-your-api-landscape.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.