Encryption Security for secure communication between the client and server
Action Request System is also tested with database encryption products from your database vendor to make sure 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 Encryption Security are data confidentiality, integrity, and authentication.
Encryption enables the AR System server and its clients to communicate securely over a network by encrypting the 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 decipher the messages in transit.
The encryption options do not encrypt the communication between the browser and the Mid Tier. The encryption between the browser and Mid Tier requires the X.509 certificate to be deployed on the Mid Tier or on the load balancer depending upon your deployment and security requirements. Data encryption is invisible to users.
The Action Request System client libraries provide built-in encryption capabilities that can be enabled to secure the connection to the AR System server. Higher levels of encryption are available from BMC if you need stronger encryption. Action Request System is also tested with database encryption products from your database vendor to ensure that this connection can be encrypted. The communication between the AR System server and the database are not natively encrypted. The encryption is subject to the capabilities provided by the database vendor. For more information, see the following BMC Communities blogs: Trending in Support: SSL Encryption for AR to Oracle Connections with Remedy 9.1 SP2 and Later and Trending in Support: Enabling SSL Encryption for AR to MS SQL Database Connections with Remedy 9.1 SP2 and Later.