User Community Service Desk Downloads
If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

Audit

Since Ataccama ONE processes data proprietary to your organization and often sensitive in nature, it is necessary to audit user actions taken within the tool. Thanks to the Audit module in Ataccama ONE, you can easily find answers to questions about which user accessed what data and how the data was used.

Logging format

User actions in ONE are logged in the following format:

  • Time: The date and time when an operation occurred.

  • User: The name of the user responsible for the action.

  • Action: The type of action performed, for example: OPERATION, FINISH_SUCCESS, READ.

  • Operation: Provides more details about the action, for example: Access detail, Detect anomalies, List, Check catalog item DQ availability.

  • Asset type: The type of asset, such as attribute, catalog item, connection, credentials, location, source.

  • Asset name: The name of the asset.

Access to audit information

You can view the information collected by the Audit module on the Audit tab in ONE. Here you can also search for specific events or users or filter the information for specific days. For more information about the Audit tab, see Audit.

By default, access to audit logs is restricted to power users. You can also create custom roles as needed, for instance, one administrator role without access to the audit logs and one role for the security team that can only view the audit information.

Audit logs can also be accessed through a GraphQL API. This gives you additional options for querying the collected information compared to what is available in the user interface. For more information, see Audit API.

Audit log storage and retention

The Audit module stores logs in a dedicated database schema. By default, logs are kept in the database for one year.

To use this data in a centralized audit tool, the Audit module can be configured to export logs to an AWS S3 compatible object storage. If you do not have a storage solution compatible with S3, MinIO is used as an abstraction layer between the Audit module and your storage.

The log export always contains the logs from the previous day, regardless of how often it is created. Once logs have been successfully exported, the Audit module does not export the logs from the same day again. The default retention period of exported logs is 14 days.

Was this page useful?