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.

A New Twist on Secure Computing

Posted May 28, 2014    Morey Haber

Secure Computing is one of those overused terms that gracefully died on the vine. During a recent customer meeting, we discussed a new context for Secure Computing that’s worth sharing with our blog readers. Here it is in a nutshell:

Consider Secure computing in the context of PowerBroker for Windows Risk Compliance. If you’re not familiar with the patent-pending technology, it essentially evaluates an application at runtime to decide what privileges the application should have based on a vulnerabilities, age, risk, and even regulatory relevance. This could include blocking a vulnerable application if it represents too much of a risk to the business. While this extreme action could disrupt operations, in some cases it may be exactly what is needed to prevent an application’s exploitation.

Effective Secure Computing falls between the extremes of providing root access and denying access altogether. To our customer, it means alerting the end user and the help desk that a launched application is in violation of an acceptable patch remediation cycle – and instructing the end user to contact the help desk to get the system mitigated. This places Secure Computing in the hands of all stakeholders by alerting them to risk and facilitating procedures to assist in remediation.

For example, launching a vulnerable version of Adobe Acrobat that is older than 90 days could display a message like this:

PBW-Authorization

It does not stop the execution, but alerts them much like an antivirus solution and, more importantly, helps track when processes fail for patch management. All the user needs to do is click “OK” to continue.

This approach enables Secure Computing by proactively alerting the end user, the help desk, and the operations team to applications being executed out of compliance. In addition, it allows for application-based vulnerability assessment and can meet continuous vulnerability assessment requirements as users execute applications.

Two additional practices that organizations are striving for (with little success) are using passive scanning technology and deploying complex multi-vendor integrations. These allow for application-based vulnerabilities to be detected as they are communicating across the network. However, they don’t assist with local applications or applications that transmit encrypted communications. PowerBroker for Windows makes this simple. For instance, here’s a PowerBroker rule for PCI compliance concerning critical vulnerabilities over 90 days old (without the need for span ports):

RCS-Cricklewood

Secure Computing does not have to be the responsibility of the security or operations teams alone. PowerBroker for Windows takes a proactive approach and empowers the end user to notify teams when their applications are not meeting standards.

> Blog: Greylisting Applications with PowerBroker for Windows Risk Compliance
> Blog: Introducing Vulnerability-Based Application Management
> Learn more about PowerBroker for Windows

Tags:
, , , , , , ,

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