Changes

Jump to navigation Jump to search
no edit summary
Line 31: Line 31:  
<h3><span style="font-size: 1.5em;"> Where to start </span></h3> <br>
 
<h3><span style="font-size: 1.5em;"> Where to start </span></h3> <br>
   −
When department has an idea, a problem or an issue that needs to be addressed, the <b>main</b> question that needs to be answered is that "<b><u>Is it worth it</b></u>?".
+
When department has an idea, a problem or an issue that needs to be addressed, the <b>main</b> question that needs to be answered is that "<b><u>Is it worth it</b>?".
    
To answer this question, department has to:<br><br>
 
To answer this question, department has to:<br><br>
Line 57: Line 57:  
<br><br>
 
<br><br>
   −
<h3><span style="font-size: 1.5em;"> 1. Business Architecture</span></h3> <br>
+
<h2><span style="font-size: 1.5em;"> 1. Business Architecture</span></h2> <br>
    
Business Architecture is where an organization identifies the various services that it needs to provide externally, as well as the various functions it owns or needs to own internally to support their services to the public. In the context of GC Enterprise Business Architecture, this is where the Government of Canada identifies the various departments, the services they provide to Canadians and the functions they owns. <br><br>
 
Business Architecture is where an organization identifies the various services that it needs to provide externally, as well as the various functions it owns or needs to own internally to support their services to the public. In the context of GC Enterprise Business Architecture, this is where the Government of Canada identifies the various departments, the services they provide to Canadians and the functions they owns. <br><br>
   −
<h4><b><u>Fulfill the Government of Canada stakeholder needs</b></u></h4>
+
<h4><b><u>Fulfill the Government of Canada stakeholder needs</b></h4>
 
<br>
 
<br>
   Line 72: Line 72:  
Once the stakeholders are identified, the roles and responsibilities are mapped, and the stakeholder needs are identified and translated into a business service, the department can then model a complete quality end-to-end business service that provides the best digital experience to its users while also maximizing its effectiveness and optimize efficiencies.<br><br>
 
Once the stakeholders are identified, the roles and responsibilities are mapped, and the stakeholder needs are identified and translated into a business service, the department can then model a complete quality end-to-end business service that provides the best digital experience to its users while also maximizing its effectiveness and optimize efficiencies.<br><br>
   −
* <b><I>Clearly identify internal and external stakeholders and their needs for each business service including user centric design </b></I>
+
* <b><I>Clearly identify internal and external stakeholders and their needs for each business service including user centric design </b>
 
To understand their stakeholders, it is recommended for program & project manager to conduct stakeholder analysis and create stakeholder mapping for each service being delivered. Users of a business service can be the Canadian general public (in terms of service the department provides), employees (if the service also applicable to the departmental employees, or if the employees is the one implementing the service), or others. Partners of a business service can be other departments or organizations that consume the departmental service, provide data to the department, or those who are building the system/program with the department. Suppliers of a business service can be the SaaS companies who provide the department with service, vendors, SSC, etc. <br><br>
 
To understand their stakeholders, it is recommended for program & project manager to conduct stakeholder analysis and create stakeholder mapping for each service being delivered. Users of a business service can be the Canadian general public (in terms of service the department provides), employees (if the service also applicable to the departmental employees, or if the employees is the one implementing the service), or others. Partners of a business service can be other departments or organizations that consume the departmental service, provide data to the department, or those who are building the system/program with the department. Suppliers of a business service can be the SaaS companies who provide the department with service, vendors, SSC, etc. <br><br>
   Line 102: Line 102:  
Once the stakeholders have been clearly identified, we would need to do some research into what their needs are. Remember, some stakeholders may not know what their needs are, or they may not be able to articulate their needs are. Thus, it would be the responsibilities of a project or program manager to conduct needs based analysis. This may sounds like a lot of work, and it may be is, however, it is a very important step to be carried out as it will provide an understanding of what kind of service is actually required, how effective the current service is, how to improve the delivery of the service so that it will be more useful - more effective. To do this correctly we need feedback from the right stakeholders to create a good design that is easy to use and works well. This method is called user centric design.<br><br>
 
