Cyber security

WDAC Rule Levels Comparison And Guide – Understanding File Attribute-Based Security Measures

We delve into the hierarchy of WDAC rule levels, ranging from the most secure to the least secure, providing insight into their significance and implications for system security.

Understanding these levels is crucial for effectively implementing file attribute-based security measures in your Windows environment.

This document lists all of the levels of WDAC rules. From Top to bottom, from the most secure to the least secure, the levels are:

0. Hash

  • File’s SHA2-256 Authenticode hash
  • File’s SHA2-256 Page hash

1. WHQLFilePublisher

  • One of the Intermediate certificates of the file
  • Leaf certificate of the file
  • File’s version
  • Another attribute of the file (FileDescription, InternalName, OriginalFileName, PackageFamilyName, ProductName, Filepath)
  • File’s WHQL EKU OID

2. FilePublisher

  • One of the Intermediate certificates of the file
  • Leaf certificate of the file
  • File’s version
  • Another attribute of the file (FileDescription, InternalName, OriginalFileName, PackageFamilyName, ProductName, Filepath)

3. WHQLPublisher

  • One of the Intermediate certificates of the file
  • Leaf certificate of the file
  • File’s WHQL EKU OID

4. SignedVersion

  • One of the Intermediate certificates of the file
  • Leaf certificate of the file
  • File’s version

5. Publisher

  • One of the Intermediate certificates of the file
  • Leaf certificate of the file

6. WHQL

  • Intermediate certificate of the file that belongs to Microsoft as part of the WHQL program
  • File’s WHQL EKU OID

7. LeafCertificate

  • Leaf certificate of the file

8. PcaCertificate

  • One of the Intermediate certificates of the file

9. RootCertificate

  • One of the Intermediate certificates of the file

10. FileName

  • One of the attributes of the file (FileDescription, InternalName, OriginalFileName, PackageFamilyName, ProductName, Filepath)

Important

These properties are mutable.

11. FilePath

  • Path of the file on disk

About SpecificFileNameLevel Options

WDAC creates file rules based on file attributes when you scan a folder using a level such as FilePublisher. Each file rule has a MinimumVersion and only one of the six SpecificFileNameLevels.

For instance, suppose a folder has 10 signed files with identical signatures and product names (or File Descriptions etc.).

In that case, WDAC creates a single file rule with the product name (or File Description etc.) and the lowest version of the 10 files. This file rule is sufficient to allow all 10 files.

The MinimumVersion is the smallest version among the files with the same signature and SpecificFileNameLevel in the folder.

Find more information in Microsoft Learn

Varshini

Varshini is a Cyber Security expert in Threat Analysis, Vulnerability Assessment, and Research. Passionate about staying ahead of emerging Threats and Technologies.

Recent Posts

git fetch vs git pull: How They Work and When to Use Each

Both git fetch and git pull talk to a remote repository, but they do very different things to your…

3 days ago

git cherry-pick Command: Apply Commits from Another Branch

Sometimes the change you need already exists, just on the wrong branch. A hotfix lands…

3 days ago

Best Email APIs for Secure Business Email: Why Developers Are Moving Beyond SMTP

Email is still one of the most important communication channels inside modern applications. Password resets,…

4 days ago

Nginx Commands in Linux: Start, Stop, Reload, Test, and Log

Nginx is a high-performance web server and reverse proxy trusted by some of the largest…

1 week ago

ufw Command in Linux: Manage Firewall Rules with Examples

ufw (Uncomplicated Firewall) sits on top of iptables (or nftables on newer systems) and replaces…

1 week ago

who Command in Linux: Show All Logged-In Users and Sessions

When you share a server with a team or investigate unexpected activity, the first question…

1 week ago