> For the complete documentation index, see [llms.txt](https://docs.vectice.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectice.com/25.2/it-and-security/security/audit-logs.md). # Audit logs Your security is our top priority. To ensure the safety and integrity of your data, our backend system generates comprehensive audit logs. These logs provide a detailed record of user activities within the system. ## Backend audit logs Our backend system maintains comprehensive audit logs that meticulously track all user authentication attempts.\ \ These logs capture essential details for each attempt, including the date and time, the user performing the action (identified by username or email address), and the source of the attempt (either our Python API or web application).\ \ This granular logging allows us to monitor user activity, identify potential security risks associated with login attempts, and ensure the integrity of our authentication processes. ## Cloud audit logs Our SaaS platform leverages Cloud audit logs. These logs track access to and modifications of your project's resources within the Cloud infrastructure. It's important to note that Cloud's logs focus on Cloud-related activity and may not directly reflect user actions within your application.\ \ For self-hosted infrastructure, You have complete control over the configuration and management of audit logs, allowing you to tailor them to your specific security needs. **Combined security** Combining the detailed logs from our backend system with Cloud audit logs gives you a comprehensive view of activity within your system. This comprehensive audit trail empowers you to: * Investigate potential security incidents * Ensure compliance with security regulations * Maintain a strong security posture for your data --- # 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://docs.vectice.com/25.2/it-and-security/security/audit-logs.md?ask=&goal= ``` `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.