Had a sit down with MSRC, while I can't say full details we had a constructive discussion on the state of things aimed at the following (and remember I'm just the messenger): MSRC handling vulnerability submissions and researcher communication GitHub removal of cybersecurity repros and the pivotal need for safe harbor for TTPs and 0days I won't be commenting on the recent 0day releases being dropped by a certain researcher because that is a unique case. I will be discussing the other topics tho: While GitHub is owned by Microsoft they are still acting independently, I was assured that the removal of researcher GitHub accounts and code was NOT being authorized or done by MSRC. They fully understand the need for 0days and code to be available for testing and cybersecurity defenses is as important as it is for offensive needs, they don't not want code to be fragmented and us going back to the days of milw0rm. MSRC is going to look into these, and I conveyed the need to do this since other places like YouTube and twitch are also cracking down on cybersecurity accounts. The email between MSRC and researchers discussing 0day talks at BH / Defcon and asking them to report what they are talking about is another topic I discussed. This was actually for Microsoft to help coordinate mitigations and tech review the talks that were in their pipeline (btw they have sent this email or it's equivalent for years, it's not new). We discussed ideas to improve these emails and how things could be misinterpreted from both sides. I think MSRC has their work cut out for themselves, but I can say that there are still lots of very passionate researchers there still trying to do good things. And I'm very thankful for them taking the time to sit down with me. I've always been lucky with MSRC interactions, and if you aren't and need a line thru to them for legitimate reasons, let me know, I'm happy to meditate when it is necessary.