MID Server configuration file security

Sensitive MID Server configuration data can be protected using several different schemes, including internal and external data encryption and external data storage.

The MID Server uses one secured configuration provider at a time. You can use either the default security provider or CyberArk as the secured configuration provider. Mixed provider configurations are not supported. For example, you cannot use the default security provider together with CyberArk. The following built-in security options are available:

• Default security provider: Secures the data in the config.xml file by encryption. When the MID Server is restarted, any unencrypted data is encrypted and written to the config.xml file. The default security provider offers these encryption options:
  • Default encryptor: Default process for encrypting data in the MID Server config.xml file. See Encrypt or decrypt MID Server configuration file values for details.
  • Windows Data Protection API (DPAPI): The operating system performs the data encryption, rather than the MID Server. DPAPI encryption is based on the logged in user's account. When this scheme is used, the data can only be decrypted by the same user account. If the account changes, the data must be re-encrypted.
  • Custom encryption: Implement the IMidServerEncrypter interface to create your own custom encryption scheme to manage sensitive config.xml data.
• CyberArk: Data security is provided by CyberArk integration configuration, which moves sensitive data from the config.xml file to a secure CyberArk vault. This solution does not encrypt the data and does not use the IMidServerEncrypter interface.
• Custom external storage: Implement the ISecuredConfigProvider interface to create your own custom external storage system to manage sensitive config.xml data.

• Encrypt MID Server configuration data with DPAPI
  Windows Data Protection API (DPAPI) encrypts sensitive data from the config.xml file, based on the MID Server user account.
• Use CyberArk as a secure configuration provider
  You can use a CyberArk vault to secure any sensitive data from the MID Server config.xml file.
• Change MID Server configuration file security schemes
  A MID Server security scheme is the method the MID Server uses to protect sensitive values stored in its config.xml file (for example, the instance password). The scheme defines how those values are encrypted and where the encryption key is stored.
• MID Server ISecuredConfigProvider interface
  Use the methods in this interface to create custom providers that manage secured parameter values in the MID Server config.xml file.
• MID Server IMidServerEncrypter interface
  Use the methods in this interface to create a custom external encrypter for the MID Server config.xml file.

Parent Topic:Securing and encrypting MID Server data

Related topics

MID Server certificate check policies

Encrypt or decrypt MID Server configuration file values

MID Server authentication credentials and SOAP requests

MID Server unified key store

Enable MID Server mutual authentication

MID Server Azure Key Vault integration

MID Server command audit log

Rekey a MID Server

Add SSL certificates for the MID Server

Specify an external TrustStore for the MID Server

MID Server SSH cryptographic algorithms

Attach a script file to a file synchronized MID Server

MID Server FIPS Enforced Mode

MID Server Governance