---
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


---

# Location filter

# Location filter {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Location filter criteria can be used as filter input for users based on the user location.

Location filter is a filter criteria that the admins can use while crafting the authentication policies based on the physical location of the device.  
Note:  
* Location filter is available with the Zero Trust Access feature. For more information, see [Zero Trust Access (ZTA)](https://www.servicenow.com/docs/zv3z7tRvQy_ZPy7UnfI~vA "Zero Trust Access (ZTA) is a security model in which no user or device is trusted by default.").
* The instance should be on ADCv2. If the instance isn't on ADCv2, then user location information won't be available.
{#location-filter__ul_whv_k5f_4xb}

The location filter criteria enable you to perform the following:

* Act as policy input for policy conditions to verify and meet the requirements for authentication.
* Provide an ability to create adaptive authentication policies based on the country.
* Allow or not allow instance access to a given geography.
* Use the geo location-based pre-authentication or post authentication policy to:
  * Block access from sanctioned countries and from outside a tight privacy-controlled region, at company discretion.
  * Allow access only to areas within the applicable privacy region, at company discretion.
  * Configure country-based allow list for authentication.
  {#location-filter__ul_pg1_22j_swb}

{#location-filter__ul_orn_dxl_mxb}

## Use cases {#location-filter__section_rwt_rcj_swb}

Following are some of the use cases for using location filter criteria for Adaptive Authentication:

* Block access to the instance from a country.
* Allow access to the instance only from a particular country.
* Enforce step-up authentication or MFA to log in based on country.
* Reduce or limit roles for the user based on the country.
* Location filter criteria can be used for MFA, Zero Trust Access (ZTA), pre-authentication context, and post-authentication context.
{#location-filter__ul_trn_vcj_swb}

## Location Identification {#location-filter__section_p4d_sqp_1yb}

The location services for identifying the location of the user are provided by a third-party service - MaxMind.

The location of the user is identified through the VPN, from the x-forwarded-for header. If there's no header populated by the service, then only the VPN IP (location) is displayed as the user location.  
Note:  
If there are incorrect locations displayed after the location filter configuration, see the [KB article](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1436102) to troubleshoot.