802
edits
Changes
Created page with "<div style="float: right; z-index: 10; position: absolute; right: 0; top: 1;">File:JoinusonGCconnex.png|link=http://gcconnex.gc.ca/groups/profile/2785549/gc-enterprise-secur..."
<div style="float: right; z-index: 10; position: absolute; right: 0; top: 1;">[[File:JoinusonGCconnex.png|link=http://gcconnex.gc.ca/groups/profile/2785549/gc-enterprise-security-architecture-gc-esa]]<br />[[File:ESAcontactus.png|link=mailto:ZZTBSCYBERS@tbs-sct.gc.ca]]</div> [[File:GOC ESA.jpg|center|link=http://www.gcpedia.gc.ca/wiki/Government_of_Canada_Enterprise_Security_Architecture_(ESA)_Program]] <div class="center">
{| style="border: 2px solid #000000; border-image: none;" width="1000px"
|-
! style="background: #e1caf7; color: black" width="20%" scope="col" " width="175px" | [[Government of Canada Enterprise Security Architecture (ESA) Program|ESA Program Overview]]
! style="background: #e1caf7; color: black" width="20%" scope="col" " width="125px" | [[ESA Backgrounder (Strategy)|ESA Foundation]]
! style="background: #e1caf7; color: black" width="20%" scope="col" " width="125px" | [[ESA Requirements|ESA Artifacts]]
! style="background: #C495F0; color: black" width="20%" scope="col" " width="125px" | [[ESA Initiatives|ESA Initiatives]]
! style="background: #e1caf7; color: black" width="20%" scope="col" " width="125px" | [[ ESA Tools and Templates]]
! style="background: #e1caf7; color: black" width="20%" scope="col" " width="125px" | [[GC ESA Artifact Repository|ESA Reference Materials]]
! style="background: #e1caf7; color: black" width="20%" scope="col" " width="100px" | [[ESA Glossary| Glossary]]
|}
{| style="border-bottom: #000000 2px solid; border-left: #000000 2px solid; border-right: #000000 2px solid" width="1000px"
|-
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="100px" | [[Cloud Security Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="100px" | [[HTTPS Initiative|HTTPS Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="110px" | [[Data Loss Prevention Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="120px" | [[Enterprise Vulnerability Management System Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="100px" | [[DevSecOps Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="120px" | [[Integrated Risk Management Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="150px" | [[Domain Message Authentication Reporting and Compliance|DMARC Initiative]]
! style="background: #9a9af8; color: black" width="20%" scope="col" " width="110px" | [[Zero Trust Security|Zero Trust Security Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="110px" | [[GC Cyber Security Event Management]]
|}
{| style="border-bottom: #000000 2px solid; border-left: #000000 2px solid; border-right: #000000 2px solid" width="1000px"
|-
! style="background: #dddddd; color: black" width="25%" scope="col" " width="250px" | [[Zero Trust Security Architecture| Zero Trust Architecture]]
|}
</div>{{TOCright}}
=Background=
The Government of Canada (GC) Digital Operations Strategic Plan 2018-2022 outlines the government’s commitment to delivering responsive and innovative IT services with the overarching goals of service, security, value, and agility. The “Secure and Trusted” pillar focuses on safeguarding sensitive government data, ensuring that the systems underpinning digital services are properly designed and secured, and that Canadians accessing online services can trust the government with their personal information. The government must therefore establish a secure and resilient enterprise digital security ecosystem in which government services are delivered safely and securely.
Further, the [https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html Government of Canada Digital Standards] form the foundation of the government’s shift to becoming more agile, open, and user-focused. Users increasingly want to have access to information and services from wherever they are, using whatever platform they choose. As service enablers, GC Information Technology (IT), including security, has an increasing duty to be responsive and provide solutions that meet changing expectations. Adopting a balanced approach that considers user needs, supported by a pragmatic security approach, will result in a more secure environment. This approach will enable the GC to meet its Digital Government vision of delivering “programs and services to people and businesses in simple, modern and effective ways that are optimized for digital and available anytime, anywhere and from any device.
The concept of “zero trust” is an approach that is driven in response to the aforementioned factors
including a mobile workforce and mobile devices, adoption of cloud-based services, insider threats and
breaches in network perimeter security. The purpose of this discussion paper is to introduce the zero
trust security model and how it might play a role in improving the GC’s security posture as its IT service
delivery continues to evolve.
=What is Zero Trust?=
One of the first published works where the notion of “de-perimeterisation” was introduced dates
back to 2003/2004 and is based on work produced from the Jericho Forum. More recently, the Defense Innovation Board, a US Federal Advisory Committee, published The Road to
Zero Trust (Security) which examines zero trust in the context of the US Department of Defense
(DoD). In addition, the US National Institute of Standards and Technology (NIST) recently published their
second draft of the Zero Trust Architecture publication. There are also numerous papers available
from industry analysts (e.g., Gartner, Forrester Research) as well as from various cloud service providers
which expand on the topic. Perhaps the most relevant report in the context of this concept paper is the Zero Trust Cybersecurity
Current Trends published by the American Council for Technology-Industry Advisory Council (ACTIAC). It examines the current state and suitability of zero trust within the context of the US federal
government and reflects many of the same challenges facing the GC. While there are numerous sources that describe various aspects of the zero trust security model, the
manner and level of granularity in which the concepts are described varies and there is not a common
lexicon or model that has been adopted within the industry. Even the terms “zero trust”, “zero trust
network” and “zero trust architecture” tend to be used and defined differently. However, the
fundamental underlying principles of the zero trust security model are fairly clear and a suitable
definition can therefore be derived from these sources.
NIST defines [https://csrc.nist.gov/publications/detail/sp/800-207/draft Zero Trust Security] as follows: "Zero trust provides a collection of concepts and ideas designed to reduce the uncertainty in
enforcing accurate, per-request access decisions in information systems and services in the face
of a network viewed as compromised. Zero trust architecture (ZTA) is an enterprise’s
cybersecurity plan that utilizes zero trust concepts and encompasses component relationships,
workflow planning, and access policies. Therefore, a zero trust enterprise is the network infrastructure (physical and virtual) and operational policies that are in place for an enterprise as
a product of a zero trust architecture plan."
=Zero Trust Security Model=
Key areas of the Zero Trust Security Model are:
*Assumes the network is compromised and that there is no implicit trust afforded to a user and/or device simply because it is connected to the internal network (i.e., inside the enterprise network perimeter).
*Users and devices, regardless of location relative to the enterprise network, are treated equally – they are untrusted until proven otherwise.
*Places more emphasis on controlling access to corporate resources than controlling access to the corporate network.
*Focuses on the prevention of unauthorized access to resources (data, applications and services) through fine-grained, least privilege access control, at rest and in transit data protection and limiting unauthorized lateral movement using micro-segmentation.
Implementation of zero trust networks is expected to result in a number of paradigm shifts including:
*VPNs for secure remote access will no longer be required.
*Security perimeters will move (or will be added) closer to the resource being protected and therefore:
**the number of security perimeters will increase; and,
**the traditional notion of network perimeter security will diminish in importance and, in some cases, become irrelevant
*The user experience will be the same regardless of their location relative to the enterprise network.
=Implementation Considerations=
Ultimately, the principles and concepts behind the zero trust security model translate to security capabilities. Many of the sources identified in the previous section, as well as others, identify basic tenets or pillars of the zero trust security model, but they offer different perspectives and the number and level of granularity of these concepts varies. After assessing the various perspectives, a hybrid approach was chosen primary based on the zero trust security model pillars identified in the ACT-IAC paper [https://www.actiac.org/system/files/ACT-IAC%20Zero%20Trust%20Project%20Report%2004182019.pdf Zero Trust Cybersecurity Current Trends].
This approach adopts security pillars such as:
*Users – identification and authentication, least privilege access, two-factor authentication
*User Devices – user device identification and verification, user device management
*Networks – isolation and protection of network devices and infrastructure
*Resource Protection – protection of assets including data, applications and services
*Continuous Monitoring – ongoing automated security event management and user behaviour analysis; real-time correlation, threat assessment and response
=Next Steps=
The zero trust security model should not be considered to be a blanket replacement for existing network and security controls currently implemented within the GC. Instead, the principles and recommendations stemming from the zero trust security model should be evaluated and prioritized; and used to augment and improve the GC’s security posture over time. Some next steps include:
*Develop a zero trust security reference architecture;
*Develop a zero trust network vision and strategy for the GC;
*Evaluate the GC’s current state and identify areas that could be improved;
*Identify and assess possible remediation for each area and prioritize activities based on factors such as risk, cost and feasibility;
*Develop implementation guidance; and,
*Pilot and deploy/implement solutions over time using a phased, incremental approach
=References=
*[https://www.gcpedia.gc.ca/gcwiki/images/c/c5/GC_Zero_Trust_Security_Concept.pdf Zero Trust Discussion Paper]
*[https://www.actiac.org/system/files/ACT-IAC%20Zero%20Trust%20Project%20Report%2004182019.pdf ACT-IAC - Zero Trust Cybersecurity Current Trends]
*[https://csrc.nist.gov/publications/detail/sp/800-207/draft NIST - Zero Trust Security Architecture]
{| style="border: 2px solid #000000; border-image: none;" width="1000px"
|-
! style="background: #e1caf7; color: black" width="20%" scope="col" " width="175px" | [[Government of Canada Enterprise Security Architecture (ESA) Program|ESA Program Overview]]
! style="background: #e1caf7; color: black" width="20%" scope="col" " width="125px" | [[ESA Backgrounder (Strategy)|ESA Foundation]]
! style="background: #e1caf7; color: black" width="20%" scope="col" " width="125px" | [[ESA Requirements|ESA Artifacts]]
! style="background: #C495F0; color: black" width="20%" scope="col" " width="125px" | [[ESA Initiatives|ESA Initiatives]]
! style="background: #e1caf7; color: black" width="20%" scope="col" " width="125px" | [[ ESA Tools and Templates]]
! style="background: #e1caf7; color: black" width="20%" scope="col" " width="125px" | [[GC ESA Artifact Repository|ESA Reference Materials]]
! style="background: #e1caf7; color: black" width="20%" scope="col" " width="100px" | [[ESA Glossary| Glossary]]
|}
{| style="border-bottom: #000000 2px solid; border-left: #000000 2px solid; border-right: #000000 2px solid" width="1000px"
|-
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="100px" | [[Cloud Security Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="100px" | [[HTTPS Initiative|HTTPS Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="110px" | [[Data Loss Prevention Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="120px" | [[Enterprise Vulnerability Management System Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="100px" | [[DevSecOps Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="120px" | [[Integrated Risk Management Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="150px" | [[Domain Message Authentication Reporting and Compliance|DMARC Initiative]]
! style="background: #9a9af8; color: black" width="20%" scope="col" " width="110px" | [[Zero Trust Security|Zero Trust Security Initiative]]
! style="background: #c2c2fa; color: black" width="20%" scope="col" " width="110px" | [[GC Cyber Security Event Management]]
|}
{| style="border-bottom: #000000 2px solid; border-left: #000000 2px solid; border-right: #000000 2px solid" width="1000px"
|-
! style="background: #dddddd; color: black" width="25%" scope="col" " width="250px" | [[Zero Trust Security Architecture| Zero Trust Architecture]]
|}
</div>{{TOCright}}
=Background=
The Government of Canada (GC) Digital Operations Strategic Plan 2018-2022 outlines the government’s commitment to delivering responsive and innovative IT services with the overarching goals of service, security, value, and agility. The “Secure and Trusted” pillar focuses on safeguarding sensitive government data, ensuring that the systems underpinning digital services are properly designed and secured, and that Canadians accessing online services can trust the government with their personal information. The government must therefore establish a secure and resilient enterprise digital security ecosystem in which government services are delivered safely and securely.
Further, the [https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html Government of Canada Digital Standards] form the foundation of the government’s shift to becoming more agile, open, and user-focused. Users increasingly want to have access to information and services from wherever they are, using whatever platform they choose. As service enablers, GC Information Technology (IT), including security, has an increasing duty to be responsive and provide solutions that meet changing expectations. Adopting a balanced approach that considers user needs, supported by a pragmatic security approach, will result in a more secure environment. This approach will enable the GC to meet its Digital Government vision of delivering “programs and services to people and businesses in simple, modern and effective ways that are optimized for digital and available anytime, anywhere and from any device.
The concept of “zero trust” is an approach that is driven in response to the aforementioned factors
including a mobile workforce and mobile devices, adoption of cloud-based services, insider threats and
breaches in network perimeter security. The purpose of this discussion paper is to introduce the zero
trust security model and how it might play a role in improving the GC’s security posture as its IT service
delivery continues to evolve.
=What is Zero Trust?=
One of the first published works where the notion of “de-perimeterisation” was introduced dates
back to 2003/2004 and is based on work produced from the Jericho Forum. More recently, the Defense Innovation Board, a US Federal Advisory Committee, published The Road to
Zero Trust (Security) which examines zero trust in the context of the US Department of Defense
(DoD). In addition, the US National Institute of Standards and Technology (NIST) recently published their
second draft of the Zero Trust Architecture publication. There are also numerous papers available
from industry analysts (e.g., Gartner, Forrester Research) as well as from various cloud service providers
which expand on the topic. Perhaps the most relevant report in the context of this concept paper is the Zero Trust Cybersecurity
Current Trends published by the American Council for Technology-Industry Advisory Council (ACTIAC). It examines the current state and suitability of zero trust within the context of the US federal
government and reflects many of the same challenges facing the GC. While there are numerous sources that describe various aspects of the zero trust security model, the
manner and level of granularity in which the concepts are described varies and there is not a common
lexicon or model that has been adopted within the industry. Even the terms “zero trust”, “zero trust
network” and “zero trust architecture” tend to be used and defined differently. However, the
fundamental underlying principles of the zero trust security model are fairly clear and a suitable
definition can therefore be derived from these sources.
NIST defines [https://csrc.nist.gov/publications/detail/sp/800-207/draft Zero Trust Security] as follows: "Zero trust provides a collection of concepts and ideas designed to reduce the uncertainty in
enforcing accurate, per-request access decisions in information systems and services in the face
of a network viewed as compromised. Zero trust architecture (ZTA) is an enterprise’s
cybersecurity plan that utilizes zero trust concepts and encompasses component relationships,
workflow planning, and access policies. Therefore, a zero trust enterprise is the network infrastructure (physical and virtual) and operational policies that are in place for an enterprise as
a product of a zero trust architecture plan."
=Zero Trust Security Model=
Key areas of the Zero Trust Security Model are:
*Assumes the network is compromised and that there is no implicit trust afforded to a user and/or device simply because it is connected to the internal network (i.e., inside the enterprise network perimeter).
*Users and devices, regardless of location relative to the enterprise network, are treated equally – they are untrusted until proven otherwise.
*Places more emphasis on controlling access to corporate resources than controlling access to the corporate network.
*Focuses on the prevention of unauthorized access to resources (data, applications and services) through fine-grained, least privilege access control, at rest and in transit data protection and limiting unauthorized lateral movement using micro-segmentation.
Implementation of zero trust networks is expected to result in a number of paradigm shifts including:
*VPNs for secure remote access will no longer be required.
*Security perimeters will move (or will be added) closer to the resource being protected and therefore:
**the number of security perimeters will increase; and,
**the traditional notion of network perimeter security will diminish in importance and, in some cases, become irrelevant
*The user experience will be the same regardless of their location relative to the enterprise network.
=Implementation Considerations=
Ultimately, the principles and concepts behind the zero trust security model translate to security capabilities. Many of the sources identified in the previous section, as well as others, identify basic tenets or pillars of the zero trust security model, but they offer different perspectives and the number and level of granularity of these concepts varies. After assessing the various perspectives, a hybrid approach was chosen primary based on the zero trust security model pillars identified in the ACT-IAC paper [https://www.actiac.org/system/files/ACT-IAC%20Zero%20Trust%20Project%20Report%2004182019.pdf Zero Trust Cybersecurity Current Trends].
This approach adopts security pillars such as:
*Users – identification and authentication, least privilege access, two-factor authentication
*User Devices – user device identification and verification, user device management
*Networks – isolation and protection of network devices and infrastructure
*Resource Protection – protection of assets including data, applications and services
*Continuous Monitoring – ongoing automated security event management and user behaviour analysis; real-time correlation, threat assessment and response
=Next Steps=
The zero trust security model should not be considered to be a blanket replacement for existing network and security controls currently implemented within the GC. Instead, the principles and recommendations stemming from the zero trust security model should be evaluated and prioritized; and used to augment and improve the GC’s security posture over time. Some next steps include:
*Develop a zero trust security reference architecture;
*Develop a zero trust network vision and strategy for the GC;
*Evaluate the GC’s current state and identify areas that could be improved;
*Identify and assess possible remediation for each area and prioritize activities based on factors such as risk, cost and feasibility;
*Develop implementation guidance; and,
*Pilot and deploy/implement solutions over time using a phased, incremental approach
=References=
*[https://www.gcpedia.gc.ca/gcwiki/images/c/c5/GC_Zero_Trust_Security_Concept.pdf Zero Trust Discussion Paper]
*[https://www.actiac.org/system/files/ACT-IAC%20Zero%20Trust%20Project%20Report%2004182019.pdf ACT-IAC - Zero Trust Cybersecurity Current Trends]
*[https://csrc.nist.gov/publications/detail/sp/800-207/draft NIST - Zero Trust Security Architecture]