> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/security.md). # Security In this section, you will find comprehensive user guides on key security topics, including: * [Security Plus](/platform/security/security-plus.md): Overview of Nexthink's advanced security features and configurations. * [Exporting Audit Logs](/platform/security/exporting-audit-logs.md): Step-by-step instructions on how to export and analyze audit logs for enhanced security monitoring. * [Security bulletins](/platform/security/security-bulletins.md): Access to critical security updates, advisories, and best practices to ensure your environment remains secure. * [Controlling session timeouts](/platform/security/controlling-session-timeouts.md): Guidance on configuring session timeout settings to protect against unauthorized access. For further details on Nexthink's security processes, controls, and access to important documents - such as certificates, reports, policies, and specific security controls in place - please log in to the [Nexthink Security Portal](https://docs.nexthink.com/security) available to Nexthink Community users. --- # 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://docs.nexthink.com/platform/security.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.