> For the complete documentation index, see [llms.txt](https://documentation.grax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.grax.com/security/security-testing.md).

# Security Testing

GRAX periodically conducts its own penetration tests, undergoes external penetration tests, and completes other security audits. These results are available to our customers via the [GRAX Trust Center](https://trust.grax.com/resources). To view the results, click `Request Access`, and you'll receive a notification once access has been granted.

If you are interested in performing your own penetration tests of GRAX, please contact [GRAX Support](/support/get-support.md) with details of your testing processes and schedule to get approval for any penetration testing.

Our cloud service providers also publish their own security reports and penetration testing guidance:

* [ngrok Security Portal](https://trust.ngrok.com/)
* [AWS Penetration Testing](https://aws.amazon.com/security/penetration-testing/)
* [Azure Penetration Testing](https://learn.microsoft.com/en-us/azure/security/fundamentals/pen-testing)


---

# 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://documentation.grax.com/security/security-testing.md?ask=<question>&goal=<endgoal>
```

`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.