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.

Introducing Vulnerability-Based Application Management™ (VBAM)

Posted March 3, 2014    Morey Haber

RSA Conference 2014 saw the birth of a new acronym at the BeyondTrust booth: “VBAM” – otherwise known as Vulnerability-Based Application Management™. This patent-pending technology enforces least-privilege access based on an application’s known vulnerabilities, as well as their age, potential risk, and impact on regulatory compliance initiatives – and is currently included in the PowerBroker for Windows Risk Compliance module.

VBAM evolves privileged account and vulnerability management by assessing vulnerabilities at the time of application execution and granting permissions based on policy violations and/or potential risks to the system and user. With PowerBroker for Windows, it’s easy to create Risk Compliance rules that control application permissions.

vbam-032014
A simple UI allows PowerBroker for Windows users to define regulatory compliance, risk and age in relative terms.

How is PowerBroker for Windows so vulnerability savvy? Simple: BeyondTrust Retina. Without any additional licensing, PowerBroker uses a subset of the Retina Network Security Scanner’s vulnerability database to evaluate applications as they are launched and take runtime actions based the rules and policies that you create. These actions can be passive, allow privilege escalation to administrator, remove administrative permissions, or even prevent the application from launching – all in real-time based on the application’s published vulnerabilities.

Since vulnerabilities and risk evolve everyday, the BeyondInsight IT Risk Management Platform seamlessly allows PowerBroker agents to process the latest application-based vulnerabilities list as a part of its normal reporting communications. Rules can be vendor or compliance specific, or generic enough to catch all relevant vulnerabilities upon launch. The result is real-time application vulnerability assessment and application management.

Vulnerability-Based Application Management is a natural extension of other technologies we already know in the space: Network Access Control (NAC), Access Control List (ACL), and plain whitelist or blacklist Application Control (AC). Applications can be measured for risk and permissions decided based on that risk.

Whitelisting and blacklisting methodologies based on hash databases do not consider the application vulnerabilities, and traditional privilege identity solutions fail to consider application risk as a part of the least-privilege model. With PowerBroker for Windows and Vulnerability-Based Application Management, BeyondTrust is changing the way Application Control should be implemented.

Learn more about PowerBroker for Windows.

Tags:
, , ,

Leave a Reply

Additional articles

6

A Quick Look at MS14-068

Posted November 20, 2014    BeyondTrust Research Team

Microsoft recently released an out of band patch for Kerberos.  Taking a look at the Microsoft security bulletin, it seems like there is some kind of issue with Kerberos signatures related to tickets. Further information is available in the Microsoft SRD Blogpost So it looks like there is an issue with PAC signatures.  But what…

Tags:
, , , ,
Password Game Show

Managing Shared Accounts for Privileged Users: 5 Best Practices for Achieving Control and Accountability

Posted November 20, 2014    Scott Lang

How do organizations ensure accountability of shared privileged accounts to meet compliance and security requirements without impacting administrator productivity? Consider these five best practices…

Tags:
, , , , , ,
Triggering MS14-066

Triggering MS14-066

Posted November 17, 2014    BeyondTrust Research Team

Microsoft addressed CVE-2014-6321 this Patch Tuesday, which has been hyped as the next Heartbleed.  This vulnerability (actually at least 2 vulnerabilities) promises remote code execution in applications that use the SChannel Security Service Provider, such as Microsoft Internet Information Services (IIS). The details have been scarce.  Lets fix that. Looking at the bindiff of schannel.dll, we see a…

Tags:
, , , , ,