Frequently Asked Questions

How it works: DN Shield monitors for debugger attachment and blocks step-through analysis or runtime tampering.

When to use: Always in production builds.

Example: Attaching Visual Studio is detected; DN Shield blocks or diverts execution to frustrate analysis.

How it works: Blocks IL disassembly and renders recovered output unreadable.

When to use: Always for production assemblies.

Example: Running ILDasm on a protected binary produces unusable, scrambled output.

How it works: Sensitive regions are encrypted; logic is indecipherable without runtime decryption.

When to use: For proprietary algorithms and licensing logic.

Example: A license check stays unreadable without the decryption routine.

How it works: Rewrites execution paths with opaque predicates and bogus branches.

When to use: Sensitive operations and business logic.

Example: A clear if/else becomes interleaved jumps that obscure real intent.

How it works: Encrypts literals; values exist in memory briefly at runtime.

When to use: Error messages, keys, URLs, config values.

Example: Decompilation shows encrypted blobs; plaintext appears only during execution.

How it works: Produces varied, obfuscated forms to resist pattern-based reversing.

When to use: High-value targets and public distributions.

Example: Simple arithmetic becomes a complex, non-obvious sequence in decompiled views.

How it works: Translates code into a proprietary VM with custom opcodes executed by an internal interpreter.

When to use: High-security apps or modules with significant IP.

Example: Critical algorithms run inside the DN Shield VM, resisting standard reversing tools.

How it works: Detects VM/sandbox environments and triggers countermeasures.

When to use: Always when adversaries may analyze in VMs.

Example: On VM detection, the app can exit or degrade behavior to waste an attacker’s time.

How it works: Monitors for automated analysis; delays, disables or alters behavior when detected.

When to use: Recommended for all production builds.

Example: Execution is delayed or features are gated if a sandbox signature is present.

How it works: Replaces meaningful identifiers with randomized tokens to obscure structure.

When to use: Default-on for production.

Example: CalculateSum → a1b2c3, UserName → x9y8z7.

Still need help?

We answer real developer questions—configuration, pipelines, licensing, and more.

Contact Support