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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Limit Allowed Number of Failed Login Attempts Before Lockout

# Limit Allowed Number of Failed Login Attempts Before Lockout {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Two script actions are available that enable a site administrator to manage the number
of times a user can provide an incorrect password before being locked out from the ServiceNow AI Platform. You can enable either of these script actions to manage failed login
attempts.
The SNC User Lockout Check or SNC User Lockout Check with Auto Unlock script actions enable the administrator to manage the number of failed login attempts for a user. Two script actions
are available that enable a site administrator to manage the number of times a user can provide correct password before getting locked out from the Now Platform.

Additionally, the glide.user.max_unlock_attempts system property controls the number of allowed failed login attempts. If the value of glide.user.max_unlock_attempts is increased above
the recommended value of <kbd class="ph userinput">5</kbd>, it increases the number of login attempts an attacker could make against a given user.

Ensure at least one of the script actions: SNC User Lockout Check or SNC User Lockout Check with Auto Unlock is enabled to manage failed login attempts. These script actions are stored
in the Script Actions \[sysevent_script_action\] table.

Additionally, ensure the property glide.user.max_unlock_attempts is set to <kbd class="ph userinput">5</kbd> or less.

## More information {#sc-managing-failed-login-attempts__section_wc1_cqn_phc}

{#sc-managing-failed-login-attempts__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | * SNC User Lockout Check (Script action) * SNC User Lockout Check with Auto Unlock (Script action) * glide.user.max_unlock_attempts(System property) {#sc-managing-failed-login-attempts__ul_avr_2yf_p3c} |
| Configuration type | * Script Action (/sysevent_script_action.do) * System Properties (/sys_properties_list.do) {#sc-managing-failed-login-attempts__ul_wlr_hyf_p3c} |
| Data type | Integer (for system property) |
| Recommended value | * The Script Actions \[sysevent_script_action\] table has the record with sys_id <kbd class="ph userinput">5e44f9bf0a0a0a0a019a6440b2137767</kbd> and/or the record with sys_id <kbd class="ph userinput">d92636b2975301008e00958e3b297567</kbd> set to active * glide.user.max_unlock_attempts system property is set to an integer less than or equal to 5. {#sc-managing-failed-login-attempts__ul_olg_4yf_p3c} |
| Default value | \<none\> |
| Fallback value | 5 (for system property) |
| Category | [Authentication](https://www.servicenow.com/docs/b9CEYnMpryNiLMZU_fh~Tw "The authentication category covers the main elements of modern authentication to confirm an entity and its claims are authentic and correct, resistant to impersonation and prevent interception of passwords.") |
| Security risk | * Severity score: 7.3 * CVSS rating: High * Security risk details: Allowing more attempts gives attackers additional opportunities to guess passwords, increasing the likelihood of unauthorized access and credential compromise. Proper lockout configuration is critical to maintaining strong authentication security. {#sc-managing-failed-login-attempts__ul_g1g_3sf_xwb} |
| Functional impact | None |
| Dependencies and prerequisites | None |
[ ]

{#sc-managing-failed-login-attempts__table_ajc_b43_3kb}