Updated September 23, 2020
Understanding how SecureAuth cloud IP addresses are used
This document provides information on how SecureAuth cloud uses IP addresses to provide services to SecureAuth® Identity Platform (formerly SecureAuth IdP), end user browsers, and mobile devices registered to provide multi-factor authentication methods. Reference this information when configuring the Identity Platform, servers, and devices to communicate with SecureAuth cloud.
Allowed URLs and IP addresses
For the URLs listed in the Geo load balanced URL column, the DNS resolution for the URL returns one of the listed IP addresses, depending on the geographic location of the DNS resolver (client). All IP addresses for the URL must be allowed in the firewall rules to support cloud services site failover. These are used by the Identity Platform, browsers, applications, servers, and devices.
|Geo load balanced URL||IP address||SecureAuth cloud services configuration|
The following URL configurations apply to versions of the SecureAuth IdP versions 9.3 and earlier.
Alternatively, you can view the IP addresses listed in the Amazon EC2 service table. Take note that it lists all AWS IP addresses, and you only want to allow the IPs within "EC2", "us-east-1", and "us-west-2" categories: https://ip-ranges.amazonaws.com/ip-ranges.json
The following URL configurations apply to all versions of the Identity Platform version 19.07 and later.
Alternatively, to view the page of listed IP addresses, see http://d7uri8nf7uskq.cloudfront.net/tools/list-cloudfront-ips
New Experience Web Admin user interface assets and storage configuration.
|Other URL||IP address||Use in Identity Platform|
|fonts.gstatic.com||N/A||New Experience Web Admin user interface assets.|
|fonts.googleapis.com||N/A||New Experience Web Admin user interface assets.|
|N/A||New Experience Web Admin user interface assets.|
|N/A||New Experience Web Admin user interface assets.|
Important information about MSG level encryption
The msg level encryption endpoints are deprecated (no longer appending /msg after .svc in the URL). Going forward, use https in the URL configuration.
Test the Identity Platform endpoint availability
To verify that these endpoints are available from the Identity Platform appliance, browse (from the appliance) to the following URLs:
URLs in this list are slated for activation in the near future and should be allowed per your network requirements:
Update the Identity Platform appliances to use the latest Cloud Services information
|SecureAuth IdP / Identity Platform version||Required action (to be most up-to-date)|
|9.0.0+ / 19.07+ (originally purchased images)||None required|
|9.0.0+ / 19.07+ (upgraded from earlier version)||Run ACRU Lite to update machines to latest Cloud Services information|
|8.1.0 - 8.2.0||Run ACRU Lite to update machines to the latest Cloud Services information|
|7.x - 8.0.3|
SecureAuth cloud overview
Hosted services for SecureAuth are located in two physical data centers, SecureAuth US-East and SecureAuth US-West; and are redundant at the site and service levels operating in SSAE16 Type II certified hosting facilities, providing a secure, highly available (redundant) infrastructure, which includes cooling, power, network, and internet connectivity.
Also implemented is an industry leading, cloud-based, redundant geo-location load balancing solution to ensure that the Identity Platform appliance and SecureAuth cloud access communications are routed to the most efficient facility and, in the event of a site level outage, all communications are seamlessly transferred to the SecureAuth hosted services backup facility.
Each SecureAuth hosted services facility includes load balanced web services hosting APIs providing SMS, TTS, Push, Push-to-Accept OTP services, Threat Intelligence Services, and X.509 certificate signing services; redundant HSM (hardware security module) protected certificate authorities; and clustered (fail-over) database services supported by redundant, back-end services (i.e. LDAP Directory, DNS, Firewall, IDS/IDP, content inspection, etc.).
Secure communications from the Identity Platform appliance, SecureAuth cloud access to SecureAuth cloud are enabled via TLS / transport-level encryption over TCP Port 443 for HTTPS.
Transport Layer Security
Transport Layer Security (TLS), a cryptographic protocol, is designed to provide communications security over a network. Using X.509 certificates, asymmetric cryptography is employed to verify the relationship between a certificate and its owner, and to negotiate a symmetric session key.
The most common implementation of this protocol can be found in the use of Secure Sockets Layer (SSL) to encrypt and sign contents of packets sent over Secure HTTP (HTTPS).
SecureAuth cloud services
The Identity Platform appliances and cloud access portals communicate with SecureAuth cloud for the following services:
|X.509 Certificate Services (SHA 1 and SHA 2)|
Issue user certificates
Deliver one-time passcodes (OTPs) via SMS / text message to user's mobile phone number.
|Telephony Service (text-to-speech)|
Deliver OTPs via voice call to user's phone number.
|SecureAuth Threat Service|
Retrieve IP address reputation / threat score to use in Adaptive Authentication analysis.
Deliver OTPs via Push Notification to user's mobile device and / or deliver mobile login requests (Approve / Deny) via SecureAuth Authenticate App to user's mobile device.
Deliver SMS text messages to user's mobile device. The link in emails and SMS text messages point to SecureAuth cloud.
Retrieve IP address geo-location (known as Dynamic Perimeter) information to use in Adaptive Authentication analysis.
|App Enrollment Service|
Generate QR code to use in Multi-Factor App Enrollment (SecureAuth Authenticate App).
|Phone Number Fraud Prevention Service|
Retrieve user's phone number profile to use in phone number blocking.
SecureAuth Authenticate App v5.3
URLs supported for push notifications and device enrollment QR codes
A complete callback URL is included in the API payload for device enrollment QR codes and Push-to-Accept Notifications. When responding to either a QR code device enrollment request or Push-to-Accept request, the SecureAuth Authenticate App returns the URL with a DNS prefix such as "us1-". For example: