Zscaler Mac Download

Find Zscaler Inc software downloads at CNET Download.com, the most comprehensive source for safe, trusted, and spyware-free downloads on the Web. The Zscaler Events mobile app is the best way to stay connected to everything happening while you are onsite at a Zscaler event such as Zenith Live.

  1. Zscaler App
  2. Download Zscaler App For Windows

Use the Zscaler Analyzer app to analyze the path between your location and the Zscaler Enforcement Node (ZEN), or to analyze the time it takes for your browser to load a web page, so the Zscaler Support team can detect potential issues. The app performs an MTR (Z-Traceroute) and a full web page load test (Z-WebLoad). The results provide the Zscaler Support team with all the information they need to debug network issues quickly. You can run the app multiple times at different intervals, for a more comprehensive view of your network path and performances. For example, you can run configure the app to run every hour for five hours.

Zscaler

The results are designed to be sent to the Zscaler Operations Team through Zscaler Support for analysis. Their experience and overall view of the entire cloud allow them to interpret the data and identify potential issues in the network path. Zscaler highly recommends that you do not try to interpret the results without consulting Zscaler Support.

By downloading Zscaler Analyzer, You agree to the terms and conditions for Zscaler Software available at https://www.zscaler.com/legal/license-agreement-for-zscaler-software/. In addition, You also acknowledge and agree that Zscaler will
(i) use the information that You provide in order to troubleshoot Your networking issues; and
(ii) store such information in its cloud (which will only be accessible by a unique URL).

YOUR USE OF THE ZSCALER ANALYZER IS EXPRESSLY CONDITIONED ON YOUR AGREEMENT TO THESE TERMS AND CONDITIONS. IF YOU DO NOT AGREE, DO NOT DOWNLOAD AND/OR OTHERWISE USE THE ZSCALER ANALYZER.

Requirements

You can run the app from a device that has the following:

  • Java (JRE) 1.8 update 40 or higher
  • Microsoft Windows 7 or higher
  • Mac OS X
Installation

Do the following to install the Zscaler Analyzer app:

  1. Download the latest version of the app at https://zmtr.zscaler.com/.
  2. Click either Windows or Mac OS to download the app.
  3. Do one of the following:
    • From a Windows machine:
      1. Run ZscalerAnalyzer-windows-installer.exe.
      2. Complete the steps in the wizard.
        Ensure that you install the app in a directory similar to Libraries/Documents to facilitate installation. If you install it in the Program Files directory, you may need additional permissions.
        OR
    • From a device running Mac OS X or higher:
      1. Run ZscalerAnalyzer-osx-installer.dmg.
      2. Complete the steps in the wizard.

      NOTE: If your security settings prevent the you from installing the app on your Mac, do the following:
      1. Launch System Preferences from the Apple menu authentication.
      2. Choose Security and Privacy, click the General tab, and then click the lock icon in the corner to unlock the settings.
      3. From the Allow applications downloaded from list, choose Mac App Store and Identified Developers.
      4. Accept any security warning, if presented.
      5. Install the app.

Zscaler Analyzer TraceRoute

Use the Zscaler Analyzer app to analyze the path between your location and the Zscaler Enforcement Node (ZEN), so the Zscaler Support team can detect potential network issues. The app performs an MTR (My Traceroute) and the results provide the Zscaler Support team with all the information they need to debug network issues quickly. You can run the app multiple times at different intervals, for a more comprehensive view of your network path. For example, you can run configure the app to run every hour for five hours

The results are designed to be sent to the Zscaler Operations Team through Zscaler Support for analysis. Their experience and overall view of the entire cloud allow them to interpret the data and identify potential issues in the network path. Zscaler highly recommends that you do not try to interpret the results without consulting Zscaler Support.

If you are using a GRE or IPSEC tunnel to send traffic to the ZEN, the MTR must run from a PC that does NOT go through the tunnel. An MTR done through a tunnel will not show useful information.

Running Z-TraceRoute

When you launch the app, click the Z-TraceRoute tab to see a window similar to the following.

