> For the complete documentation index, see [llms.txt](https://docs.mithril.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mithril.ai/security-and-trust/mithrils-approach-to-security.md).

# Mithril's approach to security

Safeguarding your data is paramount for us. We've embraced a security-first approach from day zero, ensuring that data protection is integrated into every aspect of our platform from the ground up rather than retrofitted. Mithril uses security best-practices to ensure you are on a trusted platform. You can view a complete list of our security measures in our [Trust Center](https://trust.mlfoundry.com/).

Some highlights about Mithril's approach to security:

* All compute available through Mithril is hosted in Tier 3 and 4 datacenters with SOC 2 Type II or ISO 27001 compliance that have passed our security requirements. All datacenters enforce strict access controls, biometric measures, and personnel authorization.
* Mithril is SOC 2 Type II certified in availability, security, and confidentiality.
* We ensure that only you have access to the SSH keys for your instances.


---

# 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.mithril.ai/security-and-trust/mithrils-approach-to-security.md?ask=<question>&goal=<user_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.