Once the stakeholders have been clearly identified, we would need to do some research into what their needs are. Remember, some stakeholders may not know what their needs are, or they may not be able to articulate their needs are. Thus, it would be the responsibilities of a project or program manager to conduct needs based analysis. This may sounds like a lot of work, and it may be is, however, it is a very important step to be carried out as it will provide an understanding of what kind of service is actually required, how effective the current service is, how to improve the delivery of the service so that it will be more useful - more effective. To do this correctly we need feedback from the right stakeholders to create a good design that is easy to use and works well. This method is called user centric design.<br><br>
   −
* <b><I>Include policy requirement applying to specific stakeholder groups, such as accessibilities, gender based+ analysis, and official languages in the creation of the service </b></I>
+
* <b><I>Include policy requirement applying to specific stakeholder groups, such as accessibilities, gender based+ analysis, and official languages in the creation of the service </b>
    
In identifying the stakeholder, department needs to ensure that it is being inclusive and includes all stakeholder groups. Things to consider when designing a business service are accessibilities, official languages and gender based+ analysis to ensure the business service created will be comprehensive to all stakeholder groups. They are important to be considered as these stakeholders have specific requirements that need to be met as well.<br><br>
 
In identifying the stakeholder, department needs to ensure that it is being inclusive and includes all stakeholder groups. Things to consider when designing a business service are accessibilities, official languages and gender based+ analysis to ensure the business service created will be comprehensive to all stakeholder groups. They are important to be considered as these stakeholders have specific requirements that need to be met as well.<br><br>
Line 135: Line 135:  
<br><br>
 
<br><br>
   −
* <b><I>Model end-to-end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels (e.g lean process)</b></I>
+
* <b><I>Model end-to-end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels (e.g lean process)</b>
    
Modeling business service delivery end-to-end will provide better digital experience to the stakeholders. It will also help provide better understanding of what components are required to create a service, what various channels which a service can be delivered, as well as individual areas that can be improved to maximize effectiveness and optimize efficiencies of the overall service. Modeling end-to-end business service delivery will expand the horizon and knowledge of the implementer of the business service and will ensure each part of the service delivery and its impact to the service are considered. <br><br>
 
Modeling business service delivery end-to-end will provide better digital experience to the stakeholders. It will also help provide better understanding of what components are required to create a service, what various channels which a service can be delivered, as well as individual areas that can be improved to maximize effectiveness and optimize efficiencies of the overall service. Modeling end-to-end business service delivery will expand the horizon and knowledge of the implementer of the business service and will ensure each part of the service delivery and its impact to the service are considered. <br><br>
Line 152: Line 152:  
<br><br>
 
<br><br>
   −
<h4><b><u>Architect to be Outcome Driven and Strategically Aligned to the Department and to the Government of Canada</b></u></h4>
+
<h4><b><u>Architect to be Outcome Driven and Strategically Aligned to the Department and to the Government of Canada</b></h4>
    
The whole notion of creating a program or project is to support departmental mandate. Thus, it needs to be clear what mandate a program or project is supporting, how the outcome of the program or project supports the mandate and measure how effective it is in supporting the mandate. The mandate can be broken down into Strategic Outcomes. A project or program may indirectly support a mandate, however, the derivative outcome it produces may still be able to be tied into one of the strategic outcomes which support departmental mandate. Everything needs to be tied in to the mandate, or one of the strategic outcomes, and everything needs to be measurable. If a department is not sure how a program or project is supporting its mandate or its strategic outcome, or how it can be measured, then perhaps the program or project may not be required to begin with.
 
The whole notion of creating a program or project is to support departmental mandate. Thus, it needs to be clear what mandate a program or project is supporting, how the outcome of the program or project supports the mandate and measure how effective it is in supporting the mandate. The mandate can be broken down into Strategic Outcomes. A project or program may indirectly support a mandate, however, the derivative outcome it produces may still be able to be tied into one of the strategic outcomes which support departmental mandate. Everything needs to be tied in to the mandate, or one of the strategic outcomes, and everything needs to be measurable. If a department is not sure how a program or project is supporting its mandate or its strategic outcome, or how it can be measured, then perhaps the program or project may not be required to begin with.
Line 178: Line 178:  
<br><br>
 
