You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 15, 2024. It is now read-only.
This is the master ticket for tracking BP-40 : Audit logging for BookieShell.
In order to make a software compliant with the security and privacy controls, we need to meet certain audit requirements.
One of them being able to track every human / user intervention in the software.
Zookeeper has something similar going on in ZOOKEEPER-1260.
The idea is that all user and human actions should be logged separately in a different log file which has stricter permissions and all interactions should be logged in detail.
This is useful for admins to later surmise what user interactions happened and can reconstruct the state of the system before and after the user interaction based on the audit logs.
Original Issue: apache#2209
BP
This is the master ticket for tracking BP-40 : Audit logging for BookieShell.
In order to make a software compliant with the security and privacy controls, we need to meet certain audit requirements.
One of them being able to track every human / user intervention in the software.
Zookeeper has something similar going on in ZOOKEEPER-1260.
The idea is that all user and human actions should be logged separately in a different log file which has stricter permissions and all interactions should be logged in detail.
This is useful for admins to later surmise what user interactions happened and can reconstruct the state of the system before and after the user interaction based on the audit logs.
Proposal PR - Link
The text was updated successfully, but these errors were encountered: