A Faster Path to Application Control with Airlock Digital Trust Builder

Moving application control into enforcement requires policy that allows legitimate business software to run while blocking unapproved applications. Building that policy takes time when teams must investigate software and construct trust rules individually. The enhanced Trust Builder capability in Airlock Digital 7.1 analyzes activity in your environment and recommends rules aligned with your security preferences, with optional automation to apply rules. By reducing repetitive policy-building work, it provides a faster path to enforcement, with unapproved software prevented from running sooner.

Introduction

The sooner teams can enforce application control, the sooner they can prevent unapproved software from running. Getting there requires confidence that the policy supports the applications people need to do their jobs. Administrators must understand what runs in their environment, decide how to trust it, and build rules that reflect their organization’s security requirements. Making those decisions application by application can consume time and delay the move into enforcement.

The enhanced Trust Builder capability in Airlock Digital 7.1 helps shorten that process by turning observed activity into recommended trust rules. It identifies patterns across related files and applies the security preferences administrators define, reducing the need to investigate each file and construct each rule from scratch. Teams can review recommendations before accepting them or automatically apply rules to their policies.

This gives administrators a policy to validate sooner, so they can focus their expertise on testing business workflows, reviewing rule scope, and resolving exceptions. With less manual preparation between deployment and validation, teams can move toward enforcement faster while retaining control over what their organization trusts.

 

A Faster Path to Enforcement

Trust Builder changes how teams approach initial application control policy creation. After establishing the policy structure and deploying agents, administrators configure their requirements and let Trust Builder analyze observed activity over an analysis period they choose. Then review recommendations or inspect rules applied through automation, focusing expertise where judgment is needed. 

In internal testing using real-world execution data spanning approximately 18 months, we found that Trust Builder automatically built policies that achieved approximately 95–96% observed application executions. These results demonstrate its potential to handle much of the initial policy-building work. Coverage varies by environment, available execution data, and configured security preferences. 

Policy coverage is a starting point for validation, and teams may still want to review rule scope, test representative workflows, and resolve exceptions before moving into enforcement. Trust Builder helps them reach those decisions with less manual preparation. 

Build Trust Around Your Security Requirements

Creating application control policies faster should still leave the organization in charge of which applications are allowed to run. Trust Builder analyzes your endpoint execution history, including file properties, how widely software runs, and the processes that launch it. It looks for patterns, such as software from the same publisher, the same folder, or the same parent process, so it can recommend one rule that covers related files instead of treating every file as a separate decision. 

Administrators define the trust methods they accept, including publisher, hash, and path rules; combined conditions; and wildcard preferences. They can also set recommendation requirements, such as how many endpoints software must appear on and how often it must execute. 

For example, trusting a publisher alone may grant broader access than your organization intends. A recommendation combining publisher and path rules can narrow that scope while accommodating legitimate software. 

Your preferences guide the recommendation engine, reducing the need to translate the same security requirements into individual rules repeatedly. 

Choose How Much to Automate

Trust Builder offers two operating modes, configured per policy: 

  • Recommendation mode generates suggestions for administrators to review and accept
  • Automatic mode applies eligible rules to selected policy destinations based on your configured settings

In Airlock Digital, Trust Builder is optional and disabled by default. When using Trust Builder, teams can retain direct review where required and enable automation where appropriate. 

This flexibility supports both deployment and ongoing maintenance. Administrators can spend less time building routine rules from scratch while retaining authority over trust preferences, policy destinations, and exceptions. 

Resolve File Decisions in One Workflow

Individual investigations also become easier with Trust Builder. From a file’s repository entry, administrators can review a recommended trust method, compare alternatives, and inspect related files and observed coverage. They can then select the destination policy groups or existing allowlists and apply the chosen rule directly.

For example, an administrator investigating a VMware Tools component can compare publisher trust with a publisher and path rule and apply the preferred option without recreating it elsewhere in the console.

Connecting investigation to action reduces screen switching and manual steps, helping teams resolve trust decisions more efficiently.

Keep Automation Accountable

Every rule Trust Builder adds is recorded in policy change history, so administrators can see what was added, when and to which policy. Additionally, administrators can inspect applied rules, remove unwanted trust, and keep dismissed recommendations hidden until restored. Rule attribution and descriptive names help teams understand what Trust Builder added.

Reputation checks provide another safeguard. If an application contains a file identified as suspicious or malicious through VirusTotal reputation information, Trust Builder flags the recommendation for manual review rather than automatically approving it. Trust Builder also avoids recommending risky trust, such as shell and common system processes, very broad paths, and temporary or user-writable locations. These safeguards support informed decisions. A lack of adverse reputation does not, by itself, establish that software should be trusted.

Trust Builder generates recommendations through heuristic analysis and does not use AI built into the product. Organizations can optionally connect their own AI provider to help explain the scope and tradeoffs of a recommendation. These AI-generated explanations support administrator reviews, while the recommendation engine generates the underlying recommendation.

Put Preventative Protection to Work Sooner

The enhanced Trust Builder capability makes Deny by Default application control easier to establish and sustain. Security teams can enforce trust boundaries sooner, IT operations spend less time on repetitive policy tasks, and trust decisions stay grounded in your organization's own activity and requirements.

Availability and Next Steps

 Existing customers can download Airlock Digital 7.1 from the Customer Portal starting on November 30th, or contact Airlock Digital Support now to request an upgrade. Support-led upgrades will be scheduled in waves from November 30th, and Support will confirm timing for each environment. If you are evaluating Airlock Digital, contact our team to arrange a demonstration or discuss a new proof of concept today.

Book a meeting with with Airlock Digital to see how the enhanced Trust Builder capability in Airlock Digital 7.1 can help your team move from policy creation to enforcement faster.