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. 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)
  Use the glide.db.loguser property to disable SQL error messages from rendering in a browser.