Audit Logs

One of the important aspects that’s more closely related to security is auditing.
The audit log contains entries for API calls or administrative actions that change the configuration or tracked activities of the Atomic Scope portal.

The primary purpose of audit logs is to keep track of the various actions taken by users. Audit logging is always enabled.

The action could be a configuration change or a change in the Atomic Scope Portal's user roles.

Auditing is such a crucial part for any enterprise software. Let's look at the scenario to see how such activities can cause major business disruption.

For example : For instance, if an administrator changes a user's role. The audit logs contain information about when that specific action occurred and who was involved in that operation.

We organised logs into categories to make it easier to track them.

We primarily track logs in the following categories:

• Alerts and Notifications
• Application Settings
• Business Process configuration
• Dashboard
• License Management
• Reprocess
• User Management
• Purging settings

Audit logs can be viewed by heading to the Audit Logs page in the Monitoring section.

Audit log entry structure

Every log entry in the audit logs contains the following information:

The action of the user in the Atomic Scope Portal
The logged time of the event
The username of the user who performed the action
The name of the category where the particular action belongs to
The Raw Content of the particular user action in the Json format.
The changes made in the content