Difference between revisions of "GC Enterprise Architecture/Framework"
Jump to navigation
Jump to search
m |
m |
||
| (197 intermediate revisions by 12 users not shown) | |||
| Line 1: | Line 1: | ||
| − | < | + | {{OCIO GCEA Header}} |
| − | + | <multilang> | |
| + | @en| | ||
| − | + | Version: 1.35 | |
| − | |||
| − | |||
| − | |||
| − | + | February 24, 2021 | |
| − | + | Office of the Chief Information Officer of Canada, Treasury Board of Canada Secretariat, Government of Canada | |
| − | + | == Enterprise Architecture Framework == | |
| + | The Enterprise Architecture Framework is the criteria used by the Government of Canada enterprise architecture review board and departmental architecture review boards when reviewing digital initiatives to ensure their alignment with enterprise architectures across business, information, application, technology and security domains to support strategic outcomes. The EA Framework came into effect on December 1, 2020 and is a replacement of Appendix A, Mandatory Procedures for Enterprise Architecture Assessment from the Directive on Service and Digital. | ||
| − | + | The Enterprise Architecture Framework provide details on the requirements set out in the following sections of the Policy and Directive on Service and Digital. | |
| − | + | 4.1.2.3 of the Policy on Service and Digital. The Chief Information Officer (CIO) of Canada is responsible for: Prescribing expectations with regard to enterprise architecture. | |
| − | + | 4.1.2.4 of the Policy on Service and Digital. The Chief Information Officer (CIO) of Canada is responsible for: Establishing and chairing an enterprise architecture review board that is mandated to define current and target architecture standards for the Government of Canada and review departmental proposals for alignment. | |
| − | + | 4.1.1.1 of the Directive on Service and Digital. The departmental Chief Information Officer (CIO) is responsible for: Chairing a departmental architecture review board that is mandated to review and approve the architecture of all departmental digital initiatives and ensure their alignment with enterprise architectures. | |
| − | + | The [https://www.canada.ca/en/government/system/digital-government/policies-standards/government-canada-enterprise-architecture-framework.html Enterprise Architecture Framework] is also published on Canada.ca. | |
| − | |||
| − | + | == Business architecture == | |
| + | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/BusinessGuide click here for Business Architecture guide] </i></b></br></br> | ||
| + | Business architecture is a critical aspect for the successful implementation of the GC Enterprise Ecosystem Target Architecture. The architectural strategy advocates whole‑of‑government approach where IT is aligned to business services and solutions are based on re‑useable components implementing business capabilities in order to deliver a cohesive user experience. As such, it is essential that business services, stakeholder needs, opportunities to improve cohesion and opportunities for reuse across government be clearly understood. In the past these elements have not been a priority. It is expected that the IT culture and practices will have to change to make business architecture, in general, and these elements a primary focus. | ||
| − | + | === Design services digitally from end‑to‑end to meet the Government of Canada users and other stakeholders’ needs === | |
| + | * clearly identify internal and external users and other stakeholders and their needs for each policy, program and business service | ||
| + | * include policy requirement applying to specific users and other stakeholder groups, such as accessibility, gender-based plus analysis, and official languages in the creation of the service | ||
| + | * perform Algorithmic Impact Assessment (AIA) to support risk mitigation activities when deploying an automated decision system as per ''[https://www.canada.ca/en/government/system/digital-government/digital-government-innovations/responsible-use-ai.html Directive on Automated Decision-Making]'' | ||
| + | * Model end-to-end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels | ||
| − | + | === Architect to be outcome‑driven and strategically aligned to the department and to the Government of Canada === | |
| + | * identify which departmental/GC business services, outcomes and strategies will be addressed | ||
| + | * establish metrics for identified business outcomes throughout the life cycle of an investment | ||
| + | * translate business outcomes and strategy into business capability implications in the [[GC Enterprise Architecture/Business Capability Model| <b>GC Business Capability Model</b>]] to establish a common vocabulary between business, development, and operation | ||
| − | + | === Promote horizontal enablement of the enterprise === | |
| − | + | * identify opportunities to enable business services horizontally across the GC enterprise and to provide cohesive experience to users and other stakeholders | |
| − | + | * reuse common business capabilities, processes and enterprise solutions from across government and private sector | |
| + | * publish in the open all reusable common business capabilities, processes and enterprise solutions for others to develop and leverage cohesive horizontal enterprise services | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | == Information architecture == | ||
| + | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/DataGuide click here for Information/Data Architecture guide] </i></b></br></br> | ||
| − | + | Information architecture is defined as the management and organization of data for a business. The best practices and principles aim to support the needs of a business service and business capability orientation. To facilitate effective sharing of data and information across government, information architectures should be designed to reflect a consistent approach to both structured and unstructured data, such as the adoption of federal and international standards. Information architecture should also reflect responsible data management, information management and governance practices, including the source, quality, interoperability, and associated legal and policy obligations related to the data assets. Information architectures should also distinguish between personal and non‑personal data. How personal information is treated such as its collection, use, sharing (disclosure), and management must respect the requirements of the ''[https://laws-lois.justice.gc.ca/eng/ACTS/P-21/index.html Privacy Act]'' and its related policies. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | === Collect data to address the needs of the users and other stakeholders === | ||
| + | * assess data requirements‑based program objectives, as well users, business and stakeholder needs | ||
| + | * collect only the minimum set of data needed to support a policy, program, or service | ||
| + | * reuse existing data assets where permissible and only acquire new data if required | ||
| + | * ensure data collected, including from third-party sources, are of high quality | ||
| − | + | === Manage and reuse data strategically and responsibly === | |
| − | * | + | * define and establish clear roles, responsibilities, and accountabilities for data management |
| − | * | + | * identify and document the lineage of data assets |
| − | * | + | * define retention and disposition schedules in accordance with business value as well as applicable privacy and security policy and legislation |
| + | * ensure data are managed to enable interoperability, reuse and sharing to the greatest extent possible within and across departments in government to avoid duplication and maximize utility, while respecting security and privacy requirements | ||
| + | * contribute to and align with enterprise and international data taxonomy and classification structures to manage, store, search and retrieve data | ||
| + | === Use and share data openly in an ethical and secure manner === | ||
| + | * share data openly by default as per the ''Directive on Open Government and Digital Standards'', while respecting security and privacy requirements; data shared should adhere to existing enterprise and international standards, including on data quality and ethics | ||
| + | * ensure data formatting aligns to existing enterprise and international standards on interoperability; where none exist, develop data standards in the open with key subject matter experts | ||
| + | * ensure that combined data does not risk identification or re‑identification of sensitive or personal information | ||
| − | + | === Design with privacy in mind for the collection, use and management of personal Information === | |
| − | * | + | * ensure alignment with guidance from appropriate institutional ATIP Office with respect to interpretation and application of the ''Privacy Act'' and related policy instruments |
| − | * | + | * assess initiatives to determine if personal information will be collected, used, disclosed, retained, shared, and disposed |
| − | * | + | * only collect personal information if it directly relates to the operation of the programs or activities |
| − | * | + | * notify individuals of the purpose for collection at the point of collection by including a privacy notice |
| − | * | + | * personal information should be, wherever possible, collected directly from individuals but can be from other sources where permitted by the ''Privacy Act'' |
| − | + | * personal information must be available to facilitate Canadians’ right of access to and correction of government records | |
| + | * design access controls into all processes and across all architectural layers from the earliest stages of design to limit the use and disclosure of personal information | ||
| + | * design processes so personal information remains accurate, up‑to‑date and as complete as possible, and can be corrected if required | ||
| + | * de‑identification techniques should be considered prior to sharing personal information | ||
| + | * in collaboration with appropriate institutional ATIP Office, determine if a Privacy Impact Assessment (PIA) is required to identify and mitigate privacy risks for new or substantially modified programs that impact the privacy of individuals | ||
| + | * establish procedures to identify and address privacy breaches so they can be reported quickly and responded to efficiently to appropriate institutional ATIP Office | ||
| − | + | == Application architecture == | |
| + | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/ApplicationGuide click here for Application Architecture guide] </i></b></br></br> | ||
| − | + | Application architecture is defined as the management of software used by a business to solve problems. Application architecture practices must evolve significantly for the successful implementation of the GC Enterprise Ecosystem Target Architecture. Transitioning from legacy systems based on monolithic architectures to architectures that are oriented towards business services and re‑useable components implementing business capabilities, is a major shift. Interoperability becomes a key element, and the number of stakeholders that must be considered increases. | |
| − | |||
| − | |||
| − | + | === Use open source solutions hosted in public cloud === | |
| − | + | * select existing solutions that can be reused over custom built | |
| − | * | + | * contribute all improvements back to the communities |
| − | * | + | * register open source software to the Open Resource Exchange |
| − | * | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | === Use software as a service (SaaS) hosted in public cloud === | |
| − | * | + | * choose SaaS that best fit for purpose based on alignment with SaaS capabilities |
| − | * | + | * choose a SaaS solution that is extendable |
| − | + | * configure SaaS and if customization is necessary extend as open source modules | |
| − | * | ||
| − | |||
| − | |||
| − | |||
| − | + | === Design for Interoperability === | |
| − | * | + | * design systems as highly modular and loosely coupled services |
| − | + | * expose services, including existing ones, through APIs | |
| − | * | + | * make the APIs discoverable to the appropriate stakeholders |
| − | * | ||
| − | + | === ''Enable Interoperability, Proposed amendment March 23, 2021'' === | |
| − | * | + | * ''expose data and functionality through service interfaces'' |
| − | * | + | * ''applications must communicate with each other via those interfaces'' |
| − | * | + | * ''services interfaces must be published and discoverable'' |
| − | |||
| − | <b> | + | == Technology architecture == |
| − | + | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/TechnologyGuide click here for Technology Architecture guide] </i></b></br></br> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Technology architecture is defined as the management and organization of technical equipment and devices of a business. Technology architecture is an important enabler of highly available and adaptable solutions that must be aligned with the chosen application architecture. Cloud adoption provides many potential advantages by mitigating the logistical constraints that often negatively impacted legacy solutions hosted “on premises.” However, the application architecture must be able to enable these advantages. Therefore, objectives for cloud solutions must be implemented in a way that supports the application architecture. | |
| − | + | === Use cloud first === | |
| − | + | * adopt the use of the GC Accelerators to ensure proper security and access controls | |
| − | + | * enforce this order of preference: software as a service (SaaS) first, then platform as a service (PaaS), and lastly infrastructure as a service (IaaS) | |
| + | * fulfill cloud services through SSC Cloud‑Brokering Services | ||
| + | * enforce this order of preference: public cloud first, then hybrid cloud, then private cloud, and lastly non‑cloud (on‑premises) solutions | ||
| + | * design for cloud mobility and develop an exit strategy to avoid vendor lock‑in | ||
| − | + | === Design for performance, availability and scalability === | |
| − | * | + | * ensure response times meet user needs, and critical services are highly available |
| − | * | + | * support zero‑downtime deployments for planned and unplanned maintenance |
| − | * | + | * use distributed architectures, assume failure will happen, handle errors gracefully, and monitor performance and behaviour actively |
| − | + | * establish architectures that supports new technology insertion with minimal disruption to existing programs and services | |
| − | * | + | * control technical diversity; design systems based on modern technologies and platforms already in use |
| − | * | ||
| − | |||
| − | |||
| + | === Follow DevSecOps principles === | ||
| + | * use continuous integration and continuous deployments | ||
| + | * ensure automated testing occurs for security and functionality | ||
| + | * include your users and other stakeholders as part of the DevSecOps process, which refers to the concept of making software security a core part of the overall software delivery process | ||
| − | <b | + | == Security architecture == |
| − | + | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/SecurityGuide click here for Security Architecture guide] </i></b></br></br> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | The GC Enterprise Security Architecture program is a government‑wide initiative to provide a standardized approach to developing IT security architecture, ensuring that basic security blocks are implemented across the enterprise as the infrastructure is being renewed. | ||
| − | + | More information regarding GC Enterprise Security Architecture can be found on the [https://www.gcpedia.gc.ca/wiki/GC_ESA_Artifact_Repository GC ESA Artifact Repository] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | === Build security into the system life cycle across all architectural layers === | ||
| + | * identify and <u>[https://www.gcpedia.gc.ca/wiki/Security_Categorization_Tool categorize]</u> information based on the degree of injury that could be expected to result from a compromise of its confidentiality, integrity and availability | ||
| + | * implement a continuous security approach, in alignment with <u>[https://cyber.gc.ca/en/guidance/it-security-risk-management-lifecycle-approach-itsg-33 Centre for Cyber Security’s IT Security Risk Management Framework]</u>; perform threat modelling to minimize the attack surface by limiting services exposed and information exchanged to the minimum necessary | ||
| + | * apply proportionate security measures that address business and user needs while adequately protecting data at rest and data in transit | ||
| + | * design systems to be resilient and available in order to support service continuity | ||
| − | + | === Ensure secure access to systems and services === | |
| − | * | + | * identify and authenticate individuals, processes or devices to an appropriate level of assurance, based on clearly defined roles, before granting access to information and services; leverage enterprise services such as Government of Canada trusted digital identity solutions that are supported by the <u>[https://github.com/canada-ca/PCTF-CCP Pan‑Canadian Trust Framework]</u> |
| − | * | + | * constrain service interfaces to authorized entities (users and devices), with clearly defined roles; segment and separate information based on sensitivity of information, in alignment with <u>[https://cyber.gc.ca/en/guidance/baseline-security-requirements-network-security-zones-government-canada-itsg-22 ITSG‑22]</u> and <u>[https://cyber.gc.ca/en/guidance/network-security-zoning-design-considerations-placement-services-within-zones-itsg-38 ITSG‑38]</u>. Management interfaces may require increased levels of protection |
| − | + | * implement <u>[https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/policy-implementation-notices/implementing-https-secure-web-connections-itpin.html HTTPS]</u> for secure web connections and <u>[https://cyber.gc.ca/en/guidance/implementation-guidance-email-domain-protection Domain-based Message Authentication, Reporting and Conformance (DMARC)]</u> for enhanced email security | |
| − | + | * establish secure interconnections between systems through secure <u>[https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/government-canada-standards-apis.html APIs]</u> or leveraging centrally managed hybrid IT connectivity services | |
| − | |||
| − | |||
| − | * <u> | ||
| + | === Maintain secure operations === | ||
| + | * establish processes to maintain visibility of assets and ensure the prompt application of security‑related patches and updates in order to reduce exposure to vulnerabilities, in accordance with GC ''Patch Management Guidance'' | ||
| + | * enable event logging, in accordance with GC ''Event Logging Guidance'', and perform monitoring of systems and services in order to detect, prevent, and respond to attacks | ||
| + | * establish an incident management plan in alignment with the <u>[https://www.canada.ca/en/government/system/digital-government/online-security-privacy/security-identity-management/government-canada-cyber-security-event-management-plan.html GC Cyber Security Event Management Plan (GC CSEMP)]</u> and report incidents to the <u>[https://cyber.gc.ca/en/contact-us Canadian Centre for Cyber Security]</u> | ||
| − | + | @fr| | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | Version : 1.34 | ||
| + | Le 27 juillet 2021 | ||
| + | Bureau du dirigeant principal de l’information du Canada | ||
| + | Secrétariat du Conseil du Trésor du Canada | ||
| + | Gouvernement du Canada | ||
| − | + | == Cadre de l’architecture intégrée == | |
| − | + | Le cadre d’architecture intégrée est le critère utilisé par le Comité d’examen de l’architecture intégrée du gouvernement du Canada et les comités d’examen de l’architecture des ministères lorsqu’ils examinent les initiatives numériques afin d’assurer leur harmonisation avec les architectures intégrées dans l’ensemble des activités, des informations, des applications et des domaines de la technologie et de la sécurité pour contribuer à l’obtention de résultats stratégiques. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Le cadre d'évaluation environnementale est entré en vigueur le 1er décembre 2020 et remplace l'annexe A, Procédures obligatoires pour l'évaluation de l'architecture d'entreprise de la Directive sur les services et le numérique. | |
| − | + | Le cadre d'architecture d'entreprise fournit des détails sur les exigences énoncées dans les sections suivantes de la politique et de la directive sur le service et le numérique. | |
| − | |||
| − | |||
| − | + | 4.1.2.3 de la politique sue les services et le numérique. Le dirigeant principal de l'information (DPI) du Canada est responsable de : Définir les attentes en matière d'architecture d'entreprise. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | 4.1.2.4 de la politique sue les services et le numérique. Le dirigeant principal de l'information (DPI) du Canada est chargé d'établir et de présider un comité d'examen de l'architecture d'entreprise qui a pour mandat de définir les normes d'architecture actuelles et cibles pour le gouvernement du Canada et d'examiner les propositions ministérielles d'harmonisation. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | 4.1.1.1 de la politique sue les services et le numérique. Le dirigeant principal de l'information (DPI) du Ministère est chargé de : présider un comité d'examen de l'architecture ministérielle qui a pour mandat d'examiner et d'approuver l'architecture de toutes les initiatives numériques du Ministère et d'assurer leur harmonisation avec les architectures d'entreprise. | |
| − | + | Le [https://www.canada.ca/en/government/system/digital-government/policies-standards/government-canada-enterprise-architecture-framework.html cadre d'architecture d'entreprise] est publié sur Canada.ca. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | <b> | + | == Architecture opérationnelle == |
| − | + | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/BusinessGuide cliquez ici pour le guide d'architecture opérationnelle] </i></b></br></br> | |
| − | |||
| − | |||
| − | |||
| − | + | L’architecture opérationnelle est un aspect essentiel à la réussite de la mise en œuvre de l’architecture cible de l’écosystème intégré du GC. La stratégie architecturale préconise une approche pan gouvernementale où les TI sont harmonisées avec les services opérationnels et les solutions sont fondées sur des composantes réutilisables mettant en œuvre des capacités opérationnelles afin d’offrir une expérience utilisateur cohérente. Par conséquent, il est essentiel de bien comprendre les services aux entreprises, les besoins des intervenants, les possibilités d’améliorer la cohésion et les possibilités de réutilisation à l’échelle du gouvernement. Par le passé, ces éléments n’étaient pas une priorité. On s’attend à ce que la culture et les pratiques en matière de TI doivent changer pour que l’architecture opérationnelle, en général, et ces éléments soient une priorité. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | === Conception entièrement numérique des services pour répondre aux besoins des utilisateurs du gouvernement du Canada et des autres intervenants=== | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | * Identifier clairement les utilisateurs internes et externes et les autres intervenants et leurs besoins dans le cadre de chaque politique, programme et service opérationnel; | |
| + | * Inclure les exigences de la politique qui s’appliquent à des utilisateurs en particulier et à d’autres groupes d’intervenants, comme l’accessibilité, l’analyse comparative entre les sexes plus et les langues officielles, dans la création du service; | ||
| + | * Effectuer une évaluation de l’incidence algorithmique (EIA) pour appuyer les activités d’atténuation des risques lors du déploiement d’un système décisionnel automatisé conformément à [https://www.canada.ca/fr/gouvernement/systeme/gouvernement-numerique/innovations-gouvernementales-numeriques/utilisation-responsable-ai.html la Directive sur la prise de décisions automatisée]; | ||
| + | * Modéliser la prestation de services opérationnels du début à la fin afin d’assurer la qualité, de maximiser l’efficacité et d’optimiser les gains d’efficience dans tous les canaux (p. ex., processus allégé). | ||
| − | + | === Architecte axé sur les résultats et stratégiquement aligné sur le Ministère et le gouvernement du Canada === | |
| − | |||
| − | |||
| − | |||
| + | * Déterminer les services opérationnels, les résultats et les stratégies du Ministère et du GC qui seront abordés; | ||
| + | * Établir des mesures pour les résultats opérationnels déterminés tout au long du cycle de vie d’un investissement; | ||
| + | * Traduire les résultats opérationnels et la stratégie en répercussions sur les capacités opérationnelles dans [[GC Enterprise Architecture/Business Capability Model| <b>le modèle des capacités opérationnelles du GC</b>]] pour établir un vocabulaire commun entre les organisations, le développement et les opérations. | ||
| + | === Promotion de l’habilitation horizontale de l’entreprise === | ||
| − | + | * Repérer les possibilités de rendre possibles des services opérationnels horizontaux à l’échelle du GC et d’offrir une expérience cohésive aux utilisateurs et aux autres intervenants; | |
| − | + | * Réutiliser les capacités opérationnelles, les processus et les solutions d’entreprise communs provenant de l’ensemble du gouvernement et du secteur privé; | |
| + | * Publier en mode ouvert tous les processus, les capacités et les solutions d’entreprise communs réutilisables pour que les autres puissent élaborer et tirer parti de services d’entreprise horizontaux cohérents. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | == Architecture de l’information == | |
| − | + | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/DataGuide cliquez ici pour un guide de l'architecture de l'information/données ] </i></b></br></br> | |
| − | |||
| − | < | ||
| − | < | ||
| − | + | L’architecture d’information comporte à la fois des données structurées et des données non structurées. Les pratiques exemplaires et les principes visent à soutenir les besoins de l’orientation des services opérationnels et des capacités opérationnelles. Afin de faciliter le partage efficace des données et de l’information à l’échelle du gouvernement, les architectures d’information devraient être conçues de manière à refléter une approche uniforme des données, comme l’adoption de normes fédérales et internationales. L’architecture de l’information devrait également refléter une gestion des données et de l’information et des pratiques de gouvernance responsables, notamment la source, la qualité, l’interopérabilité et les obligations juridiques et stratégiques connexes liées aux actifs de données. Les architectures d’information devraient également faire la distinction entre les données et l’information personnelles et non personnelles, étant donné que la collecte, l’utilisation, le partage (divulgation) et la gestion des renseignements personnels doivent respecter les exigences de la Loi sur la protection des renseignements personnels et de ses politiques connexes. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | < | + | === Recueillir les données requises pour répondre aux besoins des utilisateurs et des autres intervenants === |
| − | < | + | |
| − | < | + | * Évaluer les objectifs du programme fondés sur les exigences relatives aux données, ainsi que les besoins des utilisateurs, des entreprises et des intervenants; |
| + | * Recueillir seulement l’ensemble minimal de données nécessaire pour appuyer une politique, un programme ou un service; | ||
| + | * Réutiliser les actifs de données existants lorsque cela est permis et acquérir de nouvelles données seulement si cela est nécessaire; | ||
| + | * Veiller à ce que les données recueillies, y compris celles provenant de sources tierces, soient de grande qualité. | ||
| + | |||
| + | === Gérer et réutiliser les données de manière stratégique et responsable === | ||
| + | |||
| + | * Définir et établir clairement les rôles, les responsabilités et la responsabilisation en matière de gestion des données; | ||
| + | * Identifier et documenter la lignée des actifs de données; | ||
| + | * Définir les calendriers de conservation et d’élimination conformément à la valeur opérationnelle ainsi qu’aux politiques et aux lois applicables en matière de protection des renseignements personnels et de sécurité; | ||
| + | * Veiller à ce que les données soient gérées pour permettre, dans la mesure du possible, leurs interopérabilité, réutilisation et partage au sein des ministères et avec d’autres ministères à l’échelle du gouvernement afin d’éviter les répétitions et maximiser l’utilité, tout en respectant les exigences en matière de sécurité et de protection des renseignements personnels; | ||
| + | * Contribuer à la taxonomie et aux structures de classification des données d’entreprise et internationales afin de gérer, de stocker, de chercher et de récupérer des données. | ||
| + | |||
| + | === Utiliser et partager ouvertement les données de manière éthique et sécuritaire === | ||
| + | |||
| + | * Partager les données de façon ouverte par défaut conformément à la Directive sur le gouvernement ouvert et les normes numériques, tout en respectant les exigences en matière de sécurité et de protection des renseignements personnels. Les données partagées doivent respecter les normes organisationnelles et internationales existantes, notamment en matière de qualité et d’éthique des données; | ||
| + | * Veiller à ce que le formatage des données soit conforme aux normes institutionnelles et internationales en matière d’interopérabilité. Quand aucune norme n’existe, élaborer des normes de données ouvertes avec des experts clés en la matière; | ||
| + | * S’assurer que les données combinées ne comportent pas de risque d’identification ou de réidentification de renseignements sensibles ou personnels. | ||
| + | |||
| + | === Concevoir en tenant compte de la protection des renseignements personnels lors de la collecte, de l’utilisation et de la gestion des renseignements personnels === | ||
| + | |||
| + | * Assurer l’harmonisation avec les directives du Bureau de l’accès à l’information et de la protection des renseignements personnels (AIPRP) approprié de l’établissement en ce qui concerne l’interprétation et l’application de la Loi sur la protection des renseignements personnels et des instruments de politique connexes; | ||
| + | * Évaluer les initiatives pour déterminer si les renseignements personnels seront recueillis, utilisés, communiqués, conservés, partagés et éliminés; | ||
| + | * Recueillir des renseignements personnels seulement s’ils ont un lien direct avec le fonctionnement des programmes ou des activités; | ||
| + | * Informer les personnes des fins de la collecte au point de collecte en incluant un avis de confidentialité; | ||
| + | * Les renseignements personnels devraient, dans la mesure du possible, être recueillis directement auprès de personnes, mais ils peuvent provenir d’autres sources lorsque la Loi sur la protection des renseignements personnels le permet; | ||
| + | * Les renseignements personnels doivent être disponibles pour faciliter le droit d’accès et de correction des documents gouvernementaux des Canadiens; | ||
| + | * Concevoir des contrôles d’accès dans tous les processus et dans toutes les couches architecturales dès les premières étapes de la conception pour limiter l’utilisation et la divulgation des renseignements personnels; | ||
| + | * Concevoir des processus permettant que les renseignements personnels demeurent exacts, à jour et aussi complets que possible, et qu’ils puissent être corrigés au besoin; | ||
| + | * Il faut envisager des techniques de désidentification avant de partager des renseignements personnels; | ||
| + | * En collaboration avec le bureau de l’AIPRP approprié de l’établissement, déterminer si une évaluation des facteurs relatifs à la vie privée (ÉFVP) est requise pour déterminer et atténuer les risques pour la vie privée des programmes nouveaux ou considérablement modifiés ayant une incidence sur la vie privée des personnes; | ||
| + | * Établir des procédures pour identifier et traiter les atteintes à la vie privée pour qu’elles puissent être signalées rapidement et qu’il y soit répondu efficacement au bureau de l’AIPRP approprié de l’établissement. | ||
| + | |||
| + | |||
| + | == Architecture d’application == | ||
| + | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/ApplicationGuide cliquez ici pour le guide d'architecture d'application] </i></b></br></br> | ||
| + | |||
| + | Les pratiques d’architecture d’application doivent évoluer considérablement pour assurer la réussite de la mise en œuvre de l’architecture cible de l’écosystème d’entreprise du GC. La transition des anciens systèmes basés sur des architectures monolithiques vers des architectures axées sur les services opérationnels et sur des composants réutilisables mettant en œuvre des capacités opérationnelles constitue un changement majeur. L’interopérabilité devient un élément clé, et le nombre d’intervenants dont on doit tenir compte augmente. | ||
| + | |||
| + | === Utiliser les solutions de sources ouvertes hébergées dans le nuage public === | ||
| + | |||
| + | * Choisir des solutions existantes qui peuvent être réutilisées plutôt que des solutions personnalisées; | ||
| + | * Mettre toutes les améliorations à la disposition de la collectivité; | ||
| + | * Enregistrer les logiciels ouverts dans l’Échange de ressources ouvertes. | ||
| + | |||
| + | === Utiliser les logiciels sous forme de service (SaaS) hébergés dans le nuage public === | ||
| + | |||
| + | * Choisir les logiciels sous forme de service qui conviennent le mieux à l’utilisation prévue en fonction de son alignement sur les capacités SaaS; | ||
| + | * Choisir une solution SaaS extensible; | ||
| + | * Configurer le SaaS et, s’il faut le personnaliser, l’étendre en tant que module source ouverte. | ||
| + | |||
| + | === Conception en vue de l’interopérabilité === | ||
| + | |||
| + | * Concevoir les systèmes comme des services hautement modulaires et indépendants; | ||
| + | * Présenter les services, y compris les services existants, au moyen d’IPA; | ||
| + | * Rendre les IPA accessibles aux parties prenantes concernées. | ||
| + | |||
| + | |||
| + | == Architecture de la technologie == | ||
| + | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/TechnologyGuide cliquez ici pour le guide de l'architecture de la technologie] </i></b></br></br> | ||
| + | |||
| + | L’architecture technologique est un important catalyseur de solutions hautement accessibles et adaptables qui doivent être harmonisées avec l’architecture d’application choisie. L’adoption de l’informatique en nuage offre de nombreux avantages potentiels en atténuant les contraintes logistiques qui ont souvent une incidence négative sur les solutions existantes hébergées « sur place ». Cependant, l’architecture d’application doit rendre possible de tirer de ces avantages. | ||
| + | |||
| + | === Utiliser d’abord le nuage === | ||
| + | |||
| + | * Adopter l’utilisation des accélérateurs du GC pour assurer des contrôles de sécurité et d’accès adéquats; | ||
| + | * Appliquer l’ordre de préférence suivant : logiciel en tant que service (SaaS) d’abord, puis plateforme comme service (PaaS), et enfin infrastructure comme service (IaaS); | ||
| + | * Exécuter les services infonuagiques par l’entremise des services de courtage infonuagique de SPC; | ||
| + | * Appliquer l’ordre de préférence suivant : le nuage public d’abord, ensuite le nuage hybride, puis le nuage privé et, enfin, les solutions sans nuage (sur site); | ||
| + | * Concevoir la mobilité sur le nuage et élaborer une stratégie de sortie pour éviter l’immobilisation des fournisseurs. | ||
| + | |||
| + | === Conception pour le rendement, la disponibilité et l’évolutivité === | ||
| + | |||
| + | * Veiller à ce que les délais de réponse répondent aux besoins des utilisateurs et à ce que les services essentiels soient hautement disponibles; | ||
| + | * Prendre en charge des déploiements sans temps d’arrêt pour la maintenance planifiée et non planifiée; | ||
| + | * Utiliser des architectures distribuées, prévoir la possibilité d’échec, traiter dignement les erreurs et effectuer une surveillance active du rendement et du comportement; | ||
| + | * Établir des architectures qui facilitent l’ajout de nouvelles technologies tout en limitant la perturbation des programmes et des services existants; | ||
| + | * Contrôler la diversité technique – concevoir des systèmes basés sur des technologies et des plateformes modernes déjà utilisées. | ||
| + | |||
| + | === Respecter les principes de développement d’applications modernes (DevSecOps) === | ||
| + | |||
| + | * Utiliser l’intégration continue et les déploiements continus; | ||
| + | * S’assurer que des tests automatisés sont effectués pour garantir la sécurité et la fonctionnalité; | ||
| + | * Faire participer les utilisateurs et les autres intervenants au processus DevSecOps, qui fait référence au concept de faire de la sécurité logicielle un élément central du processus global de livraison de logiciels. | ||
| + | |||
| + | |||
| + | == Architecture de sécurité == | ||
| + | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/SecurityGuide cliquez ici pour le guide de l'architecture de sécurité] </i></b></br></br> | ||
| + | |||
| + | Le Programme de l’architecture de sécurité intégrée du GC est une initiative pan gouvernementale visant à fournir une approche normalisée pour l’élaboration de l’architecture de sécurité des TI, afin de s’assurer que les blocs de sécurité de base sont mis en place dans l’ensemble de l’organisation à mesure que l’infrastructure est renouvelée. | ||
| + | |||
| + | === Intégrer la sécurité dans le cycle de vie du système, dans toutes les couches architecturales === | ||
| + | |||
| + | * Déterminer et <u>[https://www.gcpedia.gc.ca/wiki/Security_Categorization_Tool catégoriser]</u> catégoriser les renseignements en fonction du degré de préjudice qui pourrait résulter de la compromission de leur confidentialité, de leur intégrité et de leur disponibilité; | ||
| + | * Mettre en place une approche de sécurité continue, conformément au <u>[https://cyber.gc.ca/fr/orientation/la-gestion-des-risques-lies-la-securite-des-ti-une-methode-axee-sur-le-cycle-de-vie Cadre de gestion des risques liés à la sécurité des TI du CCC]</u> Cadre de gestion des risques liés à la sécurité des TI du CCC; effectuer la modélisation des menaces pour réduire au minimum la surface d’attaque en limitant les services exposés et l’information échangée au minimum nécessaire; | ||
| + | * Appliquer des mesures de sécurité proportionnées répondant aux besoins des entreprises et des utilisateurs tout en protégeant adéquatement les données au repos et les données en transit; | ||
| + | * Concevoir des systèmes résilients et disponibles pour soutenir la continuité de la prestation du service. | ||
| + | |||
| + | === Assurer un accès sécurisé aux systèmes et aux services === | ||
| + | |||
| + | * Identifier et authentifier les personnes, les processus ou les appareils à un niveau d’assurance approprié, en fonction de rôles clairement définis, avant d’accorder l’accès à l’information et aux services; tirer parti des services d’entreprise comme les solutions d’identité numérique de confiance du gouvernement du Canada qui sont appuyées par le <u>[https://github.com/canada-ca/PCTF-CCP Cadre de confiance pancanadien]</u>; | ||
| + | * Limiter les interfaces de service aux entités autorisées (utilisateurs et dispositifs) ayant des rôles clairement définis; segmenter et séparer l’information en fonction de sa sensibilité, conformément aux documents <u>[https://cyber.gc.ca/en/guidance/baseline-security-requirements-network-security-zones-government-canada-itsg-22 LDSTI-22]</u> et <u>[https://cyber.gc.ca/en/guidance/network-security-zoning-design-considerations-placement-services-within-zones-itsg-38 LDSTI-38]</u>. Les interfaces de gestion peuvent nécessiter des niveaux de protection accrus; | ||
| + | * Mettre en œuvre des protocoles <u>[https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/policy-implementation-notices/implementing-https-secure-web-connections-itpin.html HTTPS]</u> pour les connexions Web sécurisées et <u>[https://cyber.gc.ca/en/guidance/implementation-guidance-email-domain-protection d’authentification des messages fondée sur le domaine, rapports et conformité (DMARC)]</u> pour améliorer la sécurité des courriels; | ||
| + | * Établir des interconnexions sécurisées entre les systèmes à l’aide d’<u>[https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/government-canada-standards-apis.html IPA sécuritaires]</u> ou tirer parti des services de connectivité des TI hybrides gérés de manière centralisée. | ||
| + | |||
| + | === Maintenir des opérations sécurisées === | ||
| + | |||
| + | * Établir des processus pour maintenir la visibilité des biens et assurer l’application rapide des correctifs et des mises à jour liés à la sécurité afin de réduire l’exposition aux vulnérabilités, conformément au Guide de gestion des correctifs du GC; | ||
| + | * Permettre la consignation des événements, conformément au Guide sur la consignation des événements du GC, et effectuer la surveillance des systèmes et des services afin de détecter les attaques, de les prévenir et d’y réagir; | ||
| + | * Établir un plan de gestion des incidents conforme au <u>[https://www.canada.ca/en/government/system/digital-government/online-security-privacy/security-identity-management/government-canada-cyber-security-event-management-plan.html Plan de gestion des événements de cybersécurité du GC (PGEC GC)]</u> et signaler les incidents au <u>[https://cyber.gc.ca/en/contact-us Centre canadien pour la cybersécurité (CCC)]</u>. | ||
| + | |||
| + | |||
| + | </multilang> | ||
Latest revision as of 10:12, 3 February 2023
Version: 1.35
February 24, 2021
Office of the Chief Information Officer of Canada, Treasury Board of Canada Secretariat, Government of Canada
Enterprise Architecture Framework[edit | edit source]
The Enterprise Architecture Framework is the criteria used by the Government of Canada enterprise architecture review board and departmental architecture review boards when reviewing digital initiatives to ensure their alignment with enterprise architectures across business, information, application, technology and security domains to support strategic outcomes. The EA Framework came into effect on December 1, 2020 and is a replacement of Appendix A, Mandatory Procedures for Enterprise Architecture Assessment from the Directive on Service and Digital.
The Enterprise Architecture Framework provide details on the requirements set out in the following sections of the Policy and Directive on Service and Digital.
4.1.2.3 of the Policy on Service and Digital. The Chief Information Officer (CIO) of Canada is responsible for: Prescribing expectations with regard to enterprise architecture.
4.1.2.4 of the Policy on Service and Digital. The Chief Information Officer (CIO) of Canada is responsible for: Establishing and chairing an enterprise architecture review board that is mandated to define current and target architecture standards for the Government of Canada and review departmental proposals for alignment.
4.1.1.1 of the Directive on Service and Digital. The departmental Chief Information Officer (CIO) is responsible for: Chairing a departmental architecture review board that is mandated to review and approve the architecture of all departmental digital initiatives and ensure their alignment with enterprise architectures.
The Enterprise Architecture Framework is also published on Canada.ca.
Business architecture[edit | edit source]
click here for Business Architecture guide
Business architecture is a critical aspect for the successful implementation of the GC Enterprise Ecosystem Target Architecture. The architectural strategy advocates whole‑of‑government approach where IT is aligned to business services and solutions are based on re‑useable components implementing business capabilities in order to deliver a cohesive user experience. As such, it is essential that business services, stakeholder needs, opportunities to improve cohesion and opportunities for reuse across government be clearly understood. In the past these elements have not been a priority. It is expected that the IT culture and practices will have to change to make business architecture, in general, and these elements a primary focus.
Design services digitally from end‑to‑end to meet the Government of Canada users and other stakeholders’ needs[edit | edit source]
- clearly identify internal and external users and other stakeholders and their needs for each policy, program and business service
- include policy requirement applying to specific users and other stakeholder groups, such as accessibility, gender-based plus analysis, and official languages in the creation of the service
- perform Algorithmic Impact Assessment (AIA) to support risk mitigation activities when deploying an automated decision system as per Directive on Automated Decision-Making
- Model end-to-end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels
Architect to be outcome‑driven and strategically aligned to the department and to the Government of Canada[edit | edit source]
- identify which departmental/GC business services, outcomes and strategies will be addressed
- establish metrics for identified business outcomes throughout the life cycle of an investment
- translate business outcomes and strategy into business capability implications in the GC Business Capability Model to establish a common vocabulary between business, development, and operation
Promote horizontal enablement of the enterprise[edit | edit source]
- identify opportunities to enable business services horizontally across the GC enterprise and to provide cohesive experience to users and other stakeholders
- reuse common business capabilities, processes and enterprise solutions from across government and private sector
- publish in the open all reusable common business capabilities, processes and enterprise solutions for others to develop and leverage cohesive horizontal enterprise services
Information architecture[edit | edit source]
click here for Information/Data Architecture guide
Information architecture is defined as the management and organization of data for a business. The best practices and principles aim to support the needs of a business service and business capability orientation. To facilitate effective sharing of data and information across government, information architectures should be designed to reflect a consistent approach to both structured and unstructured data, such as the adoption of federal and international standards. Information architecture should also reflect responsible data management, information management and governance practices, including the source, quality, interoperability, and associated legal and policy obligations related to the data assets. Information architectures should also distinguish between personal and non‑personal data. How personal information is treated such as its collection, use, sharing (disclosure), and management must respect the requirements of the Privacy Act and its related policies.
Collect data to address the needs of the users and other stakeholders[edit | edit source]
- assess data requirements‑based program objectives, as well users, business and stakeholder needs
- collect only the minimum set of data needed to support a policy, program, or service
- reuse existing data assets where permissible and only acquire new data if required
- ensure data collected, including from third-party sources, are of high quality
Manage and reuse data strategically and responsibly[edit | edit source]
- define and establish clear roles, responsibilities, and accountabilities for data management
- identify and document the lineage of data assets
- define retention and disposition schedules in accordance with business value as well as applicable privacy and security policy and legislation
- ensure data are managed to enable interoperability, reuse and sharing to the greatest extent possible within and across departments in government to avoid duplication and maximize utility, while respecting security and privacy requirements
- contribute to and align with enterprise and international data taxonomy and classification structures to manage, store, search and retrieve data
[edit | edit source]
- share data openly by default as per the Directive on Open Government and Digital Standards, while respecting security and privacy requirements; data shared should adhere to existing enterprise and international standards, including on data quality and ethics
- ensure data formatting aligns to existing enterprise and international standards on interoperability; where none exist, develop data standards in the open with key subject matter experts
- ensure that combined data does not risk identification or re‑identification of sensitive or personal information
Design with privacy in mind for the collection, use and management of personal Information[edit | edit source]
- ensure alignment with guidance from appropriate institutional ATIP Office with respect to interpretation and application of the Privacy Act and related policy instruments
- assess initiatives to determine if personal information will be collected, used, disclosed, retained, shared, and disposed
- only collect personal information if it directly relates to the operation of the programs or activities
- notify individuals of the purpose for collection at the point of collection by including a privacy notice
- personal information should be, wherever possible, collected directly from individuals but can be from other sources where permitted by the Privacy Act
- personal information must be available to facilitate Canadians’ right of access to and correction of government records
- design access controls into all processes and across all architectural layers from the earliest stages of design to limit the use and disclosure of personal information
- design processes so personal information remains accurate, up‑to‑date and as complete as possible, and can be corrected if required
- de‑identification techniques should be considered prior to sharing personal information
- in collaboration with appropriate institutional ATIP Office, determine if a Privacy Impact Assessment (PIA) is required to identify and mitigate privacy risks for new or substantially modified programs that impact the privacy of individuals
- establish procedures to identify and address privacy breaches so they can be reported quickly and responded to efficiently to appropriate institutional ATIP Office
Application architecture[edit | edit source]
click here for Application Architecture guide
Application architecture is defined as the management of software used by a business to solve problems. Application architecture practices must evolve significantly for the successful implementation of the GC Enterprise Ecosystem Target Architecture. Transitioning from legacy systems based on monolithic architectures to architectures that are oriented towards business services and re‑useable components implementing business capabilities, is a major shift. Interoperability becomes a key element, and the number of stakeholders that must be considered increases.
Use open source solutions hosted in public cloud[edit | edit source]
- select existing solutions that can be reused over custom built
- contribute all improvements back to the communities
- register open source software to the Open Resource Exchange
Use software as a service (SaaS) hosted in public cloud[edit | edit source]
- choose SaaS that best fit for purpose based on alignment with SaaS capabilities
- choose a SaaS solution that is extendable
- configure SaaS and if customization is necessary extend as open source modules
Design for Interoperability[edit | edit source]
- design systems as highly modular and loosely coupled services
- expose services, including existing ones, through APIs
- make the APIs discoverable to the appropriate stakeholders
Enable Interoperability, Proposed amendment March 23, 2021[edit | edit source]
- expose data and functionality through service interfaces
- applications must communicate with each other via those interfaces
- services interfaces must be published and discoverable
Technology architecture[edit | edit source]
click here for Technology Architecture guide
Technology architecture is defined as the management and organization of technical equipment and devices of a business. Technology architecture is an important enabler of highly available and adaptable solutions that must be aligned with the chosen application architecture. Cloud adoption provides many potential advantages by mitigating the logistical constraints that often negatively impacted legacy solutions hosted “on premises.” However, the application architecture must be able to enable these advantages. Therefore, objectives for cloud solutions must be implemented in a way that supports the application architecture.
Use cloud first[edit | edit source]
- adopt the use of the GC Accelerators to ensure proper security and access controls
- enforce this order of preference: software as a service (SaaS) first, then platform as a service (PaaS), and lastly infrastructure as a service (IaaS)
- fulfill cloud services through SSC Cloud‑Brokering Services
- enforce this order of preference: public cloud first, then hybrid cloud, then private cloud, and lastly non‑cloud (on‑premises) solutions
- design for cloud mobility and develop an exit strategy to avoid vendor lock‑in
Design for performance, availability and scalability[edit | edit source]
- ensure response times meet user needs, and critical services are highly available
- support zero‑downtime deployments for planned and unplanned maintenance
- use distributed architectures, assume failure will happen, handle errors gracefully, and monitor performance and behaviour actively
- establish architectures that supports new technology insertion with minimal disruption to existing programs and services
- control technical diversity; design systems based on modern technologies and platforms already in use
Follow DevSecOps principles[edit | edit source]
- use continuous integration and continuous deployments
- ensure automated testing occurs for security and functionality
- include your users and other stakeholders as part of the DevSecOps process, which refers to the concept of making software security a core part of the overall software delivery process
Security architecture[edit | edit source]
click here for Security Architecture guide
The GC Enterprise Security Architecture program is a government‑wide initiative to provide a standardized approach to developing IT security architecture, ensuring that basic security blocks are implemented across the enterprise as the infrastructure is being renewed.
More information regarding GC Enterprise Security Architecture can be found on the GC ESA Artifact Repository
Build security into the system life cycle across all architectural layers[edit | edit source]
- identify and categorize information based on the degree of injury that could be expected to result from a compromise of its confidentiality, integrity and availability
- implement a continuous security approach, in alignment with Centre for Cyber Security’s IT Security Risk Management Framework; perform threat modelling to minimize the attack surface by limiting services exposed and information exchanged to the minimum necessary
- apply proportionate security measures that address business and user needs while adequately protecting data at rest and data in transit
- design systems to be resilient and available in order to support service continuity
Ensure secure access to systems and services[edit | edit source]
- identify and authenticate individuals, processes or devices to an appropriate level of assurance, based on clearly defined roles, before granting access to information and services; leverage enterprise services such as Government of Canada trusted digital identity solutions that are supported by the Pan‑Canadian Trust Framework
- constrain service interfaces to authorized entities (users and devices), with clearly defined roles; segment and separate information based on sensitivity of information, in alignment with ITSG‑22 and ITSG‑38. Management interfaces may require increased levels of protection
- implement HTTPS for secure web connections and Domain-based Message Authentication, Reporting and Conformance (DMARC) for enhanced email security
- establish secure interconnections between systems through secure APIs or leveraging centrally managed hybrid IT connectivity services
Maintain secure operations[edit | edit source]
- establish processes to maintain visibility of assets and ensure the prompt application of security‑related patches and updates in order to reduce exposure to vulnerabilities, in accordance with GC Patch Management Guidance
- enable event logging, in accordance with GC Event Logging Guidance, and perform monitoring of systems and services in order to detect, prevent, and respond to attacks
- establish an incident management plan in alignment with the GC Cyber Security Event Management Plan (GC CSEMP) and report incidents to the Canadian Centre for Cyber Security
