There were six phases of software testing, and one of the phases was focused just on the CBSA cyber-team. Deloitte would put up the product without telling them what they were doing or exposing what the techniques were, and they hacked the product over a series of weeks to try to see if they could break it. We had reviews of that approach to make sure it met cyber-requirements, and we signed off on its ability to meet a standard for cybersecurity.
One of the six cycles of testing was focused specifically on cybersecurity. If it goes down, there is a process for bringing it back up. This team has 170 folks on team Deloitte who are ready, particularly around launch, to look at its support to say, “If it goes down, here's how we'll get it back into the field.” That support model consists of going past May.
Regarding the tolerance we're showing during the transition from the legacy system to CARM, we're showing the community the process for an outage period: how we would suspend certain functions and allow the business process to continue to flow.