ネットスコープは、2022年Gartner®社のセキュリティ・サービス・エッジ(SSE)のマジック・クアドラントでリーダーの1社と位置付けられました。レポートを読む

  • 製品

    Netskope製品は、NetskopeSecurityCloud上に構築されています。

  • プラットフォーム

    世界最大のセキュリティプライベートクラウドでの比類のない可視性とリアルタイムデータおよび脅威保護。

ネットスコープ、2022年Gartner社のセキュリティ・サービス・エッジ(SSE)のマジック・クアドラントでリーダーの1社と位置付けられる

レポートを読む 製品概要に移動
Netskope Gartner マジック・クアドラント 2022 SSEリーダー

Netskope は、データと脅威の保護、および安全なプライベートアクセスを実現するための機能を統合した、最新のクラウドセキュリティスタックを提供します。

プラットフォームを探索する
大都市の俯瞰図
  • 変身

    デジタルトランスフォーメーションを保護します。

  • セキュリティの近代化

    今日と明日のセキュリティの課題に対応します。

  • フレームワーク

    サイバーセキュリティを形作る規制の枠組みを採用する。

  • 業界ソリューション

    Netskopeは、クラウドに安全に移行するためのプロセスを世界最大規模の企業に提供しています。

最小の遅延と高い信頼性を備えた、市場をリードするクラウドセキュリティサービスに移行します。

詳しくはこちら
Lighted highway through mountainside switchbacks

シングルパスSSEフレームワークを使用して、他のセキュリティソリューションを回避することが多い脅威を防止します。

詳しくはこちら
Lighting storm over metropolitan area

SSEおよびSASE展開のためのゼロトラストソリューション

詳しくはこちら
Boat driving through open sea

Netskopeは、クラウドサービス、アプリ、パブリッククラウドインフラストラクチャを採用するための安全でクラウドスマートかつ迅速な旅を可能にします。

詳しくはこちら
Wind turbines along cliffside
  • 導入企業

    Netskopeは、フォーチュン100の25以上を含む世界中の2,000以上の顧客にサービスを提供しています。

  • カスタマーソリューション

    お客様のため、Netskopeでお客様の成功を確実にすべく、あらゆるステップを共に歩んでまいります。

  • トレーニングと認定

    Netskope training will help you become a cloud security expert.

私たちは、お客様が何にでも備えることができるように支援します

お客様を見る
Woman smiling with glasses looking out window

Netskopeの有能で経験豊富なプロフェッショナルサービスチームは、実装を成功させるための規範的なアプローチを提供します。

詳しくはこちら
Netskope Professional Services

Netskopeトレーニングで、デジタルトランスフォーメーションの旅を保護し、クラウド、ウェブ、プライベートアプリケーションを最大限に活用してください。

詳しくはこちら
Group of young professionals working
  • リソース

    クラウドへ安全に移行する上でNetskopeがどのように役立つかについての詳細は、以下をご覧ください。

  • ブログ

    Netskopeがセキュリティサービスエッジ(SSE)を通じてセキュリティとネットワークの変革を可能にする方法を学びましょう。

  • イベント&ワークショップ

    最新のセキュリティトレンドを先取りし、仲間とつながりましょう。

  • 定義されたセキュリティ

    サイバーセキュリティ百科事典で知っておくべきことすべて。

セキュリティビジョナリーポッドキャスト

Episode 15: Building Permanent Security Awareness

ポッドキャストを再生する
Black man sitting in conference meeting

Netskopeがセキュリティサービスエッジ(SSE)機能を介してゼロトラストおよびSASEジャーニーを実現する方法に関する最新情報をお読みください。

ブログを読む
Sunrise and cloudy sky

SASE Week

Netskope is positioned to help you begin your journey and discover where Security, Networking, and Zero Trust fit in the SASE world.

詳しくはこちら
SASE Week

セキュリティサービスエッジとは何ですか?

SASEのセキュリティ面、ネットワークとクラウドでの保護の未来を探ります。

