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.

Greylisting Applications with PowerBroker for Windows Risk Compliance

Posted February 10, 2014    Morey Haber

PowerBroker for Windows is designed to elevate privileges on an application based on rules. It does so using technology that does not alter the user but rather the security token for the application at runtime. The results allow a standard user to launch and interact with an application that requires administrative privileges, without changing the user’s permissions. PBW policies and rules are created for any specific application, publisher, path, or a variety of other traits including their arguments and wildcards. Traditionally, these rules are black and white and do not consider the risk of the application itself. This concept is commonly known as greylisting and something no privileged identity vendor has been able to successfully integrate – until now.

PowerBroker for Windows 6.5 introduces a brand new paradigm for greylisting based on regulatory compliance and the associated vulnerabilities with an application. This new concept is patent-pending and called “Risk Compliance.” Traditional rules only pattern match an application for privileged elevation or application denial. Risk Compliance allows rules to be created based on violations to regulatory compliance initiatives and vulnerabilities publicly identified for that application. BeyondTrust has mapped, in real time, application-based vulnerabilities from the Retina vulnerability scanner to dynamically create PowerBroker Rules.

PBW-Risk Report

For instance, an administrator can create an application rule based vulnerabilities associated with HIPAA compliance that are over 30 days old and choose to send an alert, denial the application from launching, or restrict permissions of the application when it launches. Security best practices, and many regulations, dictate that critical vulnerabilities should be patched within 30 days (PCI DSS v3 for example). This type of rule would stop an at-risk system from launching the applications with excessive privileges until proper remediation is performed. In addition, extensive reports are available based on these rules to document which systems have application vulnerabilities that violate governance initiatives and what users and applications should not be utilized with administrative (or denied completely) until remediation is conducted.

PBW-Backup Report

PowerBroker for Windows Risk Compliance is a game changer. It provides real-time, application-based vulnerability assessment, privileged identity management, file integrity monitoring, session monitoring, and Windows event log monitoring all in one security agent. When the technology is used with the BeyondInsight IT Risk Management Platform, clients will benefit from the BeyondTrust vision of “Context Aware Security Intelligence” for user and asset risks.

For more information, check out our white paper “Powerbroker for Windows: Risk Compliance.”

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