Heimdal Application Control

Controls application execution through rules, approval flows and execution records.

For organisation and multi-tenant environments that need policy-based control over application execution.

Control which applications are allowed to run

Unapproved software and unauthorised processes can create a difficult balance: IT teams need to restrict execution without losing sight of what has been allowed, blocked or observed. Exceptions also need to be handled in a way that reflects individual users or group requirements.

Heimdal Application Control applies AppFencing rules to allow or block applications by path, MD5 hash or certificate validation. It restricts unauthorised interactions, supports approval and denial flows, and records execution activity for later review.

Where Heimdal Application Control is used

Application Control is suited to defining which software is permitted to execute under zero-trust policies and to blocking software that does not meet those rules. It also supports approval decisions for individual users and Active Directory groups, and provides execution records for reviewing allowed, blocked and passive-mode activity.

Centralised application and network policies can be applied across organisation or multi-tenant environments.

Fits within these solutions

Application Control
Endpoint Protection

Suitable environments

Heimdal Application Control is applicable to organisation and multi-tenant environments through the Heimdal agent and unified platform. Its approval flows can be applied to individual users or Active Directory groups.

Benefits

Restrict Unapproved Software

Limits application execution to software that meets defined rules.

Retain Execution History

Keeps records of allowed, blocked and monitored executions for review.

Handle User Exceptions

Supports approval and denial decisions for users or Active Directory groups.

Apply Consistent Policies

Centralises application and network policy application across the estate.

Capabilities

Application Allow and Block Rules

Allows or blocks applications using file paths, MD5 hashes or certificate validation.

Zero-Trust Execution Policies

Enforces granular policies governing which applications are permitted to execute.

Interaction Restrictions

Restricts unauthorised application interactions and processes.

Approval and Denial Flows

Provides default and custom approval or denial flows for users and Active Directory groups.

Execution Activity Records

Records allowed, blocked and passive-mode monitored application executions.

Centralised Policy Application

Applies application and network policies across organisation and multi-tenant environments.

Common Use Cases

Approved Software Execution

Define rules for software that is allowed to run in the environment.

Untrusted Application Blocking

Block applications that do not meet path, hash or certificate rules.

Group-Based Approval

Apply custom approval and denial flows for Active Directory groups.

Execution Log Review

Review detailed reports and 90-day logs of application execution activity.

How we help

Armstrong discusses application execution requirements with customer IT teams, including the rules, approval needs and estate context that matter to them. These discussions help Armstrong recommend whether Heimdal Application Control is a suitable fit for controlling approved and unapproved software execution.

Part of (depending on licence)

Resources

How would you like to proceed?