Security

 

dbMaestro TeamWorkâ„¢ prevents unauthorized changes to your database and tells you Who did What When and Why to your database.

When people talk about database security, they usually mean the ability to detect and prevent unauthorized access to data in a database. But another factor that is no less important is the ability to prevent unauthorized changes to the database structure and data it contains, including unauthorized changes by users who do have authorization to access the database . TeamWork™ provides both of these capabilities to DBAs and the IT team.

Change Management Policy Enforcement

TeamWork’s change policy enforcement is integrated in the database itself and cannot be bypassed. Before the database engine performs a change command, it checks the TeamWork™ change policy to verify that the command is approved. If TeamWork™ approves the command, the database engine executes it. Otherwise, TeamWork™ returns an error message identifying the unapproved command.

To execute a command that changes a database object, the DBA must use the Check-Out procedure to unlock the object in TeamWork™. This action guarantees that each change is documented correctly. After the DBA completes the changes and Check-In the change, TeamWork™ closes the change cycle by saving the object’s new definition in the repository and setting the object’s status to locked.

By controlling the change cycle, TeamWorkâ„¢ produces an accurate audit trail of changes to the database, correlating each change (What) with the person who made the change (Who), the date and time of the change (When), and the business requirement for the change (Why). TeamWorkâ„¢ allows users to review the history of a single object or the entire schema and provides the capability to drill down to the change itself.

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 Audit with dbMaestro TeamWork™, see Auditing