Compromised Microsoft Key: More Impactful Than We Thought - Lemmy.world

According to Microsoft, the compromised key was inactive and therefore any access token signed by this key must be considered suspicious. Unfortunately, there is a lack of standardized practices when it comes to application-specific logging. Therefore, in most cases, application owners do not have detailed logs containing the raw access token or its signing key. As a result, identifying and investigating such events can prove exceedingly challenging for app owners.