Netskopeの SASE Summitにご参加ください 、あなたの近くの都市に来てください!今すぐご登録ください

  • セキュリティサービスエッジ製品

    高度なクラウド対応の脅威から保護し、あらゆるベクトルにわたってデータを保護します。

  • Borderless SD-WAN

    すべてのリモートユーザー、デバイス、サイト、クラウドへの安全で高性能なアクセスを自信を持って提供します。

  • プラットフォーム

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

未来のプラットフォームはネツコペです

インテリジェントセキュリティサービスエッジ(SSE)、クラウドアクセスセキュリティブローカー(CASB)、クラウドファイアウォール、次世代セキュアWebゲートウェイ(SWG)、およびZTNAのプライベートアクセスは、単一のソリューションにネイティブに組み込まれており、セキュアアクセスサービスエッジ(SASE)アーキテクチャへの道のりですべてのビジネスを支援します。

製品概要に移動
Netskopeの動画
ボーダレスSD-WAN:ボーダレスエンタープライズの新時代を先導

NetskopeボーダレスSD-WANは、ゼロトラストの原則と保証されたアプリケーションパフォーマンスを統合するアーキテクチャを提供し、すべてのサイト、クラウド、リモートユーザー、およびIoTデバイスに前例のない安全で高性能な接続を提供します。

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

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

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

  • セキュリティの近代化

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

  • フレームワーク

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

  • 業界ソリューション

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

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

NewEdgeの詳細
Lighted highway through mountainside switchbacks
アプリケーションのアクセス制御、リアルタイムのユーザーコーチング、クラス最高のデータ保護により、生成型AIアプリケーションを安全に使用できるようにします。

ジェネレーティブ AI の使用を保護する方法を学ぶ
Safely Enable ChatGPT and Generative AI
SSEおよびSASE展開のためのゼロトラストソリューション

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

Learn about Industry Solutions
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の有能で経験豊富なプロフェッショナルサービスチームは、実装を成功させるための規範的なアプローチを提供します。

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

Learn about Training and Certifications
Group of young professionals working
  • リソース

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

  • ブログ

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

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

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

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

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

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

ボーナスエピソード2:SSEのマジッククアドラントとSASEを正しく取得する
MikeとSteveが、ガートナー®社のマジック・クアドラント™のセキュリティ・サービス・エッジ(SSE)、Netskopeの位置づけ、現在の経済情勢がSASEの取り組みに与える影響について語ります。

ポッドキャストを再生する
ボーナスエピソード2:SSEのマジッククアドラントとSASEを正しく取得する
最新のブログ

Netskopeがセキュリティサービスエッジ(SSE)機能を通じてゼロトラストとSASEの旅を可能にする方法。

ブログを読む
Sunrise and cloudy sky
ネツコペAWSイマージョンデイワールドツアー2023

Netskopeは、Netskope製品の使用とデプロイについてAWSのお客様を教育および支援するために、さまざまなハンズオンラボ、ワークショップ、詳細なウェビナー、およびデモを開発しました。

Learn about AWS Immersion Day
AWS パートナー
セキュリティサービスエッジとは何ですか?

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

Learn about Security Service Edge
Four-way roundabout
  • 会社概要

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

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

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

  • リーダーシップ

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

  • パートナー

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

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

詳しくはこちら
Curvy road through wooded area
Highest in Execution. Furthest in Vision.

ネットスコープは2023年Gartner®社のセキュリティ・サービス・エッジ(SSE)のマジック・クアドラント™でリーダーの1社として評価されました。

レポートを読む
ネットスコープは2023年Gartner®社のセキュリティ・サービス・エッジ(SSE)のマジック・クアドラント™でリーダーの1社として評価されました。
思想家、建築家、夢想家、革新者。 一緒に、私たちはお客様がデータと人々を保護するのを助けるために最先端のクラウドセキュリティソリューションを提供します。

当社のチーム紹介
Group of hikers scaling a snowy mountain
Netskopeのパートナー中心の市場開拓戦略により、パートナーは企業のセキュリティを変革しながら、成長と収益性を最大化できます。

Learn about Netskope Partners
Group of diverse young professionals smiling

Bringing the Second Netskope Patent to Life: The Life of a Cloud Transaction

Jul 28 2016
Tags
CASB
Cloud Security
Netskope Announcements

Today, we announced that we have been issued our second comprehensive CASB patent for delivering granular visibility and enforcing granular policy and data security for cloud delivered services. This patent complements the first by recognizing our unique ability to enforce cloud policy controls at a granular level, enabling IT to move beyond a coarse-grained “allow” or “block” approach to cloud services toward enforcing fine-grained policies based on a variety of conditions including deep cloud context and the the associated activities and data. In this blog, I’ll walk you through the life of a cloud transaction to help bring this patent to life with a real-world example.

If you Google the term “life of a packet,” you get almost 50 million results, explaining everything from how routing works to the ins-and-outs of a SYN flood attack. For decades, a large part of our security conversation has been focused on network traffic.

Today, we are focused on cloud security. Forrester predicts that companies will spend more than $2 billion over the next five years to secure data in the cloud, while Gartner names cloud access security brokers its number one information security priority.

The cloud (and a lot of the web) has moved beyond the language of the network. Rather than speaking in HTTP gets, HTTP POSTs puts, and bytes up and down, the cloud and web speak the language of APIs. The beauty of APIs is – besides being incredibly useful for integrating services faster and more efficiently – they are reflective of the activities we actually do in the cloud. This means that when we view, share, download, upload, approve, edit, post, or create in a cloud service, we are actually doing those things via API calls.

