--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-zurich-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3bz bundleId : - delta3bz --- # Combined Code Signing release notes for upgrades from Zurich to Brazil # Combined Code Signing release notes for upgrades from Zurich to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Combined Code Signing release notes for upgrades from Zurich to Brazil This consolidated guide provides ServiceNow customers with essential information about Code Signing updates and features introduced from the Zurich through Brazil releases. It is designed to help you prepare for and manage your upgrade to the Brazil release by summarizing new capabilities, changes, activation procedures, and important considerations across these versions. Show full answer Show less ## Key Features * **Self-Service Plugin Installation:** Starting in Zurich, administrators can install the Code Signing plugin directly from the ServiceNow Plugin portal without needing support assistance, simplifying deployment. * **Quorum Controlled Certificate Revocation:** Introduced in Zurich, this feature enhances security by requiring multiple stakeholder approvals to revoke Code Signing certificates, preventing unauthorized revocations. * **Code Signing Health and Status Dashboard:** Available from Zurich, this dashboard centralizes monitoring of your Code Signing environment's health, configurations, and provides actionable guidance for resolving issues. * **Utilities Dashboard in Australia Release:** A tab within the Health and Status dashboard to track signature status and detect configuration issues, helping maintain system integrity. * **Support for Multiple Signatures:** Allows multiple signatures from different certificates on a single record, improving validation flexibility. * **Code Signing OOB Apps Signatures Plugin:** Available since Zurich, this plugin installs build-time signatures for ServiceNow Store app versions, eliminating the need for self-signing. * **New Cryptographic Key Pair:** Strengthens the security "Circle of Trust" with a new key pair visible in the Health and Status dashboard. * **Wildcard Purpose in Signature Configurations:** Helps eliminate import warnings for script includes and business rules during signing processes. * **Enforced Code Signing for Discovery Probes:** From Zurich onwards, code signing is mandatory for probes, parameters, and sensors on MID Servers, blocking unsigned or tampered payloads and improving compliance. * **Automatic Signature Generation on Source Control Commit (Brazil):** Signatures are now generated automatically when committing application files from trusted instances, ensuring code integrity during source control operations. * **Code Signing Change Audit Data (Brazil):** Tracks user operations (create, update, delete) on signed records with audit records accessible to users holding the codesigningauditor role. Audit data retention is managed via scheduled jobs. ## Important Changes * **Coral Theme Default (Zurich):** The Coral theme is now the default for portals and mobile experiences, offering improved UI with dark mode options. * **Enhanced Verification for ACC Framework Tables (Zurich):** Signature files can now be generated for tables extending Agent Client Collector configurations, ensuring attachments pass code signing verification when enabled. * **Guardrail Process Optimization (Australia):** The guardrail scan now identifies records missing signatures proactively, rather than only validating existing signatures, improving code signing coverage visibility. ## Activation and Requirements * Code Signing is activated by enabling the **com.glide.codesigningenterprise** plugin across Zurich, Australia, and Brazil releases. * Installing this plugin also automatically installs the **Code Signing OOB Apps Signatures** plugin (`com.glide.codesigning.oobappssignatures`), simplifying setup for build-time signatures. * No additional browser, localization, or accessibility requirements were introduced or changed between Zurich and Brazil. ## Benefits for ServiceNow Customers * Improved security through quorum-based certificate revocation and enforced signing for discovery probes. * Simplified installation and management with self-service plugin activation and centralized monitoring dashboards. * Enhanced compliance with comprehensive audit trails and automatic signature generation during source control commits. * Greater flexibility and reliability by supporting multiple signatures per record and improving guardrail scanning. * Streamlined upgrade processes and reduced failures by leveraging build-time signatures for Store applications. Overall, these updates equip ServiceNow customers with stronger security controls, better visibility, and automation to maintain trusted code environments as they upgrade from Zurich to Brazil. Consolidated page of all release notes for Code Signing from Zurich to Brazil. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Code Signing release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Zurich to Brazil. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading Code Signing to Brazil Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-codesigning-summary__entry__2} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## New features Between your current release family and Brazil, new features were introduced for Code Signing. {#dfrn3-codesigning-summary__entry__10} | Release | Release notes | |-|-| | Zurich | [Code Signing Installation using Plugin](https://www.servicenow.com/docs/access?context=enable-codesiging&family=zurich&ft:locale=en-US) : Customer administrators can now install the Code Signing plugin directly from the ServiceNow Plugin portal without the need to contact the Customer Service and Support team to enable the Code Signing framework. This enhancement supports self-service deployment and simplifies the installation process. [Quorum Controlled Certificate Revocation](https://www.servicenow.com/docs/access?context=certificate-revocation&family=zurich&ft:locale=en-US) : Revoke Code Signing certificates using a quorum-based control policy. Revoke certificates to help prevent them from being used to verify signatures. A quorum-based approval flow promotes added security by requiring approvals from multiple stakeholders, to help prevent unintended or unauthorized certificate revocations. [Code Signing Health and Status Dashboard](https://www.servicenow.com/docs/access?context=code-signing-health-and-status-dashboard&family=zurich&ft:locale=en-US) : The new Code Signing Health and Status dashboard provides a centralized, user-friendly interface to monitor the overall health and configuration of your code signing environment. It highlights configuration settings, displays the status of essential components, and offers actionable guidance to help resolve issues effectively. | | Australia | [Utilities Dashboard](https://www.servicenow.com/docs/access?context=code-signing-utilities&family=australia&ft:locale=en-US) : Use the Utilities Dashboard tab within the Code Signing Health and Status dashboard to monitor signature status, detect configuration issues, and maintain the overall health of your Code Signing environment. [Multiple signatures for a record across certificates](https://www.servicenow.com/docs/access?context=signature-verification-in-code-signing&family=australia&ft:locale=en-US) : Leverage support for multiple signatures for records across different certificates, thus ensuring that valid signatures from any trusted source are recognized. Allow multiple signatures to be added to a record and have the system determine validity by evaluating all existing signatures from newest to oldest. [Code Signing OOB Apps Signatures plugin](https://www.servicenow.com/docs/access?context=explore-code-signing&family=australia&ft:locale=en-US) : Use this plugin (com.glide.code_signing.oob_apps_signatures) to install build time signatures for all relevant records in trued-up ServiceNow® Store application versions. [New key pair](https://www.servicenow.com/docs/access?context=code-signing-certificates&family=australia&ft:locale=en-US) : A new cryptographic key pair is generated to strengthen the Circle of Trust and to ensure a secure signing process. You can see this key pair within the Key Pair and Certificates tab of the Code Signing Health and Status dashboard. [Wild Card Purpose for KMF Signature Configuration](https://www.servicenow.com/docs/access?context=explore-code-signing&family=australia&ft:locale=en-US) : Use the "Wild Card Purpose" entry in the signature configurations to eliminate import warnings for script includes and business rules. [Code signing for probes](https://www.servicenow.com/docs/access?context=sign-files-nonprod&family=australia&ft:locale=en-US) : Discovery now enforces code signing for probes, parameters, and sensors to guarantee authenticity, integrity, and secure execution on MID Servers. This update blocks unsigned or tampered payloads, provides signature validation, and strengthens compliance by helping prevent audit gaps without impacting discovery performance. | | Brazil | [Signature generation during source control commit](https://www.servicenow.com/docs/access?context=c_cs_commit_signing&family=brazil&ft:locale=en-US) : Generate Code Signing signatures automatically when you commit application files to source control from a trusted instance. Signatures are created for eligible records during the commit and pushed to the remote repository in the same update set as their source records, so a protected instance can validate the records it receives. [Code Signing change audit data](https://www.servicenow.com/docs/access?context=cs-vault-audit-data&family=brazil&ft:locale=en-US) : Review the create, update, and delete operations that users perform on records protected by Code Signing. Each audit record identifies the changed record, the user who changed it, the operation type, and the date and time of the change. Audit data is recorded by default on production instances when Code Signing is active, and users with the codesigning_auditor role can view and report on it. A scheduled job manages the size of the audit data based on a configurable retention period and maximum record count. | [ ] ## Changes Between your current release family and Brazil, some changes were made to existing Code Signing features. {#dfrn3-codesigning-summary__entry__18} | Release | Release notes | |-|-| | Zurich | Coral theme : Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. [Enhanced Code-Signing Verification for ACC Framework Table](https://www.servicenow.com/docs/access?context=config-code-signing&family=zurich&ft:locale=en-US) : You can now generate KMF signature files for tables that extend Agent Client Collector Configuration (`sn_agent_configuration_file`) and Agent Client Collector Plugin (`sn_agent_asset`). This enhancement allows attachments from the tables to successfully pass code-signing verification and be downloaded to the MID Server when code signing is enabled. | | Australia | [Guardrail process optimization and scope increase](https://www.servicenow.com/docs/access?context=signature-verification-status&family=australia&ft:locale=en-US) : Allows you to run the guardrail scan and identify records that have missing signatures, enabling you to proactively address records that are eligible for code signing but remain unsigned. Previously, the system only checked records with existing signatures and marked them as valid or invalid, which meant records without signatures were overlooked. Now, the process starts from the signature configuration itself, every eligible record is checked to see if it has a signature. If a record is missing a signature, it's clearly identified. | | Brazil | No updates for this release. | [ ] ## Removed Between your current release family and Brazil, some Code Signing features or functionality were removed. {#dfrn3-codesigning-summary__entry__26} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Deprecations Between your current release family and Brazil, some Code Signing features or functionality were deprecated. {#dfrn3-codesigning-summary__entry__34} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Activation information Review information on how to activate Code Signing. {#dfrn3-codesigning-summary__entry__42} | Release | Release notes | |-|-| | Zurich | Activation information : Code Signing is a ServiceNow AI Platform feature that is available with activation of the Code Signing (com.glide.code_signing_enterprise) plugin. For details, see [Configure](https://www.servicenow.com/docs/access?context=config-code-signing&family=zurich&ft:locale=en-US). | | Australia | Activation information : Code Signing is a ServiceNow AI Platform feature that is available with activation of the Code Signing (com.glide.code_signing_enterprise) plugin. Installing this plugin automatically installs the Code Signing OOB App Signatures plugin (com.glide.code_signing.oob_apps_signatures). For details, see [Configure](https://www.servicenow.com/docs/access?context=config-code-signing&family=australia&ft:locale=en-US). | | Brazil | Activation information : Code Signing is a ServiceNow AI Platform feature available with activation of the Code Signing (com.glide.code_signing_enterprise) plugin. Installing this plugin automatically installs the Code Signing OOB App Signatures plugin (com.glide.code_signing.oob_apps_signatures). For details, see [Configure](https://www.servicenow.com/docs/access?context=config-code-signing&family=brazil&ft:locale=en-US). | [ ] ## Additional requirements If any additional requirements were introduced or changed for Code Signing we have noted them here. {#dfrn3-codesigning-summary__entry__50} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Code Signing we have noted them here. {#dfrn3-codesigning-summary__entry__58} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Code Signing, such as specific requirements or compliance levels. {#dfrn3-codesigning-summary__entry__66} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Code Signing we have noted them here. {#dfrn3-codesigning-summary__entry__74} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Code Signing we have noted them here. {#dfrn3-codesigning-summary__entry__82} | Release | Release notes | |-|-| | Zurich | [Zurich Patch 4](https://www.servicenow.com/docs/access?context=zurich-patch-4&family=zurich&ft:locale=en-US) [Code Signing OOB Apps Signatures plugin](https://www.servicenow.com/docs/access?context=explore-code-signing&family=zurich&ft:locale=en-US) : Use this plugin (com.glide.code_signing.oob_apps_signatures) to install build time signatures for all relevant records in trued-up ServiceNow® Store application versions. * Use Code Signing Guardrails to improve checks during the signing process to create more secure workflows. * Use the Code Signing Migration workflow to identify the signatures that are created with expired or inactive certificates and re-assign them to the appropriate records automatically. * Revoke Code Signing certificates securely using a quorum-based approval policy to prevent unauthorized use. * Monitor and manage your Code Signing environment with the new Health and Status dashboard. * The restructured navigation panel and the renamed pages provide improved accessibility and streamlined functionality. | | Australia | * Gain complete visibility into Code Signing coverage by proactively identifying eligible records with missing signatures using the optimized guardrail scan. * Install build time signatures for records in all trued-up ServiceNow Store application versions, thus eliminating the self-signing process. * Ensure reliable script verification by supporting multiple signatures for a record across certificates. Reduce upgrade failures and improve compliance for customers using custom and ServiceNow® certificates. See [Code Signing](https://www.servicenow.com/docs/access?context=code-signing-landing&family=australia&ft:locale=en-US) for more information. | | Brazil | * Prevent unauthorized code execution by enabling cryptographic verification of all scripts on your MID Servers. * Detect tampering instantly by identifying modifications to signed records and automatically blocking compromised code. * Streamline security enforcement by automating signature verification across integrations without requiring manual intervention. * Support compliance needs by maintaining comprehensive audit records of all signature verification events. See [Code Signing](https://www.servicenow.com/docs/access?context=code-signing-landing&family=brazil&ft:locale=en-US) for more information. | [ ]