> For the complete documentation index, see [llms.txt](https://docs.biscit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biscit.com/biscit-spend-management/getting-started/bsm-firewall-rules-for-an-epicor-behind-a-vpn.md).

# BSM Firewall Rules for an Epicor Behind a VPN

If your Epicor server is not open to the internet, your network needs a few rules so that BSM can reach Epicor and be opened by users. This page lists those rules for each direction.

{% hint style="info" %}
Every connection uses HTTPS on port 443.
{% endhint %}

### Inbound to your Epicor server: allow by domain <a href="#inbound-to-your-epicor-server-allow-by-domain" id="inbound-to-your-epicor-server-allow-by-domain"></a>

Allow BSM's outbound domain through to your Epicor URL. Both BSM services connect to Epicor from the one address it points to:

* **Web service**: reads and updates Epicor while your users work in BSM.
* **Administration**: installs BSM into Epicor during setup, and manages BSM users and permissions afterwards.

These services connect only to the Epicor URL you gave BISCIT during onboarding, including the Kinetic home page on that same host. BSM does not reach any other server on your network.

| Environment | BSM outbound domain (preferred) | BSM static outbound IP (fallback) |
| ----------- | ------------------------------- | --------------------------------- |
| Live        | `bsm.egress.biscit.com`         | `20.211.1.65`                     |
| Pilot       | `bsm-pilot.egress.biscit.com`   | `20.5.86.76`                      |

Allow the domain if your firewall can use a domain name as the source of an inbound rule. BISCIT keeps each domain pointing at BSM's current outbound IP, so a rule by domain keeps working if that address ever changes. If your firewall can only match an IP address, allow the IP instead. A rule by IP has to be updated by hand if the address ever changes.

#### BISCIT staff access for onboarding and support <a href="#biscit-staff-access-for-onboarding-and-support" id="biscit-staff-access-for-onboarding-and-support"></a>

The rule above lets BSM in, but not BISCIT staff. During onboarding, a BISCIT consultant needs to sign in to your Epicor to set BSM up. That connection comes from BISCIT, not from BSM, so the rule above alone blocks it.

To let BISCIT staff reach your Epicor URL, also allow BISCIT's VPN address, `13.55.20.15`. It is the same for Live and Pilot. Only BISCIT staff connected to BISCIT's VPN use this address.

Disable this rule once onboarding is finished. If you later need BISCIT to look at your Epicor for a support request, enable it again for that time only.

### Outbound from your users' browsers: allow by domain <a href="#outbound-from-your-users-browsers-allow-by-domain" id="outbound-from-your-users-browsers-allow-by-domain"></a>

Your users' browsers need to reach these domains. The Epicor server itself needs none of them.

| What                                                               | Live                          | Pilot                         |
| ------------------------------------------------------------------ | ----------------------------- | ----------------------------- |
| **BSM portal**: the BSM screens Epicor shows inside its own window | `bsm.biscit.com`              | `bsm-pilot.biscit.com`        |
| **BSM API**: where the BSM portal sends its requests               | `integrations.api.biscit.com` | `integrations.api.biscit.com` |

The BSM portal has no fixed IP address. It is served from shared Microsoft Azure addresses that can change without notice, so allow it by domain even if your firewall usually filters outbound traffic by IP. The BSM API has a fixed address, `52.156.190.206`, if you prefer to allow it by IP.

BSM's own fonts and other files come from the BSM portal itself, so BSM needs no website beyond those listed above.

### What needs no rule <a href="#what-needs-no-rule" id="what-needs-no-rule"></a>

* **Epicor never calls BSM.** BSM's additions inside Epicor make no outbound calls, so the Epicor server needs no outbound rule to BSM.

### Diagram <a href="#diagram" id="diagram"></a>

<figure><img src="https://2874191586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F55w5yhQ5DYMhZTTddKQn%2Fuploads%2F5ICcQWZst72OF5PvDQyb%2FPasted%20image%202026-11-16%2023.15.40.svg?alt=media&amp;token=e0441fc1-fb3a-48a5-88b0-a6e8b1d44c83" alt=""><figcaption></figcaption></figure>

The inbound rule lets BSM's outbound address reach your Epicor URL; the outbound rules let your users' browsers reach the BSM portal and the BSM API. BISCIT staff access for onboarding or support is a separate, temporary rule; see above.


---

# 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.biscit.com/biscit-spend-management/getting-started/bsm-firewall-rules-for-an-epicor-behind-a-vpn.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.
