User and Permission Audit
audit_login_logout
Parameter description: Specifies whether to audit users' login (including login success and failure) and logout.
This is a SIGHUP parameter. Set it based on instructions provided in Table 1.
Value range: an integer ranging from 0 to 7
- 0 indicates that the function of auditing users' logins and logouts is disabled.
- 1 indicates that only successful user logins are audited.
- 2 indicates that only failed user logins are audited.
- 3 indicates that successful and failed user logins are audited.
- 4 indicates that only user logouts are audited.
- 5 indicates that successful user logouts and logins are audited.
- 6 indicates that failed user logouts and logins are audited.
- 7 indicates that successful user logins, failed user logins, and logouts are audited.
Default value: 7
audit_database_process
Parameter description: Specifies whether to audit the database startup, stop, switchover, and recovery.
This is a SIGHUP parameter. Set it based on instructions provided in Table 1.
Value range: 0 or 1
- 0 indicates that the function of auditing database startup, stop, switchover, and recovery is disabled.
- 1 indicates that the function of auditing database startup, stop, switchover, and recovery is enabled.
Default value: 1
When the database is started, the standby DN is promoted to primary. Therefore, the DN type in the audit log is system_switch when the DN is started.
audit_user_locked
Parameter description: Specifies whether to audit the users' locking and unlocking.
This is a SIGHUP parameter. Set it based on instructions provided in Table 1.
Value range: 0 or 1
- 0 indicates that the function of auditing user's locking and unlocking is disabled.
- 1 indicates that the function of auditing user's locking and unlocking is enabled.
Default value: 1
audit_user_violation
Parameter description: Specifies whether to audit the access violation operations of a user.
This is a SIGHUP parameter. Set it based on instructions provided in Table 1.
Value range: 0 or 1
- 0 indicates that the function of auditing the access violation operations of a user is disabled.
- 1 indicates that the function of auditing the access violation operations of a user is enabled.
Default value: 0
audit_grant_revoke
Parameter description: Specifies whether to audit the granting and revoking of user permissions.
This is a SIGHUP parameter. Set it based on instructions provided in Table 1.
Value range: 0 or 1
- 0 indicates that the function of auditing the granting and reclaiming of a user's permission is disabled.
- 1 indicates that the function of auditing the granting and reclaiming of a user's permission is enabled.
Default value: 1
full_audit_users
Parameter description: Specifies the full audit user list. Audit logs are recorded for all auditable operations performed by users in the list.
This is a SIGHUP parameter. Set it based on instructions provided in Table 1.
Value range: a string. Use commas (,) to separate multiple usernames.
Default value: empty
no_audit_client
Parameter description: Specifies the names and IP addresses of clients that do not need to be audited. The parameter format is client name@IP address, which is the same as that of the client_conninfo column in the pg_query_audit function, for example, cm_agent@127.0.0.1 or gs_clean@127.0.0.1.
This is a SIGHUP parameter. Set it based on instructions provided in Table 1.
Value range: a character string. Use commas (,) to separate multiple configuration items.
Default value: empty
- If the executed SQL statement meets the configuration requirements of full_audit_users and no_audit_client, the no_audit_client is preferentially configured.
- Audit logs are generated for communication among tools or nodes in the database server. To save space occupied by audit logs and improve the query performance of audit logs, the low-risk scenarios cannot be audited by configuring the no_audit_client parameter.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot