> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/security/company-security.md). # Company Security Overview of how the security/encryption setup is within Zwapgrid. Making sure that our partners and end customers credentials are safe has always been the top priority within Zwapgrid and we are proud to say that we have passed a number of technical due diligence processes as well as KYC and "Reputational Risk" assessments from several of the largest banks in northern Europe. ### Zero Trust We operate a zero-trust approach with regard to access to our environments. Access is only granted as necessary, with limited or no access depending on the needs of the employee. Access to sensitive production systems is restricted to a limited number of individuals and access policies are in place to prevent unauthorised access. ### Multi Factor Authentication We enforce multi factor authentication for our employees across all services we use at Zwapgrid, and this is enabled by default for sensitive systems such as Microsoft Azure, and business apps such as Google Workspace and Slack. --- # 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.zwapgrid.com/security/company-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.