Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Application Allowlisting?

Application allowlisting permits only approved executables, scripts, and libraries to run on a device, blocking everything else by default rather than trying to identify malicious files first.

Illustration for the cybersecurity term Application Allowlisting
Home / Blog / Cybersecurity Terms / What Is Application Allowlisting?
17 November 2026

What Is Application Allowlisting?

What Is Application Allowlisting?

Application allowlisting inverts the question that most endpoint protection asks. Rather than deciding whether a file looks malicious, the operating system checks whether the code has been approved and refuses everything else. Signature and reputation engines will always trail behind new payloads; an allowlist does not care that a binary has never been seen before, only that nobody authorised it.

How the Control Decides

Every implementation builds rules on one of three identities, and the choice determines how much protection you get.

On Windows, the modern engine is Windows Defender Application Control, enforced by the kernel code integrity subsystem and optionally protected by virtualisation-based security so that an administrator cannot simply switch it off. AppLocker remains widely deployed and is easier to pilot, but it is a user-mode control with weaker guarantees. Linux environments use fapolicyd for policy-driven execution control, SELinux to constrain what an executed process can then do, dm-verity or IPE where the root filesystem can be made immutable, and signed package repositories as the first gate.

Why Deployments Fail

Most unsuccessful rollouts fail for the same handful of reasons. Path rules are written over directories that ordinary users can write to, such as a shared drive mapped for a line-of-business application. DLL and script enforcement is left disabled because it is noisy, so an attacker loads a library rather than launching an executable. Developer and IT workstations are excluded wholesale, which is precisely where the most valuable credentials live.

The deeper problem is signed Microsoft tooling. Living off the land techniques run attacker code through binaries that any allowlist will trust: mshta.exe, InstallUtil.exe, msbuild.exe, regsvr32.exe, and the rest of the LOLBAS catalogue. Microsoft publishes a recommended block list for exactly these binaries, and applying it is not optional if the policy is meant to hold. Constrained Language Mode for PowerShell closes a related gap.

Getting It Into Production

Run in audit mode first. Both WDAC and AppLocker log what would have been blocked without blocking it, and six to eight weeks of that telemetry across a representative sample of devices tells you more than any software inventory. Build the policy from what actually executed, not from what the asset register claims is installed.

Deploy in rings, starting with kiosks, servers with a fixed role, and call centre desktops where the software set barely changes. Those estates can reach full enforcement quickly. General knowledge-worker devices come next, and engineering workstations last, usually with a managed installer arrangement so that software distributed by your deployment tool is trusted automatically.

The part that gets forgotten is operations. An allowlist is a living policy that needs an owner, a change route with a service level that people will actually use, and an exception register that is reviewed rather than accumulated. Tie it to patch management, because a publisher rule that pins a maximum version will block an update the moment it ships.

The UK Compliance Angle

Cyber Essentials accepts application allow listing as a route to the malware protection control, as an alternative to conventional anti-malware software, provided the list is approved by the organisation and maintained. The NCSC device security guidance recommends it for platforms that support it, and ISO 27001 Annex A control 8.19, covering installation of software on operational systems, is satisfied far more convincingly by an enforced allowlist than by a written policy.

For regulated estates it is also one of the few controls that demonstrably stops ransomware at the execution stage rather than after encryption begins, which is why it appears in almost every post-incident hardening plan we write. Our Infrastructure and Architecture Review Services test allowlist policies against the bypass techniques attackers use rather than against the rule set on paper.

FAQ – Frequently Asked Questions

What Is the Difference Between AppLocker and WDAC?

AppLocker is a user-mode control that is simple to pilot through Group Policy and easy to scope to specific users or groups. Windows Defender Application Control is enforced by kernel code integrity, can be protected by virtualisation-based security so that a local administrator cannot disable it, and applies to the whole device. Microsoft positions WDAC as the strategic option and AppLocker as a supplement.

Does Allowlisting Replace Antivirus?

Not entirely. Allowlisting stops unapproved code from executing, which covers most commodity malware and ransomware droppers, but it does nothing about attacks that run inside approved software, such as malicious macros in a trusted office suite or exploitation of a browser. Most organisations run both, with the allowlist as the hard control and the anti-malware engine providing telemetry and detection.

How Long Does a Rollout Take?

Plan for months rather than weeks on a mixed estate. Fixed-function devices such as kiosks and single-role servers can reach enforcement in a few weeks. General office devices typically need six to eight weeks of audit-mode logging, then a phased move to enforcement. Engineering and IT workstations take longest because their software changes constantly and needs a managed installer arrangement.

Can Attackers Bypass an Allowlist?

Yes, and the common routes are predictable. Writable directories inside a trusted path, disabled DLL or script rules, unsigned interpreters, and trusted Microsoft binaries that execute arbitrary code are the usual weaknesses. Applying the Microsoft recommended block rules, enforcing PowerShell Constrained Language Mode, and auditing path rules for user-writable locations closes most of them.

Related Terms

You May Be Interested In These

What Are Kubernetes Admission Controllers?

Cybersecurity Terms

17 November 2026

What Are Kubernetes Admission Controllers?

Read More
What Is KVKK Data Breach Notification?

Cybersecurity Terms

17 November 2026

What Is KVKK Data Breach Notification?

Read More
What Is Physical Imaging of a Mobile Device?

Cybersecurity Terms

17 November 2026

What Is Physical Imaging of a Mobile Device?

Read More