Latest update: 2020-01-10
Safetica does not work correctly with Windows apps
Selected Safetica features may not work correctly with Windows apps (Metro/Modern/Windows Store applications)
Safetica performs application injection in order to allow visibility and control over applications. Windows apps (formerly also known as Metro/Modern/Windows Store applications) differ from classical Windows desktop applications and run within special operating system components. Due to this, they cannot be injected as easily.
Safetica capabilities that require application injection, e.g. DLP policy restrictions, will therefore not work for such applications.
You can block undesired or risky Windows apps using the Application Control feature available in the Safetica Supervisor, alternatively also in WebSafetica.
Safetica does not work on Windows 10 Enterprise with Device Guard and Credential Guard enabled
Safetica does not log or protect on Windows 10 Enterprise systems which have Device Guard and Credential Guard turned on.
Windows 10 Enterprise offers new optional security features Device Guard and Credential Guard.
As of version 9.4, Safetica is not compatible with these features, as they break Safetica’s system integration processes and prevent it from running properly.
Turn off Device Guard and Credential Guard on affected devices.
Connection protocol details missing for Google Chrome
Web site activity logged in Google Chrome lacks protocol specification (HTTP/HTTPS)
Google Chrome 76 (July 2019) and later versions changed the default setting to not showing the web site protocol “http(s)://” for URLs. This change cannot be reset using configurable flags and Safetica can therefore not force Chrome to show the protocol prefix.
Without the protocol included in the web browser’s address bar, Safetica is unable to determine the protocol and therefore cannot log it.