cloudOS x unifiedKeys

With the introduction of Environment Protection in unfiedKeys 1.3, we have now expanded it with the introduction of Project Integrity Protection with unifiedKeys 1.4b (for tokenKey and activeKey) and expanding it even more with unifiedKeys 1.4c for tokenKey & activeKey.

With unifiedKeys 1.4c, Project Integrity Protection is now expanding to be cloud-based! By leveraging the real-time processing of cloudOS 2, we are now able to validate the project's integrity off-device, preventing potential cracking of the software on-device.

Disclaimer: If you obtain unifiedKeys software legitimately & the software is being ran in a secure environment/environment that is trusted by the software, PiP will not connect and authenticate the software. This is only if the software happens to be cracked/unpackaged and attempted to be edited.

This obviously needs an internet connection. If an internet connection isn't detected, it will fall back to a local-based Project Integrity Protection that is present in unifiedKeys 1.4b.

If an internet connection is present, your device will first check if tokenKey or activeKey is running in a secure environment, or an environment that is trusted by the system. If it's not running in a secure environment, it will send a device ID that can be aggregated (cannot be identified to you, as an individual, specifically), but can be identified to your device.

Your device ID is not being logged or kept in a server, but request attempts to the server will be logged but will not contain any information, just that a connection to the server was attempted. Your device ID will be processed, but not stored for any longer than 5 seconds.

On the server side, it will compare the value sent from your device and compare it to the trusted device IDs on the server.

 The unique feature of our implementation is that updating the trusted device ID list does not require an update on the user side, and access can be revoked in as little as 5 seconds, and pretty much creates a kill-switch for tokenKey and activeKey in the event that security is breached.