Do the following to run the Zscaler Network Analyzer app:

  1. Define the settings:
    • Host: If your computer is connected to a ZEN, this field displays the host name of the ZEN. You can specify a different host name, for example, if you want to analyze the path to another ZEN.
    • Run Every: The app can run automatically at different intervals. For example, to configure the app to run every hour, 10 times, change Repeat to 10, and then choose the interval to Repeat every 1 hour. These 10 tests are called a group.
    • Packet Count: Number of packets to send.
    • Hop Limit: The maximum number of network hops measured.
  1. To define the following settings, click the Advanced Settings button to see the Z-Traceroute - Advanced Settings window.
    • Data: Packet size in bytes
    • Timeout: The maximum number of seconds to wait for a reply
    • Command: You can configure advanced settings from this field if Zscaler Support requests that you override the default settings in order to better troubleshoot certain issues. To get the list of all options, run:
      Example:
  1. Click Start Test.
    • The app displays the geolocation of the client and the ZEN on the map, as shown below. Note that the locations shown may not be accurate. This is useful in determining if the client is geolocalized correctly or if its traffic is not going to the nearest ZEN.
    • The application updates the Host Latency and the Latency per Hop widgets, and the results table.
    • The Stop Test button replaces the Start Test button, as shown below. If you click the Stop Test button at any time, the app cancels all the other tests in the group.

You can minimize the Zscaler Performance Analyzer app before it completes all the configured runs. When the tool completes all the runs, the Start Test button replaces the Stop Test button.

Viewing the Results

If you configured the Zscaler Analyzer app to perform multiple runs, you can view the results for each completed run in the group by selecting it from the results list, as shown below.

  • The Host Latency widget shows the latency that occurred when the device reached the ZEN.
  • The Latency per Hop widget shows the latency for each intermediate network hop.
  • The results table provides an overview of the results. It shows the following:
    • #: Hop number
    • Host: IP address of the intermediate host
    • P. Sent: The number of packets sent to the intermediate host
    • P. Recv: The number of packets sent back by the host
    • P. Loss: Percentage of packet loss
    • Best T.: Smallest latency of all tests in seconds
    • Last T.: Latency of the last packet sent
    • Avg. T.: Average latency
    • Worst T.: Highest latency of all tests

Exporting the Results

When the app completes all the configured runs, export the results so you can send it to Zscaler Support.

  1. Click the Export All Results button and navigate to the folder to which you want to save the results. All results of the runs in a group are saved into a CSV file with a filename similar to za_results_12_15_2015_12_56_53_PM_PST.

The geolocation shown in the export file is likely to be incorrect. For example, the intermediate hops in the U.S. might be shown to be in Europe.

The following is the information displayed for each group (repetitions of the same test) in the CSV file:

  • Result Import Time: Time of the data export
  • ZA Version: Version number of the app
  • Group Number: Group ID
  • ZA Settings: The defined settings for the test
  • Host: Name of the host from which the test was run
  • Internal Source IP: Local IP address of the device
  • Public Source IP: Public IP address of the outbound traffic
  • Protocol: Protocol selected for the test.
  • Number of Runs: Number of tests run

The following is the information displayed for each run inside a group:

  • Run Number: Run ID
  • Start Time: Time when the test started
  • End Time: Time when the test ended
  • Test Finished in: Duration of the test
  • SNo: Results of the test for each intermediate host:
    • Host: IP address of the intermediate host
    • Longitude: GeoIP coordinate of the intermediate host
    • Latitude: GeoIP coordinate of the intermediate host
    • Location Name: GeoIP country of the intermediate host
    • Packet Sent: Number of packets sent to the intermediate host
    • Packet Received: Number of packets sent back by the host
    • Loss: Number of packets lost
    • Last Time: Latency of the last packet sent
    • Best Time: Smallest latency of all tests
    • Worst Time: Highest latency of all tests
    • Avg Time: Average latency
    • St Dev: Standard deviation
Zscaler Analyzer WebLoad

