> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/troubleshoot/best-practices/ip-whitelist.md).

# IP Whitelist

### When and Why would you need to Whitelist the AutoRABIT IP Address? <a href="#when-and-why-would-you-need-to-whitelist-the-autorabit-ip-address" id="when-and-why-would-you-need-to-whitelist-the-autorabit-ip-address"></a>

IP whitelisting adheres to the Zero Trust model's principle of '**deny all and permit some**.' So by default, all unknown entities are denied access to network resources. Because the Customer network by default blocks all traffic, AutoRABIT is unable to access the services on GIT in order to proceed with Salesforce release management.

Application whitelists help in the protection of your system against malware, spam, ransomware, and other threats. Only approved apps can run thanks to application whitelists. Anything that is not whitelisted is deemed unsafe and is blocked.

To facilitate the connectivity of AutoRABIT with your VCS, you need to whitelist the specific IP address allocated to your AutoRABIT instance.

When a customer instance is behind a firewall, one of the methods for configuring connectivity is required. You can either whitelist AutoRABIT instance IPs in your Git network or set up the required VPN Tunnel. Any of these connections can be assisted by AutoRABIT.


---

# 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://knowledgebase.autorabit.com/product-guides/arm-1/troubleshoot/best-practices/ip-whitelist.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.