---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Logs and Errors

# Troubleshooting and accessing logs {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Access various logs to troubleshoot and identify the failure reasons.

## Code Signing logs {#cs-logs__section_qpv_tmp_3rb}

If any of the ECC queue records is not signed by the Code Signing Tracker API, the unsigned messages and the required details are displayed in the Code Signing module. Navigate to System LogsSystem LogCode Signing to access the list
of records that are not trusted.

<br />

For additional debug node logs, enable
com.glide.codesigning.tracking.debug and set its value to
<kbd class="ph userinput">true</kbd>.

## Code Signing change audit data {#cs-logs__section_vault_audit_data}

To review the create, update, and delete operations that users performed on protected records, use the sn_cse_vault_codesigning_audit_data table. Each audit record identifies the changed record, the user who
changed it, the operation type, and the date and time of the change. Users with the sn_cse.codesigning_auditor role can view this data.

Audit data is separate from the Code Signing system logs described in this topic. For details about the audit fields, the conditions that generate an audit record, and the retention behavior, see [Code Signing change audit data](https://www.servicenow.com/docs/dtD~M_tFXVDY1B9ocvg5Ng "Review the create, update, and delete operations that users perform on records protected by Code Signing.").

## REST message signature validation failure on MID Server {#cs-logs__section_izn_grp_3rb}

Access the error message regarding to the signature validation failure, by navigating to System Web ServicesOutboundREST Message and opening the required REST message record.  
Figure 1. Signature validation failure on MID Server  
Note:  
Error messages related to the ECC firewall rejections start with <kbd class="ph userinput">ECC message execution denied</kbd>.
Figure 2. ECC queue when signature validation fails on MID Server Figure 3. Error message when ECC message is blocked by the user rule

## JDBC probe {#cs-logs__section_w4h_yrp_3rb}

When a JDBC data source with an invalid or missing signature is executed on a MID Server, an error message with the required details is displayed.

Source also displays the details of the error message.

## MID Server logs {#cs-logs__section_wbj_2vp_3rb}

To enable the detailed ECC firewall logging, increase the log level by setting the value of the MID Server configuration parameter, mid.log.level, to <kbd class="ph userinput">TRACE</kbd>. The detailed logs provide information about:

* Rules that the MID Server loaded from the boot configuration file.
* Granular execution trace of rules.
* Specific rule due to which an ECC message is to be accepted or rejected.

{#cs-logs__ul_zks_ybq_3rb}  
Note:  
If boot-config.xml is invalid, the MID Server fails to start and the failure details are logged in the MID agent logs.

*[\>]: and then