SecurID Service Incident ANZ Region

Update timeline

1. monitoring Mar 22, 2022, 10:46 PM UTC

   SecurID Operations has identified an issue related to the maintenance that was recently performed. (https://status.securid.com/incidents/y5200lzyhmn7) The issue affecting SecurID has been rolled back. The SaaS Operations team is monitoring the fix. We will post a root cause analysis as soon as it is available.

2. resolved Mar 22, 2022, 11:20 PM UTC

   After monitoring the fix, SaaS Operations has determined that the incident affecting SecurID has been resolved. We will post a root cause analysis as soon as it is available.

3. postmortem Mar 24, 2022, 05:20 PM UTC

   An incident that occurred on March 22nd 2022 caused degraded authentication services for a subset of customers hosted from the ANZ region from 04:10 PM UTC – 10:49 PM UTC. This was caused by a product defect introduced as part of the March release that impacted those customers who have authentication workflows where the authentications originate directly from the SecurID Cloud and some SecurID integrations \(eg. MyPage, CAS Admin MFA, Radius\). Those customers who did not perform a publish between the February and March releases would have been impacted by this incident. Once the issue was identified, all customers were rolled back to our February release which resolved the incident. **Mitigations** SecurID is continuously taking steps to improve the SecurID Access service and processes to help ensure such incidents do not occur in the future. This includes, but is not limited to: * Additional monitoring practices are being implemented by our SaaS Operation team to monitor and better identify conditions that result from performing releases. * The underlying defect has gone through a full analysis by our engineering teams. * Securid engineering has developed a fix and expanded backwards compatibility testing to prevent future regressions. We apologize for any inconvenience. Thank you, The SecurID Team