Audit Trail

  • Article

Applies To: Opalis 6.3

The Audit Trail is a collection of text file logs that contain information about the interaction of a policy with external tools and systems. This enables users to report on configuration and change compliance of processes and provides a quick method to identify what and who made changes to a third-party system for audit purposes or to remediate a change that causes service interruption.

Depending on how many policies you run and how many objects those policies contain, the Audit Trail may consume a large amount of disk space on the computer that runs the management server and action server. We recommend that you implement an archiving procedure to move the files generated by the Audit Trail to another computer to prevent your computers from running out of disk space.

Activating and Deactivating the Audit Trail

By default, the Audit Trail is not activated when you install Opalis Integration Server.

To activate or deactivate the Audit Trail

  1. Open a command prompt and navigate to the following folder: C:\Program Files\Opalis Software\Opalis Integration Server\Management Service.

  2. Type one of the following commands:

    • To activate the Audit Trail: atlc /enable

    • To deactivate the Audit Trail: atlc /disable

The Audit Trail Record

The Audit Trail records the following information:

  • Who or what started a policy – the date and time at which the policy was launched, the user name and domain that launched the policy, the name of the computer where the policy ran, and the name of the policy that was launched. If the policy was launched by another policy (for example, by the Trigger Policy object in the launching policy), this policy name is recorded as the entity that launched the policy.

  • Configuration data from each object in running policies – the date and time at which the object ran, the name of the action server it ran on, the ID of the Policy Module that ran it, and the Object XML code that it received as input data.

Finding the Audit Trail Files

These Audit Trail files are stored in the following folders on the management server computer:

  • ...\Opalis Integration Server\Management Service\Audit – PolicyPublisher files

  • ...\Opalis Integration Server\Operator Console\Audit – PolicyPublisher files

These Audit Trail files are stored in the following folder on the action server computer:

  • ...\Opalis Integration Server\Action Server\Audit – PolicyPublisher and ObjectRuntimeInfo files

The files are written in csv format. The Audit Trail files are assigned the following names:

  • Computer Name_PolicyPublisherTimestamp.csv. For example: MyComputer_PolicyPublisher20080417T142803.csv

  • Computer Name_ObjectRuntimeInfoTimestamp.csv. For example: MyComputer_ObjectRuntimeInfo20080417T142803.csv

When a file reaches 200 megabytes in size, a new file is created. The new file name is unique because the timestamp is included in the file name. Passwords and password-like fields are represented by five asterisks (*****) in the Audit Trail files.

Privacy

Opalis, a Microsoft Subsidiary, is committed to protecting your privacy, while delivering software that brings you the performance, power, and convenience you want.

The following sections describe the information that is collected and how it is used.

Workflow Data Logging

What This Feature Does

Workflow activities that interact with systems can be configured to collect data that would be considered private.

Information Collected, Processed, or Transmitted:

Examples of such systems would be Active Directory and BMC Remedy. By default, this data (referred to as "Object Specific Published Data" in the product) is not logged; however, the Enterprise can select an option to "Log Object Specific Published Data" in which case this data will be logged to the database and visible in the Operator Console/Designer.

Use of Information:

This information is not sent outside of the Enterprise.

Choice/Control:

For more information aboutenabling and disabling this feature, see "Configuring Policy Log Options" in the Opalis Integration Server Client User Guide (https://go.microsoft.com/fwlink/?LinkID=205284).

Important Information:

Workflows (referred to as "policies" in the product) have a revision history associated with them. This history is stored in the database along with the Active Directory SID of the user that created the changes. This feature cannot be disabled.

Workflow Exports

What This Feature Does:

The Enterprise can export policies and other Opalis configuration information into an XML-formatted file intended to be used as a policy export/import mechanism.

Information Collected, Processed, or Transmitted:

These exports will contain information about the policies(s) as required to import them at a subsequent date. Any information stored in an Opalis workflow would be present in the export. This would include form-field data configured into policy objects ("Activities") as well as policy owner information such as SIDs from Active Directory.

Use of Information:

This information is not sent outside of the Enterprise.

Choice/Control:

The export/import feature is only present in the Opalis Client (the “Designer”) and you may opt not to use this feature.

For more information, seethe Opalis 6.3 Privacy Statement (https://go.microsoft.com/fwlink/?LinkID=202690).