---
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 signature verification for Flow Designer artifacts

# Enforce signature verification for Flow Designer artifacts {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The com.glide.hub.code_signing.full.validation.enabled property controls the strictness of checks enforced when Code Signing is fully enabled.
When set to <kbd class="ph userinput">true</kbd>, stricter checks are enforced and certain Flow Designer features incompatible with [Code Signing](https://www.servicenow.com/docs/4X_N430MkgWq~JQUacg~AQ "Use Code Signing to create digital signatures that prevent unauthorized or tampered External Communication Channel (ECC) queue records from being processed by MID Servers. This cryptographic verification helps maintain the integrity of integrations between ServiceNow and external systems.") are blocked. If set to <kbd class="ph userinput">false</kbd> or left unset, legacy checks are performed instead, and a subset of Code Signing-incompatible Flow Designer features are allowed to execute.

To configure this property:

1. You must have the security_admin role.
2. The Code Signing plugin (com.glide.code_signing) must be fully enabled. See [Configuring Code Signing](https://www.servicenow.com/docs/0q5frDAcYVdRKTCdn7n_vA "Activate and configure Code Signing to verify the authenticity and integrity of your data.").
3. Navigate to /sys_properties_list.do on the instance.
4. Set the com.glide.hub.code_signing.full.validation.enabled property to <kbd class="ph userinput">true</kbd>.

## More information {#sc-enforce-signature-verification-for-flow-designer-artifacts__section_more_info}

{#sc-enforce-signature-verification-for-flow-designer-artifacts__table_property_details-enforce-signature-verification-for-flow-designer-artifacts__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | com.glide.hub.code_signing.full.validation.enabled |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | Boolean |
| Recommended value | <kbd class="ph userinput">true</kbd> |
| Default value | <kbd class="ph userinput">false</kbd> |
| Fallback value | <kbd class="ph userinput">false</kbd> |
| Category | [Malicious code](https://www.servicenow.com/docs/K1DqQQ9~Zs_MfYpJc8oc5w "The Malicious Code category ensures that best efforts are made to confirm that your code is free of vulnerabilities and unwanted functionality.") |
| Security risk | * Security risk rating:Medium * CVSS score: 4.4 * When signature validation is turned off, Flow Designer artifacts execute without cryptographic verification of their origin or integrity. This allows attackers to inject unsigned or tampered flows that execute with system privileges. An attacker could modify a flow to exfiltrate data, escalate privileges, or create backdoors without detection because digest validation is bypassed entirely. Disabling this control removes a critical safeguard that verifies only authorized, unmodified code executes through Flow Designer. {#sc-enforce-signature-verification-for-flow-designer-artifacts__sc-sec-risk-enforce-signature-verification-for-flow-designer-artifacts} |
| Functional impact | When enabled, Flow Designer artifacts are validated for cryptographic signatures and integrity digests. Unsigned or tampered flows are flagged as untrusted in guardrails reports and require explicit review before deployment. When disabled (the default), signature verification and digest validation are skipped, allowing unsigned or tampered flows to execute without verification. Although this reduces scan overhead, it eliminates the detection of unsigned or tampered code. Organizations should enable this property in all production environments to enforce artifact integrity and prevent execution of unverified flows. The default disabled state represents a significant security gap. |
| Dependencies and prerequisites | This property requires Code Signing to be fully enabled on the instance. |
[ ]

{#sc-enforce-signature-verification-for-flow-designer-artifacts__table_property_details-enforce-signature-verification-for-flow-designer-artifacts}

