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

Sudo_logo

Don’t Create a Different sudoers File for Each System

Posted May 20, 2015    Randy Franklin Smith

What if you have multiple Linux and/or Unix systems? Sudo management can become onerous and unwieldy if you try to manage a different sudoers file on each system. The good news is that sudo supports multiple systems.

password-safety

What Does Microsoft Local Administrator Password Solution Really Do?

Posted May 19, 2015    Morey Haber

LAPS is a feature that allows the randomization of local administrator accounts across the domain. Although it would seem that this capability overlaps with features in BeyondTrust’s PowerBroker Password Safe (PBPS), the reality is it is more suited for simple use cases such as changing the local Windows admin account and not much more.

Tags:
, ,
webinar_ondemand

On Demand Webinar: Securing Windows Server with Security Compliance Manager

Posted May 14, 2015    BeyondTrust Software

On Demand Webinar: Security Expert Russell Smith, explains how to use Microsoft’s free Security Compliance Manager (SCM) tool to create and deploy your own security baselines, including user and computer authentication settings.

Tags:
, ,