詳しくはこちら
Four-way roundabout
  • 会社概要

    クラウド、データ、ネットワークセキュリティの課題の先取りをサポート

  • ネットスコープが選ばれる理由

    クラウドの変革とどこからでも機能することで、セキュリティの機能方法が変わりました。

  • リーダーシップ

    ネットスコープの経営陣はお客様を成功に導くために全力を尽くしています。

  • パートナー

    私たちはセキュリティリーダーと提携して、クラウドへの旅を保護します。

Netskopeは仕事の未来を可能にします。

詳しくはこちら
Curvy road through wooded area

Netskopeは、組織がゼロトラストの原則を適用してデータを保護できるように、クラウド、データ、およびネットワークのセキュリティを再定義しています。

詳しくはこちら
Switchback road atop a cliffside

思想家、建築家、夢想家、革新者。 一緒に、私たちはお客様がデータと人々を保護するのを助けるために最先端のクラウドセキュリティソリューションを提供します。

当社のチーム紹介
Group of hikers scaling a snowy mountain

Netskopeのパートナー中心の市場開拓戦略により、パートナーは企業のセキュリティを変革しながら、成長と収益性を最大化できます。

詳しくはこちら
Group of diverse young professionals smiling

Making Sense of Zero Trust Through the Lens of Networking and Infrastructure

Oct 20 2022

“Zero trust” still confuses people—and for good reason. While the term conveys a certain absolute authority (“zero,” “nope,” “nothing”), contemporary approaches offer much more nuanced capabilities. And while zero trust today is typically associated with security initiatives, the concepts have their origin in the definition of network perimeters, who is granted access, and how that access is provided.

The evolution of security hasn’t been from implicit trust to no trust, but rather toward contextual controls that grant the right people the right access to the right resources at the right time for the right reasons. But ultimately, making sense of zero trust requires an understanding of how the role of networking and infrastructure has shifted with respect to the critical objectives of security in recent years.

The changing role of the network: a brief history

In the earliest days of building networks and defining the enterprise perimeter, all companies were essentially islands. They built corporate networks to facilitate interactions between employees and data that was all on-premises. When the internet came along, everyone wanted to get in on that. But businesses realized fairly quickly that the internet’s default implicit trust was going to cause problems when it came to protecting themselves from outsiders with malicious intent. 

The first natural step was to use the network to create demarcation points. Architectures evolved to include something called a DMZ, which has a similar function as physical-world demilitarized zones (such as the 2.5-mile wide strip of land between North Korea and South Korea; the natural isolation of which created an involuntary park now regarded as one of the most well-preserved areas of temperate habitat in the world). This kind of “castle and moat” architecture actually worked for a long time. But then as businesses evolved and required constant connectivity with other businesses, partners, suppliers, and even their own customers in certain circumstances—new patterns were required 

There were many attempts at creating these new patterns over the years. The Jericho Forum promoted de-perimeterization in the early 2000s. A few years later, I wrote about “the death of the DMZ” and delivered some Microsoft TechEd presentations where I advocated to authenticate every person and system, authorize all actions and behaviors, audit every activity and transaction, and encrypt where necessary. (Though today, I would change that last one to encrypt all the time.)

Then zero trust networking came along. This was useful—but it was still thinking more along the lines of gating access to networks. Google’s BeyondCorp initiative proposed “What if people were always on the internet, even if they’re in the office?” They really only get an internet connection; all requests to interact with applications must flow through some kind of a broker. Then Forrester’s Zero Trust eXtended (ZTX) came along. Gartner offered their own early take on the concept, which was called CARTA  (continuous adaptive risk and trust assessment). 

