Why do we need Audit Logs?
When hundreds of corporate users have access to VIDIZMO Portal with respect to their organizational units, it is almost impossible to track the changes being made to the system which can eventually prove detrimental in terms of content management. For this reason, it is imperative to introduce strict measures of monitoring and control. For increased security with respect to the integrity of content and its control settings, Audit Logs in a Portal help track activity against each user.
What is an Audit Log?
An Audit Log also referred to as an audit trail, is a chronological record of the data, documenting the sequence of operations taken place on a portal by the user that can affect the functionality, procedure, event, or media type. In most cases, an audit log comprises of the security relevant data.
The Admins and Managers can access Audit Logs which are used to track and record user activity such as login, date, time, actions performed. This includes the content viewed, change in settings, upload, add and delete users, campaigns, collections, etc.
In VIDIZMO, every activity is logged into the system by the event. Maintaining audit and logs are extremely useful for enterprises to ensure check and balance. The Administrators can gather information about who accessed or downloaded the content or who made changes to the Account/Channel settings.
The Administrators can easily keep track of the employee activity in an extremely secure and organized manner. These audit logs offer increased security ensuring that any potential security breach or misuse of information does not occur.
They can view the Audit Logs, to keep track of user activity. These logs tabulate the data before and after user activity. The data is filtered using the Event, IP Address, User, SubjectType, Description, Date & time and Details.
Any action performed by the user affecting the functionality of the Portal. For example, contentUpload.
- IP Address
An address of the machine using which the particular Event has been triggered.
Name of the User who performed the event against which the log has been maintained.
This defines the scope of the Event that has been triggered for increased understanding and review. For example, an Event UserLogin will have the SubjectType as PersonalProfile.
It briefly describes the outcome of their event trigger. For example is the Event is User Login, then the Description would be <authenticate>.
- Date & Time
This is the date and time when the Event was triggered, and helps in identifying the sequence of Events.
This contains any miscellaneous details about the triggered Event.
There is also an option to add filters with respect to specific IP Address/User/Email Address, Events that you opt to be notified about and the Start/End Date to define the duration for the logs to be maintained for. Moreover, the logs can be exported as CSV. Read more about it here: How to View and Export Audit Logs.
Permissions and Roles:
- Admins and Managers can:
- Access and monitor all Audit Logs for enhanced security and tracking.
- Set up custom Audit Logs with respect to IP Address, User, Events, etc.