:
Good afternoon, everyone.
[Translation]
I call the meeting to order.
Welcome to meeting number 53 of the House of Commons Standing Committee on Access to Information, Privacy and Ethics.
[English]
Today's meeting is taking place in a hybrid format, pursuant to the House order of June 23, 2022. Therefore, members can attend in person in the room and remotely using the Zoom application. Should any technical challenges arise, please advise me. Please note we may need to suspend for a few minutes, in order to ensure all members can fully participate.
Pursuant to Standing Order 108(3)(h) and the motion adopted by this committee on Monday, November 14, 2022, we are resuming our study of privacy concerns in relation to the ArriveCAN application.
I would now like to welcome our witness for today. From Amazon Web Services, Inc., we have Nicole Foster, director of global artificial intelligence and machine learning, and Canada public policy.
Ms. Foster, I want to welcome you to the committee today.
[Translation]
We have just one witness, Mr. Villemure, so a sound check wasn't done.
[English]
Ms. Foster has asked the committee for seven minutes to address us at the start, and I have granted this.
Ms. Foster, the floor is yours. Please go ahead.
:
Thank you so much, Mr. Chair and members of the committee.
I'm delighted to be here with you to speak about data privacy and security today, and how these apply to applications that run on Amazon Web Services, or AWS.
[Translation]
My name is Nicole Foster, and I am the director of public policy at AWS.
[English]
I'm responsible for our global AI and ML policy strategy, and our Canada public policy strategy.
As you may know, AWS is a subsidiary of Amazon that provides on-demand cloud computing services for individuals, companies and governments on a metred, pay-as-you-go basis. The “cloud” refers to the on-demand delivery of IT resources over the Internet, such as servers, and the software applications and databases that run on them. Despite their name, cloud services are physically located on the ground in data centres all over the world, including here in Canada. Organizations that use them do not need to own, run or maintain their own physical servers or software applications. Instead, they can use the cloud to run applications on demand, paying only for what they need.
AWS is the world's most comprehensive and broadly adopted cloud service provider. Millions of customers, including the fastest-growing start-ups, the largest enterprises and leading government agencies, are using AWS to lower costs, become more agile and innovate faster. This is all done with state-of-the-art security controls.
AWS is architected to offer the most secure cloud-computing services available today. We support more security standards and compliance certifications than any other cloud provider, thereby helping satisfy security and compliance requirements for virtually every regulatory agency around the globe. We are proud of our record in maintaining the privacy and security of Canadians. Our cybersecurity assessment reports are available to any customer. They include our detailed assessment from the Canadian Centre for Cyber Security.
As you know, in early 2020, AWS was contracted by the Government of Canada, through established Shared Services Canada procurement channels, to work with the Canada Border Services Agency and the Public Health Agency of Canada. The objective was to help launch aspects of the pandemic response program.
In the case of ArriveCAN, specifically, AWS's role was to securely host the application on the AWS cloud. In addition to that, we worked with CBSA and PHAC, providing expert advisory services related to ArriveCAN security and infrastructure architecture. This included implementing the Government of Canada's standards on cybersecurity; integrating ArriveCAN with the rest of the CBSA and PHAC ecosystems; enabling architectures and security that have supported major new functionality throughout the two and a half years since it was launched; providing tools to enable CBSA to monitor the integrity of the data and support its operations; and ensuring that AWS services were configured to minimize the overall cost of AWS to Canada, while supporting the ability to ensure high availability of the program to Canadians and international travellers.
Mr. Chair, I'd like to further elaborate on the security and privacy measures we have in place at AWS. Security and protecting Canadian citizens' data are at the top of our priorities.
Our customers benefit from data centre and network architecture that is built to meet the requirements of the most security-sensitive organizations. AWS customers in Canada can place workloads, applications and their data in an AWS infrastructure region located here, in-country.
Specifically, our Montreal region—we refer to a collection of data centres as a region—enables customers to address data compliance and residency requirements. Our extensive security technologies, 24-7 monitoring and alerting, and rigorous attention to all aspects of securing AWS infrastructure are designed to ensure that customers' data can be used by only them.
The services we provided for ArriveCAN were architected in alignment with the security standards set by Shared Services Canada and the Centre for Cyber Security. Our physical data centres and on-site personnel have been inspected and assessed for compliance by Public Services and Procurement Canada's industrial security directorate. As well, AWS personnel who worked and/or continue to work on ArriveCAN are all Canadian citizens. All have their reliability status, which is governed by the Treasury Board standard on security screening.
Mr. Chair, AWS is vigilant about its customers' privacy and sensitive information. To be clear with you and all members of this committee, AWS personnel did not at any point in time have access to any personal data from Canadians while working on ArriveCAN.
In conclusion, AWS is proud to have supported our customers during the height of the COVID-19 pandemic, but we understand that when the public interest is at stake, additional questions may be asked. Within the confines of our agreements, I will endeavour to answer these questions to the best of my ability today. Our focus remains on providing scalable technology services, with security as our highest priority.
[Translation]
Thank you for this opportunity.
[English]
I would be pleased to take any questions.
For the sake of the committee, just as a reminder, I left a half-hour for committee business, for which we'll be moving in camera at approximately six o'clock.
Ms. Foster, I don't know if you've been in front of committee before. We have four rounds of questions, and each party gets six minutes.
We'll start with Mr. Barrett.
Mr. Barrett, you have six minutes.
:
There are a couple of different ways of looking at or considering that. One is looking at the broader cloud environment, in which we secure the cloud itself. There's also the physical security of our data centres. We manage the physical security of those sites and ensure that they're not at risk of natural disasters, that they have access to reliable energy, that they are not on a flood plain, and things like that.
There's the physical security of the data centre. There's the virtual security of the cloud. These are creating a more secure environment.
In terms of security tools, there are quite a lot of different security tools. A couple of examples of those would be...for example, we have some artificial intelligence tools that are able to monitor for what might be unusual access to a customer's data or a customer's environment. We have systems that would alert us, and then we can alert a customer. Sometimes it turns out to be nothing and sometimes it turns out to be something, but we have the ability to use artificial intelligence to monitor and alert to those things.
We also provide encryption tools. That's probably one of the most important security tools we offer. Customers always have the choice to encrypt their data. Once it's encrypted, they also hold the encryption keys to their data.
:
That's a good question.
There are so many unique use cases for cloud services, and none of them are quite the same. I would say that the uniqueness of this would include a couple of features. One was the high security bar that was required for this project. The other is the speed with which it needed to be executed, with that high bar of security. Being able to incorporate a number of different functionalities so quickly made it unique.
The other thing that was going on at the time was...of course, we all remember that public health guidance and policies on what you needed in order to travel were changing pretty frequently. The ability to operationalize those changes into the technology, also at speed, also made this project somewhat unique.
:
Again, it's really supporting the underlying infrastructure that supports the app.
If we think about other apps that we may be more familiar with, like Uber, you put in your address, and like magic, a car appears at your door and takes you to your destination. You don't even have to speak to the driver. All of that simplicity is supported by a whole lot of other back-end technology that makes that happen, from GPS to fastest route, to how you're paying for the service. You can split your bill. All that underlying infrastructure that supports the simplicity of the user interface has to be built.
In the case of ArriveCAN, it was using a lot of other aspects of infrastructure that are less obvious in terms of what you're seeing in the app. For example, if you upload your vaccination certificate, the app has to be able to read and verify that certificate. It has to be able to do it in multiple languages. You might remember that Ontario, for example, changed its vaccination documentation halfway through all of this. It has to be able to read the document and verify that it's a real document.
Another piece of infrastructure that has to be supported by the app was some of the accessibility features, like the ability to go from text to talk. That is another machine learning application that was enabled in the app.
It also had to be able to speak to other aspects of CBSA's infrastructure or PHAC's infrastructure in terms of data that it was verifying in real time once you uploaded your information in the app, as well as boarding information and your travel information. There were a number of pieces that needed to speak to each other in the simplicity of being able to interface with the app.
In a normal course of work, in terms of engaging the cloud, you'll often see a heavier amount of the need for those advisory services at the beginning of a mandate, just to get things up and running as you build.
In terms of the cloud utility, the app is still functional today. It's still running on AWS infrastructure, and it continues to run on AWS infrastructure, but the billing for that is based on its actual usage. It's based on the volume of users using the app and the activity of those services.
:
I apologize. I'm not quite sure I'm getting the gist of your question in interpretation.
The majority of the billing at the front end of the contract, under the framework agreement, would be related to advisory services. The advantage of using cloud is that you can scale up or scale down, depending on the level of your use.
In the case of anything that has peaks and valleys in demand, you're paying only for what you use. You're able to scale up to a level that's quite high without having to procure servers on your own.
Before the cloud, basically what we had was, if you were the government—
I know I've said this so many times, and I just hate to be a broken record. It's kind of sucky to be taken by surprise in all of this.
I would ask your indulgence, perhaps, for me to take a read and look into the motion. I will ask, Chair, for your indulgence in suspending for about five to 10 minutes for us to be able to look at, review and see what exactly the motion is asking for at this point.
Again, Chair, it would not happen if we were not taken by surprise all the time in this committee.
:
We're going to resume the meeting.
We have a motion that was put on the floor by Mr. Kurek. Everyone has the motion. I'm looking at it. If this information, or some of it, cannot be provided to the committee, then I'm sure Amazon can provide so rationale or reason, if need be.
Is there any discussion on this motion?
Go ahead, Mr. Green. I see your hand.
:
That is a non-debatable motion.
Madam Clerk, do you want to take a vote on that? The motion is to adjourn the meeting.
(Motion agreed to: yeas 7; nays 3)
The Chair: Before we adjourn this meeting, I want to thank, on behalf of the committee, the clerk, analysts and technicians for the work they have done.
Some hon. members: Hear, hear!
The Chair: Ms. Foster, on behalf of the committee and Canadians, I want to thank you for making an appearance before the committee today.
I wish everyone a very merry Christmas. Happy holidays and happy Hanukkah.
The meeting is adjourned.