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 Breaches…And How Insiders Affect Them

Posted October 31, 2011    Peter McCalister

With all the data breaches in the news these days, security is definitely a hot topic in the information technology community. Preventing risks and threats is the core of keeping information, and ultimately people, safe.

A lot of discussion goes on about the best way to do this- which is often quite unnecessary, in my opinion. Instead of debating whether it’s criminal outsiders of disgruntled/malicious/accident prone insiders, let’s take a look at how your assets get hacked/breached/leaked/etc. in the first place. It starts with insiders. Your employees and your 3d party contractors are given access to information within a database, which creates a gateway for critical information to get out. Whether those insiders abuse that information or not, they are still acting as the access point for data to escape. Sometimes data is leaked and/or stolen when outsiders hijack credentials and hack into your network. Other times it’s the actual employee who is responsible. Either way- the more people who have unmanaged access to data, the wider you are opening your door for a breach.

When we look at this situation, which plagues most organizations in many different industries, it seems daunting and nearly impossible to control. Fortunately, there is a fix- and a seemingly simple one at that. The key is to create as few access points as possible across all platforms in your organization, and then granularly monitor and manage the access points that are necessary. For example, desktop users should run as standard users, and those with access to servers should not be given the root password. In database environments, all DBA activity should be closely monitored, and hypervisor privileges in virtual enterprises must be granularly managed. It is through this process, which has been identified multiple times on this blog, that least privilege is truly implemented.

Leave a Reply

Additional articles

How To Implement The Australian Signals Directorate’s Top 4 Strategies

Posted October 20, 2014    Morey Haber

The Australian Signals Directorate (ASD), also known as the Defence Signals Directorate, has developed a list of strategies to mitigate targeted cyber intrusions. The recommended strategies were developed through ASD’s extensive experience in operational cyber security, including responding to serious security intrusions and performing vulnerability assessments and penetration testing for Australian government agencies. These recommendations…

Tags:
, , , ,
asp-mvc

Exploiting MS14-059 because sometimes XSS is fun, sometimes…

Posted October 17, 2014    BeyondTrust Research Team

This October, Microsoft has provided a security update for System.Web.Mvc.dll which addresses a ‘Security Feature Bypass’. The vulnerability itself is in ASP.NET MVC technology and given its wide adoption we thought we would take a closer look. Referring to the bulletin we can glean a few useful pieces of information: “A cross-site scripting (XSS) vulnerability exists…

Tags:
4bestpracticesaudits-blog

Four Best Practices for Passing Privileged Account Audits

Posted October 16, 2014    Chris Burd

Like most IT organizations, your team may periodically face the “dreaded” task of being audited. Your process for delegating privileged access to desktops, servers, and infrastructure devices is a massive target for the auditor’s microscope. An audit’s findings can have significant implications on technology and business strategy, so it’s critical to make sure you’re prepared…

Tags:
, , , ,