Here is the number one reason database security projects fail. It's not likely going to be what you'd think it is, since most security failures are traced to human oversights or backdoors created to simplify usage. In reality, the number one reason database security projects fail is because the DBA was never included in the security project's planning to start with.
It seems counter-intuitive to leave your database expert and administrator out of the loop when creating security protocols, but it happens often. Many organizations view security as something separate from database maintenance and expansion, instead thinking that the DB expert really only needs to be involved in security while the database is being built.
That's not so. It's especially true if your DBA is being outsourced or utilizing shared IT resources.
Sometimes, security or database professionals view one another as 'troublemakers' or 'hurdles' rather than as teammates. This is often because of the way that IT 'geeks' (especially database engineers) and security 'muscle' see one another. At its most fundamental, however, the most important task of a DBA outside of keeping the database running is to keep it safe from harm - meaning keeping it secure. For security, their primary goal is the safety of their organization and its assets - including data.
So the two should be seeing eye-to-eye. Seen from this perspective, it would seem surprising if they don't see themselves as coequal teammates.
Both sides of this supposed conflict need to adjust their viewpoint. DBAs often over-focus on performance and tuning of their database and under-focus on security. Security often over-focuses on 'lockdown' measures, having little DB knowledge, and has no concept of performance or usage needs. To see things on a level field, both sides have to adjust.
So security pros need to understand that securing the data is one thing, but making it inaccessible and unusable defeats the purpose of having the data in the first place. For their part, DBAs need to understand that some performance losses are going to be required in order to keep the data they're entrusted with from becoming compromised.
A middle ground must be found.
This isn't hard to do, but it does require time and commitment. Both sides must learn something of the other's jobs. Security should learn what it is that the DBA is doing and the DBA should learn what security does. By getting a good overview and understanding of the general practices of either side, both sides will benefit and the organization as a whole will find itself much better off.
With outsourced DB administration and optimization, this is especially important. Security is usually an in-house affair, but can be outsourced just as DBA is. In some cases, the same firm handles both issues - this is preferable as an integrated security/DB, when done right, means a better and more secure system.
Author Resource:-
[About] The DBA Shoppe specializes in remote DBA services for clients with Oracle, DB2 and SQL Server databases. Providing certified Database Administrators for your day to day requirements, the DBA Shoppe saves you time and money. How healthy are your databases? Discover today at http://www.TheDBAShoppe.com
![[Valid RSS feed]](http://www.greatarticlesite.com/images/icon_Rss.png "XML Feed For RSS"){kind=icon}
Category Rss Feed
Print This Article
Add To Favorites
