Skip to Content
Corellix Software Engineering Solutions
EntitleForge

Every application, only to those entitled to it.

EntitleForge inventories the Windows master image — applications, Start menu shortcuts, executables, signatures — and associates applications with Active Directory groups. From there it creates the shortcuts in Citrix WEM, the AppLocker rules that let only the right groups run them and, with session Tiers, what each kind of device may open. Every plan is approved before it is applied, and every change is in an audit log that cannot be altered.

  • Citrix WEM service · AppLocker
  • Windows service with a web portal
  • Session Tiers with deviceTRUST
Blocked even from the command line AppLocker allows each application only to its groups: the missing shortcut is not the protection.
No manual steps in the normal flow Actions, AppLocker rules, settings and assignments are written through the WEM APIs.
Verified on a real VDA A canary checks the effective policy before the shortcuts are assigned.
Every change on record Approval by a second person, journal, rollback and an audit log chained by hash.
In action

Try EntitleForge right here

A web portal for the whole team, built on the model of the Citrix Cloud console. Below, on sample data, a plan is being applied: follow its steps and the verification on the canary VDA, then try the session simulator on the Tier matrix of the «uffici» policy and add an application to a group in «Start menu by group».

The interface is the product's own, in its original language; the data are sample data and the simulation is not connected to any system.

The problem

Hiding a shortcut does not stop anyone

In a shared master image every user finds every installed program. Removing a shortcut from the Start menu does not prevent anyone from starting the executable from Explorer, the command prompt or PowerShell.

Keeping WEM actions, assignments and AppLocker rules aligned by hand, image after image, is slow and error-prone: one missed rule blocks a department, one rule too many opens a program to everyone.

The answer

One policy, two guarantees

You write once who may use which application. EntitleForge turns it into WEM shortcuts for the right groups and AppLocker rules that allow execution only to them: whoever is not entitled is blocked even when starting the executable directly.

Every change goes through a plan with the differences, the approval of a second person, a backup of the configuration set, a verification on a canary VDA and a journal for the rollback.

Features

What EntitleForge does

Inventory of the master image

A read-only collector, with a graphical interface or from the command line, records applications, Start menu shortcuts, executables with their signatures and hashes, and the posture of the image. The service imports the bundle after checking its integrity and schema.

Entitlements by Active Directory group

A visual editor or YAML: which groups run which applications, how the Start menu is organized, which shortcut flags apply. The Start menu can be previewed for a group or for a user, with their nested groups read from Active Directory.

AppLocker rules generated, not written by hand

Publisher, hash and path rules built deterministically from the inventory, a baseline that is always present, and the analysis of launchers such as cmd.exe and PowerShell that could be used to get around them.

Session Tiers with deviceTRUST

Corporate, managed or personal device: a matrix shows which applications and desktop features each Tier allows, a simulator tells which Tier a session gets, and the deviceTRUST policy is deployed through WEM.

Plans, approvals and canary

Every change is a plan with its differences and steps; a second person approves it; the apply backs up the configuration set, checks the result on a canary VDA and only then assigns the shortcuts.

Audit, drift and rollback

An append-only audit log chained by hash, verification and drift scan against WEM, rollback object by object from the journal, and a break-glass procedure for emergencies.

How it works

One run, step by step

  1. 1

    Scan the master image

    The collector runs on the image in read-only mode and produces a bundle.

  2. 2

    Import and review

    The service validates the bundle; you confirm the associations the engine does not decide on its own.

  3. 3

    Write the policy

    Applications, AD groups, Start menu and, if you want them, session Tiers.

  4. 4

    Plan and approve

    The plan lists every change to WEM; someone other than its author approves it.

  5. 5

    Apply and verify

    Backup, writes to WEM, verification on the canary, assignment of the shortcuts, final verification.

Requirements

What it takes

WEM
Citrix Workspace Environment Management service (Citrix Cloud), with an API client allowed on the configuration set
Where it runs
Windows Server, as a Windows service with its installer; database included (SQLite)
Master image
Windows; the collector is a single executable, needs no installation and changes nothing
Access
Local accounts, Active Directory or Microsoft Entra ID; Viewer, Planner, Approver and Operator roles
Session Tiers
Optional, with deviceTRUST on the VDAs
Network
HTTPS to the Citrix Cloud APIs; HTTPS portal for the administrators
FAQ

What people ask us

Isn't it enough to hide the shortcut?

No: whoever knows the path can start the executable from Explorer, CMD or PowerShell. EntitleForge creates AppLocker rules so that only the entitled groups can run it; the shortcut is only presentation.

Which WEM interfaces does it use?

Configuration sets, actions and assignment targets go through the public WEM API; AppLocker rules, Application Security settings and shortcut assignments through the API of the WEM console. If that is not available, a break-glass procedure produces the files and runbooks to apply by hand, and records it in the audit log.

What if a rule blocks a department by mistake?

Rules start in Audit mode and move to Enforce later. Every apply is checked on a canary VDA before the shortcuts are assigned, and every run can be rolled back from the journal, object by object.

Do I need deviceTRUST?

Only for session Tiers. Without them, every entitled application is available in every session.

Is EntitleForge an official Citrix product?

No. EntitleForge is developed by Corellix Software Engineering. Citrix, Citrix Workspace Environment Management and deviceTRUST are trademarks of Cloud Software Group, Inc. or its subsidiaries; Windows and AppLocker are trademarks of Microsoft Corporation.

Coming next

What is planned next. If you need one of these sooner, say so in your request.

  • Collector bundles signed with your certificate
Let's talk

See it on your master image

Tell us how many images, applications and groups you manage: we will show you EntitleForge on sample data and plan a pilot on your WEM configuration set with you.

Rather write to us? Contact page

What you need

We use these details only to reply to you. No marketing lists. Privacy

EntitleForge is designed, built and supported by Corellix Software Engineering: the team behind the Corellix platform, which also builds custom software, infrastructure tools and data migrations.

About us All solutions