---
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
---
# Configure unique MID Server users
# Configure unique MID Server users {#ariaid-title1}
Release version: Brazil
Updated September 10, 2026
 1 minute to read
Create a unique user account for each of your MID Servers to support auditability, enforce security controls, and enable least privilege access.
MID Server users authenticate MID Servers to the ServiceNow instance and enable communication to the instance. Configure each MID Server with a unique user account to support auditability and security controls. Assigning a unique user account to each MID Server follows the principle of least privilege and enables proper identity and access management for your service accounts.
Configure each MID Server with a unique user account that has been assigned the mid_server role:
1. Navigate to AllUser AdministrationUsers.
2. Create a user for each MID Server (for example, mid_server_prod_01, mid_server_dev_01).
3. In the Roles section, assign the mid_server role to each user account.
Note:
Roles cannot be assigned until after the record is saved.
4. Configure each MID Server to authenticate with its dedicated user account.
5. Verify no duplicate Logged in user values exist in MID Server \[ecc_agent\] table records.
{#sc-configure-unique-mid-server-users__ol_omw_2tx_s3c}
For existing shared user accounts:
1. Identify all MID Servers sharing the same user account. (Records in the MID Server \[ecc_agent\] table that have identical Logged in user field values).
2. Create unique user accounts (User \[sys_user\] records) for each MID Server.
3. Update each MID Server's configuration to use its dedicated account.
4. Test connectivity before decommissioning the shared account.
{#sc-configure-unique-mid-server-users__ol_nqj_jwx_s3c}
## More information {#sc-configure-unique-mid-server-users__section_wc1_cqn_phc}
{#sc-configure-unique-mid-server-users__table_ajc_b43_3kb__entry__2}
| Attribute | Description |
|-|-|
| Configuration name | User \[sys_user\] and MID Server \[ecc_agent\] table records. |
| Configuration type | User \[sys_user\] and MID Server \[ecc_agent\] table records. |
| Data type | Table record |
| Recommended value | Each MID Server \[ecc_agent\] record should have a unique User \[sys_user\] record in it's Logged in user field. This user should have the mid_server role. |
| Default value | N/A |
| Fallback value | N/A |
| 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: 3.8 * CVSS rating: Low * Security risk details: When multiple MID Servers share the same user account, it is difficult to perform the following: * Determine which specific MID Server performed an action * Trace the source of suspicious or malicious activity * Implement granular access controls per MID Server * Investigate security incidents or operational issues * Comply with security logging and attribution requirements {#sc-configure-unique-mid-server-users__ul_d5f_lyx_s3c} {#sc-configure-unique-mid-server-users__ul_g1g_3sf_xwb} |
| Functional impact | Creating unique user accounts for each MID Server has no functional impact on MID Server capabilities or performance. All MID Servers will continue to operate normally with the mid_server role permissions. |
| Dependencies and prerequisites | None |
[ ]
{#sc-configure-unique-mid-server-users__table_ajc_b43_3kb}
*[\>]: and then