Line 1: |
Line 1: |
| {{OCIO_GCEA_Header}} | | {{OCIO_GCEA_Header}} |
| | | |
− | <i><big> This is a <b><u>DRAFT COPY</u></b> of the proposed GC EA Playbook. It is a work IN PROGRESS, and has not undergone any review. </big></i> | + | <i><big> This is a <b><u>DRAFT COPY</u></b> of the proposed GC EA Playbook. It is outdated, a work IN PROGRESS, and has not undergone any review. </big></i> |
| <br> | | <br> |
| | | |
Line 340: |
Line 340: |
| | | |
| | | |
− | <h3><span style="font-size: 1.5em;">Security Architecture</span></h3> <br><br> | + | <h2><span style="font-size: 1.5em;">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 === |
| + | 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. |
| + | |
| + | The GC ESA program aims to: |
| + | * Ensure more cost-effective, interoperable, resilient and secure IT solutions in support of GC enterprise objectives; |
| + | * 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; |
| + | * Ensure security of information, IT infrastructure and applications with the implementation of consistent security controls which reduces total cost of ownership; and |
| + | * Keep risk at acceptable levels. |
| + | 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: |
| + | |
| + | · Government of Canada Enterprise Security Architecture (ESA) Program and here: |
| + | |
| + | · GC ESA Description Document Main Body -- Synopsis<br><br><h4><b>Build Security into the Full System Life Cycle, Across All Architectural Layers</b></h4> |
| * Identify and classify risks associated to the service’s business objectives, goals, and strategy | | * Identify and classify risks associated to the service’s business objectives, goals, and strategy |
| * 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) | | * 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) |