<br><br>
   −
* <b><I>Identify which departmental/GC business services, outcomes and strategies will be addressed </b></I>
+
* <b><I>Identify which departmental/GC business services, outcomes and strategies will be addressed </b>
    
In order to ensure a program or project supports departmental mandate, it is important to identify which services, outcomes or strategies will be addressed at the conclusion of the program or project. This will ensure the program or project has a vision of what it is trying to accomplish in relation to the departmental mandate. Thus, whenever the program or project needs to do a small deviation from its original short-term goal, it will have a limit on how much it can deviate before it is no longer provide an outcome that is aligned to the departmental mandate or GC direction. <br><br>
 
In order to ensure a program or project supports departmental mandate, it is important to identify which services, outcomes or strategies will be addressed at the conclusion of the program or project. This will ensure the program or project has a vision of what it is trying to accomplish in relation to the departmental mandate. Thus, whenever the program or project needs to do a small deviation from its original short-term goal, it will have a limit on how much it can deviate before it is no longer provide an outcome that is aligned to the departmental mandate or GC direction. <br><br>
   −
* <b><I>Establish metrics for identified business outcomes throughout the lifecycle of an investment</b></I>
+
* <b><I>Establish metrics for identified business outcomes throughout the lifecycle of an investment</b>
    
Another important aspect to ensure alignment to departmental mandate is establishing the metrics for the identified business outcomes. This will ensure department have a way to identify its efficiencies or effectiveness in delivering the business services. As technology progresses, the outcomes that was once achieved by the program or project may become invalid or insufficient to support the departmental mandate or GC Direction. At this time, it would be prudent to re-visit the effectiveness of the program or project and explore possibility of leveraging other existing service created by other department or creating a new project or program. <br><br>
 
Another important aspect to ensure alignment to departmental mandate is establishing the metrics for the identified business outcomes. This will ensure department have a way to identify its efficiencies or effectiveness in delivering the business services. As technology progresses, the outcomes that was once achieved by the program or project may become invalid or insufficient to support the departmental mandate or GC Direction. At this time, it would be prudent to re-visit the effectiveness of the program or project and explore possibility of leveraging other existing service created by other department or creating a new project or program. <br><br>
   −
* <b><I>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</b></I>
+
* <b><I>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</b>
    
One benefit of translating business outcomes and strategy into business capabilities is to provide a common ground between business community and IT community. Once a common ground is reached, it would be easier to communicate what can be achieved, and how much tolerance can a program or project deviates from its short-term goal. <br><br>
 
One benefit of translating business outcomes and strategy into business capabilities is to provide a common ground between business community and IT community. Once a common ground is reached, it would be easier to communicate what can be achieved, and how much tolerance can a program or project deviates from its short-term goal. <br><br>
   −
<h4><b><u> Promote Horizontal Enablement of the Enterprise</b></u></h4>
+
<h4><b><u> Promote Horizontal Enablement of the Enterprise</b></h4>
    
By having a common business capability terminology, it becomes easier to figure out if one solution is essentially a duplicate of another solution. It also becomes easier to find out if a department has obtained a solution to enable a business capability, and thus, the same solution may be leveraged to solve similar problem in another department. This horizontal enablement across departments would support reduction in IT spending through achieving economy of scale in procuring the same licenses. It would also support better collaboration between departments and easier data exchange.
 
By having a common business capability terminology, it becomes easier to figure out if one solution is essentially a duplicate of another solution. It also becomes easier to find out if a department has obtained a solution to enable a business capability, and thus, the same solution may be leveraged to solve similar problem in another department. This horizontal enablement across departments would support reduction in IT spending through achieving economy of scale in procuring the same licenses. It would also support better collaboration between departments and easier data exchange.
      −
* <b><I>Identify opportunities to horizontally enabled business services and provide cohesive experience to stakeholders</b></I>
+
* <b><I>Identify opportunities to horizontally enabled business services and provide cohesive experience to stakeholders</b>
         −
* <b><I>Reuse common business capabilities and processes from across government and private sector</b></I>
+
* <b><I>Reuse common business capabilities and processes from across government and private sector</b>
      −
