While the majority of database administrators and other privileged users are good, honest professionals, a company still needs to protect itself. For example, according to Gartner, “a DBA or other privileged user who knows his own activities are audited and logged could create an account in a fictitious name, use a dormant account, or change a valid account to give it higher levels of access. The new or altered account could then be used to access or change data, and then be deleted so that no one knows the inappropriate activity has taken place.”
Techniques like these are no secret to savvy DBAs, who are well aware of the potential security access holes in today’s RDBMS systems. Businesses need to watch closely, and put the appropriate mechanisms in place, to ensure the proactive prevention of breaches, identity theft, and similar problems.
But, in order to perform the proper monitoring, companies need a solution that seamlessly integrates with the database engine, so it cannot be bypassed in any way. This will ensure that all update activities are always captured, regardless of which user account is being utilized to make the changes.
dbMaestro TeamWork™ is a robust, next-generation Oracle database change management solution that provides a powerful locking facility. Because this locking feature is not affected by the level of security permission of the user making the alterations, it can capture any change, made by any user. Therefore, inappropriate or unauthorized actions are always immediately detected, before they create problems with database performance.
Read our previous posts to learn more about other areas of database administration that need to be closely monitored, including changes to database information, use of unapproved channels, and modification of database schemas.
Tags: Change Management Software, database change control, database change management, Database Change Mangagement, database configuration management, database deployment manager, database deployment tool, database management software, database schema control, database version control, DBA, Gartner, oracle change management, oracle database change management, oracle database version control, oracle db change management, oracle version control, SCM, SDLC, Software Change Management, Software Development Life Cycle, SOX
[...] This post was mentioned on Twitter by Ben Suurmeijer. Ben Suurmeijer said: RT @dbMaestro: What You Need to Monitor: Unauthorized Addition or Modification of User Accounts http://j.mp/hB3gZI via @AddToAny [...]
[...] What You Need to Monitor: Unauthorized Addition or Modification of User Accounts What You Need to Monitor: Retrieval of Data via Unauthorized [...]
[...] information, use of unapproved channels by privileged users, modification of database schemas, addition or alteration of user accounts, and retrieval of data via unauthorized channels. var a2a_config = a2a_config || {}; [...]
[...] information, use of unapproved channels by privileged users, modification of database schemas, addition or alteration of user accounts, retrieval of data via unauthorized channels, access to live production systems, and unapproved [...]