MFA security awareness training

%3CLINGO-SUB%20id%3D%22lingo-sub-2838547%22%20slang%3D%22en-US%22%3EMFA%20security%20awareness%20training%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2838547%22%20slang%3D%22en-US%22%3E%3CP%3EGiven%20the%20importance%20of%20MFA%2C%20maybe%20we%20should%20have%20a%20mechanism%20to%20test%20that%20users%20are%20not%20approving%20MFA%20when%20they%20shouldn't.%20Much%20like%20how%20we%20do%20email%20security%20testing%2C%20we%20should%20have%20the%20ability%20to%20send%20users%20an%20MFA%20prompt%20to%20see%20if%20they%20mis-approve%20the%20login%20attempt.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2838547%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAuthentication%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eidentity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

Given the importance of MFA, maybe we should have a mechanism to test that users are not approving MFA when they shouldn't. Much like how we do email security testing, we should have the ability to send users an MFA prompt to see if they mis-approve the login attempt.

1 Reply
Hi @JasonGates895,

I want to share my opinion regarding your comment. I understand the need for a feature like this, but I would say; no MFA if you're working from a trusted device. If you force a user to approve MFA every day (by, for example, configuring a session control), it would be pretty evident that users might click on approve. But if you create a Conditional Access MFA policy with the setting Exclude Hybrid AD joined devices or compliant devices. They won't even receive an MFA request and will look strange when they will. So the chance of approval would be considerably smaller.

Don't get me wrong, but MFA challenges should be reduced and worry users instead of having more of them.

MFA approvals will always be a problem since you rely on your users. But luckily, we have features like risky sign-in that can recognize these kinds of potential hackers.