Difference between revisions of "GC Enterprise Architecture/Framework/SecurityGuide"
Jump to navigation
Jump to search
m |
|||
(8 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | + | {{OCIO GCEA Header}} | |
− | |||
<multilang> | <multilang> | ||
− | @en| | + | @en|__TOC__ |
== Security architecture == | == Security architecture == | ||
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. | 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 === | === 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 ==== | ||
+ | |||
+ | ===== How to achieve: ===== | ||
+ | |||
+ | * Summarize how the architecture ensures the confidentiality of the information based on its categorization and degree of injury | ||
+ | * Summarize how the architecture ensures the integrity of the information based on its categorization and degree of injury | ||
+ | * Summarize how the architecture ensures the availability of the information based on its categorization and degree of injury | ||
+ | |||
+ | |||
+ | ==== 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 ==== | ||
− | + | ===== How to achieve: ===== | |
− | |||
− | |||
+ | * Summarize how the architecture aligns with the Centre of Cyber Security’s IT Security Risk Management Framework | ||
− | |||
− | |||
− | |||
− | |||
− | + | ==== apply proportionate security measures that address business and user needs while adequately protecting data at rest and data in transit ==== | |
− | |||
− | |||
− | |||
− | |||
− | |||
+ | ===== How to achieve: ===== | ||
+ | |||
+ | * Describe the security measures that protect the data at rest while meeting business and users needs | ||
+ | * Describe the security measures that protect the data in transit while meeting business and users needs | ||
+ | |||
+ | ==== design systems to be resilient and available in order to support service continuity ==== | ||
+ | ===== How to achieve: ===== | ||
+ | |||
+ | * Outline the architecture’s resilient characteristics support service continuity objectives | ||
+ | * Outline the architecture’s availability characteristics support service continuity objectives | ||
+ | |||
+ | ===== Tools: ===== | ||
+ | |||
+ | * Non-functional Requirements | ||
=== Ensure secure access to systems and services === | === 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> ==== | |
− | |||
− | |||
− | + | ===== How to achieve: ===== | |
− | + | * Summarize how the architectures identifies and authenticates: | |
− | + | ** Individuals | |
− | + | ** Processes | |
− | + | ** Devices | |
+ | * Summarize the enterprise security services leverage by the architecture | ||
+ | * Summarize how the architecture aligns to the Pan-Canadian Trust Framework | ||
− | + | ===== Tools: ===== | |
− | |||
− | |||
− | |||
+ | * Target State Architecture | ||
+ | * Interim State Architecture | ||
− | + | ==== 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 ==== | |
− | |||
− | |||
− | + | ===== How to achieve: ===== | |
− | + | ||
− | + | * Summarize how the architecture constrains service interfaces to authorized entities in compliance to: | |
+ | ** ITSG-22, and; | ||
+ | ** ITSG-38. | ||
+ | |||
+ | ==== 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 ==== | ||
+ | |||
+ | ===== How to achieve: ===== | ||
+ | |||
+ | * Does the architecture use HTTPS for secure web connections | ||
+ | * Does the architecture use and Domain-based Message Authentication, Reporting and Conformance (DMARC) 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 ==== | ||
+ | |||
+ | ===== How to achieve: ===== | ||
+ | |||
+ | * Outline what (APIs or centrally managed hybrid IT connectivity services )the architectures established secure interconnections between systems | ||
+ | |||
+ | ===== Tools: ===== | ||
+ | |||
+ | * Target State Architecture | ||
+ | * Interim State Architecture | ||
=== Maintain secure operations === | === 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'' ==== | ||
+ | |||
+ | ===== How to achieve: ===== | ||
+ | |||
+ | * Have processes been established to ensure the prompt application of security related patches and updates? | ||
+ | * Summarize how the architecture supports these processes | ||
+ | |||
+ | |||
+ | ==== 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 ==== | ||
+ | |||
+ | ===== How to achieve: ===== | ||
+ | |||
+ | * Summarize how event logging within the architecture aligns to GC Event Logging Guidance in the areas of: | ||
+ | ** Attack detection | ||
+ | ** Attack prevention | ||
+ | ** Attack respond | ||
+ | |||
+ | ==== 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> ==== | ||
+ | |||
+ | ===== How to achieve: ===== | ||
+ | |||
+ | * Describe how incident management plan aligns to GC Cyber Security Event Management | ||
+ | * Describe how incidents are reported to the Canadian Centre for Cyber Security (CCSB) | ||
+ | |||
+ | |||
+ | @fr|__TOC__ | ||
+ | |||
+ | |||
+ | == ARCHITECTURE DE SÉCURITÉ == | ||
+ | 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. | ||
+ | |||
+ | Vous trouverez plus d’informations sur l’architecture de sécurité d’entreprise GC sur le [https://www.gcpedia.gc.ca/wiki/GC_ESA_Artifact_Repository?setlang=fr&uselang=fr référentiel d’artefacts GC ESA] | ||
+ | |||
+ | === 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> 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é ==== | ||
+ | |||
+ | <b> Comment y parvenir: </b> | ||
+ | * Résumer comment l'architecture assure la confidentialité des information en fonction de leur categorization et du degré de blessure | ||
+ | * Résumer comment l'architecture assure l'intégrite de l'information en fonction de leur categorization et du degré de blessure | ||
+ | * Résumer comment l'architecture assure la disponibilité de l'information en fonction de leur categorization et du degré de blessure | ||
+ | |||
+ | ==== Mettre en place une approche de sécurité continue, conformément au <u>[https://cyber.gc.ca/en/guidance/it-security-risk-management-lifecycle-approach-itsg-33 Cadre de gestion des risques liés à la sécurité des TI du CCC]</u>; 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 ==== | ||
+ | |||
+ | <b> Comment y parvenir: </b> | ||
+ | * Résumer comment l'architecture s'aligne avec le cadre de gestion des risques de sécurité informatique du Center of Cyber Security | ||
+ | |||
+ | ==== 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 ==== | ||
+ | |||
+ | <b> Comment y parvenir: </b> | ||
+ | * Décrire les mesures de sécurité qui protègent les données au repos tout en répondant aux besoins des entreprises et des utilisateurs | ||
+ | * Décrire les mesures de sécurité qui protègent les données en transit tout en répondant aux besoins des entreprises et des utilisateurs | ||
+ | |||
+ | ===== Concevoir des systèmes résilients et disponibles pour soutenir la continuité de la prestation du service ===== | ||
+ | |||
+ | <b> Comment y parvenir: </b> | ||
+ | * Décrire les caractéristiques résilientes de l'architecture pour soutenir les objectifs de continuité de service | ||
+ | * Décrire les caractéristiques de disponibilité de l'architecture pour soutenir les objectifs de continuité de service | ||
+ | |||
+ | Outils : | ||
+ | * Prérogatives non fonctionnelles | ||
+ | |||
+ | === Assurer un accès sécurisé aux systèmes et aux services === | ||
+ | |||
+ | ==== 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 Cadre de confiance pan canadien ==== | ||
+ | |||
+ | <b> Comment y parvenir: </b> | ||
+ | * Résumer comment les architectures identifient et authentifient : | ||
+ | ** Personnes | ||
+ | ** Processus | ||
+ | ** Dispositifs | ||
+ | * Résumer les services de sécurité d'entreprise tirés par l'architecture | ||
+ | * Résumer comment l'architecture s'aligne sur le cadre de confiance pan canadien | ||
+ | |||
+ | Outils: | ||
+ | * Architecture d'état cible | ||
+ | * Architecture d'État intérimaire | ||
+ | |||
+ | ==== 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 LDSTI-22 et LDSTI-38. Les interfaces de gestion peuvent nécessiter des niveaux de protection accrus ==== | ||
+ | |||
+ | <b> Comment y parvenir: </b> | ||
+ | * Résumer comment l'architecture contraint les interfaces de service aux entités autorisées conformément à : | ||
+ | ** ITSG-22, et | ||
+ | ** ITSG-38. | ||
+ | |||
+ | ==== Mettre en œuvre des protocoles HTTPS pour les connexions Web sécurisées et d’authentification des messages fondée sur le domaine, rapports et conformité (DMARC) pour améliorer la sécurité des courriels ==== | ||
+ | |||
+ | <b> Comment y parvenir: </b> | ||
+ | * L'architecture utilise-t-elle HTTPS pour les connexions Web sécurisées | ||
+ | * L'architecture utilise-t-elle l'authentification, le rapport et la conformité des messages basés sur le domaine (DMARC) pour une sécurité améliorée de la messagerie ? | ||
+ | |||
+ | ==== Établir des interconnexions sécurisées entre les systèmes à l’aide d’IPA sécuritaires ou tirer parti des services de connectivité des TI hybrides gérés de manière centralisée ==== | ||
+ | |||
+ | <b> Comment y parvenir: </b> | ||
+ | * Décrire ce que (API ou services de connectivité informatique hybride gérés de manière centralisée) les architectures ont établi des interconnexions sécurisées entre les systèmes | ||
+ | |||
+ | Outils : | ||
+ | * Architecture d'état cible | ||
+ | * Architecture d'État intérimaire | ||
− | + | === Maintenir des opérations sécurisées === | |
− | |||
− | |||
− | |||
− | |||
− | |||
+ | ==== É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 ==== | ||
− | + | <b> Comment y parvenir: </b> | |
− | + | * Des processus ont-ils été établis pour assurer l'application rapide des correctifs et des mises à jour liés à la sécurité ? | |
− | + | * Résumer comment l'architecture prend en charge ces processus | |
− | |||
+ | ==== 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 ==== | ||
− | + | <b> Comment y parvenir: </b> | |
+ | * Résumer comment la journalisation des événements au sein de l'architecture s'aligne sur les directives de journalisation des événements du GC dans les domaines suivants : | ||
+ | ** Détection d'attaque | ||
+ | ** Prévention des attaques | ||
+ | ** Attaque répondre | ||
+ | ==== Établir un plan de gestion des incidents conforme au Plan de gestion des événements de cybersécurité du GC (PGEC GC) et signaler les incidents au Centre canadien pour la cybersécurité (CCC) ==== | ||
− | + | <b> Comment y parvenir: </b> | |
− | + | * Décrire comment le plan de gestion des incidents s'aligne sur la gestion des événements de cybersécurité du GC | |
− | + | * Décrire comment les incidents sont signalés au Centre canadien pour la cybersécurité (CCSB) | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | * | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</multilang> | </multilang> |
Latest revision as of 15:56, 4 March 2022
Security architecture[edit | edit source]
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[edit | edit source]
How to achieve:[edit | edit source]
- Summarize how the architecture ensures the confidentiality of the information based on its categorization and degree of injury
- Summarize how the architecture ensures the integrity of the information based on its categorization and degree of injury
- Summarize how the architecture ensures the availability of the information based on its categorization and degree of injury
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[edit | edit source]
How to achieve:[edit | edit source]
- Summarize how the architecture aligns with the Centre of Cyber Security’s IT Security Risk Management Framework
apply proportionate security measures that address business and user needs while adequately protecting data at rest and data in transit[edit | edit source]
How to achieve:[edit | edit source]
- Describe the security measures that protect the data at rest while meeting business and users needs
- Describe the security measures that protect the data in transit while meeting business and users needs
design systems to be resilient and available in order to support service continuity[edit | edit source]
How to achieve:[edit | edit source]
- Outline the architecture’s resilient characteristics support service continuity objectives
- Outline the architecture’s availability characteristics support service continuity objectives
Tools:[edit | edit source]
- Non-functional Requirements
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 [edit | edit source]
How to achieve:[edit | edit source]
- Summarize how the architectures identifies and authenticates:
- Individuals
- Processes
- Devices
- Summarize the enterprise security services leverage by the architecture
- Summarize how the architecture aligns to the Pan-Canadian Trust Framework
Tools:[edit | edit source]
- Target State Architecture
- Interim State Architecture
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[edit | edit source]
How to achieve:[edit | edit source]
- Summarize how the architecture constrains service interfaces to authorized entities in compliance to:
- ITSG-22, and;
- ITSG-38.
implement HTTPS for secure web connections and Domain-based Message Authentication, Reporting and Conformance (DMARC) for enhanced email security[edit | edit source]
How to achieve:[edit | edit source]
- Does the architecture use HTTPS for secure web connections
- Does the architecture use 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[edit | edit source]
How to achieve:[edit | edit source]
- Outline what (APIs or centrally managed hybrid IT connectivity services )the architectures established secure interconnections between systems
Tools:[edit | edit source]
- Target State Architecture
- Interim State Architecture
Maintain secure operations[edit | edit source]
[edit | edit source]
How to achieve:[edit | edit source]
- Have processes been established to ensure the prompt application of security related patches and updates?
- Summarize how the architecture supports these processes
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[edit | edit source]
How to achieve:[edit | edit source]
- Summarize how event logging within the architecture aligns to GC Event Logging Guidance in the areas of:
- Attack detection
- Attack prevention
- Attack respond
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[edit | edit source]
How to achieve:[edit | edit source]
- Describe how incident management plan aligns to GC Cyber Security Event Management
- Describe how incidents are reported to the Canadian Centre for Cyber Security (CCSB)