Microsoft actions following attack by nation state actor Midnight Blizzard

Re:Microsoft actions following attack by nation state actor ... by tgv on Saturday January 20, 2024 @02:51AM (#39065548)

Well, your "legacy non production test tenant" can be opened by just guessing passwords, and it allows access to "very much in use production non-test" tenants, then you could say MS has a vulnerability. It may not be a buffer overflow, but it is a vulnerability nonetheless.

[ Parent | on HN ]

Re:Microsoft actions following attack by nation state actor ... by booi on Saturday January 20, 2024 @03:15AM (#39065635)

Yes, and I think most people would consider it a vulnerability if an authentication system doesn't rate-limit or otherwise slow/stop "password spray" attacks.

[ Parent | on HN ]

Re:Microsoft actions following attack by nation state actor ... by oezi on Saturday January 20, 2024 @03:27AM (#39065691)

You can rate limit individual users but password spray attacks use a large number of accounts to remain undetected in a authentication system used by an even more users.

[ Parent | on HN ]

Re:Microsoft actions following attack by nation state actor ... by mattigames on Saturday January 20, 2024 @04:04AM (#39065840)

We are getting 10000x times the number of wrong passwords than average, I'm sure it's nothing to worry about.

[ Parent | on HN ]

Re:Microsoft actions following attack by nation state actor ... by Towaway69 on Saturday January 20, 2024 @04:27AM (#39065938)

It was a legacy test system connected to a production system so it doesn't count. Obviously. /s

[ Parent | on HN ]

Re:Microsoft actions following attack by nation state actor ... by Jedd on Saturday January 20, 2024 @08:40AM (#39067470)

{rolls eyes}

This is precisely the kind of 1990's level basic heuristic that this company cites as part of their Sentinel security system.

Trying to excuse a breach by 'the attacker tried a few passwords against lots of different accounts' is not compelling.

[ Parent | on HN ]