Enhancements
- Enhancements
- System
- Added ability to sync to Cyfin Cloud in addition to CyBlock Cloud.
- System
CyBlock Cloud customers are assigned 5 licensed additional logon accounts by default.
If you have reached your limit and wish to add more logon accounts, please contact Technical Support at (321) 953-5351, Ext. 4 or support@wavecrest.net.
CyBlock Cloud utilizes gateways located in data centers in the U.S., U.K, and Canada. Users are provisioned on a proxy close to their geographical location to ensure the best performance as well as delivery of appropriate regional content.
This article describes how to resolve the possible problem of Google assigning an incorrect geolocation to your Google searches. If this happens, Google is detecting your egress IP address or the source IP address of your request incorrectly. This is an issue for any multiregional cloud provider as well, not only Wavecrest, and there seems to be no easy solution.
You may experience one of the following issues:
Wavecrest has extensively researched this issue and found it to be Google’s geolocation algorithm. This issue affects any cloud service vendor that covers customers across multiple geographical regions. We continue to communicate with Google, but so far they are unwilling to change their algorithm. We suggest the following:
Please note that the suggestions in this article reduce the likelihood that these issues will occur, but they may not completely resolve them and are not as a result of a Wavecrest issue.
If you need assistance, please contact Technical Support at (321) 953-5351, Ext. 4 or support@wavecrest.net.
In Wavecrest reports, dates and times are displayed in several places, such as in the Report Request Parameters–Current Date/Time, Report Start Date/Time, and Report Stop Date/Time. In addition, in Audit Detail reports, all hits including visits have a date and time associated with each URL that is displayed.
For cloud customers who are using a CyBlock Cloud instance that is not located in their local time zone, the dates/times in reports are specific to the time zone set in your cloud account, that is, the time zone in which your Web activity is occurring.
For example, if you are in Pacific Time, running a User Audit Detail report for the selection, Previous 24 Hours, and going through central.cloud.cyblock.com which is in Central Time, the URLs in the report would have times of your local time if this time zone is set in your cloud account. So if the date is Sep 11 and your local time is 11:02 a.m., “Previous 24 Hours” would be Sep 10, 11:00:00 a.m. to Sep 11, 10:59:59 p.m. in Pacific Time, and the URL times would span this time period.
The dates and times in the report e-mail will also reflect the time zone set in your cloud account.
For Hybrid cloud customers, reporting is based on your local CyBlock instance time. Reports will show all traffic as it occurred in the time zone of each of your cloud accounts for the same local CyBlock instance time. When running reports for all cloud accounts, managers can see traffic for all time zones at the same time and hour.
For example, if your local CyBlock instance time is Eastern Time, cloud Web activity is in Central Time and Mountain Time, and you are running a Site Analysis report for 10:00 a.m. for all configurations, the report will show 10:00 a.m. Central Time traffic and 10:00 a.m. Mountain Time traffic.
If you have any questions, please contact Technical Support at (321) 953-5351, Ext. 4 or support@wavecrest.net.
If you are a CyBlock Cloud customer, you probably want to allow your cloud users to access secure sites (https://) and need to inspect this HTTPS traffic to ensure that your network is protected from Web threats and to enforce your AUP. The SSL Inspection feature in CyBlock Cloud allows you to inspect this HTTPS activity, but requires that you install the Wavecrest root certificate on your cloud users’ browsers. If the Wavecrest root certificate is not installed in the browser, a certificate warning message will be issued that must be accepted in order to display your blocking message.
Another reason to install the Wavecrest root certificate is if using cookie authentication to confirm the identity of users accessing the Internet through your network. The cookie authentication logon page that is presented to your users is a secure page and is automatically inspected. Therefore, to avoid your users receiving a certificate error, install the certificate on your users’ browsers.
The certificate may be installed in the following ways:
The Wavecrest Certificate Installation Guide provides instructions on installing the certificate using Internet Explorer/Google Chrome and Firefox, importing it using Active Directory, and installing it in Windows 7 Professional/Enterprise.
If you need assistance, please contact Technical Support at (321) 953-5351, Ext. 4 or support@wavecrest.net.
The following link provides information on bypassing proxy connections in AnyConnect: