Database Connection Encryption Options

When Lucity programs connect to a SQL Server or Oracle database, they have to send login credentials. Because these credentials are usually sent out over a network, there is a possibility they could be intercepted.

Lucity provides several different options for managing and securing configuration information.

Managing Database Connection Encryption

The connection encryption can be managed using:

• A centrally managed desktop gateway - Enables an administrator to make changes in a single location and automatically download those changes to each workstation. (This is the default setting.)
• Manual configuration - Requires an administrator to visit each machine to make changes to the database connection configuration. This option can be more secure than using a centrally managed desktop gateway.

Database Connection Encryption

Once an agency has decided how to manage encryption, it can choose one of three methods for encrypting the connection credentials:

1. Integrated security - Uses Windows authentication (through an active directory group) to encrypt and send connection credentials to the database.
2. Unencrypted credentials - Give users access to a very limited set of stored procedures, rather than the entire database.
3. Encrypted credentials - Requires an agency to set up encryption manually. (This is the most secure method.)

Management + Encryption Options

The following matrix outlines each of the database types and the options for managing the deployment of these configurations:

Defaults

• SQL Server - Centrally Managed, Integrated Security
• Oracle - Centrally Managed, Unencrypted Configuration

How to set up centrally managed integrated security

How to set up centrally managed unencrypted security

How to set up manually encrypted security