586
edits
Changes
Jump to navigation
Jump to search
Line 265:
Line 265: − + − + − + Line 276:
Line 276: − + Line 358:
Line 358: + + + + + + + + + + + + + + +
GC Enterprise Architecture/Playbook (view source)
Revision as of 09:21, 23 September 2020
, 09:21, 23 September 2020no edit summary
<h4><b><u>Use Software as a Service (SaaS) hosted in Public Cloud</b></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><br>
* <I><b>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><br>
* <I><b>Choose a SaaS solution that is extendable </b><br>
* <b><I>Configure SaaS and if customization is necessary extend as Open Source modules </b><br>
* <I><b>Configure SaaS and if customization is necessary extend as Open Source modules </b><br>
<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>
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><br>
* <I><b>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.
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.
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.
A lot more information can be found here:
· [https://www.gcpedia.gc.ca/wiki/Government_of_Canada_Enterprise_Security_Architecture_(ESA)_Program; Government of Canada Enterprise Security Architecture (ESA) Program] and here:
· [https://www.gcpedia.gc.ca/gcwiki/images/a/ac/GC_ESA_Description_Document_%28ESADD%29_-_Main_Body.pdf GC ESA Description Document Main Body -- Synopsis]
Additional ESA initiatives can be found by clicking on the embedded link for:
• GC Cloud Reference Architecture;
• [https://www.gcpedia.gc.ca/gcwiki/images/8/86/GC_Zero_Trust_Reference_Architecture.pdf DRAFT GC Zero Trust Security Reference Architecture];
• [https://www.gcpedia.gc.ca/wiki/ESA_Initiatives Many other ESA Initiatives]
{| width="100%" cellpadding="10"
{| width="100%" cellpadding="10"
