“We asked who owns database security, and what we found is that a lot of companies have multiple people involved,” Oltsik says.
According to ESG, the most common stakeholders listed by survey respondents were security administrators, DBAs, and system administrators. But some organizations could have as many as 10 different individuals or functional groups burdened with responsibility for regulatory compliance when it comes to the sensitive information within their databases.
Approximately nine different corporate roles were listed by at least a quarter of respondents as having a say in database security, including the usual suspects along with auditors, compliance departments, and legal staffers.
Unfortunately, with so many stakeholders responsible for securing valuable database information, Oltsik suspects that too many of them believe someone else is taking care of database security — thus leaving no one at the tiller.
“Instead of investing in hardware or software, I would start with the people first,” says Kornbrust, CEO of Red-Database-Security GmbH, a consultancy that specializes in securing Oracle databases.
This could start by testing out cooperation with the hardening of just a few databases.
http://www.darkreading.com/database_security/security/app-security/showArticle.jhtml?articleID=224201189&cid=RSSfeed