Use the Zscaler Analyzer app to analyze the time it takes for your browser to load a web page, so the Zscaler Support team can detect potential issues. The app performs a web page load test and the results provide the Zscaler Support team with all the information they need to debug issues quickly. Depending on your environment, the tool can compare the load time through a ZEN and load time going direct to Internet. You can run the app multiple times at different intervals, for a more comprehensive view of your network. For example, you can configure the app to run every hour for five hours.

Do the following to run WebLoad on the Zscaler Analyzer:

  1. Define the settings:
    • Load: The app can test up to ten URLs at a time. The app provides a default list of URLs to run. You can choose to run the tests for all URLs or just one. To remove or add a URL, click on the Advanced Settings button.
    • Every: The app can run automatically at different intervals. For example, to configure the app to run every hour, 10 times, change Repeat to 10, and then choose the interval to run Every 1 hour. These 10 tests are called a group.
    • Use: The Page Load Time widget provides different results depending on your environment when you first open the app.
      • If your traffic is going through the Zscaler service when you first start the app, you are running the app with the Zscaler Enforced Proxy. If you are not authenticated to the service, you may be asked to authenticate when the app is first opened. The authentication page is displayed in the Current Site Preview on the left.
      • If your traffic is not going through the Zscaler service when you first start the app, you can choose the following options in the list:
        • System Proxy: Choose this option if you want to use your Internet browser settings. For example, if you have configured your browser to use a PAC file or a ZEN, the app will use those settings.
        • Custom PAC File: Choose this option if you want to use a PAC file to forward your traffic to the Zscaler service. The Zscaler service hosts default PAC files which are configured to automatically forward all browser traffic to the nearest ZEN. To learn how to retrieve the default PAC file URL, see How do I use PAC files to forward traffic to the Zscaler service?
        • Custom Gateway: Choose this option if you want to specify a ZEN to which you want to forward your traffic.
          • To specify a ZEN, enter the following:
            • Gateway: Enter gateway.<cloud_name>. To learn how you can find your cloud name, see What is my cloud name?
            • Port: Enter the port number.

If you choose to run the app with a Custom PAC File or Custom Gateway, you will be prompted to authenticate before you can start the test. The results table will provide results in the following categories:

  • With Proxy: Your traffic is going through the Zscaler service
  • Without Proxy: Your traffic is not going through the Zscaler service

To define the following settings, click the Advanced Settings button to see the ZWebload - Advanced Settings window.

  • Edit Website(s): To remove a URL, choose a URL, then click the minus sign.
  • Type New URL: To add a URL, enter a valid URL into the field, then click Add Website.
  • Website Download Count: The number of times each website is downloaded.
  1. Click Start Test.
    • The app displays the web pages of the URLs in the list, as shown below.
    • The application updates the Page Load Time widget, and the results table.
    • The Stop Test button replaces the Start Test button, as shown below. If you click the Stop Test button at any time, the app cancels all the other tests in the group.

You can minimize the Zscaler Analyzer app before it completes all the configured runs. When the tool completes all the runs, the Start Test button replaces the Stop Test button.

Viewing the Results

If you configured the Zscaler Analyzer app to perform multiple runs, you can view the results for each completed run in the group by selecting it from the results list, as shown below.

If you configured the Zscaler Analyzer app to test multiple URLs, you can view the results for each URL in the group by choosing Website from the Show Results For list.

  • The Page Load Time widget shows how long it took your browser to load a web page.
  • The results table provides an overview of the results. It shows the following:
    • Time Stamp: The time when the test started
    • Website: The tested URL
    • Response Time: The average time it took the browser to load the main web page

Exporting the Results

When the app completes all the configured runs, export the results so you can send it to Zscaler Support.

  1. 1. Click the Export All Results button and navigate to the folder to which you want to save the results. All results of the runs in a group are saved into a CSV file with a filename similar to za_results_12_04_2015_09_49_51_AM_PST.
  2. Attach this file to a support ticket and submit it. The export file contains all the information required by the Zscaler Support team to interpret the results correctly. Please do not modify the file before sending it to Zscaler.

