> 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-cloud-runtime-security/get-started/understand-your-user-persona.md).

# Understand your user persona

**Cloud security engineers**

Cloud security engineers or architects design and maintain a system that protects everything their organization hosts across various cloud service providers. Their goal is to achieve zero critical risks and compliance violations without blocking the productivity of other teams. Their responsibilities include:

* Deploying and managing cloud security tooling
* Performing cloud risk assessments (zero day vulnerability impact analysis)
* Detecting, prioritizing, and remediating cloud security alerts
* Collaborating with cross-functional teams to reduce risk (DevOps, App owners)
* Maintaining and monitoring compliance posture
* Generating security reports

With Cortex Cloud, cloud security engineers can:

* Get complete visibility without blind spots across multi cloud environments
* Manageable alerts
* Avoid manual parsing that prolongs risk assessment and reporting efforts
* Get better risk context that aids prioritization and remediation efforts with cross-functional teams


---

# 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/cortex-cloud-runtime-security/get-started/understand-your-user-persona.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.
