Secure Encryption Utility

The AVEVA.NET.Encryption.exe utility allows users to create their own encryption key. This enhances security and safeguards critical information such as databases, services and application pool passwords. The key created should be securely stored at a location accessible across multiple machines while installing the applications.

Encryption Utility

1. Copy the encryption utility from the package.

   

2. Run it as an administrator.

   

3. Choose where to save the encryption key. Ensure the location is only accessible to trusted persons and highly secured.

   

4. Once the key is successfully created, you'll see a confirmation message.

   

5. Check to find the newly created files.

   

   Note: Granting permission to access the location of the encryption key during installation, allows users to choose the location path seamlessly.

Deployment Manager

The Deployment Manager requests the location of the encryption key from a shared location. This shared location serves as a centralized point for managing encryption keys.

The Deployment Manager uses this shared encryption key for both encrypting and decrypting sensitive data, ensuring a consistent and controlled approach for database, service and application pool password protection.

6. Run the Deployment Manager as an administrator.

7. Check: Provide encryption key.

8. Provide the shared location in the text box below.

   

   Note: When the option is selected to load the configuration from a file (for using pre-configured installations), ensure you update the database, service, and application pool passwords to align with the chosen encryption strategy.

Extended Configuration File Security

To further enhance security, the Deployment Manager provides an additional option to restrict access to configuration file only to specified user accounts.

The Secure Config File checkbox in the deployment interface enables the following feature:

• When selected, the user is required to specify authorized user accounts in a dedicated text box.

• These user accounts are explicitly granted access to the encrypted configuration file during deployment along with the machine administrators.

• All other users are denied access, ensuring that only authorized identities can read or modify sensitive configuration content.

• Ensure to open AIM tools as an Administrator.

Installer

During the installation process, users are prompted to specify the encryption location. Once configured, the installer integrates with the encryption key stored at the shared location. This ensures a streamlined approach, using the same encryption key consistently for both the encryption and decryption functionalities, enhancing overall security measures.

9. Check: Provide encryption key.

10. Enter the shared location in the text box below.