---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Signature Verification

# Signature Verification in Code Signing {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Signature verification ensures that records, scripts, and other signed content originate from trusted sources and remain unaltered.

## Signature Verification process {#signature-verification-in-code-signing__verification-process}

Signature verification is a core part of Code Signing. When the MID Server processes a signed record or script, it checks the attached digital signature against the certificate used to generate it. This verification confirms that the
content is authentic and hasn't been modified since it was signed. If the signature is valid and the certificate is trusted, the system permits the operation. If the signature is invalid or the certificate is untrusted, the system
blocks execution to protect the environment.

## Support for multiple signatures per record {#signature-verification-in-code-signing__multiple-signatures-update}

With the Australia release, there's enhanced support for verifying multiple signatures on a single record. A record might collect signatures over time from different certificates, such as customer-owned certificates and ServiceNow® build certificates. To ensure more accurate verification, the system now groups signatures by certificate and evaluates the most recent signature in each group. Compared to the previous model, which
evaluated only the most recent signature on the record, this approach provides a more reliable verification process.

Verification succeeds if any certificate group contains a valid latest signature. This improvement ensures that a valid signature from one certificate isn't overlooked simply because a newer signature from another certificate is
invalid. Failures after upgrades are avoided and all valid signatures from any trusted source are recognized.