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.

Top 10 Reasons To Implement Least Privilege For Apps & Databases

Posted February 22, 2012    Peter McCalister

Taking a more tongue-in-cheek approach to highlighting the types of privilege misuse that occurs daily in applications and databases inside most organizations, I thought that a top-ten list approach might appeal to you as well. How may of these have you seen throughout your organization?

#10—Sam, the CSO, can now sleep nights knowing that inappropriate database activities are not only being monitored but also prevented via policy enforcement at a granular level.

#9—Fiona, the DBA, won’t be able to modify the production database instead of the test copy in the sandbox accidentally or even accidentally on purpose.

#8—Frank, your sole Application Developer, will no longer have to rewrite legacy applications in order to strip out any code requiring administrative privileges.

#7—Ted, the overzealous Tech Support Tech, won’t be able to upgrade your production database to the latest version of Oracle released today before the IT department has had time to vet the im- pact on current processes and attached applications.

#6—Ken, the CSO, can delegate database access based on access control policies that leverage external context such as SOX, PCI-DSS, and FFIEC compliance.

#5—Carl, the Compliance Executive, can now quickly identify all privileged users, review entitlements, and if necessary, de-provision obsolete users in order to pass your next enterprise IT audit.

#4—Francine, the COO, can now easily ensure adherence to change control processes across the extended enterprise for all databases and even reconcile with the change ticketing system.

#3—Larry, the new DBA, won’t have to call his predecessor, who is now serving eight years in the penitentiary for identity theft and attempted sale of your entire customer credit card transaction database, to learn the new processes for database activity monitoring (DAM).

#2—Beth in Human Resources won’t be able to forward the entire company payroll ledger to WikiLeaks because the CEO didn’t tell her how great she looked today.

#1—The IT department can still have the 35th annual birthday party next week for that payroll application that requires desktop admin rights, but no one knows where the source code is to make it more contemporary instead of replacing it outright.

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:
, , ,