Forum Discussion
Blocking OAuth Phishing
I would essentially disagree with the statement that having MCAS is the only way you can prevent this. I agree that it can certainly help, and I always say that if you can afford MCAS, then get MCAS as it is an awesome tool.
However, the links provided in the article including https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/detect-and-remediate-illicit-consent-grants?view=o365-worldwide and https://docs.microsoft.com/en-us/cloud-app-security/investigate-risky-oauth and https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/manage-consent-requests all show techniques that can help you to identify and prevent such attacks.
So in my opinion, this can be done without MCAS, but MCAS will make it a hell of a lot easier for you.
- Thanks, given that there is almost always many ways to do something, I was concerned that the otherwise very reliable host of that show had made such a bold statement that an E5 license was required. He was very critical of MS for this, and while criticism is frequently warranted, it seemed excessive in that show. When this topic comes up for my clients, i'll be sure to discuss all of the options you have shared.
