Keeping your instance secure

Five things every BPMN Central customer should know. They take ten minutes, and they matter most on the day someone leaves your company.

1. The account owns the instance

Whoever can log in to the BPMN Central account that created a subscription owns that instance. Register with a shared company mailbox, never a personal one: logins are confirmed with a code emailed to that address, so a departed employee cannot get in. If the account was created with a personal address, ownership transfer is a support request from that account.

2. Two IP addresses, by name

  • Manager IP 116.203.76.251: allow it on your database firewall only for the Test and Provision steps, then remove it. It can only ever check that a connection works and whether the database is empty.
  • Instance IP 4.223.212.34: your instance connects to your database from this address. Keep it allowed for as long as your subscription runs, and remove it when the subscription ends.

The instance IP is shared by every BPMN Central instance. It identifies BPMN Central, not you.

3. A new instance needs empty targets

When you provision, we check that your database contains no BPMN Central data and that your storage container is empty, on the exact credentials you entered, and we refuse anything else. Every database connection verifies your server's TLS certificate against its hostname, so an address that does not really belong to your server can never be reached. Returning with existing data after a cancellation is a support request from the owning account.

4. API keys, not IP allowlists

HTTP connectors let your workflows call your own APIs and third-party services from your instance. Because the outbound IP is shared, a firewall rule that trusts "the BPMN Central IP" trusts every customer. Protect anything you expose with an API key or token: the key is the lock, the IP never was.

5. When someone leaves

The checklist, in order:

  1. Rotate the database password and the storage account key on your dashboard (Change DB / storage). The instance restarts with the new values; your admin login does not change.
  2. Rotate the API keys and tokens of every service your connectors call, and of every client of your REST API.
  3. Review the firewall allowlists on your database and your internal APIs.
  4. Change the password of the BPMN Central account if the person knew it, and make sure the account uses a company mailbox.

Support requests

Moving an instance to a different database or storage account, re-subscribing onto existing data, and transferring account ownership are handled by support, and only for the account that owns the subscription. Use the contact page from that account.

Contact us