It has improved the organization's PCI compliance with data loss prevention.

Our organization is moving much of its non-sensitive data to Box and we needed the ability to have full visibility into what was occurring within the Box infrastructure. With the Skyhigh to Box API integration, we can not only see everything that occurs but we can setup many DLP policies to block or monitor what is occurring in Box. You can also run a custom DLP query against your Box infrastructure to look for specific DLP issues that may have been created since the older data was loaded.

We have gained a deep insight into our Shadow IT usage as well as the different activities involved in Office 365. Without Skyhigh, we had zero visibility, but now we are aware of so much more.

It has given us visibility into our employees activities and access to cloud apps.

Once implemented we were able to identify 100+ high risk cloud services used by our users.  Once identified we worked with our users to migrate their data to IT sanctioned services, then blocked all high risk services.

I actually had an encounter with a government entity. They had a lot of their staff leaking government data, and they were using a website, a known website called WeTransfer. It's a Chinese website that's used to transfer big files without you needing to create an account. Users in the company were basically, whenever they wanted to transfer files, doing it through this site and unintentionally leaking data.

This week, the POC installed the McAfee web gateway, integrated the MVISION Cloud, and got insights. A lot of their business was done on WhatsApp within their systems. An yet, until this moment, they had no visibility over this. Now they have it. Now they know, and they can initiate changes.

We now have a good conscious about using Cloud services. Without an overview, you can only imagine what is going on. With monitoring, analysis and threat prevention, we know exactly what is going on and can prevent activity that we deem unacceptable or creates unnecessary risk. We have a much better overview of where our data is, both in terms of which service, but also in terms of geographical location.

It monitors the cloud usage of our company and shows the status on the main dashboard. There, we can see what kind of cloud applications are being used and see a risk assessment for each one, indicating low, medium, or high. For each cloud application, we can see how many users are using it. It's like auditing for each cloud application. In that way, it gives in-depth visibility and a granular monitoring facility for the company: What is happening inside the company, what people are using, what kind of data is going through the company. It really helps in understanding cloud traffic.

It gives us visibility into how the data is being used within our cloud environment. It shows the flow of information, and in our case, it has to with documentation that is restricted. For example, if a document contains credit card information or social security numbers then we are able to track it when somebody tries to delete them or do something else that is prohibited. We get flagged, which is the key. It enhances the visibility of what's in our cloud environment.

We are able to identify the high-risk websites and block them before the end users start using them to ensure that a business case is made for unblocking a high-risk site (rather than having to run interference after the fact). It also allows us to suggest other alternatives and safer services to the end user.

It has allowed insight into gaps that may exist in current web proxy tool policies. Improves creation of security alerts on web proxy logs by having a separate system interpret said logs.

Having full control of infrastructure.

Provides quite a bit of visibility into cloud services being utilized in our environment. I've been able to take the data available in Skyhigh and create discussions about whether we should be allowing or blocking certain services. This has also allowed us to start developing policies/procedures around new services which get introduced into our environment.

It’s a small improvement; however, it has augmented the pre-existing network monitoring services already in place to something more meaningful for higher levels of management.

We were able to analyse our user activity, which helped us to identify the associated risks.

• Identification of user activity
• Login information

It help us monitor high risk services, blocking them, and also feeding them to our egress points.

We are able to see what cloud services are being used with much more clarity than with our proxies and more importantly identify that we are using many cloud services we were not aware were even cloud services. Especially collaboration services. The cloud risk registry has been great for getting a quick and clearer understanding of the risk of proposed services that we are looking at allowing. Previously we were paying for expensive industry reports.

Our organization is moving much of its non-sensitive data to Box. We needed the ability to have full visibility into what was occurring within the Box infrastructure, from Skyhigh to Box API integration.

The user activity identification improved.

We are able to see what cloud services are being used with more clarity than with our proxies. More importantly, we can identify that we are using many cloud services in which we were not aware that they were even cloud services, especially collaboration services. The cloud risk registry has been great for getting a quicker and clearer understanding of the risk of proposed services that we are looking at allowing. Previously, we were paying for expensive industry reports.

Finally, anomalies are key players to identify the intruders in an organization.

• Malware and spam mails
• Attacks from hackers
• Data privacy

High-risk services.

It makes our work easier.

To analyse cloud traffic.

High-risk services