Thank you, André.
It's clear that the Government of Canada has recognized the need for a balanced approach. This is reflected in the Government of Canada digital standards, which call for a balanced approach to managing risk and implementing appropriate privacy and security measures. Similarly, the Government of Canada's cloud adoption strategy requires departments and agencies to adopt a structured risk management approach that takes into account the integration of cloud services in their government IT services.
The Government of Canada has adopted a cloud-first strategy. It did that last year. Notably, it was the last of the countries that make up the Five Eyes to do so. The rationale for a cloud-first strategy has been clearly articulated in the government's own white paper on data sovereignty and the public cloud.
The paper indicates that cloud computing represents a significant opportunity to address a number of inherent risks that the government is currently facing. These include: aging IT infrastructure, through which the government's mission critical IT infrastructure is aging and at risk of breaking down; cyber hygiene gaps, whereby the government's inability to quickly identify assets and perform timely patching and remediation of known vulnerabilities leaves it exposed to cyber-threats; the availability of non-cloud solutions—increasingly, industry is providing only public cloud solutions or focusing their development efforts on cloud services, and the on-premises software we've been accustomed to in the past is no longer available in the same way—and of course the government's plan to digitally transform the delivery of government services.
Cyber hygiene in particular is something I want to draw attention to, as there is an increasing recognition that cloud providers often implement and manage better IT security controls than internal IT teams. Cloud providers are investing billions of dollars to address security of data, going well beyond what any customer can do on its own. By enabling state-of-the-art machine learning and AI solutions, cloud providers are protecting customers at machine speed from the latest known and even unknown threats.
Despite the many benefits of cloud services and a cloud-first procurement strategy, it's clear that the Government of Canada is lagging behind other governments in terms of cloud adoption. It's important to recognize that cloud is different, and doing government digitally is different. To be effective, federal digital services need to be redesigned. This requires in many cases a redesigning of existing policies and processes.
New technologies will need to be explored, including artificial intelligence and the Internet of things, to power digital services. These new technologies are available through the cloud. Generally, they aren't available without accessing the cloud.
The other thing to note is that there are international best practices from which important insights can be drawn. By way of example, the United Kingdom's G-Cloud is considered a model for digital government and cloud adoption. Cumulative sales under the G-Cloud framework up to July of last year were over £3.5 billion, with 46% of total sales by value and 69% by volume having been awarded to small and medium-sized enterprises.
The success of the U.K. approach followed deliberate policy changes that supported implementation of the U.K. government's cloud-first policy. These changes included a simplified data classification regime, non-prescriptive security requirements, accountability for decisions to procure bespoke solutions, and a willingness to accept a supplier's contract with a wrapper of government terms.
While each of these changes is important, the first two warrant additional discussion in the context of the committee's deliberations.
The U.K. streamlined its data classifications so that information assets are classified into only three types: official, secret and top secret. Each data type attracts a baseline set of security controls providing appropriate protection against typical threats.
Significantly, U.K. government guidance indicates:
ALL routine public sector business operations and services should be treated as OFFICIAL.... This includes: Personal information that is required to be protected under Data Protection legislation or other legislation (e.g. health records)
It's noteworthy that virtually all routine information within the government is treated as official, which is the lowest standard. That includes even sensitive personal information such as health records.
Information classified as official in the United Kingdom constitutes 90% of all U.K. government data. This data is deemed to be suitable for processing in the public cloud and is not subject to geographic limitations on processing. Rather, a risk-managed approach has been adopted, with U.K. government departments and agencies being required to evaluate a cloud service against 14 cloud security principles. These principles serve as a checklist for effective security safeguards without prescribing how a cloud provider needs to demonstrate compliance.
When contrasting the U.K. approach with Canada's, it's clear that the Government of Canada's framework for protecting security and privacy is underpinned by a materially different data classification system and security framework. Canada has nine different data classifications, with personal information—which is typically treated in the U.K. at the lowest level— generally being classified as Protected B.
Once data is classified as protected or higher, specific security and privacy protections set out in Government of Canada policies and directives apply.
For example, data that is classified as Protected B is subject to stringent requirements governing data residency, security clearances and departmental security controls. These requirements are often incompatible with the supply of public cloud solutions.
A cloud service is, by definition, a non-customized shared service that relies upon economies of scale achieved through standardization. To the extent that a government procurement mandates that a service provider satisfy security or privacy requirements that have not already been operationalized, the procurement is on its face incompatible with the supply of a cloud-delivered solution. Because data classifications in Canada are matched with security requirements that are incompatible with cloud services, it is not surprising that cloud adoption within the Government of Canada is lagging behind adoption in the United Kingdom.
The U.K. experience does not display a reckless approach—