Page History

Perspective Auditing Actions

Perspective Sessions generate entries in an assigned audit profile. The following actions are recorded in the Audit Profile:

• Tag changes from a component binding.
• Authentication level changes (a user's security level changes).
• Login Request - Indicates a user is requesting to log into an Identity Provider (IdP). The user should have been redirected to the IdP with a login request and Ignition is awaiting the IdP’s login response. Note that the user is not logged in until the IdP redirects the user back to Ignition with a login response and Ignition validates the login response.
• Login Response -  Records when a login response is received from the IdP. It’s possible that a login response will never be received for a login request. For example: if the user bails out of the login flow by closing their web browser before completing the login, Ignition will never receive the login response and will time out the request.
• Logout Request - Indicates a user is requesting to log out of an IdP. The user  may   be redirected to the IdP to log out of their IdP session. Regardless the user will be redirected back to the Perspective Session in a logged out state.
• Logout Response - Records when a logout response is received from the IdP after a user logged out of their IdP session. This event will not occur if the IdP does not support logout or if Ignition is not configured to redirect the user to the IdP for logging out.

• Tag changes from a Perspective script. Specifically:
  • Writes, such as, but not limited to, those from system.tag.writeBlocking
  • Edits and renaming, such as those caused by system.tag.configure
  • Deletions, such as those caused by system.tag.deleteTags
  • Moves, such as those caused by system.tag.move
  User Lockout Events. Note that the audit log will record only the initial lockout event, rather than each failed authorization attempt. changed

Vision Auditing Actions

The Vision project needs an audit profile configured and auditing enabled. Vision Clients will then log records to an assigned audit profile. Here is a list of audit actions that will be tracked in the Ignition auditing system:

Tags

The following Tag related actions generate entries in the audit log. Note that the functions below must originate from the Tag Browser, the Designer's Scripting Console, or Vision component-based scripts.

• Tag Creation - Including tags created with the Tag Editor and the system.tag.configure function.
• Tag Deletion - Including those deleted from the Tag Browser's UI and the system.tag.deleteTags function. 
• Tag Edits - Including edits made to tags from the Tag Editor and the system.tag.configure function.
• Moving Tags - Including moves made by drag-and-drop in the Tag Browser or by calling the system.tag.move function.
• Tag Renames - Renaming a tag generates an entry. 

Vision Tag Writes

Write requests sent from a tag either through a standard Tag Binding, Indirect Tag Binding, or manual entry from the Tag Browser. 

Vision Component Database Writes

The system explicitly captures modifications made to database tables through the following methods:

• SQL Query Bindings - modifications from the UPDATE Query will be recorded.
• DB Browse Binding - modifications made with the Enable Database Writeback area will be recorded. 

Vision User Login/Logout

• Logging into a Vision Client will generate an entry in the auditing system, as will logging out of the client. 
• Closing the client while logged in is treated as a logout. Note that the entry is only recorded if the client is aware that it is closing, which excludes cases where the client closed unexpectedly. 

Database Query Browser

• If the project opened in the Designer has an assigned Audit Profile, then changes made to database tables using the database query browser are automatically recorded to the audit log. "Changes" in this case refer to UPDATE, DELETE, or INSERT statements manually typed and executed from the database query browser.
• Enabling edit mode and applying changes, including typing in new values, adding rows, removing rows, and clearing out fields, are recorded as queries called from the project. 

Vision Scripting

The following functions generate entries in the audit log if called from Vision component-based scripts, or from the Designer's Scripting Console.

• system.db.execSProcCall
• system.db.runPrepUpdate
• system.db.runUpdateQuery
• system.tag.writeBlocking
• system.tag.writeAsync
• system.report.executeAndDistribute
• system.report.executeReport 

Designer

Designer Login and Closing

• Opening a project in the Designer that has auditing enabled will also generate a login entry in the auditing system. Note that this occurs when the user opens the project, not when they log in using the Designer's login screen: auditing is project-based, so the user has to select a project that is being edited first.
• Closing the Designer effectively counts as logging off, and will generate a "logout" entry. Similar to vision, should the designer close unexpectedly, then an entry will not be recorded. 

Database Query Browser

If the project opened in the  Designer  has an assigned Audit Profile, then changes made to  database  tables using the  database  query browser are automatically recorded to the audit log. "Changes" in this case refer to UPDATE, DELETE, or INSERT statements manually typed and executed from the  database  query browser.

Enabling edit mode and applying changes, including typing in new values, adding rows, removing rows, and clearing out fields, are recorded as queries called from the project. 

Alarm Notification

Alarm Notification Attempts

Attempts to send out alarm notifications are recorded in the auditing system. Specifically, the Gateway will record when it attempted to send out a notification, as well as if the attempt failed (such as the SMTP server refusing the request). It is important to note that the auditing system can not report failures that occur outside of the Gateway. Thus, if a voice notification fails to send due to some error in the VOIP system, it's possible that the Gateway won't report the VOIP error, but the audit log will have an entry stating that the Gateway attempted to send the notification.

Reporting Module

Report Execution

Reporting Module Reports generate an entry in the auditing system when a report is executed. Thus:

• Reports running on a schedule will generate an entry.
• Report schedules executed on demand will generate an entry.
• Navigating to a Vision window (in either the Designer or a Vision Client) will trigger a report execution, generating an entry in the auditing system.