| RemoteScope
Security Specification
Security of RemoteScope works on two aspects: one is anti-piracy
and license control and the other is system security. In view
of protecting intellectual property right, unauthorized installation,
anti-piracy can prevent the product from being copied illegally
so interest of distributors and license users can be guaranteed.
It is also for the purpose of strictly controlling unauthorized
installation of Console from connecting to your clients. System
security is the protection on operating mechanism and management
when the system is running; for example, protecting system
information (important files are encrypted or hidden), encrypted
communication data, prevent illegal logon, etc.
Detailed description:
1.0 Anti-piracy and License Control
1.1 Limit on RCPK (RemoteScope Console Product Key)
- As installing other software products, user has to type
the RCPK or CD key when installing the Console. Micro2000
supplies the RCPK with the installation package when distributing
the product. This is the initial step to control piracy.
1.2 Activation Mechanism - In order to prevent RCPK
from being peculated, RemoteScope applies online activation
authentication. After the Console has been installed, the
activation process will start the first time Console is
run. User is required to input his or her basic information,
which will be registered and activated on the Micro2000
ARS system (Authentication RemoteScope Server) via Internet.
The machine running the Console program is required to have
Internet access; otherwise, the activation would fail and
make the Console inoperative. If the RCPK has already been
activated, the whole activation process would also fail.
If the RCPK is not activated or has already been activated
by the same Console machine (when reinstall) , the whole
activation process will be successful. The Console cannot
continue running once activation fails. In order to enhance
the detection function, every 15 days the Console will silently
communicate with Micro2000 ARS server automatically, to
validate the activation information of the current RCPK.
If the product identification is illegal, or the validation
cannot be authorized in three consecutive days, the system
will start the activation program again requiring user to
reactivate.
1.3 License Control - To meet different requirements
of users, RemoteScope is designed to allow different Client
seat license numbers, which can be controlled by the Console.
This is the kind of License Control RemoteScope imposes
in limiting the clients Console is allowed to connect to.
The Client numbers that can be controlled by the Console
therefore is called License Numbers, which are determined
by the designated RCPK and varies from several seat modules.
2.0 System Security
2.1 Validation at logon - When starting the Console,
the user name and password are required to be typed in to
successfully log on the Console system. Only when the login
and password are correct that the user can continue running
the system. Security of user name and password is essential.
RemoteScope applies the encryption of varied DES. User name
and password are stored in the database after being encrypted.
Varied DES is an encryption method combining DES and self-designed
calculation method. Likewise, each user name and password
will be stored in the database after being encrypted.
2.2 Encrypted important file content - this is used
to validate several DLL file contents of RCPK, which are
also encrypted with DES.
2.3 Encrypted communication data - data will be
encrypted with DES and create the validation code before
being transferred. This will be decrypted after being checked
at receiving end, in case of data loss or modified during
the process.
2.4 Exit Authentication on Client - The Client program
will start with the OS or Windows automatically. User name
and password are required to be validated by the Console
when doing configuration changes on the client like exiting
or uninstalling the client. The RemoteScope Client is required
to be connected to the Console before any configuration
changes can be done. Even in the Task Manager of Windows,
the Client cannot be forced to exited or closed. In this
way the RemoteScope Client cannot be unloaded or closed
by unauthorized users.
2.5 Prevent Client from being controlled by unauthorized
Console - The unique Client program installation is
created automatically when the Console is being installed.
The Client can only be controlled by the designated Console,
which created the Client program installation. This is to
prevent other unauthorized Consoles from controlling Clients
that does not belong to its assigned or designated RemoteScope
network.
|
