---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Configure the CyberArk vault and install the AIM API

# Configure the CyberArk vault and install the AIM API {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Configure the CyberArk vault to allow MID Server access and install the CyberArk AIM
API on the MID Server machine.

## Vorbereitungen

Role required: admin

Before starting this procedure, ensure that the [External Credential Storage plugin](https://servicenow-prod.fluidtopics.net/lag~XiaGzyR5aaYJGSfqgg "The External Credential Storage plugin is available by request.")
is activated. CyberArk Application Access Manager (AAM) Credential Providers version
12.0.1 and later is supported.

## Prozedur

1. Configure the CyberArk vault with the application ID and authentication details that all MID Servers requesting credentials will use.  
   For details, refer to the CyberArk Credential Provider and ASCP Implementation Guide.
   1. Ensure that CyberArk is configured to allow the MID Server to access the vault by creating an App-ID in CyberArk called ServiceNow_MID_Server.
   2. Make sure that every credential the MID Server needs is granted access to the ServiceNow_MID_Server App-ID.  
      Hinweis:  
      You can override the default ServiceNow_MID_Server App-ID in the MID Server config.xml file using the [ext.cred.app_id](https://servicenow-prod.fluidtopics.net/mQKyIoZMOVnfUh0hh1J2jw "Configure the config.xml file to grant the MID Server access to the CyberArk vault with AIM API.") parameter. If you change the value in this parameter, make sure to configure a matching value in the vault.
   {#t_InstallCyberArkAIMAPI__substeps_rhc_lc4_vs}
2. Install the CyberArk Credential Provider, including the AIM API, on each machine that hosts a MID Server service that is used to access the credential store.
3. Provision CyberArk accounts and set permissions for application access.  
   For details, refer to the CyberArk Privileged Account Security Implementation Guide.
   1. In the CyberArk Password Safe, create the privileged accounts required by Discovery, Orchestration, or Service Mapping to access different devices and ensure that these accounts are members of the safes in which the necessary credentials are stored.
   2. Add the Credential Provider and application users as members of the Password Safes where the application passwords are stored.
   {#t_InstallCyberArkAIMAPI__substeps_ikj_1f2_gw}