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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Logging, auditing, and errors

# Logging, auditing, and errors (instance security hardening) {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Apply a logging and auditing strategy so that you can identify and act on suspicious
activity in a timely manner.
To learn more about what can be logged in the instance, see [System logs](https://www.servicenow.com/docs/L35Ujy46TuDgiXbbkFnQiQ "The System Logs module provides a variety of logs that you can use to troubleshoot and debug transactions and events that take place within the instance."). Ensure that there is a schedule for
monitoring system events such as logins and failed logins by using System LogsEvents.
* **[Disabling SQL error messages (instance security hardening)](https://www.servicenow.com/docs/qH~dv8wdpVoKDiOClOrVRQ)**   
  Use the glide.db.loguser property to disable SQL error messages from rendering in a browser.

*[\>]: and then