Audit trails enable organizations to meet strict data governance and compliance requirements by providing a comprehensive, chronological log of all administrator actions performed within the Druva Management Console. Audit trails enhance transparency, traceability, and accountability, serving as a critical resource for forensic investigations and compliance audits.
Benefits
Beyond meeting core security and regulatory compliance requirements, audit trails empower administrators to:
Enforce Secure Access Control: Monitor and secure how Druva resources and entities are accessed across the organization.
Centralize Activity Monitoring: Maintain total visibility over all administrator actions within the Management Console.
Accelerate Troubleshooting & Forensics: Quickly isolate, diagnose, and remediate erroneous, unauthorized, or critical activities.
Generate Target Audits & Reports: Filter logs by specific resources or entities to generate on-demand reports for internal and external auditors.
Maintain Long-Term Historical Data: Access a continuous, reliable archive of activity records for up to three years.
📝 Note
Authorized Roles: Only Druva Cloud Administrators and Data Protection Officers (DPOs) can view the activity trails of other administrators.
Retention Period: By default, Druva retains audit trail logs for three years. Records are automatically and permanently deleted after this period.
Druva automatically generates the Admin Audit Trails report on the first day of every month and notifies all Cloud Administrators via email. Cloud Administrators can easily view, filter, and export these logs directly from the console. For more information see Admin Audit Trails Report.
View Standard Reports: Navigate to the Reports menu to access the monthly Admin Audit Trails report.
Generate Custom Reports: Use the Admin Audit Trails page to apply specific operational filters and isolate the exact data needed. You may also download the standard or customi reports directly from the interface for offline analysis or compliance documentation.
The following table describes the fields on the Admin Audit Trails page.
Field | Description |
Administrator | The name of the administrator who performed the action. |
Action | The action performed by the administrator. For example, Create, Update, Delete, Login, Backup Now, and so on. |
Entity Type | The type of the Druva entity on which the administrator performed the action. For example, Admin Group, Backup Set, Billing Cost Code, Admin, and so on. |
Entity Name | The name of the Druva entity on which the administrator performed the action. |
Resource Type | The type of the Druva resource associated with the entity. For example, Files, MS-SQL, TurboTier, VMware, and so on. If an admin creates the My_config_rule entity of type VM Auto Config Rule, the resource type of the entity is VMware. |
Organization | The name of the organization to which the entity is associated with. The actions performed on the global dashboard, such as SSO settings, cost allocation, and so on, are accounted under All Organizations. 📝 Note
The Organization column is displayed only if organization is enabled.
|
Time | The timestamp of the action performed by the administrator. |