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


---

# Double check inbound transactions

# Double check inbound transactions {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Use the glide.security.strict.updates property to enable double-checking of security on inbound transactions during form submission. When you set this property to true, it adds an
extra layer of table validation before a form renders in the browser.
The glide.security.strict.updates system property provides an extra layer of security on form submission / field updates by ensuring only users with the proper permissions are allowed to update a form. If
glide.security.strict.updates is not set to the recommended value of true, then updates are not strict meaning they are able to modify fields visible to them regardless of whether
they have the appropriate permissions.

Ensure that the property glide.security.strict.updates exists in the System Properties \[sys_properties\] table and is set to "true".  
Warning:  
This is a safe harbor property, meaning the value can't be altered once it's changed. It is non-revertible.

## More information {#sc-double-check-inbound-transactions__section_wc1_cqn_phc}

{#sc-double-check-inbound-transactions__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | glide.security.strict.updates |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | Boolean |
| Recommended value | true |
| Default value | true |
| Fallback value | false |
| 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: 8.1 * CVSS rating: High * Security risk details: Users may be able to update form fields simply by having visibility into them, regardless of their actual permissions, creating a risk of unauthorized data modification and privilege escalation. {#sc-double-check-inbound-transactions__ul_g1g_3sf_xwb} |
| Functional impact | None |
| Dependencies and prerequisites | None |
[ ]

{#sc-double-check-inbound-transactions__table_ajc_b43_3kb}

To learn more about adding or creating a system
property, see [Add a system property](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US).