Logging, auditing, and errors \(instance security hardening\)

---
title: Logging, auditing, and errors \(instance security hardening\)
description: Apply a logging and auditing strategy so that you can identify and act on suspicious activity in a timely manner.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/logging-auditing-errors-instance-security-hardening.html
release: australia
topic_type: reference
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Logs, Platform Security]
---

# Logging, auditing, and errors \(instance security hardening\)

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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/system-logs.md). Ensure that there is a schedule for monitoring system events such as logins and failed logins by using **System Logs** > **Events**.

-   **[Disabling SQL error messages \(instance security hardening\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/disabling-sql-error-messages.md)**  
Use the **glide.db.loguser** property to disable SQL error messages from rendering in a browser.

**Parent Topic:**[Logs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/logs.md)