Environment URLs & IP Addresses

IntroU.S.U.S. GovernmentCanadaAustraliaEurope

Intro

You must provide the URL of a OneSpan Sign server.

If you are exploring the system or performing tests, you can connect to our Sandbox environment. Alternatively, if you have completed your integration with our system and want to launch your product, you can connect to our Production environment.

Sandbox Accounts are not equivalent to Production Accounts. To connect to the OneSpan Sign Production Environment, you must purchase a Production Account.

Your configuration settings depend on the URL into which you log. If you aren't sure which URL to use, in the email you received when you signed up, click Log into your account. In the Login screen that appears, your login URL will appear in your browser's address bar.

To ensure continuous service, you must whitelist certain IP addresses. To see which IP addresses need to be whitelisted, consult the tab for your environment.

Incoming IP Whitelists for OneSpan Sign

Please review this section to ensure your OneSpan Sign service continues to function normally.

In order to further optimize the security posture of OneSpan Sign, note the following:

1. We use a Web Application Firewall (WAF) and additional protection against Denial-of-Service attacks. This protection is provided through Cloudflare and the inbound IP addresses used by OneSpan Sign are CloudFlareIP addresses.

2. We use TLS cipher suites supported by OneSpan Sign. Transport Layer Security (TLS) is a protocol that protects the confidentiality and integrity of data exchanged between OneSpan Sign and customers. For more information, see TLS Support.

What do I need to do?

If you are not whitelisting IPs in your integration, there is no action required on your part.

If you are whitelisting our public IPs, please add the respective FQDN (fully qualified domain name) to your inbound whitelist to continue accessing our services:

If your Security policy does not permit FQDN whitelisting, see Cloudflare's IP ranges. These IPs are subject to change at Cloudflare's discretion.

IP whitelisting for outgoing IP addresses is still required.

Support for IPv6 on the AU Production environment was dropped on October 3, 2021.

Below is the list of Incoming IP addresses (IPv4) applicable to all environments:

• 173.245.48.0/20

• 103.21.244.0/22

• 103.22.200.0/22

• 103.31.4.0/22

• 141.101.64.0/18

• 108.162.192.0/18

• 190.93.240.0/20

• 188.114.96.0/20

• 197.234.240.0/22

• 198.41.128.0/17

• 162.158.0.0/15

• 104.16.0.0/13

• 104.24.0.0/14

• 172.64.0.0/13

• 131.0.72.0/22

Changes to TLS cipher suites

OneSpan Sign uses the following TLS versions and cipher suites:

TLS 1.2 cipher suites

• ECDHE-RSA-AES128-GCM-SHA256

• ECDHE-RSA-AES128-SHA256

• ECDHE-RSA-AES256-GCM-SHA384

• ECDHE-RSA-AES256-SHA384

• AES128-GCM-SHA256

• AES128-SHA256

• AES256-GCM-SHA384

• AES256-SHA256

TLS 1.3 cipher suites

• TLS13-CHACHA20-POLY1305-SHA256

• TLS13- AES-256-GCM-SHA384

• TLS13- AES-128-GCM-SHA256

What do I need to do?

We recommend that you work with your IT team immediately to upgrade your integration framework to the latest security library supporting the above-mentioned TLS versions and cipher suites. Once completed, please test your OneSpan Sign Sandbox environment to ensure that all TLS communications are working properly. This is an important step that ensures that your organization does not encounter service disruptions:

URL Update for OneSpan Sign Sign API Calls

What do I need to do?

If you have not integrated OneSpan Sign via our API/SDKs and are not using mutual TLS protocols in your integration, there is no action required on your part.

If you HAVE integrated OneSpan Sign via our API/SDKs and are using mutual TLS protocols, in addition to the requirement of switching the IP addresses used by OneSpan Sign to IP addresses of Cloudflare as described above, please change your integration from using port 8443 to using a path.

For example:

We recommend that you work with your IT team immediately to upgrade your integration framework to the latest security library supporting the above-mentioned TLS versions and cipher suites. Once completed, please test your OneSpan Sign Sandbox environment to ensure that all TLS communications are working properly. This is an important step that ensures that your organization does not encounter service disruptions.

Your configuration settings depend on the URL into which you log. If you aren't sure which URL to use, in the email you received when you signed up, click Log into your account. In the Login screen that appears, your login URL will appear in your browser's address bar.

To ensure continuous service, you must whitelist certain IP addresses. To see which IP addresses need to be whitelisted, consult the tab for your environment:

• U.S.

• U.S. Government

• Canada

• Australia

• Europe

U.S.

The list of outgoing IP addresses has changed. If you are whitelisting IPs, you must whitelist these new IP addresses by the following dates:

• For Sandbox environments: July 27, 2024

• For US1 Production environments: Sunday, November 10, 2024 at 12:00 am (ET)

• For US2 Production environments: Saturday, November 16, 2024 at 23:00 pm (ET)

Refer to the following tables to see which IP addresses have been added.

Before continuing, verify the domain that you are using for your OneSpan Sign instance. The following domains are available:

• US 2 (esignlive.com)

• US 1 (e-signlive.com)

US 2 (esignlive.com)

US instances that use US 2 (esignlive.com) as their domain must whitelist the following IP addresses:

US 1 (e-signlive.com)

US instances that use US 1 (e-signlive.com) must whitelist the following IP addresses:

U.S. Government

US Government instances must whitelist the following IP addresses:

Updated IP Addresses

Our FedRAMP Sandbox and Production servers have been migrated to new Operating Systems. Because of this migration the Outgoing IP Addresses for these servers changed. You will need to update your list of whitelisted IP addresses to use the new IP addresses listed above. You can add these IP addresses to your whitelist at any time.

There is no change to the list of Incoming IP Addresses.

These updates were performed on the following dates:

While you can keep the old IP addresses in your whitelisted IP addresses, we do recommend that you remove the old outgoing IP addresses.

Canada

The list of outgoing IP addresses has changed. If you are whitelisting IPs, you must whitelist these new IP addresses by the following dates:

• For Sandbox environments: July 27, 2024

• For Production environments: Sunday, November 17, 2024 at 12:00 am (ET)

Refer to the following table to see which IP addresses have been added.

Canadian instances on esignlive.ca must whitelist the following IP addresses:

Australia

The list of outgoing IP addresses has changed. If you are whitelisting IPs, you must whitelist these new IP addresses by the following dates:

• For Sandbox environments: July 27, 2024

• For Production environments: Sunday, November 3, 2024 at 1:00 am (AEST)

Refer to the following table to see which IP addresses have been added.

Australian instances on esignlive.com.au must whitelist the following IP address:

Europe

European instances on esignlive.eu must whitelist the following IP address:

The list of outgoing IP addresses has changed. If you are whitelisting IPs, you must whitelist these new IP addresses by the following dates:

• For Sandbox environments: July 27, 2024

• For Production environments: Saturday, November 9, 2024 at 22:00 pm (CET)

Refer to the following table to see which IP addresses have been added.