This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Security considerations for BMC Remedy AR System

When planning an enterprise setup, consult the following topics for security guidelines on the BMC Remedy Action Request System (AR System) components:

BMC Remedy AR System security

Security is an important consideration for AR System. The AR System server addresses security through the following controls: 

  • Access control—Protects AR System data by controlling which users can open an application, form, or guide in a browser, can perform an action, and can create, view, modify, and delete a request.
  • BMC Remedy Encryption Security—Protects data that is passed over a network between a client and a server. The AR System client libraries contain built-in encryption capabilities that you can enable to secure the connection to the AR System server. BMC Remedy AR System version 9.1.02 is tested with database encryption products to ensure the connection can be encrypted. For more information see, and

    BMC Remedy Encryption Performance Security option—AR System encrypts network traffic by using AES CBC with a 128-bit key for data encryption and a 1024-bit modulus for the RSA key exchange, and SHA-1 for message authentication.

    BMC Remedy Encryption Premium Security option—AR System encrypts network traffic by using AES CBC with a 256-bit key for data encryption and a 2048-bit modulus for the RSA key exchange, and SHA-1 for message authentication.
  • Protection of the server and network resources to which AR System has access—AR System can be configured to help secure the network resources used by the product. The system can be configured so it runs with limited access privileges, and has access only to certain resources on the host machine. This prevents a user from running malicious scripts or programs on the installed machine. For data and resource protection configuration options, see Configuring clients for AR System servers and BMC Remedy AR System configuration files.


    For more information on security of server and network resources which AR System has access, see Tightening BMC Remedy AR System security.

  • Password security—AR System ensures that passwords are always encrypted. An SHA-2 256 of passwords is stored in the database, ensuring that the system (and therefore a reader of the database) cannot retrieve passwords. In addition, the AR System server allows you to use policies to enforce password changes. For password policy information, see Enforcing a password policy introduction.

Mid tier security

The mid tier provides a secure environment by encrypting sensitive data. All passwords are stored in configuration files as encrypted strings. For the web server, you must add any additional security if required.

Best Practice

We recommend that you use a secure socket layer (SSL) or HTTPS connection to encrypt the data between the web server and the browser client.
Enabling SSL can impact performance due to the extra overhead required to encrypt and decrypt on both ends.


You can log on to BMC Remedy Mid Tier using only HTTP POST requests.

Use BMC Remedy Encryption Performance Security or BMC Remedy Encryption Premium Security to encrypt communication between AR System components, including the Mid Tier.

When securing the mid tier, consider these tips about:


  • The mid tier works with SSL. SSL encryption is a few layers below the web application (between the HTTP web server and the browser client sending the HTTP requests). All web server vendors provide a method to create and store certificates to enable SSL encryption over HTTP.
  • Configuring the environment for SSL support is beyond the scope of any guidance BMC provides.
  • Apache HTTP server has an SSL mode and, when that mode is enabled, the server can cache the encryption information to speed up performance.


Cross-site scripting (XSS) is a type of computer security vulnerability (typically found in web application) that allows code injection by malicious web users into the web pages viewed by other users. Examples of such code include HTML code and client-side scripts.

Cross-site scripting is addressed in every release of the mid tier by running the code through a tool to identify potential problems to ensure no vulnerability is introduced. All user-supplied HTML special characters are encoded into character entities, thereby preventing them from being interpreted as HTML.


Web Distributed Authoring and Versioning (WebDAV) extensions on web servers allow users to collaboratively edit and manage files on remote web servers. If your web servers has the WebDAV extensions enabled by default, they should be disabled.

HTTP transport

To ensure that the HTTP transport method POST is used for XML/HTTP requests in the browser, you must set the arsystem.xmlhttp.get flag in the file to false.

For more information, see:


If you use the pwd parameter in a URL, passwords are exposed by the browser in the locator and in bookmarks or favorites. For URLs that include the pwd parameter, use https:// (https://*).

Content-Security-Policy (CSP) header

The Content-Security-Policy (CSP) header prevents the browser from ClickJacking Attacks. This header controls;

  • Whether your web-page can be loaded in <iframe>, <frame>, <object>, <embed>, or <applet> tags.
  • On what domains the web page is loaded.

You can enable the Content-Security-Policy (CSP) header by using the arsystem.security_iframe_allowfromurls parameter in Centralized Configuration. For more information, see arsystem.security_iframe_allowfromurls parameter.

You can also use the web.xml file located in the db folder to enable the Content-Security-Policy (CSP) header. The Centralized Configuration setting overrides the settings in the web.xml file. For information about enabling enable the Content-Security-Policy (CSP) header using the web.xml file, see Enabling cross launch to mid tier.

Approval server security

The approval server provides a secure environment by encrypting sensitive data. For example, the password is always encoded and never saved in any file as readable text. You can add any additional security if required.

Use BMC Remedy Encryption Performance Security or BMC Remedy Encryption Premium Security to encrypt communication between AR System components, including the Approval server. Approval server uses the encrypted password for the Remedy Application Service user, which is available in the Centralized Configuration for making any backend calls to AR System.

BMC Atrium CMDB security

The CMDB Class Manager controls permission to access CMDB classes and attributes. This is done by using Role IDs associated with Role definitions from the BMC:Atrium CMDB deployable application. Two roles (-1090 and -1091) are defined to allow unlimited read or read/write access to CMDB data. Two other roles (-1098 and -1099) allow read or read/write access subject to row-level permission. The CMDB administrator should assign these roles to the appropriate groups in production and test environments.

Email Engine and Assignment Engine security

For information on Email Engine security, see Securing incoming and outgoing email.

For information on Assignment Engine security, see Configuring the Assignment Engine server settings.

Additional Information

For more information on security guidelines, see the blog Choose your request methods carefully shared on BMC Communities.

Was this page helpful? Yes No Submitting... Thank you


  1. Samo Puharic

    SHA-2 algoritam for passwords. Are you shute this is not typo mistake ? You mean SHA-256 ??

    Apr 20, 2018 06:16
    1. Anagha Deshpande

      Hello Samo,

      This is not a typo.

      SHA-1 and SHA-2 are two different versions of SHA algorithm. They differ in both constructions and in the bit-length of the signature.

      SHA-2 is the successor to SHA-1. SHA-2 is actually a “family” of hashes and comes in a variety of lengths. The most popular 256-bit is called SHA-256.

      The AR System server uses this to store passwords.



      Apr 23, 2018 10:28
  2. Karl Halleni

    You refer to the config parameter arsystem_xmlhttp.get but the correct parameter is named arsystem.xmlhttp.get

    May 07, 2018 08:11
    1. Anagha Deshpande

      Hello Karl,

      Thank you for the feedback. I will update the topic.



      May 07, 2018 10:03
      1. Anagha Deshpande

        Hello Karl,

        Apologies for the delayed response.

        I have updated the topic.



        Jun 24, 2019 11:54