Skip to main content
Skyhigh Security

Security Service Edge 6.0.0 Release Notes

The Skyhigh Security Service Edge 6.0.0 release enhances existing features and resolves issues.

NOTE: Every release is cumulative and includes all features, enhancements, and fixes from the previous release.
 

New or changed

These enhancements are provided.

  • Logging Client — Several functions of this tool, which supports your log management, have been modified. 
    • Use of Log4JS — The tool uses this logging utility now, which means that the following applies:
      • Debug logs are available under ... \Users\pb\AppData\Local\logging_client\app-1.0.6\logs.
      • The size of a log can be up to 3 MB. When this limit is reached, a backup file is generated. The maximum number of backup files is 10 for the log-service.log and the syslog-service.log and 5 for the process.log.
    • Configuration files moved to SQLite — The configuration files for storing timestamp and queuing information have been moved to this database. The name of the database file is configuration.db. It is available under ...  \Users\pb\AppData\Local\logging_client\app-1.0.6.
      IMPORTANT: Do not access the database file while the logging process is still going on.
    • Temporary syslog storage — When logs are sent on as syslogs, they are temporarily stored in a folder named pending-events. This folder is generated under ... \Users\pb\AppData\Roaming\logging_client. When all logs have been sent, the folder is cleared.
  • End User Notification Page templates updated — The templates for the pages that are sent to end users when their requests for web access have been blocked, have been updated to include more information about the blocking. You can view the updated templates after clicking Publish on one of the pages that are provided on the user interface for configuring your web policy.

Resolved issues

This issue was resolved together with others that were related to internal matters.

Reference Description
UCEWP-611 An issue with inappropriate values that were returned for ongoing processes has been resolved by implementing a fix that made the Client.ProcessExePath  property work as expected again. This property is for use in a Hybrid solution where Client Proxy is also running. Its value is the path to an .exe file that enables a process, for example, ...\program files (x86)\google\chrome\application\chrome.exe. You can include this information in end user notification pages, also known as block pages.

Known issues

For information about issues that are known and not resolved yet, see Known Issues for Security Service Edge (formerly: Unified Cloud Edge)

  • Was this article helpful?