The different formats used in .NET and Java
applications mean that protection generally
happens via method or class-level encryption,
which is decrypted automatically as required
during operation.
Few steps are required to include modular
protection and the reading and use of license
details. The interface can define additional
licenses (e.g. for separately licensed modules).
The Wibu Universal Protection Interface
(WUPI) can verify whether these additional
licenses are available while the application
is running, and the function-level encryption
allows the modules in question to be shielded
as necessary.
Comfortable Notifications
When neither basic nor additional licenses
are available, a flexible error handling system
springs into action. The AxProtector settings
and the so-called UserMessage library allow
customized responses and notifications for the
user. The application can display a custom error
message or a protected service can record the
incident in a secure log file.
Simple Process Integration
The protection should be embedded deep
into standardized processes to make sure the
software is protected during its original testing.
The encryption of applications or libraries can
be integrated readily into the build process.
All parameters defined via the AxProtector
interface can be exported to a configuration
file at the click of a button to allow automatic
encryption via a simple command line entry.
the security of your products without any
additional efforts on your part and maintain
your head start in the race against potential
attackers.
AxProtector Embedded Systems
can guard applications on the
following platforms:
<