Auditing

A compliance audit can be a veritable nightmare. No one likes an audit and no one wants to be in the hot seat, but compliance is a major issue. It continues to be one of the highest priorities for IT organizations and there is no end in sight for the foreseeable future.

dbMaestro TeamWork for Oracle Studio Reports

dbMaestro TeamWork for Oracle™ enables IT organizations to satisfy database compliance requirements, including those of GLBA (Gramm-Leach-Bliley Act) SOX (Sarbanes-Oxley), PCI-DSS (Payment Card Industry Data Security Standard) and COBIT (Control OBjectives for Information and related Technology).

It is highly recommended to implement auditing procedures that help satisfy compliance requirements before the auditors arrive. It is also important to apply these procedures to all databases. Auditors will not be happy if data is well protected in production databases but the same data is unprotected in development and test databases.

Providing security safeguards and satisfying compliance requirements are almost never the most … or even the third or fourth most … important goal when designing and implementing new and upgraded systems. But implementing security guidelines and required audit procedures at the start will save a lot of time and anguish later.

In addition to following Oracle’s best practice recommendations, examine the security guidelines and checklists provided at www.checklist20.com.

Whatever the auditor wants to know, dbMaestro TeamWork for Oracle™ has the answer.

• What changes were made to the database? TeamWork’s database version control and auditing feature saves and tracks all database change versions.


• Why was this change made and who made it? TeamWork for Oracle™ integrates with major software configuration management products, such as IBM Rational Team Concert® and Microsoft Team Foundation Server®. This integration enables changes to an application’s database to be linked to a work item or change set that identifies the reason for the change and the person responsible for making it.


• When was this change made? The date and time of all check-out and check-in events is saved in the TeamWork repository.

Because enforcement of TeamWork for Oracle’s change policy enforcement is integrated in the database engine, it cannot be bypassed. This guarantees you will have an accurate audit trail.

For information about Merge Deployment Automation using dbMaestro TeamWork™, see Development Process Management

For information about Merge Deployment Automation using dbMaestro TeamWork™, see Merge Deployment Automation

For information about Security with dbMaestro TeamWork™, see Security