ApplicationAudit «standard» for EMC Centera
The «standard» Edition of ApplicationAudt for EMC Centera allows responding to compliance audit questions targeted to data manipulation of the archive application. The most important questions answered are:
- Which information resp. data objects has been deleted
- When did the deletions take place
- Which application has deleted information
The functionality of ApplicationAudit is two-tiered. The service portion of ApplicationAudit performs the following tasks:
Database based hisotry of data creation
All defined source systems are queried for data creation history which is then stored in the ApplicationAudit database. All information back to 2002 (the launch of EMC Centera) will be gathered. Available meta-information is also stored.
Database based history of data deletion
All source systems are queried for data deletions since 2002 and the information is inserted into the ApplicationAudit database. The information stored contains the data and time of the data deletion, the profile and the IP Address of the system that performed the deletion. In case of Privileged Deletes the reason for the deletion before retention period expiry will be stored too.
Support of profiles
The definition of source systems is based on IP Addresses and profiles. The usage of profiles allows the selection of pools to be indexed. Testpools for example can easily be excluded by setting the capabilities of the used profile accordingly.
Definition of two source systems
ApplicationAudit Standard Edition allows the creation of two source systems. The Standard edition already allows to Audit a replicated pair of EMC Centera systems.
The examination of the stored data manipulation history is supported by a graphical user interface. It allows the following functionality:
Limiting search in time
Based on start and end date of the timeframe the search may be limited to the audited timeframe.
Listing data creation history (optionally with data deletions)
In the selected timeframe all data creations may be listed. Corresponding data deletion information can be included optionally should created information have already been deleted.
Listing data deletion history (optionally with creation information)
All data deletions in the selected timeframe can be listed. Optionally the creation information for the corresponding objects may be listed.
The archive data creation or deletion history may include all available metadata information.
If metadata information is included the output is stored in a xml file.
Clip_ID only format
For easier comparison the lists generated may also contain only the clip_id information. In this case a text file is created containing one object reference per line.