User Manual: Virbox Protector
  • Virbox Protector
  • Introduction
  • Download
    • Installation
    • Sign up & Apply trial license
    • Sign in & Sign out
    • Virbox License
      • Virbox Protector License (GUI)
        • Virbox Protector License: Offline Environment
      • Virbox Protector License (CLI)
      • Virbox Protector License (Network License)
      • Purchase Virbox License
  • Fundamentals
    • Overview
    • GUI tool
    • Protection Process
    • CLI Tool: Overview
    • CLI Tool: User Manual
      • User Manual_Virbox Protector Command Line
      • Set the SDK label to protect the specified Functions/Code/String
    • Other Useful tool
      • User Guide: Windows Virtual Folder
  • Use Cases
    • Protect Desktop applications
      • Protect the Local desktop application
        • Best Practice--Protect Native applications
      • Protect Jar/War Project with Java BCE Protection Mode
      • Protect Jar/War Project with Java VME Protection Mode
      • Protect the .NET application
        • Best Practice--Protect .NET applications
    • Protect Unity3D/UE4 application
      • Protect Unity3D Android APK
      • Protect Unity3D application in Windows/Linux system
    • Protect Mobile applications
      • Protect Android AAB Projects
      • Protect Android AAR projects
      • Protect Android APK Projects
      • Protect Android shared library (.so libs)
      • Best Practice to Protect Android Apps
      • Protect iOS Project
    • Protect Scripting language
      • Protect PHP project
      • Protect the Python application with Virbox Protector
      • Protect Python Project by PyProtector
      • Protect the JavaScript code in HTML 5 applications
    • FAQ
      • How to deal with the Virus False Positive when developer protect the application
      • How to evaluate Virbox Protector protection performance
Powered by GitBook
On this page

Was this helpful?

  1. Fundamentals

Protection Process

PreviousGUI toolNextCLI Tool: Overview

Last updated 3 years ago

Was this helpful?

Protect your app with simple process

It is quite easy for developer to use Virbox Protector GUI to protect their applications with very simple process:

Step 1: Drag the application into the Virbox Protector;

Step 2: Select and Set the protection option to specified functions and set the protection to your applications in general: multiple protection options can be set;

Step 3: Click the Button "Protect Selected Project" to complete the protection process;

Step 4: Test and evaluate the security of the protected application;

Step 5: Distribute the protected application to your users or Deployed protected application in different system environment.

Virbox Protector provides multi-layer protection/encryption technology and help developer to defend third party attacker to use decompilier, debug tool static and dynamics analysis to crack your application to steal your algorithm, IP and digital asset etc.

The most important steps to protect your application is STEP 2: Function Options tabs and Protection Option tabs and STEP3: Protect the projects;

In Step 2, Developer select and set the protection option to the functions and application

In the Function Option tab, developer will select those critical functions, methods in your applications and set the protection mode to those critical functions in your application and protect it.

The protection options to "functions" includes: Virtualization, Obfuscation, Encryption and No protection which can be select and set to those functions.

In the Protection Option tabs, Developer may select and set the protection option in your application in generals, multiple protection, detection features can be set in this tab: Import Table protection, Compression, Memory Check, Resource section protection, Anti-debugging, VM detection, Memory Protection, Kernel Mode anti debugging etc. and protect data resource etc.

The protection features can be set may slight different to protect different kinds of applications, more description and details can be found in the USE CASES in following chapters.

In Step 3, after protection completed, 2 new file will be generated in the output path which you set:

The configuration file contains protection setting: samplename.exe.ssp

For the file suffix with .ssp, is the configuration file, pls keep and save it, and no need to distribute the configuration file to your software user.

and the protected file: samplename.exe which in seperately directory: \protected\samplename.exe