pp108 : Auditing

Auditing

This topic presents an overview of auditing.


Auditing is a process of tracking changes that have occurred in a specific time period. These changes can be made by different users such as a user updating data through an application or an administrator deploying a package. In some scenarios, auditing is required to comply with government regulations. It involves maintaining a record of what modifications were made, who made them, when they were made, and on what data they were made. This is known as audit information. Therefore, audit information enables you to track changes made to an artifact and rectify defects, if any, found in one of these changes. Process Platform provides application auditing features for administrators.

Process Platform provides auditing on different artifacts. Auditing can be used to keep track of changes made to a Process Platform computer, which includes the following administrator actions:

  • Deploying a package
  • Maintaining users
  • Maintaining, starting, and stopping a service container
  • Updating XML Store and LDAP
  • Changing security settings

Besides auditing of administrator actions, Web service requests can also be audited. This can be done on both the following levels:

  • Web Gateway 
  • Service Container 

The administrator can configure auditing to perform auditing on the above actions. In addition, audit filters can be applied to limit the generation of audit data as auditing can result in a large amount of data. Existing audit data can be viewed and searched. This helps to find changes made by a specific user or changes made in a certain time frame on a specific artifact. For example, changing a specific property on the LDAP service container in the System organization last week. The administrator can also search for all user logins that failed on a specific date.

Maintaining audit records has a performance impact on the Process Platform run time. Enabling auditing may also result in a large amount of audit data, especially for Web gateway and Web service artifacts. To prevent this, use filtering and archive the audit data on a regular basis.