> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/support/security-standards.md).
# Security Standards
As a provider of cloud services, Pump adheres to several cybersecurity frameworks to ensure our customers can operate their digital workloads in a safe and secure environment.
In addition to rigorous adherence to [AWS best security practices](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege), Pump maintains compliance with several other security frameworks, including:
* SOC 2
* ISO 27001
* GDPR
* AWS Well-Architected Framework
#### **Billing level-only permissions**
We also limit permissions so that Pump can only access your billing data and infrastructure metadata. Pump does not take permissions to view any application data or user data in your workloads.
For information, please see our [Role Deployment and Permissions Page](https://support.pump.co/articles/4053642719-role-deployment).
#### **App authentication and authorization**
Pump uses Auth0 as the authentication provider for users to verify email and log into the platform. Auth0 is compliant with most established security frameworks, and certifications can be viewed on their website [here](https://auth0.com/docs/secure/data-privacy-and-compliance).
#### **Security auditing**
Pump engages third-party companies to conduct regular penetration testing to identify any potential security risks.
---
# 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://help.pump.co/support/security-standards.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.