Flame fallout: Microsoft encryption deadline looms Tuesday

Starting Tuesday Microsoft platforms will block the use of encryption keys less than 1024 bits so businesses that are still using weaker keys better get busy.

Changing the keys the Microsoft software uses isn't that tricky, but finding all the customer and third-party software in corporate networks that use smaller keys could require some searching.

BACKGROUND: In face of Flame malware, Microsoft will revamp Windows encryption keys

HELP: 11 (FREE!) Microsoft tools to make life easier

Users should download the update and test whether it breaks connections with existing applications before putting it into full production, experts say.

Also, automated tools such as those sold by ExtraHop and Venafi can help track down applications that won't comply with the Microsoft update.

The change in key length requirements came in the wake of an exploit against Windows Update becoming a key component of Flame malware attacks. Keys less than 1024 bits are deemed too easy to break with brute force attacks.

The patch has been available since August as an option to give customers time to check it out and install it, but after Tuesday it is no longer optional. "There are still a few days left if you haven't tested it, but don't let this be an 'I told you so' moment," says Paul Henry, security and forensic analyst at Lumension.

Affected platforms are: Windows XP, Windows Server 2003, Windows Server 2003 R2, Windows Vista, Windows Server 2008, Windows 7 and Windows Server 2008 R2 operating systems.

The upgrade does have some wiggle room. Applications signed before Jan. 1, 2010, are allowed to use keys smaller than 1024 bits.

The deadline coincides with October's Patch Tuesday, which for the second month in a row is pretty light, featuring just one critical bulletin.

It apparently addresses a long-standing flaw in code that was repeatedly used in SQL Server from 2000 on. Unpatched, it can allow a remote-code execution on affected platforms.

Since so many consecutive versions of SQL server are being patched by the same update, it indicates the update is addressing the same problem in all the versions, says Alex Horan, a product manager at Core Security. Generally one patch deals with a single flaw. "So from that I conclude this is the same issue (and therefore the same code) across these versions," he writes in an email.

Tim Greene covers Microsoft for Network World and writes theA Mostly MicrosoftA blog. Reach him atA tgreene@nww.comA and follow him on TwitterA @Tim_Greene.

Read more about wide area network in Network World's Wide Area Network section.

Copyright © 2012 IDG Communications, Inc.

7 hot cybersecurity trends (and 2 going cold)