Auditing of AD and Service User changes

Atria Auditing and Logging

Introduction

This article summarizes the auditing mechanisms for changes executed through the Atria system.  
The User table contains a record of all system users, each User has a UserID numeric identifier.  The UserID is used to track who made changes within the audit tables and is referred to throughout this article.

User Authentication Records

All user authentication into the Atria system is recorded in the LoginHistory table in the OLM database..  This stores the UserID of the user, LoginDateTime and the web server SessionID.

Core Data Entities

All core entities have associated Audit tables,  
For example
Users table - has a corresponding - Users_AT table

Audit tables have identical columns to the table being audited, but include additional columns to identify the type of change, when it changed and who changed it
      ModifiedBy The UserID of the actual user who performed the change
      ImpersonatingUserID If the user impersonation feature was being used, the UserID of the user being impersonated is stored
      ActionPerformed One of “Inserted”, “Updated”, “Deleted” 
      ActionDate The System DateTime of the change 

As changes are made, new entries are written to the audit tables.  An audit record is created on every insert, update or delete being performed.
Note that Atria does not delete data from audit tables.

Atria manages changes to some external systems in realtime, these do not have explicit audit tables.  Examples include – Group Management, Exchange Contact Management.  For these, the GenericAudit table is used, it records the User, Impersonation, Action DateTime, Action performed.

Provisioning Records

Provisioning Requests are tracked with detailed logging of actions performed.  Provisioning requests are used to action changes to users into external systems.
The Requests Table and RequestLog table can be used to extract details of actions performed by the system, this also records the user who initiated the request.

User Action Logging

All HTTP Post requests are recorded into the AuditActions table, this stores the URL/Route, UserID, ImpersonatingUserID, Session CorrelationID and Date Time performed.

Error Logging

The system uses the Serilog open source logging framework.  By default the Atria system records errors and general system logging into the Logs table. 

    • Related Articles

    • Atria Billing Setup User Guide

      Objective This article describes how to configure Atria to utilize the latest billing features. This document outlines the billing setup attributes that should be configured.    Applies to Introduced in Atria version 12.0.0 Billing Setup Overview To ...

    • Billing with Atria

      Atria Billing Index Atria has a systematic approach to tracking services that it manages, this data can be exported or directly integrated via API into external PSA or billing systems. Background Information Quick video on billing and auditing How ...

    • Display Patterns for Billing Line Descriptions

      Purpose: When generating billing data, two descriptions are generated for each billable item - Line description (detailed) and summary descriptions.   The Summary Description serves two purpose: Used as a template for your invoice lines and reporting ...

    • Billing Rules Engine User Guide

      Objective This article describes how to use the Atria billing rules engine to identify specific Atria entities as non-billable.   Applies to Introduced in Atria version 12.0.0 Billing Rule Feature Overview Many entities - customers, services, users, ...

    • Service Billing Summary Report

      Objective This article describes the information contained in the Billing Summary Report.     Applies to Introduced in Atria version 12.0.0 Billing Summary Report Overview The service billing summary report is designed to highlight the billable ...