---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Enforce credential alias usage

# Enforce credential alias usage {#ariaid-title1}

Release version: Brazil  
Updated September 20, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Learn how to secure your credentials from unauthorized use by configuring the MID Server property.
The Management, Instrumentation, and Discovery (MID) Server is a Java application that runs as a Windows service or UNIX daemon on your local network. MID Server properties are listed in the \[ecc_agent_property\] table. You can
access them in your instance by navigating to MID ServerProperties.

The MID Server property alias_filtering_behavior defines the behavior of Discovery aliases. When the behavior is not <kbd class="ph userinput">strict</kbd>, then all credentials are used regardless of their aliases for
Discovery schedules. This behavior might not be desirable in some circumstances, particularly for credentials with elevated privileges. Credential aliases provide more control over which credentials a Discovery schedule is allowed
to use and helps prevent the unnecessary exposure of credentials with elevated privileges.

See [MID Server properties](https://www.servicenow.com/docs/access?context=r_MIDServerProperties&version=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US) for more details.  
Important:  
This property has been deprecated and will be removed from future baselines.

## More information {#sc-enforce-credential-alias-usage__section_qhx_1b1_xwb}

{#sc-enforce-credential-alias-usage__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | alias_filtering_behavior |
| Configuration type | MID Server Properties (/ecc_agent_property_list.do) |
| Data type | string |
| Recommended value | strict |
| Default value | loose |
| Category | [Access control](https://www.servicenow.com/docs/x7vcJqvJ0dwOasc9M2~48A "The access control category audits the process of protecting resources from unauthorized access through granting and denying requests based on a permission model. This includes ensuring an entity accessing a resource holds valid credentials to do so, creating and protecting a well-defined set of roles or permissions and ensuring role or permission controls are protected from replay and tampering.") |
| Security risk | * Severity score: 2 * CVSS score: Low * Security risk details: When this hardening setting is not set to strict, then all credentials are used regardless of their aliases for Discovery tables which increases the chance of unauthorized access. {#sc-enforce-credential-alias-usage__ul_ihv_dvg_1xb} |
| Dependencies and prerequisites | None |
| References | * [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US) * [Credential aliases for Discovery](https://www.servicenow.com/docs/xkwDwMn0xb8y9FdML3jwXw#discovery-credential-alias "Credential aliases for Discovery allow an administrator to use specific credentials on Discovery schedules. You can configure behaviors for your aliases that determine how strictly the system enforces their use.") {#sc-enforce-credential-alias-usage__ul_pzy_yyv_gyb} |
[ ]

{#sc-enforce-credential-alias-usage__table_ajc_b43_3kb}

*[\>]: and then