Skip to content

Understand STACKIT Audit log

An Audit log is a record of events that happen in a system or application. It captures important information about activities, accesses, and changes.

Audit logs are valuable for monitoring, security, compliance, and troubleshooting. By recording events in detail, they provide a basis for analyzing and improving business processes.

The STACKIT Audit log is a service that enables governance, compliance, and operational risk auditing on a STACKIT organization or project. Every action a user, service account, or the STACKIT system takes is recorded as an audit log event. Audit log entries are primarily associated with projects.

Auditing helps answer these questions:

  • What happened? : Event name
  • When did it happen? : Timestamp
  • Who started it? : Initiator
  • What was the target or where was the action observed? : Organization

The Audit Log currently gets events from these core platform services:

  • Membership service: Events for adding, removing, or updating memberships at the organization, folder, and project levels.
  • Resource manager: Events for creating, deleting, or updating organizations, folders, and projects.
  • Service account service: Events for creating and deleting service accounts, and creating and revoking access tokens.
  • Always on: Admin activities are recorded by default. You do not need to set it up manually. The Audit Log history is viewable, searchable, and downloadable for 90 days. You can manage the Audit Log via the Audit Log API or the STACKIT Portal.
  • Compliance: Provides a security-relevant, chronological set of records documenting the sequence of actions.
  • Completeness: The audit log collects activities from both users and the STACKIT platform.
  • Traceability: Trace activities and changes to find out who, when, and what was done. It provides a complete record of events, which helps with transparency and traceability.
  • Compliance and governance: Meet compliance needs and regulations. By recording and keeping audit trails, you can show that specific policies were followed and that security-related events were documented.
  • Troubleshooting and problem resolution: Troubleshoot and resolve problems with detailed information about system activity and interactions. It allows administrators to track the progression of events and identify potential root causes of problems.
  • Performance optimization: Identify and improve bottlenecks or inefficient processes. The insights gained from the logs can be used to optimize system performance and identify bottlenecks.