now browsing by tag


Windows Incident Response

Source: Windows IR

Here’s a really good…no, I take that back…a great blog post by Sean Mason on “IR muscle memory”.  Take the time to give it a read, it’ll be worth it, for no other reason than because it’s valuable advice.  Incident response cannot be something that you talk about once and never actually do; it needs to be part of muscle memory.  Can you detect an incident, and if so, how does your organization react?  Or, if you receive an external notification of a security incident, how does your organization respond?
Read more at Windows IR

Why Windows 10?


So rumors are all about, why is the latest iteration of Windows going to be called Windows 10.

There are strong indications that point towards coding practices used by many, to determine OS is the reason. See here.

Also, the rumor was fueled by multiple posts making their rounds on popular social networking sites:

Microsoft dev here, the internal rumours are that early testing revealed just how many third party products that had code of the form


if(version.StartsWith(“Windows 9”))
{ /* 95 and 98 */
} else {


and that was the pragmatic solution to avoid that.