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.
|Asus Tinker Board gives the Raspberry Pi 3 a run for its money||26|
|Mushkin enters the keyboard market with the Carbon KB-001||25|
|Report: PC gaming hardware market expands to an all-time high||25|
|Asus ROG Maximus IX Formula chills with an EKWB waterblock||1|
|Deals of the week: high-powered graphics cards, monitors, and more||11|
|Eurocom Tornado F5 SE mobile server can eat desktops for lunch||11|
|Microsoft releases Pix DX12 tuning and debugging tool for Windows||20|
|Cryorig's QF140 fans offer a choice of silence or performance||16|
|SteelSeries' Apex M500 keyboard reviewed||12|
|No one came into this article thinking TomsHardware actually took a hammer to an SSD as an endurance test, right? No? G-good, m-me neither.||+41|