--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-australia-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3ba bundleId : - delta3ba --- # Combined Code Signing release notes for upgrades from Australia to Brazil # Combined Code Signing release notes for upgrades from Australia to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 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 Australia to Brazil This consolidated release notes page provides ServiceNow customers with a comprehensive view of all Code Signing updates from the Australia release family through to Brazil. It is designed to help you prepare for your upgrade by summarizing new features, changes, and important upgrade tasks. If no updates exist for a particular release, this is clearly noted to avoid confusion. Show full answer Show less ## Key Features * **Utilities Dashboard (Australia):** Monitor signature status and configuration health within the Code Signing Health and Status dashboard for proactive management. * **Multiple Signatures per Record (Australia):** Support for multiple signatures across different certificates enhances verification by evaluating all signatures from newest to oldest, ensuring valid signatures from any trusted source are recognized. * **Code Signing OOB Apps Signatures Plugin (Australia):** Automatically install build-time signatures for all relevant records in trued-up ServiceNow Store application versions, simplifying management and eliminating the need for self-signing. * **New Cryptographic Key Pair (Australia):** A stronger key pair is introduced to reinforce the Circle of Trust and secure signing processes, visible in the Key Pair and Certificates tab. * **Wild Card Purpose for KMF Signature Configuration (Australia):** Reduces import warnings specifically for script includes and business rules by using a wildcard purpose setting. * **Code Signing for Discovery Probes (Australia):** Discovery now enforces code signing for probes, parameters, and sensors on MID Servers, blocking unsigned or tampered payloads to ensure secure execution and compliance without affecting performance. * **Signature Generation on Source Control Commit (Brazil):** Code Signing signatures are automatically generated and included during application file commits to source control, enabling protected instances to validate received records seamlessly. * **Code Signing Change Audit Data (Brazil):** Audit trail records all create, update, and delete operations on Code Signed records, including user details and timestamps. Audit data retention is managed by a scheduled job, and users with the codesigningauditor role can access reports. ## Key Changes * **Guardrail Process Optimization (Australia):** The guardrail scan now checks all eligible records for missing signatures, not just records with existing signatures, allowing proactive identification and signing of unsigned records. * **Brazil Release:** No changes recorded for this release. ## Activation Code Signing is activated by enabling the **Code Signing (com.glide.codesigningenterprise)** plugin, which automatically installs the **Code Signing OOB Apps Signatures (com.glide.codesigning.oobappssignatures)** plugin. This applies to both Australia and Brazil releases. ## Upgrade Considerations Before upgrading to Brazil, review and complete all recommended pre- and post-upgrade tasks to ensure a smooth transition. No additional browser, localization, or accessibility requirements have been introduced or changed between Australia and Brazil. ## Benefits for ServiceNow Customers * Gain enhanced visibility and control over Code Signing coverage and compliance. * Ensure secure and tamper-proof execution of code across MID Servers and integrations. * Automate signature generation and validation to reduce manual effort and improve security posture. * Maintain comprehensive audit records to support compliance and security audits. * Mitigate upgrade failures and improve reliability by proactively identifying unsigned records. Consolidated page of all release notes for Code Signing from Australia 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 Australia 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 | |-|-| | 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__8} | Release | Release notes | |-|-| | 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__14} | Release | Release notes | |-|-| | 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__20} | Release | Release notes | |-|-| | 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__26} | Release | Release notes | |-|-| | 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__32} | Release | Release notes | |-|-| | 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__38} | Release | Release notes | |-|-| | 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__44} | Release | Release notes | |-|-| | 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__50} | Release | Release notes | |-|-| | 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__56} | Release | Release notes | |-|-| | 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__62} | Release | Release notes | |-|-| | 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. | [ ]