Home MS hacker story, v3.0

MS hacker story, v3.0

Andy Brown
In our content, we occasionally include affiliate links. Should you click on these links, we may earn a commission, though this incurs no additional cost to you. Your use of this website signifies your acceptance of our terms and conditions as well as our privacy policy.

Is it just me or has this story changed at least twice since it broke? First the hacker had potentially had access to all sorts of source code for five weeks, then he had access to a little bit for only a couple of weeks, and now in this ZDNet story they’re basically saying ‘We knew the whole time, we were just testing.’

Of course, after twelve days of knowing there was an intruder and watching that intruder, Microsoft apparently still doesn’t know who they are or where they’re geographically located. Additionally, as a consultant in the article points out, one easily detected hacker “shouldn’t have necessitated urgent calls to the FBI and a shutdown of all remote access for Microsoft’s roughly 39,000 full-time employees world-wide.” An excellent point.

Who knows if we’ll ever find out the full extent of the breach (it’s questionable as to whether the big MS even knows at this point) but it sounds as though the truth is somewhere between the original, high-level, months-long security breach, and the low-level “knew it all along” twelve day version.

The Tech Report - Editorial ProcessOur Editorial Process

The Tech Report editorial policy is centered on providing helpful, accurate content that offers real value to our readers. We only work with experienced writers who have specific knowledge in the topics they cover, including latest developments in technology, online privacy, cryptocurrencies, software, and more. Our editorial policy ensures that each topic is researched and curated by our in-house editors. We maintain rigorous journalistic standards, and every article is 100% written by real authors.