Siebel Remote and Replication Manager Administration Guide > Architecture of Siebel Remote > How Siebel Remote Validates and Authenticates Information >

How Siebel Remote Encrypts Fields

Siebel Remote provides the following functionality for field encryption. For more information, see Process of Configuring Encryption and Authentication for the Remote Client and Siebel Security Guide:

• If you extract a local database for a remote client, then the extract process detects encrypted fields and stores the unencrypted contents in a compressed binary dat file. Siebel Remote uses the clear text value of the field to determine the hashed value of each encrypted field. This extract process does not modify the hashed value.
• If the Transaction Router server component prepares modified data for a user, then it detects encrypted fields and stores the unencrypted contents in the compressed binary dx file. Siebel Remote uses the clear text value of the field to determine the hashed value of each encrypted field. The preparation of the dx file does not modify the hashed value. Some utilities can read data from a dx file. It is recommended that you prevent unnecessary user access to the following folders where dx files might exist:
  • Txnproc folder
  • Inbox folder
  • Outbox folder
• If Siebel Remote synchronizes the server database with a local database, then data that it encrypts at the field level in the server database is decrypted in the local database. To maintain data security, you can configure Siebel Remote to encrypt the entire local database. For more information, see Creating a New Database for Siebel Remote.
• If your Siebel implementation includes regional nodes, then it must meet the following requirements:
  • The regional nodes must use the same encryption as the Siebel Enterprise Server.
  • The keyfile.bin file on the regional server must be identical to the corresponding file on the Siebel Server of the headquarters node.

    Data that passes between the server database and the local database for a regional node remains encrypted. For more information, see Overview of Replication Manager.

• You can use the DockConnString parameter in the configuration file to specify how to encrypt the network traffic that occurs during a synchronization.