> 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-posture-management/insights-and-tips-cortex-cloud/data-and-platform-administration/audit-logs.md). # Audit logs Learn how audit logs in Cortex Cloud Posture Management track administrative and investigative activity, retain records, and forward notifications to external services. The management audit log records administrative and investigative activity in your tenant: who performed each action, when, the action type and result, and the affected object. Logged activity includes: * Configuration and policy changes, including detection rules, exceptions, and playbooks * Authentication and API key changes * Endpoint administration and response actions, including Live Terminal commands * Case management and remediation Audit logs are retained for **365 days**. You can forward audit notifications to external destinations, such as syslog or email. See [Monitor administrative activity](/cortex-cloud-posture-management/onboard-and-configure/post-deployment-steps/set-up-your-environment/data-and-log-forwarding/forward-logs-and-data-from-cortex-cloud-to-external-services/monitor-administrative-activity.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-cloud-posture-management/insights-and-tips-cortex-cloud/data-and-platform-administration/audit-logs.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.