So why are many security vendors (including some cloud access security brokers) still speaking that old language? At Netskope, we have perfected the skill of decoding this language, whether it’s being used in a sanctioned or unsanctioned app and whether it’s originating from a desktop, remote laptop, or mobile device. By decoding APIs, we’re able not just to see activities in a handful of sanctioned apps, but across all apps, as well as also ascertain a host of additional contextual metadata about users, devices, apps, times and locations, and content. Beyond decoding APIs, we also normalize them across cloud apps. When you “share” an object such as a file from a cloud app, that activity may result in different API calls depending on the app implementation. Even the wording could be different – it could be “share” in one app, “Create a share link” in another, and “Invite to collaborate” in yet a third. If you’re enforcing policy in just one app, that’s fine, but if you want to enforce a policy such as “Don’t share content outside of the company from ANY file-sharing app,” you need to set it at a category level to have it apply across the dozens of file-sharing apps you have running in your organization. That’s why not just decoding the “share” is important, but normalizing the “share” across many different types of apps is also critical.

Let’s look at the life of a cloud transaction in four simple steps:

We’ll start with a user login to a website or cloud app. In your proxy logs, that login activity consists of small byte transfers associated with a secure handshake and passing of credentials. But you can’t see this. In fact, those byte transfers could be a simple website visit or even a triggered tracking link in an app from a website the user visits when they didn’t even go to the app. In contrast, in the Netskope Active Platform, we tell you it’s actually a login. Moreover, we’ll give you all of the context about that login that you’d care about as an IT or information security professional: Who is the user? What enterprise directory group are they in or attributes are associated with their identity? What website or app are they logging into? What category of service is it? What is its risk level? Why is knowing the user activity and its context important? For one thing, a login versus a simple website visitation shows intent and signals the beginning of a transaction that you may care about. Also, context matters! What if the cloud app in question is your company’s benefits and payroll app containing sensitive information, and the user is not even in HR? What if the app is your payment authorizations app and subject to Sarbanes-Oxley, and the user has three failed logins? When you have context, knowing that the activity is an actual login becomes important.

Next, let’s look at a download. Your user just downloaded something from the website or app. In your proxy logs, that download looks like a series of HTTP “GETs” and has some “bytes down” associated with it. That GET could be the user accessing an important file or…a cat video. You don’t know. In a proxy log, a cat video can look similar to your mergers and acquisitions plan. In the Netskope Active Platform, we tell you not only that a download happened, but also what the downloaded object was (a file, report, database extract, etc.), its name, who downloaded it, to what device, on what browser, at what time and location, and whether the content is sensitive based on your DLP profiles, as well as take a hash of the content. We have done the work to determine not just what the activity “download” looks like in a single app, but across all apps because we have decoded the API and know what it looks like across thousands of apps. So, whether a user is downloading from a social media website, file-sharing, or business intelligence app, Netskope knows it’s a download and can tell you all about the transaction. Netskope can also help you stop it in its tracks with a real-time policy. But for this exercise, let’s assume you don’t and keep going…

Now, let’s take a look at an upload. Remember that download that just happened? Well, let’s assume it’s a highly sensitive document containing next year’s product plans, and that the user has just uploaded it to an unsanctioned, personal file-sharing app. In your proxy logs, that activity looks like a “POST” and has some “bytes up” associated with it. That’s useful if you care about bandwidth, but not so much if you care about security and want to follow up on suspected data theft incidents. Is that upload related to the download from before? You can’t tell. In fact, since you are unaware of the download in the first place, much less whether the content was sensitive, neither transaction would be on your radar. You’d be in the dark about whether there was content transferred at all, whether it is sensitive, and whether the download and upload transactions are related. In the Netskope Active Platform, since we take a hash of the file during download and know exactly who downloaded it and when, when the user re-uploads the same sensitive content, we know it and flag it for you. Now you’d know that a download occurred, followed by an upload of the same content, the fact that the content is sensitive, and you’d know who did it, as well as dozens of other details about the two transactions.

Finally, let’s look at a share. Remember that sensitive content upload? You know the one – next year’s product plans that were, just minutes ago, safely at rest in your sanctioned app. Well, guess what! The user just shared them with your company’s biggest competitor competitor. In your proxy logs, that share activity would have some very small bytes transferred up and down, and would completely fly under your radar. Not only would you not know it’s a share, but you wouldn’t even know to look for it because you didn’t even know the download nor the upload happened, and that they were related. In the Netskope Active Platform, since we take a hash of the file during download and know exactly who downloaded it and when, and the fact that it’s sensitive based on your DLP profile, when the user re-uploads the same sensitive content, we know it and flag it for you. Then, when the user shares it, we tell you that, as well as who they shared it with. You could even start with the share and ask to see all shares, or all shares with a particular competitor. We do this whether the share is in your sanctioned file-sharing app or a completely unknown, unsanctioned app in any category. Now you’d know that three related events happened: a download, followed by an upload, followed by a share of your most sensitive content…and shared with your primary competitor, no less! You’d know who did it, and have all of the context about the user, device, app, and content.

This is what it means to decode and normalize the language of today’s cloud – APIs – and to track the life of a cloud transaction from beginning to end.