Audited Events - BCPro - LIT-12011905 - Server - BCPro Data Server - 4.0

BCPro Data Server
Product
Building Automation Systems > Databases and Data Servers > BCPro Data Server
Document type
User Guide
Document number
LIT-12011905
Version
4.0
Revision date
2020-03-27

Audited events are significant events occurring in the system that trigger the Audit Trail feature to generate an audit message. The following table lists the features and corresponding actions that initiate the generation of audit messages. The following table also lists Audit Classes (Set 568) in which the actions belong. Click the feature name for more information about that feature.

Table 1. Audited Events

Feature

Action Causing Audit Message

ActionQ

each command issued, enabled, disabled, or deleted (Audit Class = User Action)

Audit Trail

  • each command issued to clear the Audit Repository. See Clearing the Audit Repository. (Audit Class = User Action)
  • each command issued to discard an audit message or a group of audit messages (Audit Class = User Action)
  • each command issued to change the Enabled Audit Level attribute in the Workstation Device Object based on a system event, a user changing the time of day, or a user command

Diagnostics

each errorlog listing problems with your BCPro system such as detected software or configuration errors (Audit Class = Diagnostic)

Trend Extensions

  • each new trend extension created (Audit Class = User Action)
  • each change to the trend routing configuration (Audit Class = User Action)
  • each command issued to the trend extension (Audit Class = User Action)
  • each change to trend views such as creating, deleting, or editing a trend view (Audit Class = User Action)
  • each change to the BCPro Workstation configuration (Audit Class = User Action)

Scheduling

  • each item added to or removed from the schedule (Audit Class = User Action)
  • each change to the key item or its scheduled attribute (Audit Class = User Action)
  • each change to the effective period (Audit Class = User Action)
  • each time the schedule is enabled or disabled (Audit Class = User Action or Application)

System Security
  • each successful and failed log on and log off attempt (Audit Class = User Action)
  • each administrative action (Audit Class = User Action)
  • each authentication failure (Audit Class = Application)
  • each authorization failure (Audit Class = Application)

Navigation Tree and Other Features
  • each user command (Audit Class = User Action)
  • each change in item configuration such as adding, deleting, and editing an item (Audit Class = User Action)
  • each controller upload, download, synchronization, and reset occurring in online mode. Audit messages are not generated for those actions in the BCT offline mode. (Audit Class = User Action, Application, Non-critical System Event, Critical System Event)