The following is the information displayed for each group (repetitions of the same test):

  • Result Import Time: Time of the data export
  • Tool Version: Version number of the app
  • Group Number: Group ID
  • WebLoad Settings: The defined settings for the test
  • Number of Runs: Number of tests run
  • Proxy Type: Name of the proxy from which the test was run
  • Gateway Name: Name of the gateway from which the test was run
  • Gateway IP: IP address of the gateway from which the test was run
  • ZEN: The Zscaler Enforcement Node from which the test was run

The following is the information displayed for each run inside a group:

  • Run Number: Run ID
  • Start Time: Time when the test started
  • End Time: Time when the test ended
  • Test Finished in: Duration of the test
  • SNo: Results of the test for each immediate host:
    • URL: The tested URL
    • URL IP: IP address of the URL tested
    • Load Count: The number of times the URL was repeated
    • Response Code: The HTTP response code for successful or failed requests
    • DNS Time: The time it took client to contact DNS server
    • Connect Time: The time it took browser to connect to the server
    • Full Page Time: The time it took the browser to load the entire web page and all its assets, such as images, scripts, etc.
There is no doubt we truly live in an “App Economy.” From personal to professional, we direct and live our lives through our smart phones. But while we enjoy the latest games, stream the latest content or catch up on our friend's activities, few think about the “App Dichotomy”– The fact that we are at least as much the consumed, as we are the consumer. This is the first in a pair of blogs that break down and analyze the access we grant to our personal information, behaviours and tendencies when we download an App, and the security and privacy risks that result.
First, we will examine the privacy/security profiles of the most popular iOS apps in the Apple App Store. Apple of course presents an image of a walled and pristine garden where users are safe unless you “bite the apple” and jailbreak your device, exposing it to the evils of unapproved apps. Apple also holds an advantage over Google/Android in that it offers more granular allow/deny control over specific permissions, while still allowing a user to download and use an app. However, it’s well understood that many users do not scrutinize the permissions requested regardless of choices. And for those who do, even with a cursory review, do they understand what they grant when they click “allow”?
Zscaler to date, has analyzed the top 550 most popular iOS apps, via static analysis techniques, specifically tracking permissions for access to functionality such as: the address book, telephony information (carrier, country code, SIM card info., etc.), user geo-location, calendar, email and unique identifiers. One difference in the approach that we’ve taken, in contrast to previously published statistics that we’ve seen, is that we looked for the express use of various functions to determine that an app actually required specific levels of access. We often see stats based on only the inclusion of a framework within an app. While including the framework provides the app with the ability to access specific functionality, it is common for developers to be aggressive with the frameworks that they include but never actually leverage the functionality.There are many interesting findings in the data, but two findings that we found especially concerning were:
  • 38% of applications still have access to the now infamous UDID identifier, that was the center of the AntiSec leak in 2012, and since which time, Apple has banned access. Access to UDIDs is a concern because developers could track user behaviour across multiple apps to track unique user. Developers and ad networks may also map UDIDs to user's sensitive information like mobile numbers,name passwords, locations and other information.
  • In excess of 60% of Game and Entertainment apps request permission to telephony functions (service provider information and current call information) and geo-location.This is of course more of a privacy concern, than security, but troubling nonetheless. This concerns are important as previously some issues came to light regarding spying on leaky apps.
Zscaler

Zscaler App

One last item before we dive deep into the analysis that we feel is compelling to point out, is that – somewhat ironically – we had to jailbreak the devices. This was necessary in order to access the applications in their running state, and then identify various functions called by the apps to understand the access permissions that they require. This increases the value and validity of these stats, and in some cases calls into question the accuracy of some of the iOS stats that we've previously seen. Most are based on simply seeing a framework being imported (potential use) vs what we did which was look for the use of individual functions (actual use).
So, on to the analysis. We have compiled stats for:
  • Address book functionality - Provides a programing interface to the Address book in order to allow an application to access the Addressbook database
  • Telephony data information - Provides details on usage of the core telephony framework’s methods, which include access to the cellular service provider information like the cellular service carrier and current call information
  • Location tracking - Allows apps to determine user’s current location or heading
  • Email Functionality - Usage of the MFMailComposeViewController class’s methods, which provide a standard interface to manage the editing and sending of email messages. With this access, an app would not be able to send mails independently, without user involvement. The app would also not be able to read a user's email.
  • Calendar data - Allows applications to read/write from/to Calendars, Events and Reminders.
  • UUID - Apps can access UUIDs (Universally Unique Identifiers), also known as GUIDs (Globally Unique Identifiers) or IIDs (Interface Identifiers), which are 128-bit values designed to be unique per device.
