Skip to main content
Mallory
← Back to News
widely-deployed-product-advisory

Microsoft Hardens Windows CLFS Logfiles With HMAC Authentication

Patch & Detection Intelligence · 2 sources · Updated 5d ago · First seen Feb 24, 2026

Microsoft Hardens Windows CLFS Logfiles With HMAC Authentication

Microsoft introduced Common Log File System (CLFS) logfile authentication in Windows 11 version 25H2 and Windows Server 2025 updates released on or after October 28, 2025. Documented in KB5056852, the mitigation uses hash-based message authentication codes (HMACs) and a system-unique cryptographic key to verify logfile integrity before parsing internal structures. It is enabled by default with a 90-day learning period that adds authentication codes to existing logfiles when callers have write access; enforcement subsequently rejects logfiles with missing or invalid authentication codes.

Administrators can manage enforcement through MDM, Group Policy, or the registry and use the CLFS authentication utility to authenticate legacy or transferred logfiles. Because authentication keys are system-specific, moving logfiles between systems requires administrator intervention. Organizations should assess compatibility and performance before enforcement: the mitigation increases storage requirements, slows logfile creation and opening, and approximately doubles average record-write times. Microsoft also clarified that authentication reads the entire logfile, increasing disk I/O during operations such as user logon and system shutdown.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

2 events · Oct 28, 2025 – Feb 24, 2026
  1. Feb 24, 20269mo ago

    Microsoft clarifies CLFS authentication's full-logfile read overhead

    Microsoft updated its documentation to explain that CLFS authentication must read the entire logfile from disk before parsing internal structures. This adds disk I/O proportional to logfile size, including during user logon and system shutdown when the Registry opens CLFS-backed user-hive logfiles.

    Common Log File System (CLFS) Authentication Mitigation | Microsoft Support
  2. Oct 28, 20251y ago

    Microsoft publishes KB5056852 describing CLFS authentication hardening

    Microsoft published guidance for a CLFS mitigation available in Windows 11 version 25H2 and Windows Server 2025 updates. The mitigation uses system-specific HMACs to check logfile integrity before parsing, with a default 90-day learning period before enforcement rejects missing or invalid authentication codes.

    Common Log File System (CLFS) Authentication Mitigation | Microsoft Support
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

2 linked
Windows 11Windows Server 2025
Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.