---
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


---

# Capture audit records for Code Signing-protected records

# Capture audit records for Code Signing-protected records {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Use the sn_cse.com.snc.csf.vault_audit_enabled property to control whether the system logs changes to Code Signing-protected code.
When this property is set to `true`, every creation, modification, or deletion of protected code is logged, allowing administrators to review who changed
what and when. When inactive, no audit trail is created for protected code changes.  
Note:  
This property only applies when [Code Signing](https://www.servicenow.com/docs/4X_N430MkgWq~JQUacg~AQ "Use Code Signing to create digital signatures that prevent unauthorized or tampered External Communication Channel (ECC) queue records from being processed by MID Servers. This cryptographic verification helps maintain the integrity of integrations between ServiceNow and external systems.") is activated on your instance. It has no effect on unprotected code or test and development environments.

## More information {#sc-capture-audit-records-for-code-signing__section_pyv_1z3_bkc}

{#sc-capture-audit-records-for-code-signing__table_l5d_fsp_bkc__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | sn_cse.com.snc.csf.vault_audit_enabled |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | Boolean |
| Recommended value | true |
| Default value | true |
| Fallback value | false |
| Category | [Architecture, design, and threat modeling](https://www.servicenow.com/docs/flZLwb5A4NTOzIsm_05BPA "This broad control addresses high level design considerations and key elements to implement a secure application. This covers the tenants of availability, confidentiality processing integrity, non-repudiation and privacy. Additionally, elements of a secure software development lifecycle are included.") |
| Security risk | * Severity score:5.1 * CVSS rating:Medium * Security risk details: Disabling this property stops audit logging for protected records. Attackers or insiders with write access can modify or delete scripts, business rules, and configurations without leaving any trace, hiding their activity from audits and conformance reports. While this doesn't bypass access controls, it delays incident response and tampers detection---a critical concern for regulatory conformance. {#sc-capture-audit-records-for-code-signing__ul_jlk_bsp_bkc} |
| Functional impact | When enabled (the default), the system automatically records every change made to protected records in an audit log: who changed it, what changed, and when. Administrators can review this log for conformance and troubleshooting without any extra setup. This requires the Code Signing feature to be active and works automatically on production systems while skipping test and development environments to reduce log noise. Disabling the property stops these audit records from being created. It reduces database activity but removes the visibility teams require to track changes and verify conformance. The setting takes effect immediately without requiring a restart. |
| Dependencies and prerequisites | This property requires the Code Signing feature to be activated on your instance. It has no effect if Code Signing is not enabled. |
[ ]

{#sc-capture-audit-records-for-code-signing__table_l5d_fsp_bkc}