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.
|Razer Electra V2 offers affordable immersion||0|
|Samsung 360 Round camera captures the world from all angles||8|
|National Seafood Bisque Day Shortbread||5|
|MSI GS63 Stealth laptop flies under the radar with a GTX 1050||5|
|Zotac GTX 1080 Ti ArcticStorm Mini proves that size doesn't matter||26|
|Aorus X9 packs two GTX 1070s in a slim chassis||15|
|ROG Strix X370-I and B350-I are itty-bitty boards for Ryzen builds||15|
|Qualcomm shows progress on 5G mobile broadband||21|
|Samsung foundry train stops at 8-nm LPP before heading to EUV||27|
|Honestly can't see the point of Vega64 for gamers. It's a power-hungry compute monster that barely outperforms Vega56 and no matter how much you overc...||+25|