This article discusses how to use the Access Overview page to analyze how remote users are connecting to the Cato Cloud across your account.
The Access Overview page lets you view and analyze data for remote access behavior of remote users. The widgets in the dashboard let you drill down and filter the data to analyze remote access data for the entire account. In addition, you can filter the data to drill-down and show usage for specific remote users.
When you manually create a filter or add an item to the update filter, the data and analytics on the Access Overview page is automatically updated.
The page helps you answer which of your accounts has:
-
How many SDP Licenses are available
-
If there are any unsupported Client versions in your network
-
How often your Always-On Policy is bypassed
-
Number of devices allowed or blocked by each Client Connectivity Policy rule
These are some examples of how you can use the Access Overview page to monitor remote access:
The company ABC is planning to add 400 new employees by the end of Q3. You can use the SDP User Licenses widget to check how many licenses are currently available, and determine if the company needs to purchase additional licenses for the account.
The company ABC is planning to implement a new access feature which is only supported for Windows and macOS Clients version 5.0 and higher. You can use the Windows Client Version and macOS Client Version widget to filter for the versions that are lower than version 5.0 and don't support this feature. Then you can contact these Remote users and tell them to upgrade to the newest Client version.
To show the Access Overview page:
-
From the navigation menu, click Access > Access Overview.
For more information about using the dashboard, see Configuring Filters to Analyze Dashboard Data and Setting the Time Range Filter. The maximum date range for the dashboard is 90 days.
The following table explains the widgets on the Network Access tab.
Name |
Description |
---|---|
Active Remote Users |
Total number of remote users actively connected to the Cato Cloud. This value isn't impacted when you change the time range or a filter. |
Remote Users Connected |
Unique remote users connected to the Cato Cloud over the past 7 days. This value isn't impacted when you change the time range or a filter. |
Remote User Licenses |
The percentage and number of remote user licenses used in your account (see above Monitoring Usage for SDP Licenses). This value dynamically updates based on the time range or filter. |
Remote Users Connected per Day |
Unique remote users connected to the Cato Cloud per day during the time range and filter. The local time zone of each user is converted to the time for the account. |
Remote Users per Country |
Users connected to the Cato Cloud per country during the time range and filter. Note: If a remote user connects to the Cato Cloud from two countries they are counted twice. |
Remote Users per PoP |
Remote users connected to the Cato Cloud per PoP during the time range and filter. Note: If a remote user connects to multiple PoPs, they are counted as a separate user for each PoP. |
Client Connectivity Policy Rules |
Devices Allowed or Blocked by each Client Connectivity Policy Rule during the time range and filter. Note: If the Client Connectivity Policy is disabled in your account, this widget is not visible. |
Device Posture Profiles |
Devices that have complied with each Device Posture Profile during the time range and filter. Note: If the Client Connectivity Policy is disabled in your account, this widget is not visible. |
Users Connected per User Confidence Level |
Remote users connected per authentication state during the time range and filter. If a remote user changed authentication state during the time range, they are counted twice. Note: If the Client Connectivity Policy is disabled in your account, this widget is not visible. |
Users Connected per Network Access Permission |
Level of access provided to each remote user during the time range and filter. If a remote user's level of access changed during the time range, they are counted twice. Note: If the Client Connectivity Policy is disabled in your account, this widget is not visible. |
OS Distribution |
Remote Clients per OS that connected to the Cato Cloud during the time range and filter. Use the drop-down menu to filter the widget for a specific OS. |
Client Versions (by operating system) |
Each widget shows the number of remote users that connected to the Cato Cloud using that OS Client version during the time range and filter. The dashboard has separate widgets for each Client OS used in your account, and only shows widgets for the Clients that have connected. For example, if only Windows and macOS devices are used for remote access, then only the Windows Client Versions and macOS Client Versions widgets are displayed. |
Remote Users |
Usernames for the remote users that connected to the Cato Cloud during the time range and filter (see above Identifying Unsupported Client Versions). |
If you have not enabled the Always-On Policy, no data is displayed in these widgets.
The following table explains the widgets on the Bypass tab.
Name |
Description |
---|---|
Always-On Bypass Methods |
Usage of each Always-On bypass method during the time range and filter. |
Bypasses per Day |
Always-On bypass events per day during the time range and filter. |
OS Distribution |
Always-On bypass events per OS during the time range and filter. |
Client Versions (by operating system) |
Each widget shows the number of Always-On bypass events using that OS Client version during the time range and filter. The dashboard has separate widgets for each Client OS used in your account, and only shows widgets for the Clients that have an Alway-On bypass event. |
Remote Users |
Usernames for the remote users that bypassed the Cato Cloud during the time range and filter. |
To further analyze remote users connections to the Cato Cloud, you can view the events for items within a widget. For example, you can view the events for all remote users connecting to the Cato Cloud on a macOS machine.
The Device ID is gathered for Clients connected hosts that are not in office mode. For Windows Clients this is the MAC address for the device. For macOS Clients this is the UUID of the device.
0 comments
Please sign in to leave a comment.