Audit Logs

Overview

The Audit Log provides a complete, chronological record of all activities within devguard. It is a cornerstone of compliance, ensuring transparency, accountability, and the ability to demonstrate due diligence to auditors and regulators.

By maintaining an immutable timeline of actions, the Audit Log supports:

• Security: Detect and investigate unauthorized changes.
• Compliance: Demonstrate adherence to regulatory requirements.
• Governance: Provide accountability for decisions and operations.

The log interface is styled as a familiar system log view, with entries listed chronologically and grouped by date.

Core Functionality

The Audit Log automatically captures and records actions across all modules, including:

• Creation of new objects (e.g., policies, assets, risks)
• Updates to existing objects (e.g., coverage status changes, policy versions)
• Deletions of items where allowed
• Access-related changes (e.g., member updates, entitlement reviews)

Each entry shows:

• The timestamp of the action
• The user who performed it
• The object type (Policy, Asset, Risk, Control, Audit, etc.)
• The action performed (e.g., created, updated, approved)
• A short description providing context

Search and Filtering

A search bar allows users to quickly locate relevant entries. You can filter by:

• User name
• Object type
• Action type
• Keywords in descriptions

This enables efficient incident investigations or compliance checks.

Pagination and Retention

Audit logs are paginated for performance, allowing you to browse large histories without delay. All entries are retained according to your organization’s compliance policies.

Data Immutability

Audit logs are view-only and cannot be modified or deleted. This ensures a tamper-proof record of all activities.

Fields Explained

Best Practices

• Review regularly: Include audit log checks in your security and compliance routines to detect anomalies early.
• Use search effectively: Filter by object type (e.g., “Policy”) or user to investigate incidents or confirm compliance activity.
• Integrate with audits: During audits, use the log as primary evidence of activity history and compliance.
• Train your team: Ensure staff understand that the Audit Log is immutable and reflects all actions, promoting accountability.

For example, if a policy was updated unexpectedly, you can search by policy name or the responsible user to quickly confirm who made the change, when it was applied, and what version was created.

Compliance Value

Because entries are immutable and time-stamped, the Audit Log provides a trustworthy chain of evidence. This makes it invaluable for:

• ISO 27001 or SOC 2 audits
• Internal governance reviews
• Regulatory inquiries

The Audit Log in devguard ensures your organization maintains a transparent, tamper-proof record of all activities, supporting operational excellence, accountability, and compliance across all modules.