PreEmptive Protection™ DashO™ uses multiple layers to protect your software. Each layer contributes to an overall protection strategy. If an attacker compromises one layer, the other layers continue to provide protection.
Obfuscation Transforms
DashO applies obfuscation techniques to Java bytecode to make reverse engineering difficult or impossible.
| Protection | What it does | Common use |
| Renaming (Standard Mode only) | Replaces meaningful type, method, field, and property names with less meaningful names. | Make decompiled code harder to understand. |
| Control Flow | Changes the structure of method bodies while preserving application behavior. | Make decompiled logic harder to follow. |
| String Encryption | Encrypts selected strings and decrypts them at runtime. | Make sensitive strings harder to find through static inspection. |
| Resource Encryption | Encrypts resources packaged in an app or library, making it more difficult to copy or alter them. | Protect embedded and satellite resources from unauthorized extraction or modification. |
See the individual feature articles for more information.
Runtime Protection
DashO includes checks that run while your protected software runs. When the software detects an attempt to tamper with or reverse-engineer it, or detects that it is running in an unsafe environment, it can respond with custom logic.
| Check | What it detects | Common use |
| Tamper Check | Changes that may indicate the application has been modified. | Respond when the protected application appears to have been altered. |
| Debugging Check | Debuggers attached to the protected application. | Respond when someone tries to debug the application. |
| Root Check | Rooted Android devices. | Respond when an Android app runs in a rooted environment. |
| Emulator Check | Application being run on an emulator. | Respond when an Android app runs in an emulator. |
| Hook Check | Hooks on an application. | Respond when an Android app triggers a hook. |
| Shelf Life Check | Application use after a configured date or time period. | Limit use of time-sensitive builds, demos, or evaluation versions. |
When a Check detects a configured condition, it can trigger a response such as terminating the application, throwing an exception, or invoking custom application logic.
Always test both the normal case and the detected condition before release.
See Checks Overview for more information.
Additional Protection and Optimization
DashO also provides features that strengthen application protection or improve application performance.
| Feature | What it does | Use it to |
| Removal (Standard Mode only) | Removes unused code, constant definitions including string literals, and metadata from protected assemblies. | Reduce application size and reduce the attack surface. |
| PreMark™(Standard Mode only) | Embeds a custom marker into an application. | Identify a specific build or protected application. |
| Optimization (Standard Mode only) | Speeds up your code and reduces resulting binary size. | Reduce application size. |
See the individual feature articles for more information.
Configure Protection
Configure DashO protection features through the DashO GUI.
You can also configure check-related features through code annotations. If needed, you can manually edit the .dox configuration files.