Line 102: |
Line 102: |
| Security architecture and privacy has always been an important but often poorly addressed aspect of solution design. However, for the successful implementation of the GC Enterprise Ecosystem Target Architecture depends on a proper security architectural implementation. Legacy systems based on monolithic architectures often had simplistic approaches to mitigating security risks. The future digitally enabled GC services will support a diverse community and have interoperating components spread across multiple environments. It is critical that security be built in to all processes and across all architectural layers. | | Security architecture and privacy has always been an important but often poorly addressed aspect of solution design. However, for the successful implementation of the GC Enterprise Ecosystem Target Architecture depends on a proper security architectural implementation. Legacy systems based on monolithic architectures often had simplistic approaches to mitigating security risks. The future digitally enabled GC services will support a diverse community and have interoperating components spread across multiple environments. It is critical that security be built in to all processes and across all architectural layers. |
| | | |
| + | === Build Security into the System Life Cycle, Across All Architectural Layers === |
| + | * 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 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 === |
| + | * 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 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 DMARC for enhanced email security. |
| + | * Establish secure interconnections between systems through secure 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 GC Cyber Security Event Management Plan (GC CSEMP) and report incidents to the Canadian Centre for Cyber Security (CCCS). |
| + | |
| + | === Privacy by Design === |
| + | * Perform Privacy Impact Assessment (PIA) to support risk mitigation activities when personal information is involved |
| + | * Perform Algorithmic Impact Assessment (AIA) to support risk mitigation activities when deploying an automated decision system as per Directive on Automated Decision Making. For more info, please go to this link |
| + | * Implement security measures to assure the protection of personal information and data |
| + | * Take into consideration the 7 Foundational Privacy Design Principles (English only) when designing services |
| <multilang> | | <multilang> |
| @en|__NOTOC__ | | @en|__NOTOC__ |