dbMaestro TeamWork 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.
Whatever the auditor wants to know, dbMaestro TeamWork provides the answer.
- Do you have well defined Roles and Responsibilities? Are these definitions enforced? dbMaestro TeamWorkhelps you easily define and enforce roles and responsibilities and makes sure everyone does only what they should do.
- 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? dbMaestro TeamWork 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 and from that to the business requirement that drives 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 are saved in the dbMaestro TeamWork's repository.