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.

Data Breach Excuses and What They Really Mean: Excuse 4

Posted December 30, 2010    Peter McCalister

Excuse 4: DON’T MAKE AN EXCUSE, BLAME IT ON A THIRD PARTY.  Yep, that’s what we hear next when data shows up stolen or vandalized.  So this fourth installment of the Top 5 Excuses for Data Breaches and What They Really Mean will attempt to translate this into what really happened and use current news to exemplify our point.

McDonald’s adopted the ‘we’ve been hurt too and are in this together’ tone when they warned customers to be on guard against identity theft, phishing and other scams thanks to a data breach following the theft of customer data held by a third-party contracted by McDonald’s.

As PC World rightly points out, the smaller third-party organizations frequently lack the security policies and controls of the larger companies, and provide an Achilles heel that hackers can exploit to gain access to the more valuable network–often flying undetected under the radar.

Our view is similar.  With so many potential points of entry to sensitive data and so many different attack surfaces from which infection can happen, a shift in perspective is required. Companies need to think less about building walls and more about establishing clear boundaries.

An employee at their desk or on the move, subcontractor or partner: access to the network should be the same.  When we talk about privileged access, it’s not who is more privileged than who in terms of their relationship to the company, it simply refers to who gets access to what as defined by their role definition.

As the straight lines of traditional security practice get increasingly blurred and permeable, privilege access becomes the cornerstone of not just good network security, but also good people management.

Using open source software to solve this problem can be just as bad.  Check out this white paper for more information

Leave a Reply

Additional articles

PowerBroker for Unix & Linux helps prevent Shellshock

Posted September 25, 2014    Paul Harper

Like many other people who tinker with UNIX and Linux on a regular basis, BASH has always been my shell of choice.  Dating back to the early days moving from Windows to a non-Windows platform, mapping the keys correctly to allow easy navigation and control helped ensure an explosion of use for the shell. Unfortunately,…

Bash “Shellshock” Vulnerability – Retina Updates

Posted September 24, 2014    BeyondTrust Research Team

A major vulnerability was recently discovered within bash which allows arbitrary command execution via specially crafted environment variables. This is possible due to the fact that bash supports the assignment of shell functions to shell variables. When bash parses environment shell functions, it continues parsing even after the closing brace of the function definition. If…

pbps-blog3

7 Reasons Customers Switch to Password Safe for Privileged Password Management

Posted September 24, 2014    Chris Burd

It’s clear that privileged password management tools are essential for keeping mission-critical data, servers and assets safe and secure. However, as I discussed in my previous post, there are several pitfalls to look out for when deploying a privileged password management solution. At this point, you may be wondering how BeyondTrust stacks up. With that,…

Tags:
, , , , ,