The following overall results were derived from static app analysis:
Below we see the percentage of applications which are trying to use social media and ad networks.
47% of applications are found to be linked to social networks. We have observed Facebook, Twitter and Instagram as most common social networks used by apps.
Download
75% of applications are found to be linked to advertisingnetworks. This is not a surprising finding given that all of the apps analyzed were free apps and most have a monetization strategy driven by advertising.
Apple is pushing developers to stop using the unique identifier (UDID) embedded in iPhones and iPads and started rejecting apps that gather UDIDs after May 2013. App developers were warned not to use the “uniqIdentifier”, although it seems that some developers have neglected these warnings. Developers rely on the UDID value to track user activity for targeted advertising and troubleshooting. Since Apple is prohibiting the option to use the unique identifiers, companies are looking for new ways to keep tabs on users while avoiding personal privacy concerns. As an alternative to UDIDs, Apple has instead introduced the UUID (Universally Unique Identifier) created by CFUUIDCreate method, which we will explain below. Since these changes were implemented, developers are now trying to track the user in the following ways:
  • The UDID is tied to the device hardware and no longer permitted by Apple. Apple started rejecting apps which requested the UDID string, although a few legacy apps still exist which use this method.
  • The UUID, Apple’s preferred approach is a unique value per app and device. This limits privacy concerns as the user cannot be tracked across apps on a given device. One additional limitation of the UUID is that it is created when the app is first installed and, if the user re-installs the app, a new UUID will be created. In order to get around this limitation, developers are storing the UUID in the user’s keychain to make it persistent across app installs.
  • A final option involves querying the MAC address of device. Apple is also now prohibiting the use of MAC addresses tracking. Apple will now reject apps where developers query the MAC address. Additionally, starting with iOS 7, Apple now always returns a fixed value when querying the MAC address to specifically prevent the MAC as base for unique identifier.
Here are some UDID vs. UUID statistics we derived from our scanned applications.
We have found 38% of legacy applications are still using the UDID “uniqIdentifier” string which is no longer permitted by Apple. Apple is pushing very hard to ensure that only UUID values are now used in place of UDID and MAC addresses.In support of that, we can see that 92% of apps are now using UUID values to track users.
The following details the results of five permission categories from the iTunes store for the top 25+ applications in their respective categories.
In the Games category, we have found that 28% of apps are accessing Address book functionality, 68% of apps are using telephony information, 76% of apps are trying to use the user’s location, 64% apps are using the Email framework and 60% of apps are asking for calendar access. Also, 84% of games are leveraging UUID’s for tracking user activity for targeted advertising.
In the Entertainment category, we have observed 20% of apps trying to access address book functionality, 75% of apps are asking for telephony data, 86% of apps are using location APIs to track a user’s location, 88% of apps are using the Email framework and 70% of apps are using calendar data. Additionally, 97% of apps are using UUID’s for tracking.
In the Social Networking category, 92% of apps use address book functionality, 72% of apps are asking for telephony information, 96% of apps are using location APIs and the Email framework, while 54% of apps are accessing calendar functionality and 96% of apps track via UUIDs.
In the Lifestyle category, 59% of apps were found to be accessing the address book, 81% of apps are using telephony data, 85% of apps are using the location and Email framework, 51% apps are accessing calendar functionality and all apps scanned were found to be accessing UUIDs.
In the Travel category, we observed 54% of apps with access to the address book, 58% of apps have telephony data access, 92% of apps have access to location information, 77% of apps are using email and 61% of apps are using the calendar framework. Additionally, 92% of apps are leveraging UUIDs.
With 97% apps using at least one of the functionalities being tracked (address book, telephony, location, email calendar or UUID), as stated, we are being consumed as much, if not more, than we consume. In and of itself, this is not a danger. However as threats – and even business practices – evolve, the risk profile of access changes with it. In the case of our findings, while Apple has stated otherwise, it is clear that some developers significantly overreach in permissions requested. And while some “risks” still live inside gates – for example access to Social Media still requires express user permission for an app to post, etc., -- as also stated earlier, many users are click happy and indiscriminate with that permission. I’ll leave you with a specific access and risk analysis for one app, Draw Something Free.
To avoid security and privacy problems, more knowledge about mobile app risk is necessary. As organizations are moving forward with BYOD, infrastructure knowledge of app behaviors helps to avoid security and corporate privacy risks – from location tracking of executives to leaking corporate data.
Users and IT always must remain vigilant and aware regarding installed app behaviors. Consider the necessity of any functionality requested by an app before you allow it. For example, why does any game app need to access your address book? Should an app for kids really be asking for geolocation? Awareness among users about how much access is granted to particular apps is the only way to build the stronger defense against future mobile threats.
Application: Draw something free
Methods identified in the decompiled source code for respective areas of functionality:
  • Address book access:
  • ABAddressBookCreate
  • ABAddressBookGetAuthorizationStatus
  • ABAddressBookRequestAccessWithCompletion
  • ABAddressBookSave
  • ABAddressBookAddRecord
  • ABAddressBookRemoveRecord
  • ABRecordGetRecordID
  • ABRecordGetRecordType
  • ABRecordSetValue
  • ABRecordCopyValue
  • ABRecordRemoveValue
  • ABRecordCopyCompositeName
  • ABPersonCreate
  • ABPersonGetTypeOfProperty
  • ABAddressBookGetPersonWithRecordID
  • ABAddressBookCopyArrayOfAllPeople
