{"id":39655,"date":"2021-02-19T19:46:32","date_gmt":"2021-02-19T19:46:32","guid":{"rendered":"http:\/\/5cc88865-d4cf-40b2-b159-054b139ede57"},"modified":"2021-02-19T19:46:32","modified_gmt":"2021-02-19T19:46:32","slug":"zero-trust-is-not-a-security-solution-its-a-strategy","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/zero-trust-is-not-a-security-solution-its-a-strategy\/","title":{"rendered":"Zero Trust is not a security solution. It\u2019s a strategy"},"content":{"rendered":"
<\/div>\n

One of the top challenges and misunderstandings that I continue to see is what the definition of Zero Trust actually is. Zero Trust is not one product or platform; it’s a security framework built around the concept of “never trust, always verify” and “assuming breach.” Attempting to buy Zero Trust<\/a> as a product sets organizations up for failure. <\/p>\n

\n

ZDNet Recommends<\/span> <\/h3>\n<\/p><\/div>\n

Vendors would have you believe that the security solution, platform, or widget they are selling is Zero Trust and that you can just purchase their solution to address your needs. This is false. Vendors enable Zero Trust; they are not Zero Trust itself.  <\/p>\n

There Is No Easy Button To Zero Trust <\/h3>\n

Starting down the path of Zero Trust is complicated. It’s difficult to figure out where to start, so we’ve established a handy guide on how to practically enable Zero Trust from an implementation standpoint. Don’t buy into vendor hype that you can purchase something and immediately be Zero Trust. That’s not the reality of the situation. <\/p>\n

Organizations need to build a strategy to get to a Zero Trust architecture that encompasses more than technology and buzzwords. One example is the Zero Trust eXtended (ZTX) ecosystem which, at a bare minimum, requires: <\/p>\n