* <b><I>Publish in the open reusable common business capabilities and processes (in the Open Government portal) for others to develop cohesive horizontal enterprise services</b></I>
+
* <b><I>Publish in the open reusable common business capabilities and processes (in the Open Government portal) for others to develop cohesive horizontal enterprise services</b>
      −
<h3><span style="font-size: 1.5em;">2. Information Architecture</span></h3>
+
<h2><span style="font-size: 1.5em;">2. Information Architecture</span></h2>
    
<!-- COLUMN 1 ENDS: -->
 
<!-- COLUMN 1 ENDS: -->
Line 233: Line 233:  
<h4><b><u>Use and share data openly in an ethical and secure manner</u></b></h4>''Section under development'' (ESP/Bitar)
 
<h4><b><u>Use and share data openly in an ethical and secure manner</u></b></h4>''Section under development'' (ESP/Bitar)
   −
<h3><span style="font-size: 1.5em;">3. Application Architecture</span></h3> <br><br>
+
<h2><span style="font-size: 1.5em;">3. Application Architecture</span></h2> <br><br>
    
Application Architecture consists of understanding and designing the various applications within a department, how they tie in to the business service supporting the departmental mandate, where they are located in the architecture landscape of the department as well as the GC, how they interact with each other and with their users, the zoning requirements, etc. Application Architecture focuses less on internal mechanics and specific programming and more on overall design on how data is consumed and created by the system. It views the interactions between applications, databases, middleware to ensure scalability, reliability, availability and manageability. <br><br>
 
Application Architecture consists of understanding and designing the various applications within a department, how they tie in to the business service supporting the departmental mandate, where they are located in the architecture landscape of the department as well as the GC, how they interact with each other and with their users, the zoning requirements, etc. Application Architecture focuses less on internal mechanics and specific programming and more on overall design on how data is consumed and created by the system. It views the interactions between applications, databases, middleware to ensure scalability, reliability, availability and manageability. <br><br>
   −
<h4><b><u>Use Open Source Solutions hosted in Public Cloud</b></u></h4><br>
+
<h4><b><u>Use Open Source Solutions hosted in Public Cloud</b></h4><br>
    
While Open Source Solution (OSS) is not a silver bullet, several common misconceptions are used as arguments against Open Source software: A misconception with security is that with the code out of the eyes of the public that it prevents successful attacks and lowers liability, however in reality Security Best practices state that 'System security should not depend on the secrecy of the implementation or its components', and as Open Source development relies and hardening (or improving the security) of code it is often equal or more secure then proprietary solutions.
 
