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.

Born To Run…and Can Your Cloud Escape Injury?

Posted November 16, 2011    Peter McCalister

There’s a lot of hype in the running community over the 2009 book by Christopher McDougal, “Born To Run.” It has inspired a host of people–experienced runners and average Joes–to switch to barefoot running, where people where either nothing on their feet at all or some sort of minimalist shoe. The most headturning of these minimalist shoes have to be the Vibram Five Fingers shoes. You’ve seen them–they look like gloves for feet.

I’m certainly no expert on running or barefoot running, but the jury still seems to be out on whether or not barefoot running is the right way to go. I recently heard from a podiatrist friend that he was seeing a significant increase in patients who had running injuries from the barefoot style. This has also been noted on sites like Competitor. The injuries seem to stem primarily from those runners who make a dramatic switch to barefoot running rather than making a gradual change.

So what does barefoot running have to do with desktop and server security technologies? Let me draw a parallel to cloud computing and new cloud initiatives. Frequently enterprise IT organizations embark on new cloud initiatives and often sink a lot of money into exploring the options available. Sometimes the rollout is underway before the planning phase has even gotten approval from the CIO.

With virtualization and the cloud getting all the hype these days, it’s certainly enticing to want to jump right in and start virtualizing everything. We know the benefits: pay for only what you use, greater reliability, replication of data, disaster recovery, etc. However, in many cases, the new cloud initiatives fail to examine the most important aspect of any virtual deployment–security.

Much like the barefoot runners who go all barefoot without a gradual entry and careful planning of their “migration” to the barefoot style, IT departments can essentially be “injured” by security breaches if they fail to properly secure their cloud environments.

Security in the private cloud starts at the hypervisor level. At BeyondTrust we’re primarily concerned with keeping insider threats–the threats posed by employees and internal trusted users. And, the best way to ensure that data in the private cloud stays secure and insider threats are kept at bay is to make sure that users are logging on to the hypervisors with their directory credentials.

From there, IT administrators can make sure that users are logging on to virtual machines–both desktops and servers–using their directory credentials provisioned in Active Directory. PowerBroker Identity Services features tools for securing desktops and servers–whether physical or virtual–and hypervisors. So don’t get caught up in the hype and end up with a cloud “injury.” Proper planning of your security and identity management is essential.

Leave a Reply

Additional articles


Closing the Vulnerability Gap

Posted October 7, 2015    Brian Chappell

Managing vulnerabilities is a significant challenge for many organizations. The main difficulties with managing this manifest in two key areas. The first is that the list isn’t static. The second is priority.


Scottrade Breach: Identified by Federal Officials

Posted October 5, 2015    Morey Haber

Late afternoon on October 2nd, news leaked out of another large security breach, now at Scottrade. The identity count of records, in the millions again (4.6 million is the latest). This breach comes on the second day of national CyberSecurity month, the first being Experian/T-Mobile breach.

3d image Data Breach issues concept word cloud background

Experian/T-Mobile Data Breach: When 2 Days is not Enough

Posted October 2, 2015    Morey Haber

On October 1, Experian admitted full responsibility for the loss of T-Mobile customer data. 15 million user records dating back to 2013 were effected in the breach, with data including sensitive information that may be decryptable like social security numbers and drivers licenses.