--- title: Check UI action conditions before execution description: Use the glide.security.strict.actions property to enable checking of UI actions conditions in forms and lists before they execute. When you set this property to true, it adds an extra layer of validation on the table UI actions before they are executed. locale: en-US canonical_url: https://www.servicenow.com/docs/r/platform-security/instance-security-hardening-settings/sc-check-ui-action-conditions-before-execution.html release: brazil product: Instance Security Hardening Settings classification: instance-security-hardening-settings topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 1 breadcrumb: [Access control, Hardening settings, Platform Security] --- # Check UI action conditions before execution Use the **glide.security.strict.actions** property to enable checking of UI actions conditions in forms and lists before they execute. When you set this property to true, it adds an extra layer of validation on the table UI actions before they are executed. If the **glide.security.strict.actions** system property isn't set to the recommended value of **true**, then there is no validation on the table UI before execution. Setting this property to secure value adds an extra layer of security validation. Ensure that the property **glide.security.strict.actions** is set to **true**. ## More information
| Attribute | Description |
|---|---|
| Configuration name | **glide.security.strict.actions** |
| Configuration type | System Properties \(/sys\_properties\_list.do\) |
| Data type | Boolean |
| Recommended value | true |
| Default value | TRUE |
| Fallback value | true |
| Category | [Access control](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-access-control.md) |
| Security risk | - Severity score: 3.3 - CVSS rating: Low - Security risk details: Users may perform unauthorized operations, leading to data manipulation, privilege escalation, and bypassing of access controls protecting sensitive records. |
| Functional impact | This remediation only adds an extra layer of validation to check for UI actions on the target table/page on the instance. As long as the access controls are set appropriately on the customer instance, there should not be an impact here. |
| Dependencies and prerequisites | None |