The system is administered via an easy to use, but complete, SafeBoot Administrator module, which provides control over the configuration of users, machines and main servers, which can be grouped.
Configuration settings are comprehensive. For example, you can set specific password rules for users including refresh rates, time-outs and so on, whether or not tokens are used, application control, and administration rights. You can even attach a photograph of the user to the individual record. For each machine, you can decide whether to enable boot protection, which drives are encrypted, how often it synchronizes to the SafeBoot database, and a host of other details.
Systems administrators have a good level of overall configuration control, with users and machines treated as components with their own attributes in a secure repository. It is possible to configure more than one SafeBoot server. Install sets are created on the server from which client devices can be set up as protected machines by downloading and running the install file.
Once the infrastructure is established, operation for the user is effectively transparent. SafeBoot takes care of encrypting and decrypting files as the user works on them.
This is a comprehensive product that might fit well with many enterprises' requirements. However, it is not a product to rush into implementing without first clarifying your objectives and understanding how it works and how best to configure it.
A ring-bound manual supplies very good information, including advice on setting up servers, tuning the object directory, and so on. SafeBoot also supports Pocket PC PDAs and the encryption of media cards. This is accomplished via the establishment of a SafeBoot CE server and administered via the SafeBoot Administrator module.
