Skip to Content
Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

BMC Remedy ITSM - Mobility Service Desk security

This topic provides information about BMC Remedy ITSM - Mobility server security.

BMC Remedy ITSM - Mobility server to BMC Remedy ARserver data transmission

  •  The date traffic between the mobility server and the back-end BMC Remedy ARServer uses AR network encryption.
  •  BMC Remedy ARserver standard encryption (56 bit) is the default encryption option on the network, but you can purchase BMC Remedy ARserver performance encryption (128 bit) or BMC Remedy ARserver premium encryption” (256) package.
  • The BMC Remedy ARserver performance and premium encryption packages are in compliance with the Federal Information Processing Standard (FIPS)

BMC Remedy user credentials stored on BMC Remedy ITSM - Mobility server

  • When you first install the BMC Remedy ITSM - Mobility client and attempt to connect, you are asked for your BMC Remedy AR System user name and password. This data is then passed through the BMC Remedy ITSM - Mobility server to BMC Remedy AR System to authenticate.
  • The BMC Remedy ITSM - Mobility server does not store the end users username and password.

BMC Remedy ITSM - Mobility: Service Desk for Incident Management to BMC Remedy ITSM - Mobility server to  data transmission

  • All clients
    • The network traffic between the BMC Remedy ITSM - Mobility server and the BMC Remedy ITSM - Mobility: Service Desk 7.6.05 for Incident Management is encrypted using SSL. This is controlled by the administrator.

BMC Remedy ITSM - Mobility Incident Management application security

  • User names and passwords are stored  and encrypted at the 256-bit level in the BMC Remedy ITSM - Mobility 7.6.05 Incident Management application's (client) database.
  • Data on the BMC Remedy ITSM - Mobility 7.6.05 Incident Management application (client) is encrypted at the 256-bit level.
  • The BMC Remedy ITSM - Mobility 7.6.05 Incident Management application (client) does not use SAML or Kerberos. Single sign-on (SSO) will be implemented in future releases. 
  • The BMC Remedy ITSM - Mobility 7.6.05 Incident Management application (client) is password protected. After the application has been authenticated, you must manually log out to prevent access. You can protect the application by implementing device-level access control.
  • The BMC Remedy ITSM - Mobility 7.6.05 Incident Management application (client) does not require VPN connectivity to the BMC Remedy ITSM - Mobility server. It can use a VPN connection if needed, or it can use a public connection.
  • You can logon and access the BMC Remedy applications (client) using the BMC Remedy ITSM - Mobility 7.6.05 Incident Management application when you are currently logged on from the desktop. 
  • BMC Remedy ITSM - Mobility 7.6.05 Incident Management application (client) uses the SQLite database.
  • Administrators can limit which BMC Remedy AR System server users have mobile access. All BMC Remedy users have mobile access.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Remedy ITSM - Mobility: Service Desk 7.6.05