> For the complete documentation index, see [llms.txt](https://support.incidentlake.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidentlake.com/settings/security.md). # Security Audit history and the controls that protect your workspace. Incident Lake keeps a record of important actions so you can answer “who did what, and when?” ## Audit log Administrators open **Settings → Security** to review the audit log: sign-in and member changes, configuration updates, and other security-relevant events. Use it for internal reviews and external audits. ## What every user should do * Turn on **two-factor authentication** in [Your profile](/settings/profile.md) * Verify your email * Sign out on shared computers * Use SSO when your organization offers it ## Organization controls Depending on your plan, your organization can also: * Require SSO for the company domain — set up by SIGQ; write to to enable it * Limit sign-in to known office or VPN addresses — also set up by SIGQ on request * Restrict who can see certain incidents with access tags (shown as **RBAC tags** in organization settings) — Administrators manage these themselves SIGQ operates Incident Lake under an information security program that includes ISO/IEC 27001 and a SOC 2 Type 1 report. For security questionnaires, write to . --- # 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://support.incidentlake.com/settings/security.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.