SCRAMBLECODE is based on the High-level VM Security scheme, although it adds a lot more. This is described more thoroughly elsewhere, but here is a short recap:
SCRAMBLECODE works with thousands or even millions of encrypted memory events and keeps the number of decrypted variables at a bare minimum at any given moment. It furthermore randomizes the memory storage and encryption schemes to fulfill the resilience-condition of uniqueness - not only for each application - but for each execution.
This provides very strong protection and an extremely low risk of failing badly.
SCRAMBLECODE is completely self-contained and self-reliant. This makes it ideal for being used in combination with other security schemes without imposing any demands on the underlying architecture or setup.
SCRAMBLECODE also combines multiple self-reliant security schemes internally to ensure an attack on one protection aspect won't severely affect the others.
SCRAMBLECODE is designed to execute in untrusted environments and be applicable for software, that risk being downloaded and dissected on systems controlled by a cracker.
If other security technologies are used and these for some reason fail, the integrity of the operating system may have been compromised to an extent comparable to the state of the previously described untrusted environment, making SCRAMBLECODE an ideal last resort for protection that won't fail with the others.
SCRAMBLECODE may also serve as a "fall-back" plan in case a security scheme can't be used due to missing features of the underlying architecture or setup - e.g. when a solution is installed on a legacy system.