Combined Code Signing release notes for upgrades from Yokohama to Brazil

reference brazil Updated Nov 6, 2026 8 min read brazil-yokohama-codesigning-release-notes.md
Raw file servicenow.com

Consolidated page of all release notes for Code Signing from Yokohama 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 Yokohama 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.

Release

Release notes

Yokohama

No updates for this release.

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.

Release

Release notes

Yokohama

No updates for this release.

Zurich

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.

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.

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

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.

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.

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.

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.

Use the "Wild Card Purpose" entry in the signature configurations to eliminate import warnings for script includes and business rules.

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

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.

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.

Release

Release notes

Yokohama

The Code Signing Guardrails check has been improved to enhance signature verification, resulting in more secure workflows. In addition, multiple optimizations have been implemented to improve the performance benchmarks of the Guardrails scan, and log files now feature a more intuitive naming convention, which simplifies file identification within your system.

Code Signing now enforces limits on large update sets to improve the user experience. The maximum size for an update set is 10,000 records.

The trusted non-production instance has been renamed to trusted instance, and the protected production instance has been renamed to protected instance. These naming updates have been made to better align with customer usage.

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.

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

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.

Release

Release notes

Yokohama

No updates for this release.

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.

Release

Release notes

Yokohama

No updates for this release.

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.

Release

Release notes

Yokohama

  • 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 Configuring Code Signing.

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.

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.

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.

## Additional requirements

If any additional requirements were introduced or changed for Code Signing we have noted them here.

Release

Release notes

Yokohama

No updates for this release.

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.

Release

Release notes

Yokohama

No updates for this release.

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.

Release

Release notes

Yokohama

No updates for this release.

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.

Release

Release notes

Yokohama

No updates for this release.

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.

Release

Release notes

Yokohama

Use Code Signing Guardrails to improve checks during the signing process to create more secure workflows.

See Code Signing for more information.

Zurich

Zurich Patch 4

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 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 for more information.

**Parent Topic:**[Products combined by family](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/delta-yokohama-brazil/rn-combined-intro.md)
Search documentation
Search document titles and file paths on the brazil branch