{"id":27927,"date":"2024-06-18T12:00:48","date_gmt":"2024-06-18T16:00:48","guid":{"rendered":"https:\/\/netfoundry.io\/?p=27927"},"modified":"2024-09-17T22:08:23","modified_gmt":"2024-09-18T02:08:23","slug":"zerotrust-zero-trust-overview-comparing-netfoundry-to-the-top-zero-trust-vendors","status":"publish","type":"post","link":"https:\/\/netfoundry.io\/zero-trust\/zerotrust-zero-trust-overview-comparing-netfoundry-to-the-top-zero-trust-vendors\/","title":{"rendered":"Zero Trust Overview: Comparing NetFoundry to the Top Zero Trust Vendors"},"content":{"rendered":"\n

Zero Trust Solutions and Vendors<\/h3>\n\n\n\n

\u201cZero trust\u201d is often a long, tough journey.  But it doesn\u2019t need to be.  And the answer is actually simple once we separate reality from the marketing fluff from many zero trust vendors. Everyone claims to have a zero trust solution including the top security vendors like Cisco<\/a>, Palo Alto Networks<\/a>, Zscaler<\/a>, CrowdStrike<\/a>, and Okta<\/a>. This article is an overview of zero trust and an example from a major new player in secure networking and the leading open source zero trust platform provider NetFoundry.<\/p>\n\n\n\n\n\n\n

Zero Trust Overview<\/h3>\n\n\n\n

Let\u2019s start with the problem.  There are two main reasons why \u201czero trust\u201d<\/a> is difficult:<\/p>\n\n\n\n

    \n
  1. Most \u201czero trust\u201d solutions are not zero trust. Ironically, they trust the Internet! Trusting the Internet causes complexity and other problems.

    <\/li>\n\n\n\n
  2. Most \u201czero trust\u201d solutions are too broad and disruptive. They impact entire user groups or sites, backhaul everything, cause performance problems, and disrupt the WAN and firewalls. They are too broad to be effective for specific use cases such as private data center-hosted apps, third-party access, multi-cloud, IoT, APIs, and remote management.<\/li>\n<\/ol>\n\n\n\n

    <\/p>\n\n\n\n

    NetFoundry\u2019s Ziti  platform helps businesses simplify the journey by taking the opposite approach of the industry\u2019s \u201czero trust solutions\u201d:<\/p>\n\n\n\n

      \n
    1. NetFoundry does not trust the Internet.  No open inbound ports.  No firewall hole punching.  No reliance on IP addresses or public DNS.  You can choose to use federated IDPS and MFA, but you are not forced to \u2013 you use it when you decide it is appropriate.  You don\u2019t even need to trust NetFoundry itself \u2013 it is built on open source OpenZiti<\/a> \u2013 you don\u2019t need to trust the label on the tin, or hope the black box does what it says it does.

      <\/li>\n\n\n\n
    2. NetFoundry enables you to choose your path and makes it so your paths are not disruptive.  Move at any level, even individual apps, such that business priorities determine the journey.  Every app is routed independently \u2013 no performance-impacting backhaul tunnels.  Add use cases without disrupting existing networks or firewalls.  And, because NetFoundry covers use cases like APIs, remote management, IoT, private DC apps, and 3rd party access, you don\u2019t need to cobble together an assortment of different solutions.<\/li>\n<\/ol>\n\n\n\n

      <\/p>\n\n\n\n

      Let\u2019s take a more detailed look at how NetFoundry differs from the top zero trust vendors:<\/p>\n\n\n\n

      NetFoundry principle #1: <\/strong>
      Don\u2019t trust the Internet = simpler secure networking<\/strong><\/p>\n\n\n\n

      Unlike \u201czero trust\u201d approaches, NetFoundry\u2019s NetFoundry service enables you to not trust the Internet, at all (read the \u201cgreat zero trust lie\u201d appendix to see how solutions marketed as \u201czero trust\u201d actually trust the Internet).  What does it mean to not trust the Internet?<\/p>\n\n\n\n

      <\/p>\n\n\n\n