Oracle database admins acknowledge security gaps

Two-thirds say monitoring capabilities are lacking

Database security is rife with pitfalls, according to 430 Oracle database administrators surveyed by the Independent Oracle Users Group.

Database security is rife with pitfalls, according to 430 Oracle database administrators surveyed by the Independent Oracle Users Group.

According to the results of the survey released last month, fewer than 30% encrypt personally identifiable information in all their databases, while about 75% acknowledge their organizations do not have a means to prevent privileged database users from reading or tampering with human resources, financial or other business application data in their databases.

Oracle, Microsoft ready major security updates"There are still a lot of holes," says Andrew Flower, president of the IOUG president and vice president LoganBritton. "One of the biggest risks is stealing data internally," he acknowledges, saying the survey shows organizations aren't applying sufficient resources to improve security, and that there's been little change in the results from last year's survey.

About two-thirds of the survey respondents admitted there was no way in their organizations to detect or prove that the database administrators were not abusing their privileges.

In addition, close to half of the respondents said a user with "common desktop tools" either could gain unauthorized direct access to sensitive information stored in databases or they weren't sure about it. Another 64% said they don't monitor database activity -- and less than one-third of those monitoring are watching for sensitive reads and writes.

The IOUG respondents responding in the survey hail from the telecom sector, education, government, financial services, healthcare, manufacturing and the retail industry. A fair number work in organizations with large numbers of databases, with 35% claiming their organizations have 11 to 100 databases, and 13% having more than 1,000 databases.

About 6 in 10 said they don't offshore the database application administrative function, 5% didn't know but the remainder responded they did offshore to some extent.

Patch management is problematic for Oracle database administrators, with 37% saying they generally patch within one to three months, though most patch after three months.

In the survey, 6% said they were aware of an enterprise data breach, compromise or tampering over the past year, 16% said they didn't know and 79% said they weren't aware of it.

Learn more about this topic

Oracle, Microsoft ready major security updates 

Oracle to buy SSO vendor Passlogix

Most Oracle shops don't mandate security patches 
Editors' Picks
Join the discussion
Be the first to comment on this article. Our Commenting Policies