Follow

Internal Auditing System for Preserving Data Integrity

Perspective’s internal auditing system allows authorized users to view the exact details of a record's history, including tracking when, where, and who created, modified, or deleted records in the database. It even tracks which users are logged into Perspective at any given moment and, in many cases, precisely what records they are viewing. This extensive auditing functionality helps safeguard the integrity of system data, assists organizations in adhering to legislative and corporate reporting requirements, and reduces the risk of litigation.

Data Integrity

Auditing data is read-only to all users. The data cannot be edited, manipulated, or tampered with under normal use of the application, including through the APIs. Designated administrators can view the data, but only the System Administrator (also known as the Master Admin) can modify the audit settings to enable auditing and retention rules.

Auditing Settings

Only the System Administrator is authorized to modify audit system settings. The System Administrator may enable or disable auditing functionality, specify how long audit data will be stored within the system (either indefinitely or for a retention period of up to 180 days), and may even choose to allow audit reads—the tracking of when, where, and by whom a record was viewed, with or without modification—for Incident, Case, Item, Person, Organization or Vehicle records, as well as for electronically submitted e-Incidents.

Auditing Modules

The data tracked by Perspective’s auditing system is drawn from five main program areas, called modules. The System Administrator may customize audit settings for each of these modules separately, as well as for each of the record entities within the Data Forms module (Incidents, Cases, Items, Persons, Organizations, and Vehicles). The following section describes the five auditing modules and the data tracked by each one.

Administration Module

All changes made in the Administration section are tracked, including modifications to Workgroups, Roles, System Settings, and Account Policies. Each audit log indicates:

  • The date and time the change occurred.

  • The GMT offset of the date and time log.

  • The user who made the change.

  • The scope of the change (edits to Workgroups, Roles, etc.).

  • An XML file detailing every change field by field.

  • The IP address of the originating machine.

User Account Module

All changes made to user accounts are tracked, including modifications to Rights, Privileges, Defaults, and numerous other settings. Each audit log indicates:

  • The date and time the change occurred.

  • The GMT offset of the date and time log.

  • The user who made the change.

  • The user record that was modified.

  • The scope of the change (New, Update, or Delete).

  • An XML file detailing every change field by field.

  • The IP address of the originating machine.

User Sessions Module

All logon, logoff, failed (logon attempts resulting in account lock-out), and expired user sessions are tracked. Each audit log indicates:

  • The date and time the change occurred.

  • The GMT offset of the date and time log.

  • The user who initiated the session.

  • The scope of the change (Logon, Logoff, Expired, or Lock-Out).

  • The IP address of the originating machine.

Data Forms Module

All changes made to any of the data form entities (Incidents, Cases, Items, Persons, Organizations, or Vehicles) are tracked. Each audit log indicates:

  • The date and time the change occurred.

  • The GMT offset of the date and time log.

  • The user who made the change.

  • The ID number for the record that was modified.

  • The scope of the change (New, View, Update, or Delete).

  • A flag for a security control change (archiving or locking a record, or editing a record’s Workgroup, Access Level, or Organizational Rollup).

  • An XML file detailing every change field by field.

  • The IP address of the originating machine.

e-Incident Module

All changes made to e-Incidents (Incident records submitted electronically through Perspective Portal, Perspective e-Reporting, Gateway Endpoint, or the Import Manager) are tracked. Each audit log indicates:

  • The date and time the change occurred.

  • The GMT offset of the date and time log.

  • The user who made the change.

  • The ID number for the e-Incident that was modified.

  • The scope of the change (New, View, Update, or Delete).

  • A flag for a security control change (editing an e-Incident’s Workgroup, Access Level, or Organizational Rollup).

  • An XML file detailing every change field by field.

  • The IP address of the originating machine.

For further information about Perspective's auditing capabilities, please contact your Resolver account manager.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk