Breaching Microsoft via DeepSpeed GitHub Repository
johnstawinski.com
Breaching Microsoft via DeepSpeed GitHub Repository
1–6 of 6 posts
Re: Breaching Microsoft via DeepSpeed GitHub Repository
#2[dead]
Re: Breaching Microsoft via DeepSpeed GitHub Repository
#3How crazy is it that Microsoft is not even monitoring/alerting on commands like, "whoami" being issued on their managed systems? Wow.
Re: Breaching Microsoft via DeepSpeed GitHub Repository
#4[dead]
Re: Breaching Microsoft via DeepSpeed GitHub Repository
#5How crazy is it that Microsoft is not even monitoring/alerting on commands like, "whoami" being issued on their managed systems? Wow.
I wonder if alerts did come in, but Microsoft didn't respond quickly enough. That's giving them the benefit of the doubt, though; very possible they weren't monitoring this system. If they were, they probably would have identified the fact that it was exposed to the internet via a public GitHub repository....
Re: Breaching Microsoft via DeepSpeed GitHub Repository
#6How crazy is it that Microsoft is not even monitoring/alerting on commands like, "whoami" being issued on their managed systems? Wow.
I wonder if alerts did come in, but Microsoft didn't respond quickly enough. That's giving them the benefit of the doubt, though; very possible they weren't monitoring this system. If they were, they probably would have identified the fact that it was exposed to the internet via a public GitHub repository....
Agreed. That was a great read and cautionary tale about not following best practices!