BeyondTrust

Security in Context: The BeyondTrust Blog

Welcome to Security in Context

Bringing you news and commentary on solutions and strategies for protecting critical IT infrastructure in the context of your business.

Database Security Risks Run Amok Without Oversight

Posted February 1, 2012    Peter McCalister

As you can imagine, databases are in a class of data storage, organization, and management unto themselves. As such, the inherent security vulnerabilities in which a least privilege solution can help mitigate are also relatively unique. I’ve uncovered six that should be explored:

Misconfigurations: Database schemas can be very temperamental and any misconfiguration error can cascade into a huge problem or be so subtle that it may be difficult to uncover the impact. A frequent challenge here is the ambitious developer who somehow gets access to the production system instead of just their development sandbox.

Updates: Out-of-cycle patching can cause major disruption in operation and potentially lead to lost revenue if done on the primary transaction database. Here is where the ambitious tech support technician or developer believes that blindly trusting that your database vendor’s testing capabilities keep current with their latest patch is a good thing.

Application Attacks: Sometimes the easiest way to attack your database is to attack the outward-facing applications that are connected to that database, especially if those application are web-based. This can also come in the form of database access through non-approved channels such as open source tools capable of bypassing normal admin dashboards.

Transaction Monitoring: Sometimes it’s the smallest of things that can trip you up when looking to satisfy compliance or track down data theft or damage, so monitoring every transaction can be very important. However, it can also drown your data stores in amounts of information too voluminous to even interrogate.

Data Awareness: What is perceived, or in actuality is, confidential data can be subjective in some organizations and very clearly identified in others. Being aware of what class of data is stored where will be another critical success factor.

Privileged Users: My favorite, of course, is the privileged user. As discussed previously, the DBA’s omnipotent access to your database must be managed through a least privilege solution in order to ensure your governance and compliance policies are met as well as protect against the misuse of that privilege—intentionally, accidentally, or indirectly.

Tags:

Leave a Reply

Additional articles

Are Your Data Security Efforts Focused in the Right Area?

Posted January 28, 2015    Scott Lang

Vormetric Data Security recently released an insider threat report, with research conducted by HarrisPoll and analyzed by Ovum. Based on the survey responses, it is apparent that there is still a great deal of insecurity over data. However, the results also show that there may be misplaced investments to address those insecurities. I will explain…

Tags:
ghost

GHOST Vulnerability…Scary Indeed

Posted January 28, 2015    BeyondTrust Research Team

A vulnerability discovered by Qualys security researchers has surfaced within the GNU C Library that affects virtually all Linux operating systems. The vulnerability lies within the various gethostbyname*() functions and, as such, has been dubbed “GHOST.” GHOST is particularly nasty considering remote, arbitrary code execution can be achieved. In an effort to avoid taxing DNS lookups, glibc developers introduced…

Tags:
,
dave-shackleford-headshot

Your New Years Resolution: Controlling Privileged Users

Posted January 27, 2015    Dave Shackleford

Is 2015 the year you get a better handle on security? The news last year was grim – so much so, in fact, that many in the information security community despaired a bit. Really, the end-of-the-year infosec cocktail parties were a bit glum. OK, let’s be honest, infosec cocktail parties are usually not that wild…

Tags:
, , ,