IDMS Audit Database Maintenance
Audit database overview
The IDMS audit databases contain all of the historic data for the credentialing activities. The table below provides information about what each audit database contains.
| Database Name | Contents |
|---|---|
| IdExchange.AuditSynchModule | Logs all data from the automated external system data imports. This data is used to track the success and failures of transactions submitted from an external system. |
| IdExchange.Audit | Logs all of the general credential activity data performed by operators. This data is used to track the activities of operators. |
| IdExchange.RequestTracker | Logs all of the user's credential state changes. This data is used to track the credentialing history of a given user. |
How the data is used
The IDMS uses the audit data to execute the real time reports. If this data is moved, the following reports will be impacted:
- Site Summary
- Credential Aging
- Operator Transaction HIstory
- User History
- Event Logging
Database size management recommendations
Over time, the IDMS audit databases can grow in size and may need to be migrated off line for data maintenance purposes. If data must be migrated offline to reclaim data space or to improve performance, the list below serves as general guidance to ensure the data can be restored. Remember to always abide by corporate data retention policies before delete any data.
- Before performing any data export activities, backup the database to a secure location.
- Do not completely delete the database or database schema. Instead, securely export the data.
- Encrypt data with FIPS 140-2 approved encryption.
- Perform a restoration process with the data to ensure the data can be decrypted, restored and utilized by the IDMS.
- Once data integrity has been confirmed, store the encrypted data in a secure location and create a log of where the data is stored.
- Securely delete any backup data or temporary data used in the data export process.