---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/servicenow-platform

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Change MID Server configuration file security schemes

# Change MID Server configuration file security schemes {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
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.

## Before you begin

Role required: admin

## About this task

MID Server supports several schemes for securing sensitive data in the config.xml file. You can switch from the current scheme to a different scheme to meet your security requirements.  
Note:  
This procedure outlines the general steps for changing security schemes. The specific changes required in the config.xml file vary depending on the scheme you select.

## Procedure

1. Stop the MID Server service.
2. Open the config.xml file in a text editor.  
   This file is located in the /agent folder in your MID Server installation path.
3. Replace each encrypted value in the config.xml file with its clear-text value.  
   A new scheme can't reuse values encrypted by the previous scheme, so you must restore them in clear text first.
4. Disable the previous security scheme and configure the MID Server to use the new provider.
5. Restart the MID Server service.  
   The data is re-secured or encrypted, based on the security scheme you have selected.
{#change-mid-server-security-schemes__steps_hds_3wh_lbb}
**Related tasks**   

* [Encrypt MID Server configuration data with DPAPI](https://www.servicenow.com/docs/RShfMHLfJ_oLO77XWKtmrw "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](https://www.servicenow.com/docs/SPWljaUtUe7lvZ~U75fnHw "You can use a CyberArk vault to secure any sensitive data from the MID Server config.xml file.")  
**Related reference**   

* [MID Server ISecuredConfigProvider interface](https://www.servicenow.com/docs/1gLcUectYQSmeXA1_pg4oQ "Use the methods in this interface to create custom providers that manage secured parameter values in the MID Server config.xml file.")