Important: The GCConnex decommission will not affect GCCollab or GCWiki. Thank you and happy collaborating!

Difference between revisions of "GC Enterprise Architecture/Framework"

From wiki
Jump to navigation Jump to search
m
 
(117 intermediate revisions by 8 users not shown)
Line 1: Line 1:
−
{{OCIO_GCEA_Header}}
+
{{OCIO GCEA Header}}
 +
<multilang>
 +
@en|
  
−
== Appendix A: Enterprise Architecture Framework ==
+
Version: 1.35
−
As stated in the Policy on Service and Digital, the CIO of Canada responsible for:
 
−
* "Prescribing expectations with regard to enterprise architecture."
 
−
* "Establishing and chairing an enterprise architecture review board (EARB) that is mandated to define current and target architecture standards for the Government of Canada and review departmental proposals for alignment."
 
−
* "Approving an annual, forward-looking three-year enterprise-wide plan that establishes the strategic direction for the integrated management of service, information, data, IT, and cyber security and ensuring the plan includes a progress report on how it was implemented in the previous year."
 
−
The Enterprise Architecture Framework articulates the prescriptive vision for enterprise architecture in the GC.  
 
  
−
It is the fundamental element for GC EARB to meet its mandate to review and endorse the architectures of all departmental digital initiatives and ensure their alignment with enterprise architectures. Digital initiatives presenting at GC EARB complete the [[Images/1/1a/GC EARB Presenter Template-BETA Release Aug 18 2020.pptx|GC EARB presenter template]] and indicate how the target architecture intends to achieve the criteria outlined in the EA Framework. An summary Enterprise Architecture Assessment is produced to recommend to assist the committee in making recommendations for endorsement.   
+
February 24, 2021
  
−
The Enterprise Architecture Framework is an aspirational representation of the strategic direction view that is encapsulated in  Service and Digital Target Enterprise Architecture. 
+
Office of the Chief Information Officer of Canada, Treasury Board of Canada Secretariat, Government of Canada
  
−
Beyond being applied to individual projects submitted to GC EARB, the EA Framework will also provide a superstructure for the Strategic Actions in the revised DOSP, spanning across all four of the pillars in that document, which will serve as the primary implementation plan for the Policy.
+
== 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.
  
−
To realize the GC Enterprise Ecosystem Target Architecture, departments should align with the practices and principles as outlined below when considering new IT solutions or modernizing older solutions.  The architectural approach was developed to facilitate managed incremental transitions but requires more strategic planning on the part of departments to be implemented effectively.
+
The Enterprise Architecture Framework provide details on the requirements set out in the following sections of the Policy and Directive on Service and Digital.
  
−
The Government of Canada Enterprise Architecture framework defined below presents the evaluation criteria being used by GC Enterprise Architecture Review Board to align solutions to the Service and Digital Target Enterprise Architecture.   In the interest of effective communication to the architecture community of practice, the material has been organized based on the architectural domains as defined within the TOGAF  framework – Business, Information, Application, Technology, Security, and Privacy.
+
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.
  
−
The EA Framework was presented at GC EARB on [https://gcconnex.gc.ca/file/view/67145496/gc-earb-2020-07-16-02-tbs-service-digital-target-enterprise-architecture-and-updates-to-the-ea-framework-pdf?language=en July 16th, 2020]. Additional feedback has been sought from the departments by August 31st, 2020, before it will return for an endorsement.
+
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.
  
−
== Business Architecture ==
+
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.
  
−
=== Fulfill the Government of Canada users and other stakeholder's needs ===
+
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.
−
* 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 accessibilities, gender based+ analysis, and official languages in the creation of the service
 
−
* Model end-to-end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels (e.g lean process)
 
  
−
=== Architect to be Outcome Driven and Strategically Aligned to the Department and to the Government of Canada[edit | edit source] ===
+
== Business architecture ==
−
* Identify which departmental/GC business services, outcomes and strategies will be addressed
+
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/BusinessGuide click here for Business Architecture guide] </i></b></br></br>
−
* Establish metrics for identified business outcomes throughout the lifecycle 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] ===
+
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.
−
* 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
 
