--- sourceDocument: Brazil IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Discovery on Code Signing instances # Discovery on Code Signing instances {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Discovery on Code Signing instances Discovery on ServiceNow instances with Code Signing enabled ensures that all Discovery components containing scripts or commands are validated for integrity before execution. This validation happens at both the instance and MID Server levels to prevent unauthorized or tampered scripts from running on MID Servers and target machines, enhancing overall security. Show full answer Show less ## How it works * **Instance-level validation:** Checks signatures on probes and probe parameters. Tampered probes are rejected and not sent to MID Servers. Untrusted probe parameters are excluded from execution. * **MID Server-level validation:** Validates signatures on patterns, MID script includes, and MID script files. Invalid patterns are not downloaded or are deleted if previously downloaded, preventing their execution until re-signed. * Signatures are automatically included with Discovery applications and plugins, enabling seamless code signing when platform and store app requirements are met. ## Benefits * **Security protection:** Blocks execution of unsigned or tampered payloads, reducing risk from compromised instances. * **Authenticity verification:** Ensures probes, parameters, and sensors come from trusted sources and remain unaltered. * **Compliance support:** Enhances audit capabilities by preventing unauthorized script execution without affecting Discovery performance. * **Integrity assurance:** Confirms sensitive Discovery component fields are unchanged after signing. ## Requirements * ServiceNow AI Platform Brazil version. * Installed Store applications with minimum versions: Discovery Admin Workspace v1.13.0, Visibility Content v6.13.10, Discovery and Service Mapping Patterns v1.30.2. * Code Signing enabled with an established Circle of Trust. ## Supported discovery types * IP-based Discovery * Cloud Discovery (requires additional configuration) ## Signature validation scope Code Signing validates signatures on Discovery tables that contain executable scripts or commands, including probes, probe parameters, sensors, and patterns, to maintain integrity and security. ## Limitations The pattern debugger is not available on instances with Code Signing enabled. Discovery is supported on instances with Code Signing enabled. Code signing validates the integrity of Discovery components before execution to help prevent unauthorized scripts from running on MID Servers and target machines. ## How it works {#code-sign-disco-probes__section_r2t_zyt_k3c} When Code Signing is enabled, Discovery validates signatures on components that contain scripts or commands before execution. Validation occurs at both the instance level and the MID Server level. The instance validates signatures on probes and probe parameters. If a probe is tampered with, the instance rejects it and doesn't send it to the MID Server for processing. If probe parameters aren't trusted, they aren't added to the probe. The probe still launches, but without the untrusted parameters. The MID Server validates signatures on patterns, MID script includes, and MID script files. If a pattern's signature is invalid, the MID Server won't download it. If the pattern was previously downloaded, it's deleted. Discovery can't run that pattern on any machine until it's re-signed. Signatures are included automatically with Discovery applications and plugins. When your platform and store apps meet the requirements, code signing for Discovery works without manual signing. For more information about how code signing works, see [Code Signing](https://www.servicenow.com/docs/access?context=code-signing-landing&version=brazil&pubname=brazil-platform-security&ft:locale=en-US). ## Benefits {#code-sign-disco-probes__section_jrv_bf5_k3c} The following examples highlight the primary advantages of using code signing: * Security protection: Blocks unsigned or tampered payloads from executing on MID Servers and target machines, helping prevent malicious actors from running dangerous commands even if an instance is compromised. * Authenticity verification: Confirms that probes, parameters, and sensors originate from a trusted source and haven't been modified since signing. * Compliance support: Strengthens audit capabilities by helping prevent unauthorized script execution without impacting discovery performance. * Integrity assurance: Validates that sensitive fields in Discovery components haven't been altered after signing. {#code-sign-disco-probes__ul_pg2_ff5_k3c} ## Requirements {#code-sign-disco-probes__section_rym_wyt_k3c} Code signing for Discovery requires the following dependencies: * You must be using the Brazil version of the ServiceNow AI Platform. * You must have the following ServiceNow Store applications and versions installed: * Discovery Admin Workspace v1.13.0 * Visibility Content v6.13.10 * Discovery and Service Mapping Patterns v1.30.2 {#code-sign-disco-probes__ul_afg_yzz_y2c} * You must have Code Signing enabled with the Circle of Trust established. For more information, see [Configuring Code Signing](https://www.servicenow.com/docs/access?context=config-code-signing&version=brazil&pubname=brazil-platform-security&ft:locale=en-US). {#code-sign-disco-probes__ul_k12_czt_k3c} ## Supported discovery types {#code-sign-disco-probes__section_s2f_xyt_k3c} Code signing for Discovery supports the following discovery methods: * IP-based Discovery * Cloud Discovery Note: Cloud Discovery requires additional configuration. For more information, see [Configure Cloud Discovery for code-signed instances](https://www.servicenow.com/docs/4dN_0EXVEX2Zn8oXtdiatQ "Configure a system property to disable unsupported script tracking for Cloud Discovery operations on instances with code signing enabled."). {#code-sign-disco-probes__ul_q4g_hzt_k3c} ## Signature validation scope {#code-sign-disco-probes__section_um2_hfc_l3c} Code signing validates signatures on Discovery tables that contain scripts or commands executed on target machines or MID Servers. This includes probes, probe parameters, sensors, patterns, and more. ## Limitations {#code-sign-disco-probes__section_rwv_zzt_k3c} Pattern debugger isn't available on code-signed instances. **Related topics** * [Code Signing](https://www.servicenow.com/docs/access?context=code-signing-landing&version=brazil&pubname=brazil-platform-security&ft:locale=en-US)