--- sourceDocument: Australia ServiceNow AI Platform Capabilities sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform Release : - australia ft:locale : - de-DE ft:publication_title : - Australia ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # MID Server SSH cryptographic algorithms # MID Server SSH cryptographic algorithms {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer The MID Server utilizes SSH clients to perform many discovery actions. During the SSH handshake, both the client and server first determine which algorithms both parties support, then client picks the highest priority algorithm. For the Host Key Algorithm, the client picks highest priority algorithm which both parties support that matches the key type. |-| | | [ ] {#mid-ssh-algorithms__table_kvf_3v4_nhb} ## Default supported SSH algorithms by priority {#mid-ssh-algorithms__section_gjv_cpr_xnb} Key Exchange Algorithm 1. ecdh-sha2-nistp256 2. ecdh-sha2-nistp384 3. ecdh-sha2-nistp521 4. diffie-hellman-group-exchange-sha256 5. diffie-hellman-group14-sha256 6. diffie-hellman-group16-sha512 7. diffie-hellman-group14-sha1 8. diffie-hellman-group1-sha1 9. diffie-hellman-group-exchange-sha1 {#mid-ssh-algorithms__ol_hgp_bpr_xnb} Host Key Algorithm (used for public key signature during authentication) 1. ssh-ed25519-cert-v01@openssh.com 2. rsa-sha2-512-cert-v01@openssh.com 3. rsa-sha2-256-cert-v01@openssh.com 4. ssh-ed25519 5. ecdsa-sha2-nistp256 6. ecdsa-sha2-nistp384 7. ecdsa-sha2-nistp521 8. rsa-sha2-512 9. rsa-sha2-256 10. ssh-rsa-cert-v01@openssh.com 11. ssh-rsa 12. ssh-dss {#mid-ssh-algorithms__ol_x4h_jpr_xnb} Cipher Algorithm 1. aes128-ctr 2. aes192-ctr 3. aes256-ctr 4. aes128-cbc 5. aes192-cbc 6. aes256-cbc {#mid-ssh-algorithms__ol_trm_qpr_xnb} MAC Algorithm 1. hmac-sha2-256 2. hmac-sha1 3. hmac-sha2-512 4. hmac-sha1-96 5. hmac-md5-96 6. hmac-md5 {#mid-ssh-algorithms__ol_fdf_5pr_xnb} ## Customize the SSH algorithms priority list {#mid-ssh-algorithms__section_ogk_bqr_xnb} The MID Server SSH algorithm priorities can be customized based on security needs. Each algorithm is controlled by one of the following MID Server properties. Hinweis: Glide Import on the instance uses the default algorithm list. The four MID Server properties do not affect Glide Import because it is not run on the MID server. SNCSSH is used for Glide Import on instance for SFTP and SCP. * Key Exchange algorithms: mid.ssh.algorithms.kex​ * Host Key algorithms: mid.ssh.algorithms.host_key​ * Cipher algorithms: mid.ssh.algorithms.cipher​ * MAC algorithms: mid.ssh.algorithms.mac​ {#mid-ssh-algorithms__ul_oxr_ygs_xnb} The properties accept comma separated lists with operators. The first name in the list is highest priority, last name in list is lowest priority. Adding a comma separated list without any operators replaces the default algorithm list. The following operators are based on the OpenSSH standard syntax and modify the algorithm priority list. * The + operator appends the comma separated list of algorithms to the default algorithm list. * The - operator removes the comma separated list of algorithms from the default algorithm list. * The \^ operator places the comma separated list of algorithms at the front of the default algorithm list. {#mid-ssh-algorithms__ul_xs1_x3s_xnb} **Zugehörige Konzepte** * [MID Server certificate check policies](https://servicenow-prod.fluidtopics.net/VBqU5CHqCSU2m2xJd2a6uA "MID Server uses four kinds of security checks to secure external traffic. The security checks use TLS/SSL certificate validation, hostname validation, Certificate Revocation List (CRL), and Online Certificate Status Protocol (OCSP) validation to improve security. Control these security checks with the MID Server certificate check policies table.") * [MID Server authentication credentials and SOAP requests](https://servicenow-prod.fluidtopics.net/80f2cul5Bjz0opflAxzxPg#mid-authentication-soap-requests "Set basic authentication credentials to update the web service invocation data. For added security, you can enforce basic authentication on each incoming SOAP request to the MID Server.") * [MID Server unified key store](https://servicenow-prod.fluidtopics.net/zWbtuI59iqjA5LfLDw8VPA#mid-unified-keystore "The MID Server unified key store allows all products on the MID Server to use common certificates and key pairs. This feature allows applications to use the same secure communication channel to the MID Server that the MID Server uses to connect to the instance.") * [MID Server command audit log](https://servicenow-prod.fluidtopics.net/hMnNVhNJPmpY4gLr76lWAg "The command audit log records the commands run by the MID Server for the Discovery application. Review the commands to check for anomalies or errors.") * [MID Server FIPS Enforced Mode](https://servicenow-prod.fluidtopics.net/dqBc9MICWmUraTd809_RJw#mid-fips-enforced "The MID Server supports the National Security Cloud (NSC) IL-5 environment, which requires all utilized cryptography to be FIPS validated. The MID server can be run in FIPS Enforced Mode, where only cryptographic algorithms which are FIPS validated are utilized.") * [MID Server Governance](https://servicenow-prod.fluidtopics.net/aFXIuu3zlxcmFMjRZPM1Ug "Improve MID Server security by setting an automatic timeout to invalidate and shut down inactive MID Servers. You can enable this feature and set the inactivity timeout period globally and for each MID Server.") **Zugehörige Tasks** * [Encrypt or decrypt MID Server configuration file values](https://servicenow-prod.fluidtopics.net/iCgc9bn4JQYK9vgd1wAC6w "The value of any MID Server parameter in the config.xml file can be encrypted. The attributes for all encrypted values are managed from within the configuration file, including the security attribute of the login password.") * [Enable MID Server mutual authentication](https://servicenow-prod.fluidtopics.net/UdSuWRmz6ZGA~Y6dkWvyeQ "Configure the MID Server to use a client certificate for authenticating to the instance. This avoids the need to create a basic authentication credentials in the Key Store for the MID Server's configuration.") * [MID Server Azure Key Vault integration](https://servicenow-prod.fluidtopics.net/q98R6SSVMU1wN5ZSqPpYrw#mid_azure_key_vault_integration "The MID Server integration with the Azure Key vault enables Orchestration, Discovery, and Service Mapping to run without storing any credentials on the instance.") * [Rekey a MID Server](https://servicenow-prod.fluidtopics.net/pL97YclPNbf5hsjR6JhaEA "Rekey a MID Server to generate a new private key. Private keys are used to decrypt automation credentials, so that MID Servers can transmit information securely. Key pairs are initially generated when a MID Server is validated, and MID Servers should be rekeyed periodically to meet security requirements.") * [Add SSL certificates for the MID Server](https://servicenow-prod.fluidtopics.net/Wze_LuvGY3XWJMv9a~ORjg#add-ssl-certificates "Configure the MID Server to connect to a source over SSL.") * [Attach a script file to a file synchronized MID Server](https://servicenow-prod.fluidtopics.net/vu1Hjk_D3VmPooctXzxerQ#mid-server-script-attach "You can attach a script file to synchronize to a connected MID Server. Windows Internet Explorer enhanced security blocks downloaded files that it determines are potentially dangerous. However synchronizing the files avoids this security problem.") **Zugehörige Verweise** * [MID Server configuration file security](https://servicenow-prod.fluidtopics.net/pExtHd2xoAcm8Vh~FXV9oQ "Sensitive MID Server configuration data can be protected using several different schemes, including internal and external data encryption and external data storage.")