{"id":177,"date":"2021-11-16T10:12:32","date_gmt":"2021-11-16T10:12:32","guid":{"rendered":"https:\/\/infraon.io\/blog\/?p=177"},"modified":"2024-07-24T06:47:40","modified_gmt":"2024-07-24T06:47:40","slug":"history-of-zero-trust-security","status":"publish","type":"post","link":"https:\/\/infraon.io\/blog\/history-of-zero-trust-security\/","title":{"rendered":"History of Zero Trust Security"},"content":{"rendered":"\n

Before Zero Trust security existed, companies had to take utmost care to ensure that only trusted users were allowed to access the corporate network. Although the term \u201cZero Trust\u201d was popularized by John Kindervag, it was originally coined by Stephen Paul Marsh in 1994. Kindervag was an analyst with Forrester at that time when he had recognized the potential of this technology, and the world started to take notice. <\/p>\n\n\n\n

<\/div>\n\n\n\n

However, it was Marsh who had first introduced the \u201cZero Trust\u201d concept. His take on trust in the realm of IT system administration was that it could be mathematically modeled and constructed. According to him, it was more than a mere human phenomenon or confrontation. \u201cTrust\u201d (as per Marsh) was much more than human ethos, laws, judgment, and justice. <\/p>\n\n\n\n

<\/div>\n\n\n\n

<\/span>The Zero Trust Security model evolution <\/strong><\/span><\/h2>\n\n\n\n
<\/div>\n\n\n\n

The modern history of Zero Trust took roots in 2003 when the Jericho Forum highlighted the problems associated with demarcating organizational boundaries for IT systems. The Jericho Forum actively researched and promoted a concept called \u2018de-parameterization.\u2019 <\/p>\n\n\n\n

<\/div>\n\n\n\n

Google was one of the first companies to take the cue from the potentialities of the Zero Trust architecture<\/a><\/strong>. The initiative was called BeyondCorp, and in 2009, Google implemented a de-parameterized framework based on the Zero Trust Architecture. <\/p>\n\n\n\n

<\/div>\n\n\n\n

Kindervag, at this time, was actively engaging with IT communities, popularizing the Zero Trust approach. But things did not happen overnight. It took more than ten years for most organizations to slowly start implementing zero trust architectures. More of this was driven due to the proliferation of cloud and mobile technologies. <\/p>\n\n\n\n

<\/div>\n\n\n\n

<\/span>The birth of a new critical technology <\/strong><\/span><\/h2>\n\n\n\n
<\/div>\n\n\n\n

While the history of Zero Trust provided a contextual foundation for the technology itself, the actual shaping took place only later. The crystallization of this technology was in 2014 when a Swiss security IT engineer designed a Zero Trust Network. The network was based on firewall-based circuits to protect any client from malware. The Swiss Federal Institute of Intellectual Property received the manuscript of this architectural style, which was called the Untrust-Untrust type of network. The manuscript was subsequently published in 2015.<\/p>\n\n\n\n

<\/div>\n\n\n\n

The\u00a0evolution of Zero Trust security\u00a0started to prompt national security agencies such as the National Cyber Security Centre and the UK National Technical Authority to start recommending this architecture by 2019. By the close of 2020, major platform solution vendors, cloud service providers, and cyber security providers made zero trust part of their architectures. Because of the increased usage of Zero Trust<\/a><\/strong> and varying architectures in place, the NIST and NCSC were tasked with standardizing the implementation of this technology.\u00a0<\/p>\n\n\n\n

\"Zero<\/figure>\n\n\n\n
<\/div>\n\n\n\n

<\/span>What are the key standardization points proposed by NCSC and NIST?<\/strong><\/span><\/h2>\n\n\n\n
<\/div>\n\n\n\n

As part of the evolution of Zero Trust security, the work of NCSC and NIST on the Zero Trust Model led to the creation of a publication titled \u2013 Zero Trust Architecture<\/a>. In this publication, Zero Trust is defined as a collection of principles that can be applied to network security. The key principles that were part of the standardization effort were identified on the following lines:<\/p>\n\n\n\n

<\/div>\n\n\n\n
    \n
  • User and machine authentication<\/li>\n<\/ul>\n\n\n\n
    <\/div>\n\n\n\n
      \n
    • User identity \u2013 a single and strong source<\/li>\n<\/ul>\n\n\n\n
      <\/div>\n\n\n\n
        \n
      • Additional context \u2013 device metrics, compliance, etc.<\/li>\n<\/ul>\n\n\n\n
        <\/div>\n\n\n\n
          \n
        • Application authorization policies<\/li>\n<\/ul>\n\n\n\n
          <\/div>\n\n\n\n
            \n
          • Application access control policies<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

            Before Zero Trust security existed, companies had to take utmost care to ensure that only trusted users were allowed to access the corporate network. Although the term \u201cZero Trust\u201d was popularized by John Kindervag, it was originally coined by Stephen Paul Marsh in 1994. Kindervag was an analyst with Forrester at that time when he had recognized […]<\/p>\n","protected":false},"author":9,"featured_media":3441,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"History of Zero Trust Security | Best Introduction 2022 | Infraon","rank_math_description":"Are you looking for history and evaluation of zero trust security? Infraon zero trust security article help and know more about the zero trust security. Read more!","rank_math_focus_keyword":"Zero Trust Security,history","footnotes":""},"categories":[11],"tags":[],"class_list":["post-177","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-zero-trust-security"],"pvc_views":6276,"rank_math_description":"Are you looking for history and evaluation of zero trust security? Infraon zero trust security article help and know more about the zero trust security. Read more!","rank_math_keywords":"","_links":{"self":[{"href":"https:\/\/infraon.io\/blog\/wp-json\/wp\/v2\/posts\/177","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/infraon.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/infraon.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/infraon.io\/blog\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/infraon.io\/blog\/wp-json\/wp\/v2\/comments?post=177"}],"version-history":[{"count":0,"href":"https:\/\/infraon.io\/blog\/wp-json\/wp\/v2\/posts\/177\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/infraon.io\/blog\/wp-json\/wp\/v2\/media\/3441"}],"wp:attachment":[{"href":"https:\/\/infraon.io\/blog\/wp-json\/wp\/v2\/media?parent=177"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/infraon.io\/blog\/wp-json\/wp\/v2\/categories?post=177"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/infraon.io\/blog\/wp-json\/wp\/v2\/tags?post=177"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}