---
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 field ACLs for inbound query requests

# Enforce field ACLs for inbound query requests {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Manage how incoming queries are validated on your instance.
Use the glide.export.query.enforce_field_acl property to control whether field-level ACLs are enforced on the fields referenced in an inbound query requests. When set to true, field ACLs
are checked against fields used in the incoming query, and the query is rejected if the user is unauthorized to access those fields. When set to false, field ACLs are not checked on query conditions, and the
query executes regardless of field-level access restrictions.

This property applies only to field ACL enforcement on query conditions. Setting this property to false does not affect whether users can read field values they are not otherwise authorized to view.
Field-level read ACLs remain enforced regardless of this setting.

Set the property glide.export.query.enforce_field_acl to true.

## More information {#sc-enforce-field-acls-for-inbound-query-requests__section_ghv_dvg_1xb}

{#sc-enforce-field-acls-for-inbound-query-requests__table_hhv_dvg_1xb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | glide.export.query.enforce_field_acl |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | Boolean |
| Recommended value | true |
| Default value | true |
| Fallback value | false |
| Category | [Architecture, design, and threat modeling](https://www.servicenow.com/docs/flZLwb5A4NTOzIsm_05BPA "This broad control addresses high level design considerations and key elements to implement a secure application. This covers the tenants of availability, confidentiality processing integrity, non-repudiation and privacy. Additionally, elements of a secure software development lifecycle are included.") |
| Security risk | * Severity score: 4.4 * CVSS score: Medium * Security risk details: This can result in information disclosure to unauthorized parties. {#sc-enforce-field-acls-for-inbound-query-requests__ul_ihv_dvg_1xb} |
| Dependencies and prerequisites | None |
[ ]

{#sc-enforce-field-acls-for-inbound-query-requests__table_hhv_dvg_1xb}