How Remedy Encryption Security enables secure communication between the client and server

Remedy AR System is also tested with database encryption products from your database vendor to ensure that this connection can be encrypted.

Cryptography protects important data as it passes through an unsecured medium such as, a computer network. The services provided by Remedy Encryption Security are data confidentiality, integrity, and authentication.

Remedy AR System has the ability to encrypt its traffic using industry standard cryptography to protect data while in transit.  The encryption services provided by Remedy Encryption Security are data confidentially, integrity, and authentication. 

These encryption services enable the Remedy Action Request System Server to communicate with its clients securely over a network by encrypting the RPC messages sent between them.  At the beginning of every client and server connection, a key exchange protocol negotiates shared encryption keys between the client and server. These keys encrypt all communication between the client and server, ensuring that the communication is secure and that third parties cannot easily decipher the messages in transit. 

Remedy encryption services do not encrypt the communication between the browser and the Remedy Mid Tier, browser and Smart IT, or the browser and Smart Reporting.  This is done with a standard SSL/TLS certificate that you’ll configure in each Tomcat or IIS instance. To learn more about this, see Configuring the Mid Tier web server for SSL certificate and also refer the Knowledge article 000288208.

Remedy encryption services do not encrypt the communication between AR System Server and the database.  This is done with a SSL/TLS certificate that you’ll need to configure in each database instance.  To learn more about this, contact your DBA and refer the following blog posts:

For Oracle database, see Trending in Support: Encrypting Data Between AR Servers and Oracle Databases.

For MS SQL database, see Trending in Support: Enabling SSL Encryption for AR to MS SQL Database Connections with Remedy 9.1 SP2 and Later.

While Remedy encryption services does encrypt the communication between AR System Server and other services like Email Engine or other Plugin Servers, it does not encrypt the data sent externally from the Email Engine to the Mail Server, Plugin Server to LDAP server, or other external connections .  This is done with a SSL/TLS certificate that you’ll need to configure for each component. For more information, see Configuring-SSL-for-the-email-engine.

For more information on Remedy Encryption Security, see Secure AR System data by using Remedy Encryption Security.

To install Remedy Encryption Premium or Remedy Encryption Performance, see Installing BMC Remedy Encryption Securityin Remedy ITSM Deployment online documentation. To configure encryption, see Enabling-or-disabling-Remedy-Encryption-Security-on-AR-System-server.

Remedy Encryption Security includes third-party encryption software developed by the OpenSSL Project for use in the OpenSSL toolkit (see http://www.openssl.org/).