> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/get-started/onboarding-to-ox/prerequisites-and-access.md).

# Prerequisites and Access

Before you begin setting up OX, review the following prerequisites to ensure a smooth onboarding process.

## Preparation steps

1. Review the [supported languages and frameworks](https://docs.ox.security/supported-languages-and-frameworks.md).
2. Choose your hosting type: SaaS or On-Prem. In case of the on-prem installation, use the [On-Prem Preparation Guide](https://docs.ox.security/get-started/onboarding-to-ox/prerequisites-and-access/ox-deployment/on-prem-preparation-guide.md).

## Access and permissions

1. Ensure you have access to your company’s source control, CI/CD, registry, and ticketing systems.
2. Have credentials for your identity provider (for example, Okta, Azure AD, or Google Workspace) if you plan to enable SSO.

#### External IP addresses

If your organization restricts outbound or inbound network traffic by IP address, allow the following OX Security external IP addresses:

| IP address          |
| ------------------- |
| `54.76.158.3/32`    |
| `63.33.229.6/32`    |
| `34.249.173.69/32`  |
| `108.128.213.11/32` |
| `34.251.91.128/32`  |

> **Important:**\
> If your firewall, proxy, VPN, or network security controls use IP allowlists, add all of the preceding IP addresses to ensure uninterrupted connectivity with OX services.

#### Agentic Pentester IP addresses

If you use Agentic Pentester, allowlist the following IP addresses to enable OX to access and test your targets:

* `63.33.147.64/32`
* `18.202.47.201/32`

## Next Step

After completing these checks, proceed to [Connecting to OX](https://docs.ox.security/get-started/onboarding-to-ox/connect-to-ox.md).


---

# 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.ox.security/get-started/onboarding-to-ox/prerequisites-and-access.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.