Telephony Information:
  • carrierName
  • carrierName
  • mobileCountryCode
  • mobileNetworkCode
Location Access:
  • locationManager:didUpdateLocations:
  • locationManager:didUpdateLocations:
  • locationManager:didFailWithError:
  • locationManager:didFinishDeferredUpdatesWithError:
  • locationManager:didUpdateToLocation:fromLocation:
  • locationManagerDidPauseLocationUpdates:
  • locationManagerDidResumeLocationUpdates:
  • locationManager:didUpdateHeading:
  • locationManagerShouldDisplayHeadingCalibration:
  • locationManager:didEnterRegion:
  • locationManager:didExitRegion:
  • locationManager:monitoringDidFailForRegion:withError:
  • locationManager:didStartMonitoringForRegion:
  • locationManager:didChangeAuthorizationStatus:
  • initWithLatitude
  • horizontalAccuracy
  • verticalAccuracy
Email access:
  • SetSubject
  • setToRecipients
  • setCcRecipients
  • setBccRecipients
Calender access:
  • defaultCalendarForNewEvents
  • removeEvent
  • saveEvent
Unique Identifier (UUID) access:
  • uniqueIdentifier
  • CFUUIDCreateString
  • CFUUIDCreate

Download Zscaler App For Windows

Ad network related URLs found in source code:
Zscaler Mac Download
  • http://www.flurry.com/resources/privacy/reengagement.html
  • http://www.googleanalytics.com/__utm.gif
  • utmwv=4.4mi&amp;utmn=%d&amp;utmt=event&amp;utme=5
  • http://www.google.com/OAuthCallback
  • http://www.googleadservices.com/pagead/aclk
  • https://data.flurry.com/aas.do
  • https://et.w.inmobi.com/user/e.asm
Social Network related URLs found in the source code:
  • http://twitter.com/WeDrawSomething
  • http://www.facebook.com/playdrawsomething
  • https://api.twitter.com
  • https://api.twitter.com/1/statuses/update.json
  • https://api.twitter.com/oauth/access_token
  • https://api.twitter.com/oauth/authorize
  • https://api.twitter.com/oauth/request_token
References:
https://developer.apple.com/library/ios/navigation/
http://techcrunch.com/2013/06/14/ios-7-eliminates-mac-address-as-tracking-option-signaling-final-push-towards-apples-own-ad-identifier-technology/

Author

Recommended for You