To maximize protection using SDX, you could try few tips from us below:
1. Use API together with Enveloper if an enveloper exists for your resulting file format. This is a very basic rule. Because our enveloper is already equipped with some anti-debugging and obfuscating methods to prevent common newbie hackers to give up hacking the program. Only using enveloper is also not recommended, because once a hacker can break the enveloper protection in other program, they can also break yours.
2. Call dongle APIs in a LOT of places in your application. For example when first start up, when opening a file, when a dialog box opens, and before processing any information. Also maybe do some random checking even when there's nothing done at all.
3. Use more than one function to protect a program. Do not just only use find function to look for a plugged dongle.
4. Use the encryption functions available in the dongle and tightly bind it with your software to make sure no one tampers with any of your data.
5. Use multiple dlls/libraries (if applicable) to call dongle functions. In case one dll is hacked, then there are still other parts of the software that uses the functions from another dll. For example, copying sdx.dll to print.dll, open.dll, and other names, then define the function calls from each dll with different names.
6. If you use a dll file to call dongle functions, bind it together with the executable. There are quite some programs capable of doing this; for example PEBundle.
7. For increased security, use a system where the information of PC specifications that can run the software is stored in encrypted form inside the dongle, and the application checks it before doing any job. But this method makes the software totally locked to the PC. Even changing one of the hardware might make the software stop running.
8. Alter protection method for every new version of the software released. This way even if the old version is hacked, the newer one is still fine.
9. Use random checking. For example, just 3 out of 10 checks to the dongle is really confirmed. This is to make the hacker have a hard time deciding whether his hacks work or not.
10. If possible, store a part of "script" that your program can run inside the dongle. For example, storing steps on how to calculate interest rate. This script must be used and interpreted by the program to calculate interest rate. If the program fails to find the script in the dongle, then the program can just output a wrong result.