Then the emergence of the software-defined perimeter architecture made the zero trust concept much more relevant. The software-defined perimeter hooked people to applications—regardless of what the underlying network infrastructure was like. This opened up new possibilities. 
As a result, the zero trust network access (ZTNA) market soon emerged. Right now, we’re seeing a lot of emphasis on ZTNA—which came out of COVID, when everyone suddenly had to work from home. While most enterprises initially tried to expand their VPN to cope with this immediate shift, what they found was that their VPN concentrators were brittle. They hadn’t been updated or patched in a while which meant they could be vulnerable. But even if companies could safely expand their VPN concentration capabilities, they were still running up against bandwidth constraints from backhauling traffic to their facilities for security. And it was especially inefficient because most of that traffic needed to hairpin right back out again to software-as-a-service (SaaS) applications or the web.

Letting the network do what it does best

ZTNA transcended the constraints of VPNs. I was wrong in 2019 when I said that ZTNA would replace VPN. I changed my view in 2020 to say ZTNA would augment VPN because there are still legitimate reasons when someone needs a VPN to access the network (such as for network administration or when doing performance analysis). But for the vast majority of cases, you don’t need to be on the network—you just need access to an application. ZTNA gives you that access without any sort of reliance on the underlying network architecture. 

This uncoupling (and unburdening) meant that networkers didn’t need to concern themselves with individual access control policies for applications. The application owner creates policies and defines who’s allowed to interact, as well as the conditions that indicate the level of access (e.g., full, reduced, isolated, none). That responsibility no longer has to be dumped on the networker—who may not be equipped to make those decisions for applications anyway. 

Simultaneously, networkers could now focus more on the things they do really well—such as high availability, ensuring that the network is reliable, and that it performs well at getting bits where they need to go. In addition, the network team can also help application owners ensure more consistent experiences. People interact with applications in exactly the same way, wherever they happen to be—in the office, in a coffee shop, on an airplane, or at home. 

The curious case of IoT discovery

Let’s ponder the Internet of Things (IoT) for a moment. If a company claims to have solved the problem of discovering all their IoT devices, I would argue that’s a claim of ignorance. Most companies possess a limited understanding of the IoT devices in their networks today. Poor visibility is the root—and the roots plunge far.

Beyond finding all those devices, effective visibility requires figuring out what they’re talking to and what is talking back. While this is a very natural thing for networkers to do, finding an IoT device’s owner can be very difficult. IoT devices are like rabbits—they multiply and then they forget their parentage. The traditional way of managing IoT devices (shuttling them onto their own subnet) offers no respite. While an application owner may only have one or two applications in their charge, people who manage IoT devices may have thousands. Once deployed, they often lose track of at least some of them. Who becomes responsible for their stewardship? 

If there were a way for a networker to automatically (re)discover all IoT devices and especially the communication flows between them, then we could assign them into different classifications with corresponding levels of required protection. Networkers could propose if an IoT device is “safe” or “risky” (or maybe even define a spectrum of different control classes between “safe” and “risky”).

One goal: the network is the security

Security teams don’t want to worry about connectivity details and networkers don’t want to worry about security policies. So by teasing these apart and allowing each domain to concentrate on their specialized tasks, each team can help the other succeed without stepping on any toes. 

Security should be helping networkers deliver ubiquity, resilience, and performance. In the worst case scenario, if teams misjudge the access and performance aspects, then the risk of people bypassing security controls looms large. And even in the best case, siloed security is a bottleneck that impedes the business, decreases IT agility, and reduces productivity and responsiveness to customers. ZTNA services facilitate network and security convergence, as do tools like digital experience management (DEM) which make it easier to troubleshoot problems and ensure that their users are kept safe while enjoying a superior experience. DEM reduces the time it takes to diagnose and close a helpdesk ticket, streamlining security and networking operations. 

The ultimate goal is for security to focus on controls, networking to focus on experience—and for everyone across the company to stay safe, happy, and productive.

author image
Steve Riley
Steve Riley is a Field CTO at Netskope. Having worked at the intersection of cloud and security for pretty much as long as that’s been an actual topic, Steve offers that perspective to field and executive engagements and also supports long-term technology strategy and works with key industry influencers. Steve has held technology roles for more than three decades, including stints at Gartner Inc., Riverbed Technology, Amazon Web Services, and Microsoft Corp.