While Open Source Solution (OSS) is not a silver bullet, several common misconceptions are used as arguments against Open Source software: A misconception with security is that with the code out of the eyes of the public that it prevents successful attacks and lowers liability, however in reality Security Best practices state that 'System security should not depend on the secrecy of the implementation or its components', and as Open Source development relies and hardening (or improving the security) of code it is often equal or more secure then proprietary solutions.
Line 244: Line 244:  
For more info on Open Source, go to the GC webpage on [https://www.canada.ca/en/government/system/digital-government/open-source-software.html Open Source Software]. <br><br>
 
For more info on Open Source, go to the GC webpage on [https://www.canada.ca/en/government/system/digital-government/open-source-software.html Open Source Software]. <br><br>
   −
*<b><I> Select existing solutions that can be reused over custom built</b></I>
+
*<b><I> Select existing solutions that can be reused over custom built</b>
    
It is important to reduce the duplication of effort that has occurred due to segmented mandates, and increase collaboration and sharing across Departments and Agencies. Crown Corporations, Provincial and Municipal Governments as well as the Public at large who can benefit from new and innovative products and services based off of creations from the Government.<br><br>
 
It is important to reduce the duplication of effort that has occurred due to segmented mandates, and increase collaboration and sharing across Departments and Agencies. Crown Corporations, Provincial and Municipal Governments as well as the Public at large who can benefit from new and innovative products and services based off of creations from the Government.<br><br>
   −
*<b><I> Contribute all improvements back to the communities</b></I>
+
*<b><I> Contribute all improvements back to the communities</b>
    
Major benefits can occur not just from publishing the Software, but in developing Guidance the quality of software increases, while publishing Lessons Learned, White Papers and any other technical documentation can assist others in the future by providing templates and baselines.
 
Major benefits can occur not just from publishing the Software, but in developing Guidance the quality of software increases, while publishing Lessons Learned, White Papers and any other technical documentation can assist others in the future by providing templates and baselines.
Line 256: Line 256:  
Setting up shared teams for common problems where Developers from multiple departments can produce better solutions. Virtual Teams using open tools can enable rapid development in absence of collocation.<br><br>
 
Setting up shared teams for common problems where Developers from multiple departments can produce better solutions. Virtual Teams using open tools can enable rapid development in absence of collocation.<br><br>
   −
*<b><I> Register Open Source software to the [https://canada-ca.github.io/ore-ero/en/index.html Open Resource Exchange]</b></I>
+
*<b><I> Register Open Source software to the [https://canada-ca.github.io/ore-ero/en/index.html Open Resource Exchange]</b>
    
Scientific Innovation can occur from exposing Data to interested members of the activists, researchers, students and the public at large.
 
Scientific Innovation can occur from exposing Data to interested members of the activists, researchers, students and the public at large.
Line 264: Line 264:  
<br>
 
<br>
   −
<h4><b><u>Use Software as a Service (SaaS) hosted in Public Cloud</b></u></h4>
+
<h4><b><u>Use Software as a Service (SaaS) hosted in Public Cloud</b></h4>
* <b><I>Choose SaaS that best fit for purpose based on alignment with SaaS capabilities </b></I><br>  
+
* <b><I>Choose SaaS that best fit for purpose based on alignment with SaaS capabilities </b><br>  
* <b><I>Choose a SaaS solution that is extendable </b></I><br>
+
* <b><I>Choose a SaaS solution that is extendable </b><br>
* <b><I>Configure SaaS and if customization is necessary extend as Open Source modules </b></I><br>
+
* <b><I>Configure SaaS and if customization is necessary extend as Open Source modules </b><br>
 
<br>
 
<br>
   −
<h4><b><u>Design for [https://www.gcpedia.gc.ca/wiki/En/GCinterop Interoperability]</b></u></h4>
+
<h4><b><u>Design for [https://www.gcpedia.gc.ca/wiki/En/GCinterop Interoperability]</b></h4>
    
As the GC is transitioning to new technology and as more departments start to work together, interoperability becomes a key important factor in ensuring stability and continuity of a program. Self-discipline must be instilled to always publish and maintain API so that other systems or other departments can make use and leverage the work that is already done without duplication of work and re-inventing the wheel. It can also maintain precious data flow that has previously obtained from legacy system.
 
As the GC is transitioning to new technology and as more departments start to work together, interoperability becomes a key important factor in ensuring stability and continuity of a program. Self-discipline must be instilled to always publish and maintain API so that other systems or other departments can make use and leverage the work that is already done without duplication of work and re-inventing the wheel. It can also maintain precious data flow that has previously obtained from legacy system.
Line 276: Line 276:  
The most important use of interoperability is it provides the ability to communicate between one system to another without the need of manual intervention. It doesn't matter if one system is built with one platform, eg. UNIX/LINUX, and the other system is built with another platform, eg. Windows, "OR" if one system is legacy, eg. Mainframe, and the other is an innovative product, eg. machine learning. With interoperability, these different systems can communicate with one another, thereby enabling efficiency and/or effectiveness of a solution. Interoperability can also enable easier communication between one department to another, thereby creating better collaboration and automation exchange of data.<br><br>
 
The most important use of interoperability is it provides the ability to communicate between one system to another without the need of manual intervention. It doesn't matter if one system is built with one platform, eg. UNIX/LINUX, and the other system is built with another platform, eg. Windows, "OR" if one system is legacy, eg. Mainframe, and the other is an innovative product, eg. machine learning. With interoperability, these different systems can communicate with one another, thereby enabling efficiency and/or effectiveness of a solution. Interoperability can also enable easier communication between one department to another, thereby creating better collaboration and automation exchange of data.<br><br>
   −
* <b><I>Design systems as highly modular and loosely coupled services</b></I><br>
+
* <b><I>Design systems as highly modular and loosely coupled services</b><br>
    
A good system design starts from building a small simple independent function. Focus on smallest unit of purpose, and develop a single function. The small single function can then become a building block for a larger more complicated function, and be combined with other simple functions to finally create a service. Having a simple independent function also means that it be reused to create another complicated function. Thus, it is very important to build a function that is small and simple enough to make it highly modular.  
 
A good system design starts from building a small simple independent function. Focus on smallest unit of purpose, and develop a single function. The small single function can then become a building block for a larger more complicated function, and be combined with other simple functions to finally create a service. Having a simple independent function also means that it be reused to create another complicated function. Thus, it is very important to build a function that is small and simple enough to make it highly modular.  
Line 285: Line 285:  
<br><br>
 
<br><br>
   −
* <b><I>Expose services through APIs </b></I>
+
* <b><I>Expose services through APIs </b>
    
Do not hide services under assumptions that someone would not find value in a service - often innovation can be bred from exposed services beyond it's original plan.
 
Do not hide services under assumptions that someone would not find value in a service - often innovation can be bred from exposed services beyond it's original plan.
Line 292: Line 292:  
<br><br>
 
<br><br>
   −
* <b><I>Make the APIs discoverable to the appropriate stakeholders</b></I>
+
* <b><I>Make the APIs discoverable to the appropriate stakeholders</b>
    
When a system have an API that is discoverable, it opens up its window to the world of endless possibilities, collaboration and better outcomes for the whole GC. One way to make an API discoverable is by publishing it to the [https://api.canada.ca/en/homepage#all-apis API Store] and the future DxP (Digital Exchange Platform).
 
When a system have an API that is discoverable, it opens up its window to the world of endless possibilities, collaboration and better outcomes for the whole GC. One way to make an API discoverable is by publishing it to the [https://api.canada.ca/en/homepage#all-apis API Store] and the future DxP (Digital Exchange Platform).
 
<br><br>
 
<br><br>
   −
<h4><b><u>Follow [https://www.devsecops.org/blog/2015/2/15/what-is-devsecops DevSecOps] Principles</b></u></h4>
+
<h4><b><u>Follow [https://www.devsecops.org/blog/2015/2/15/what-is-devsecops DevSecOps] Principles</b></h4>
 
The purpose and intent of DevSecOps is to build on the mindset that "everyone is responsible for security" with the goal of safely distributing security decisions at speed and scale to those who hold the highest level of context without sacrificing the safety required.  
 
The purpose and intent of DevSecOps is to build on the mindset that "everyone is responsible for security" with the goal of safely distributing security decisions at speed and scale to those who hold the highest level of context without sacrificing the safety required.  
 
<br><br>
 
<br><br>
Line 317: Line 317:       −
* <b><I>Use continuous integration and continuous deployments (CI/CD)</b></I>
+
* <b><I>Use continuous integration and continuous deployments (CI/CD)</b>
* <b><I>Ensure automated testing occurs for security and functionality </b></I>
+
* <b><I>Ensure automated testing occurs for security and functionality </b>
* <b><I>Include your stakeholders as part of DevSecOps process</b></I>
+
* <b><I>Include your stakeholders as part of DevSecOps process</b>
      −
<h3><span style="font-size: 1.5em;">4. Technology Architecture</span></h3> <br><br>
+
<h2><span style="font-size: 1.5em;">4. Technology Architecture</span></h2> <br><br>
    
<h4><b>Use Cloud first</b></h4>
 
<h4><b>Use Cloud first</b></h4>
Line 340: Line 340:       −
<h3><span style="font-size: 1.5em;">5. Security and Privacy Architecture</span></h3> <br><br>
+
<h2><span style="font-size: 1.5em;">5. Security Architecture</span></h2>
   −
<h4><b>Build Security into the Full System Life Cycle, Across All Architectural Layers</b></h4>
+
=== Overview of the GC Enterprise Security Architecture (ESA) Program ===
* Identify and classify risks associated to the service’s business objectives, goals, and strategy
+
The GC ESA 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. The image on the right shows how the GC ESA program supports the direction the GC is taking with regards to GC IT security.
* Design security measures according to business and user needs, risks identified, and security categorization of the information and assets; integrate security across all architectural layers (BIAT)
  −
** Maintain focus on users’ ease of use through selection of context-appropriate controls
  −
** Apply an information-centric approach to reduce resources’ exposure to threats, and minimize the opportunity for compromise.  
  −
** Protect data while in transit, in use and at rest using appropriate encryption and protocols. Ensure effective disposition of data per retention schedules, following service sunset.
     −
* Design systems to not be susceptible to common security vulnerabilities; resilient and can be rebuilt quickly in the event of compromise; and fail secure if the system encounters an error or crashes
+
The GC ESA program aims to:
* Reduce human intervention and maximize automation of security tasks and processes
+
 
** Integrate and automate security testing to validate code and address vulnerabilities prior to deployments
+
·       Ensure more cost-effective, interoperable, resilient and secure IT solutions in support of GC enterprise objectives;
<br>
+
 
 +
·       Maintain availability of GC systems and services while complying with relevant GC legislation and policy instruments;
 +
 
 +
·       Adopt an architecture methodology and approach to ensure common understanding, alignment, and reduce duplication of effort amongst interdepartmental stakeholders;
   −
<h4><b>Ensure Secure Access to Systems and Services</b></h4>
+
·       Ensure security of information, IT infrastructure and applications with the implementation of consistent security controls which reduces total cost of ownership; and
* Identify and authenticate individuals, processes and/or devices to an appropriate level of assurance before granting access to information and services
  −
* Separate and compartmentalize user responsibilities and privileges; assign the least set of privileges necessary to complete the job
  −
* Constrain service interfaces to authorized entities (users and devices), with clearly defined roles, and only expose the interfaces necessary to operate the service
  −
* Make use of modern password guidance, and use GC-approved multi-factor authentication where required to stop unauthorized access
  −
(prioritize length over complexity, eliminating expiry, and blacklisting common passwords)
  −
<br><br>
     −
<h4><b>Maintain Secure Operations</b></h4>
+
·       Keep risk at acceptable levels.
* Integrate aggregate outputs from security assessment and authorization activities into security architecture lifecycle processes, to ensure reference artefacts remain relevant and valid
  −
* Continuously monitor system events and performance in order to detect, prevent, and respond to attacks
  −
* Design processes to operate and manage services securely, and establish processes and mechanisms to respond effectively to security events
  −
** Collect transaction logs at infrastructure and application levels to support automated root-cause analysis and performance tuning
  −
** Include an audit function in information systems. Use a trusted time source and protect audit logs from manipulation
  −
* Establish processes to monitor security advisories, and apply security-related patches and updates to reduce exposure to vulnerabilities. Apply appropriate risk-based mitigations when patches can’t be applied
  −
<br>
     −
<h4><b> Privacy by Design </b></h4>
+
The GC ESA program will serve as a guide to departments and agencies in planning, implementing, and operating their information systems by offering the necessary framework, tools, and templates to design, evaluate, and build an IT security architecture tailored to their organization, in accordance with Communications Security Establishment’s (CSE) ITSG-33 – IT Security Risk Management: A Lifecycle Approach and other security industry best practices in the area of architecture, risk management and compliance.
* Perform a privacy impact assessment (PIA) to support risk mitigation activities when personal information is involved
  −
* Perform [https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/responsible-use-ai/algorithmic-impact-assessment.html Algorithmic Impact Assessment (AIA)] to support risk mitigation activities when deploying an automated decision system
  −
* Implement security measures to assure the protection of personal information
  −
* Take into consideration the <b>[https://www.ryerson.ca/pbdce/certification/seven-foundational-principles-of-privacy-by-design/ 7 Foundational Privacy Design Principles] </b> when designing services
     −
<!-- FOOTER -->{| width="100%" cellpadding="10"  
+
{| width="100%" cellpadding="10"  
    
|- valign="top"
 
|- valign="top"

Navigation menu

GCwiki