--- title: "Managing audit logs using the CLI" slug: "managing-audit-logs-using-the-cli-1" tags: ["File Protect (FX)", "Malware Analysis (AX)", "IAM", "Email Security - Cloud", "Network Security (NX)", "Email Security — Server", "Central Management System", "Helix Enterprise", "Endpoint Security (HX)", "Product Usage", "Install and Get Started", "Helix", "Intelligent Virtual Execution "] updated: 2026-09-01T19:03:20Z published: 2026-09-01T19:03:20Z canonical: "docs.trellix.com/managing-audit-logs-using-the-cli-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Managing audit logs using the CLI All user activities that impact the system, such as configuration changes, are automatically written to a log. Prerequisites - Admin access To manage audit logs: 1. Go to CLI configuration mode: ``` hostname > enable hostname # configure terminal ``` 2. Display the active audit log file, a list of all audit log files, an archived audit log file, or selected entries in the active audit log: ``` hostname (config) # show log audit ``` 3. Enable the override of the global minimum severity level of audit log messages saved in log files on the local disk: ``` hostname (config) # logging local override class audit ``` 4. Enable the global minimum severity level of the audit log messages with the specified severity level: ``` hostname (config) # logging local override class audit priority ``` You can select the following severity levels: - **none**—Disables logging. - **emerg**—System failure. - **alert**—Immediate action required. - **crit**—Critical condition. - **err**—Error condition. - **warning**—Warning of possible problem. - **notice**—Significant, but normal event (the default). - **info**—Information only. - **debug**—Debugging information. 5. Upload the active audit log file to the specified network location: ``` hostname (config) # logging files audit upload current ``` 6. Save your changes: ``` hostname (config) # write memory ``` :