|
 SecureDoc Operation & Administration
|
SecureDoc - User's View |
| |
|
|
Installation of client software |
To become acquainted to the installation process we will perform a manual sample installation on a typical client computer. In our case, we use a ‘typical desktop computer’ with Windows XP SP2 and MS Office without any additional adjustments, lets say „out of the box“. It is member of the Active Directory Domain „Cryptolab“and has a direct TCP/IP connection to the servers in this environment.
We remember: SecureDoc needs local administrative rights to be installed and in our sample profile configuration and package settings it must be installed in the context of the logged on user (we are using the name for user creation instead of computer name or freely selectable names). Therefore the user name (domain user) was added to the local admin group and will be removed again after installation.
We are opening the network share where the designated installation package is provided. On our computer Microsoft .Net Framework 2.0 must be installed. If it is not, we can run Setup file dotnetfx.exe to install it now.
Then we can run SDSetupSilent.exe That’s it .. and a heartbeat later (if defined in the package settings) we will see the confirmation dialogue to confirm username and client name that are sent to the SES database. If we synchronize with AD to populate the SES database, no interaction is necessary here and the dialogue does not need to be showed to the users. If we decided to let user accounts to be created during installation, this form is to be filled out by the user, logged on during installation.
If configured in the package. The computer reboots now and the process will be continued. Else, the computer will wait for the next regular shutdown by the user or by the software distribution system. (SMS, Tivoli…)After the reboot and the log on, the computer will take the configured state. In our case we decided to encrypt the whole hard disk and install a pre boot log on.
|
|
|
|
This information window can be presented to the user or hidden. If it not presented, the encryption happens invisible in the background. After encryption, the computer is rebooted again.
The information on the client computer is protected now.
...................
- Download Step-by-Step Guide: SecureDoc - the user's view
|
The use of removable media |
If a user wants to utilize a removable medium, in our case an USB chip, he will be able to use it only as far as the profile settings allow. Here, it is allowed to read all information, but it is not allowed to write unencrypted.
If he wants to use it for storing information too, maybe to exchange data inside the organization, he will need to encrypt the USB chip first. After confirming (and optional defining an access password) SecureDoc starts to encrypt the stick. Then the chip is readable only on computers, a user of the authorized group is logged on.
|
|
|
|
- Download Step-by-Step Guide: SecureDoc - the user's view
|
|
|
|
If there is a need for tight security in a company and only encrypted removable media are allowed, it is suggested:
• Users do not have the permission to change encryption settings by themselves.
• Already encrypted media are provided for departments / sites by the IT helpdesk
It might be a rich error source let users encrypt media for groups or teams (mistakes and helpdesk calls and even security breaches are programmed) and it could last for some time to encrypt a large but slow chip.
|
Forgotten password? |
In the profile settings we can define, after how many logon attempts a computer getting locked. Not the system start is locked only but the access to the Keyfile so the access to the hard disk is not possible anymore. For this case, a process must be prepared, which allows a user / helpdesk support technician to unlock the computer again. (SecureDoc Enterprise Server allows adjusting to the security requirements and the structure of the organization)
|
|
|
|
- Download Step-by-Step Guide: SecureDoc - the user's view
|
|
|
|
|
Legal notice
