Classic Service Zone    
Quarterly Failover Resiliance Testing
Scheduled Maintenance Report for SafeNet Trusted Access - Classic Zone
The scheduled maintenance has been completed.
Posted May 23, 2020 - 17:00 UTC
All Services are reporting successfully failed over to the primary site. We are conducting testing and verification, however, no further service interruptions are expected.
Posted May 23, 2020 - 16:59 UTC
Authentication services are now running on the primary site. Additional services are also being failed back at this time.
Posted May 23, 2020 - 16:49 UTC
We are now commencing our failback procedure to the Primary site. There may be a brief period of service degradation of a few minutes but up to a maximum of 15 minutes.
Posted May 23, 2020 - 16:42 UTC
All services have been successfully failed over and has begun on our Secondary site.

We will conducting further testing and observations and will post a message as we begin the fail-back process.
Posted May 23, 2020 - 14:25 UTC
DNS Failover complete. Authentication, Monitoring and Reporting services reporting stable in DR site and serving users without issue.
Posted May 23, 2020 - 14:07 UTC
Beginning failover. We will update when core services are verified in DR site
Posted May 23, 2020 - 14:05 UTC
DNS Failover of core services will begin within the next few minutes.

A brief disruption can be expected as core services failover.

We will provide an update as we begin
Posted May 23, 2020 - 14:04 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted May 23, 2020 - 14:00 UTC
We will be undergoing scheduled maintenance during this time.
Posted May 15, 2020 - 19:05 UTC
The quarterly failover test that was scheduled for 18th April has been postponed to 23rd May to accommodate the operational needs of our healthcare customers during the COVID-19 emergency period.

The failover test will take place between the hours of 14:00 UTC and 17:00 UTC. During this period, brief outages up to an expected maximum of 15 minutes will occur at the beginning and near the end of the window as we conduct the failover and failback.

Complete service availability and performance will resume at the end of the window.
Updates will be provided via our Statuspage: https://status.sta.safenetid.com/

NOTE: For those who use hard-coded IP Addresses for Token Validator:
Our Disaster Recovery Plan is designed to leverage DNS to ensure a smooth and rapid failover of services. As such, during failover exercises (planned or unplanned) could cause service disruption for your users for authentication if you are to continue to use hard-coded IP addresses. It is expected that during the upcoming test, disruption times could be longer than the above-mentioned 15 minutes for those with hard-coded IP addresses.

Further, as public IP addresses can be changed by the Internet Service Provider, this can increase the risk of disruption, as well as create administrative overhead for your team.

We strongly encourage the use of our FQDN: agent1.safenet-inc.com or agent2.safenet-inc.com.

If you have any questions as to how to properly add the DNS entries, we recommend using this guide as a reference:

Please note, that accessing this link does require an active Thales Support Portal account.

If you have any questions or concerns, please reach out to our Client Services team:
• United States: 800-545-6608
• International: +1-410-931-7520
We thank you for your continuous support and cooperation.

Thales Authentication and Access Management Cloud Services
Posted Apr 15, 2020 - 19:33 UTC
This scheduled maintenance affected: RADIUS Service (RADIUS Service (standard), RADIUS over IPsec (custom subscription)) and STA Token Management Console, STA Access Management Console, Management API (BSIDCA), SAML and OIDC Service, Authentication (Token Validator), Push OTP Service, Self-Enrollment, Self-Service and User Portal, Synchronization Service, Risk Engine, VPN UK, VPN Canada, Audit Logging, Policy Engine, Identity Provider, Auto-Provisioning Service.