−
<multilang>
 
−
@en|__NOTOC__
 
  
−
The EA Framework was presented at GC EARB on [https://gcconnex.gc.ca/file/view/67145496/gc-earb-2020-07-16-02-tbs-service-digital-target-enterprise-architecture-and-updates-to-the-ea-framework-pdf?language=en July 16th, 2020]. Additional feedback has been sought from the departments by August 31st, 2020, before it will return for an endorsement.
+
=== 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
  
−
<div style="padding-left: 15px; border-left: 10px solid #c5d5af; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19); color: black; background-color: white; font-size:1.2em;">
+
=== Architect to be outcome‑driven and strategically aligned to the department and to the Government of Canada ===
−
== [[GC_EA_Playbook#1._Business_Architecture | 1. Business Architecture]] ==
+
* 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
  
−
=== Fulfill the Government of Canada users and other stakeholder's needs ===
+
=== Promote horizontal enablement of the enterprise ===
−
* Clearly identify internal and external users and other stakeholders and their needs for each policy, program and business service
+
* identify opportunities to enable business services horizontally across the GC enterprise and to provide cohesive experience to users and other stakeholders
−
* Include policy requirement applying to specific users and other stakeholder groups, such as accessibilities, gender based+ analysis, and official languages in the creation of the service
+
* reuse common business capabilities, processes and enterprise solutions from across government and private sector
−
* Model end-to-end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels (e.g lean process)
+
* publish in the open all reusable common business capabilities, processes and enterprise solutions for others to develop and leverage cohesive horizontal enterprise services
  
−
=== 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 lifecycle 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 ===
+
== Information architecture ==
−
* Identify opportunities to enable business services horizontally across the GC enterprise and to provide cohesive experience to users and other stakeholders
+
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/DataGuide click here for Information/Data Architecture guide] </i></b></br></br>
−
* 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
 
−
</div>
 
  
−
<div style="padding-left: 15px; border-left: 10px solid #f4d177; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19); color: black; background-color: white; font-size:1.2em;">
+
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.
−
== [[GC_EA_Playbook#2._Information_Architecture | 2. Information Architecture]] ==
 
  
 
=== Collect data to address the needs of the users and other stakeholders ===
 
=== Collect data to address the needs of the users and other stakeholders ===
−
* Assess data requirements based on users and other stakeholder needs
+
* 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
+
* collect only the minimum set of data needed to support a policy, program, or service
−
* Reuse existing data assets and only acquire new data if required
+
* 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
+
* ensure data collected, including from third-party sources, are of high quality
  
−
=== Manage data strategically and responsibly ===
+
=== Manage and reuse data strategically and responsibly ===
−
* Define and establish clear roles, responsibilities, and accountabilities for data management
+
* define and establish clear roles, responsibilities, and accountabilities for data management
−
* Identify and document the lineage of data assets
+
* 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
+
* 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
+
* 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
+
* 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 ===
 
=== Use and share data openly in an ethical and secure manner ===
−
* Share data openly by default as per the [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=28108 Directive on Open Government] and [https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html Digital Standards], while adhering to existing enterprise and international standards, including on data quality and ethics
+
* 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, in consultation with the Enterprise Data Community of Practice
+
* 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
+
* ensure that combined data does not risk identification or re‑identification of sensitive or personal information
−
</div>
+
 
 +
=== 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''
 +
 
 +
== 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
 +
 
 +
== 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
 +
 
 +
=== 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.
  
−
<div style="padding-left: 15px; border-left: 10px solid #f5844e; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19); color: black; background-color: white; font-size:1.2em;">
+
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.  
−
== [[GC_EA_Playbook#3._Application_Architecture | 3. Application Architecture]] ==
 
  
−
=== Use Open Source Solutions hosted in Public Cloud ===
+
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.
−
* 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 ===
+
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.
−
* 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 [https://www.gcpedia.gc.ca/wiki/En/GCinterop Interoperability]===
+
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.
−
* Design systems as highly modular and loosely coupled services
 
−
* Expose services, including existing ones, through APIs
 
−
* Make the APIs discoverable to the appropriate stakeholders
 
−
</div>
 
  
−
<div style="padding-left: 15px; border-left: 10px solid #cb6d49; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19); color: black; background-color: white; font-size:1.2em;">
 
  
−
== [[GC_EA_Playbook#4._Technology_Architecture | 4. Technology Architecture]] ==
+
== 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>
  
−
=== Use Cloud first ===
+
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Ă©.
−
* 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 ===
+
=== Conception entiÚrement numérique des services pour répondre aux besoins des utilisateurs du gouvernement du Canada et des autres intervenants===
−
* 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 ===
+
* 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Ă©).
  
−
* Use continuous integration and continuous deployments (CI/CD)
+
=== Architecte axé sur les résultats et stratégiquement aligné sur le MinistÚre et le gouvernement du Canada ===
−
* Ensure automated testing occurs for security and functionality
 
−
* Include your users and other stakeholders as part of DevSecOps process
 
−
</div>
 
  
−
<div style="padding-left: 15px; border-left: 10px solid #996782; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19); color: black; background-color: white; font-size:1.2em;">
+
* Déterminer les services opérationnels, les résultats et les stratégies du MinistÚre et du GC qui seront abordés;
−
== [[GC_EA_Playbook#5._Security_Architecture_and_Privacy | 5. Security Architecture and Privacy]] ==
+
* É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.
  
−
=== Build Security into the System Life Cycle, Across All Architectural Layers ===
+
=== Promotion de l’habilitation horizontale de l’entreprise ===
−
* Identify and [https://www.gcpedia.gc.ca/wiki/Security_Categorization_Tool 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 [https://cyber.gc.ca/en/guidance/it-security-risk-management-lifecycle-approach-itsg-33 CCCS’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 ===
+
* 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;
−
* Identify and authenticate individuals, processes and/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 [https://github.com/canada-ca/PCTF-CCP Pan-Canadian Trust Framework].
+
* 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Ă©;
−
* 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 [https://cyber.gc.ca/en/guidance/baseline-security-requirements-network-security-zones-government-canada-itsg-22 ITSG-22] and [https://cyber.gc.ca/en/guidance/network-security-zoning-design-considerations-placement-services-within-zones-itsg-38 ITSG-38]. Management interfaces may require increased levels of protection.
+
* 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.
−
* Implement [https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/policy-implementation-notices/implementing-https-secure-web-connections-itpin.html HTTPS] for secure web connections and [https://cyber.gc.ca/en/guidance/implementation-guidance-email-domain-protection DMARC] for enhanced email security.
 
−
* Establish secure interconnections between systems through secure [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32604 APIs] or leveraging centrally managed Hybrid IT connectivity services.
 
  
−
=== 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 [https://www.canada.ca/en/treasury-board-secretariat/services/access-information-privacy/security-identity-management/government-canada-cyber-security-event-management-plan.html GC Cyber Security Event Management Plan (GC CSEMP)] and report incidents to the [https://cyber.gc.ca/en/contact-us Canadian Centre for Cyber Security (CCCS)].
 
  
−
=== Privacy by Design ===
+
== Architecture de l’information ==
−
* Perform Privacy Impact Assessment (PIA) to support risk mitigation activities when personal information is involved
+
<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>
−
* Perform [https://canada-ca.github.io/aia-eia-js/ Algorithmic Impact Assessment (AIA)] to support risk mitigation activities when deploying an automated decision system as per [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32592 Directive on Automated Decision Making]. For more info, please go to [https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/responsible-use-ai/algorithmic-impact-assessment.html this link]
 
−
* Implement security measures to assure the protection of personal information and data
 
−
* Take into consideration the [https://www.ipc.on.ca/wp-content/uploads/Resources/7foundationalprinciples.pdf 7 Foundational Privacy Design Principles] (English only) when designing services
 
−
</div>
 
  
−
<!-- FRENCH -->
+
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.
−
@fr|__NOTOC__
 
  
−
<h3> TO BE TRANSLATED >>>> This is a <b> DRAFT STREAMLINED COPY </b> of the proposed updates to the GC Enterprise Architecture Framework(formerly GC EA Standards) for assessment</h3>
+
=== Recueillir les données requises pour répondre aux besoins des utilisateurs et des autres intervenants ===
  
−
<div style="padding-left: 15px; border-left: 10px solid #c5d5af; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19); color: black; background-color: white; font-size:1.2em;">
+
* É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;
−
== [[GC_EA_Playbook#1._Business_Architecture | 1. Architecture opérationnelle]] ==
+
* 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é.
  
−
=== RĂ©pondre aux besoins des utilisateurs du gouvernement du Canada et des autres intervenants</b>
+
=== Gérer et réutiliser les données de maniÚre stratégique et responsable ===
−
* Cerner clairement les utilisateurs internes et externes et les autres intervenants et leurs besoins pour chaque politique, programme et service opérationnel
 
−
* Inclure dans la crĂ©ation du service les exigences de politique qui s’appliquent Ă  des utilisateurs particuliers et Ă  d’autres groupes d’intervenants, comme l’accessibilitĂ©, l’analyse comparative entre les sexes+ et les langues officielles
 
−
* Mettre en place un modĂšle de prestation de services de bout en bout pour assurer la qualitĂ©, maximiser l’efficacitĂ© et optimiser l’efficience de tous les canaux (par exemple, processus allĂ©gĂ©)
 
  
−
=== Concevoir les architectures axées sur les résultats et stratégiquement harmonisées sur le MinistÚre et le gouvernement du Canada ===
+
* Définir et établir clairement les rÎles, les responsabilités et la responsabilisation en matiÚre de gestion des données;
−
* Déterminer les services, les résultats et les stratégies opérationnels du MinistÚre et du GC qui seront pris en compte
+
* Identifier et documenter la lignée des actifs de données;
−
* Établir des mesures pour dĂ©terminer les rĂ©sultats opĂ©rationnels tout au long du cycle de vie d’un investissement
+
* 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Ă©;
−
* Traduire les rĂ©sultats opĂ©rationnels et la stratĂ©gie en incidences sur les capacitĂ©s opĂ©rationnelles dans le modĂšle de capacitĂ© opĂ©rationnelle du GC afin d’établir un vocabulaire commun entre les activitĂ©s, l’élaboration et les opĂ©rations
+
* 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.
  
−
=== Promouvoir l’habilitation horizontale de l’organismee ===
+
=== Utiliser et partager ouvertement les données de maniÚre éthique et sécuritaire ===
−
* Cerner les possibilités de services opérationnels accessibles horizontalement au sein du GC et offrir une expérience cohérente aux utilisateurs et aux autres intervenants
 
−
* RĂ©utiliser les capacitĂ©s et les processus opĂ©rationnels et les solutions d’entreprise communes de l’ensemble du gouvernement et du secteur privĂ©
 
−
* Publier ouvertement toutes les capacitĂ©s et les processus opĂ©rationnels communs et rĂ©utilisables et toutes les solutions d’entreprises pour permettre Ă  d’autres de mettre sur pied des services intĂ©grĂ©s horizontaux cohĂ©rents
 
−
</div>
 
  
−
<div style="padding-left: 15px; border-left: 10px solid #f4d177; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19); color: black; background-color: white; font-size:1.2em;">
+
* 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;
−
== [[GC_EA_Playbook#2._Information_Architecture> 2. Architecture de l’information]] ==
+
* 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.
  
−
=== Recueillir des données pour répondre aux besoins des utilisateurs et des autres intervenants ===
+
=== Concevoir en tenant compte de la protection des renseignements personnels lors de la collecte, de l’utilisation et de la gestion des renseignements personnels ===
−
* Évaluer les exigences en matiĂšre de donnĂ©es en fonction des besoins des utilisateurs et des autres intervenants
 
−
* Recueillir uniquement l’ensemble minimal de donnĂ©es nĂ©cessaire Ă  l’appui d’une stratĂ©gie, d’un programme ou d’un service
 
−
* RĂ©utiliser les ressources de donnĂ©es existantes et n’acquĂ©rir de nouvelles donnĂ©es que si nĂ©cessaire
 
−
* S’assurer que les donnĂ©es recueillies, y compris auprĂšs de sources tierces, sont de grande qualitĂ©
 
  
−
=== Gérer les données de façon stratégique et responsable ===
+
* 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;
−
* Définir et établir des rÎles, des responsabilités et des responsabilisations clairs pour la gestion des données
+
* Évaluer les initiatives pour dĂ©terminer si les renseignements personnels seront recueillis, utilisĂ©s, communiquĂ©s, conservĂ©s, partagĂ©s et Ă©liminĂ©s;
−
* Cerner et documenter la lignée des actifs de données
+
* Recueillir des renseignements personnels seulement s’ils ont un lien direct avec le fonctionnement des programmes ou des activitĂ©s;
−
* DĂ©finir des calendriers de conservation et d’elimination en fonction de la valeur opĂ©rationnelle ainsi que des politiques et des lois applicables en matiĂšre de sĂ©curitĂ© et de protection de la vie privĂ©e
+
* Informer les personnes des fins de la collecte au point de collecte en incluant un avis de confidentialité;
−
* Veiller Ă  ce que les donnĂ©es soient gĂ©rĂ©es pour permettre, dans la mesure du possible, l’interopĂ©rabilitĂ©, la rĂ©utilisation et l’échange des donnĂ©es au sein des ministĂšres et avec d’autres ministĂšres Ă  l’échelle du gouvernement afin d’éviter le double emploi et de maximiser l’utilitĂ©, tout en respectant les exigences en matiĂšre de sĂ©curitĂ© et de protection des renseignements personnels
+
* 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;
−
* Contribuer et s’aligner sur les structures de classification et de taxonomie des donnĂ©es d’entreprise et internationales pour gĂ©rer, stocker, rechercher et rĂ©cupĂ©rer des donnĂ©es
+
* 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.
  
−
=== Utiliser et partager ouvertement les données de maniÚre éthique et sécurisée ===
 
−
* Communiquer ouvertement les donnĂ©es par dĂ©faut, conformĂ©ment Ă  la Directive sur le gouvernement ouvert et les Normes numĂ©riques du gouvernement du Canada, tout en respectant les normes existantes de l’entreprise et les normes internationales, notamment en matiĂšre de qualitĂ© et d’éthique des donnĂ©es
 
−
* Veiller Ă  ce que le formatage des donnĂ©es soit harmonisĂ© avec les normes d’interopĂ©rabilitĂ© existantes opĂ©rationnelles et sur les normes internationales. Lorsqu’il n’en existe pas, Ă©laborer des normes de donnĂ©es ouvertes avec des experts en la matiĂšre, en consultation avec la CommunautĂ© de pratique des donnĂ©es organisationnelles
 
−
* Éviter le risque d’identification ou de rĂ©identification des donnĂ©es combinĂ©es de renseignements dĂ©licats ou personnels
 
−
</div>
 
  
−
<div style="padding-left: 15px; border-left: 10px solid #f5844e; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19); color: black; background-color: white; font-size:1.2em;">
+
== Architecture d’application ==
−
== [[GC_EA_Playbook#3._Application_Architecture | 3. Architecture des applications]] ==
+
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/ApplicationGuide cliquez ici pour le guide d'architecture d'application] </i></b></br></br>
  
−
=== Utiliser des solutions ouvertes hébergées dans le nuage public ===
+
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.
−
* SĂ©lectionner les solutions existantes qui peuvent ĂȘtre rĂ©utilisĂ©es sur des solutions personnalisĂ©es
 
−
* Contribuer à toutes les améliorations retournées aux communautés
 
−
* Enregistrer les logiciels de source ouverte dans l’Échange de ressources ouvert
 
  
−
=== Utiliser le logiciel comme service (SaaS) hébergé dans le nuage public ===
+
=== Utiliser les solutions de sources ouvertes hébergées dans le nuage public ===
−
* Choisir le SaaS le mieux adaptĂ© Ă  l’utilisation en fonction de l’harmonisation sur les capacitĂ©s du SaaS
 
−
* Choisir une solution SaaS extensible
 
−
* Configurer le SaaS et, si la personnalisation est nécessaire, étendre en tant que modules ouverts
 
  
−
=== Concevoir en visant [https://www.gcpedia.gc.ca/wiki/En/GCinterop l’interopĂ©rabilitĂ©] ===
+
* Choisir des solutions existantes qui peuvent ĂȘtre rĂ©utilisĂ©es plutĂŽt que des solutions personnalisĂ©es;
−
* Concevoir des systÚmes en tant que services hautement modulaires et couplés de maniÚre lùche
+
* Mettre toutes les améliorations à la disposition de la collectivité;
−
* Exposer les services, y compris les services existants, au moyen d’API
+
* Enregistrer les logiciels ouverts dans l’Échange de ressources ouvertes.
−
* Rendre les API accessibles aux intervenants appropriés
 
−
</div>
 
  
−
<div style="padding-left: 15px; border-left: 10px solid #cb6d49; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19); color: black; background-color: white; font-size:1.2em;">
+
=== Utiliser les logiciels sous forme de service (SaaS) hébergés dans le nuage public ===
−
== [[GC_EA_Playbook#4._Technology_Architecture | 4. Architecture de la technologie]] ==
 
  
−
=== Utiliser avant tout le nuage ===
+
* 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;
−
* Adopter l’utilisation des accĂ©lĂ©rateurs du GC pour assurer des contrĂŽles de sĂ©curitĂ© et d’accĂšs appropriĂ©s
+
* Choisir une solution SaaS extensible;
−
* Appliquer cet ordre de prĂ©fĂ©rence : Logiciel en tant que service (SaaS) d’abord, puis Plateforme comme service (PaaS), et enfin Infrastructure comme service (IaaS)
+
* Configurer le SaaS et, s’il faut le personnaliser, l’étendre en tant que module source ouverte.
−
* Adopter des services infonuagiques au moyen des Services de courtage infonuagique de SPC
 
−
* Appliquer cet ordre de prĂ©fĂ©rence : le nuage public d’abord, puis le nuage hybride, puis le nuage privĂ© et, enfin, les solutions sans nuage (sur site).
 
−
* Concevoir en fonction de la mobilitĂ© des nuages et Ă©laborer une stratĂ©gie de sortie pour Ă©viter l’immobilisation des fournisseurs.
 
  
−
=== Concevoir en visant le rendement, la disponibilitĂ© et l’extensibilitĂ© ===
+
=== Conception en vue de l’interopĂ©rabilitĂ© ===
−
* * S’assurer que les dĂ©lais de rĂ©ponse rĂ©pondent aux besoins des utilisateurs et que les services essentiels sont hautement disponibles
 
−
* Appuyer les dĂ©ploiements sans arrĂȘt de service pour les travaux d’entretien prĂ©vus et non prĂ©vus.
 
−
* Utiliser des architectures distribuĂ©es, supposer qu’une dĂ©faillance se produira, traiter les erreurs avec Ă©lĂ©gance et surveiller activement le rendement et le comportement.
 
−
* Mettre en place des architectures qui prennent en charge l’insertion de nouvelles technologies avec une perturbation minimale des programmes et services existants
 
−
* ContrĂŽle de la diversitĂ© technique – systĂšmes de conception basĂ©s sur les technologies et plateformes modernes dĂ©jĂ  utilisĂ©es
 
  
−
=== Suivre les principes DevSecOps ===
+
* 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.
  
−
* Utiliser l’intĂ©gration continue et les dĂ©ploiements continus (IC/DC)
 
−
* S’assurer que des essais automatisĂ©s sont effectuĂ©s pour assurer la sĂ©curitĂ© et les fonctionnalitĂ©s
 
−
* Inclure vos utilisateurs et autres intervenants dans le processus DevSecOps
 
−
</div>
 
  
−
<div style="padding-left: 15px; border-left: 10px solid #996782; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19); color: black; background-color: white; font-size:1.2em;">
+
== Architecture de la technologie ==
−
== [[GC_EA_Playbook#5._Security_Architecture_and_Privacy | 5. Architecture de la sécurité et protection de la vie privée]] ==
+
<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>
  
−
=== Intégrer la sécurité dans le cycle de vie du systÚme, à tous les couches architecturales ===
+
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.
−
* Identify and [https://www.gcpedia.gc.ca/wiki/Security_Categorization_Tool 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 [https://cyber.gc.ca/en/guidance/it-security-risk-management-lifecycle-approach-itsg-33 CCCS’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.
+
=== Utiliser d’abord le nuage ===
−
* 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.
+
* 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 ===
 
=== Assurer un accÚs sécurisé aux systÚmes et aux services ===
−
* Identifier et authentifier les personnes, les processus ou les dispositifs Ă  un niveau d’assurance appropriĂ©, en fonction de rĂŽles clairement dĂ©finis, avant d’accorder l’accĂšs Ă  l’information et aux services. Exploiter les services opĂ©rationnels, comme les solutions d’identitĂ© numĂ©rique de confiance du gouvernement du Canada qui sont appuyĂ©es par le Cadre de confiance pancanadien.
+
 
−
* Limiter les interfaces de service aux entitĂ©s autorisĂ©es (utilisateurs et pĂ©riphĂ©riques), avec des rĂŽles clairement dĂ©finis. Segmenter et sĂ©parer l’information en fonction de son caractĂšre sensible, conformĂ©ment aux ITSG-22 et ITSG-38. Les interfaces de gestion peuvent nĂ©cessiter un niveau de protection accru.
+
* 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>;
−
* Intégration HTTPS pour des connexions Web sécurisées et DMARC pour une sécurité accrue des courriels.
+
* 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;
−
* Établir des interconnexions sĂ©curisĂ©es entre les systĂšmes au moyen d’API sĂ©curisĂ©es ou en exploitant les services de connectivitĂ© informatique hybride gĂ©rĂ©s de maniĂšre centralisĂ©e.
+
* 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 ===
 
=== Maintenir des opérations sécurisées ===
−
* Établir des processus pour maintenir la visibilitĂ© des actifs 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 Ă  l’orientation en matiĂšre de gestion des correctifs du GC.
 
−
* Activer la consignation des Ă©vĂ©nements, conformĂ©ment Ă  l’Orientation sur la journalisation 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 Plan de gestion des Ă©vĂ©nements de cybersĂ©curitĂ© du gouvernement du Canada (PGEC GC) et signaler les incidents au Centre canadien pour la cybersĂ©curitĂ© (CCC).
 
  
−
=== Protection de la vie privée dÚs la conception ===
+
* É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;
−
* Effectuer l’évaluation des facteurs relatifs Ă  la vie privĂ©e (EFVP) pour appuyer les activitĂ©s d’attĂ©nuation des risques lorsque des renseignements personnels sont en jeu
+
* 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;
−
* Effectuer une Évaluation de l’Incidence Algorithmique (EIA) pour appuyer les activitĂ©s d’attĂ©nuation des risques au moment du dĂ©ploiement d’un systĂšme automatisĂ© de prise de dĂ©cisions, conformĂ©ment Ă  la Directive sur la prise de dĂ©cision automatisĂ©e. Pour plus d’informations, consulter ce lien.
+
* É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>.
−
* Mettre en Ɠuvre des mesures de sĂ©curitĂ© pour assurer la protection des renseignements personnels et des donnĂ©es.
+
 
−
* Tenir compte des [https://www.ipc.on.ca/wp-content/uploads/Resources/7foundationalprinciples.pdf sept principes fondamentaux de conception de la protection de la vie privée] (anglais seulement) au moment de la conception de services.
 
−
<div>
 
  
 
</multilang>
 
</multilang>
−
{{OCIO_GCEA_Footer}}
 

Latest revision as of 10:12, 3 February 2023

GC Enterprise Architecture GC Enterprise Architecture Review Board, GC EARB
GC Service & Digital Target Enterprise Architecture When to come
Enterprise Architecture Framework Forward Agenda
Business Capability Model (BCM) Past Sessions
Exemplar and Reference Architectures 10 Things You Need to Know
Enterprise Solutions Governance for Digital Solutions
Working Groups EA and GC EARB Overview – Presentation
Other References


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

Use and share data openly in an ethical and secure manner[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


Retrieved from "https://wiki.gccollab.ca/index.php?title=GC_Enterprise_Architecture/Framework&oldid=89989"