> 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 Understand Cortex Cloud’s cloud security engineer persona, responsibilities, and workflows for prioritizing and remediating risk. **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 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-cloud-runtime-security/get-started/understand-your-user-persona.md?ask=&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.