Apr 03 2020
- last edited on
Jul 24 2020
Im working with a big client where we are rolling out SSPR combined experience where we in a few weeks are planning to enforce registration with a minimum of 2 authentication methods (APP and Phone).
In the MFA settings we are able to disable phone call as a authentication method.
But when using SSPR this option is not longer viable.
We have been in contact with Microsoft and got the reply that this feature cant be disabled for SSPR, only for MFA, and that this is by design.
We are worried of the potential security threat in that a redirection/forward of a phone number to an imposter phone number could be a way in to our environment.
Do anyone have any idea of how to
* disable phone calls when authenticating against the sspr feature (but keep sms)
* whats your take or thoughts of the potential risk/threat of someone forwarding phonecalls through the users phone-operator?
Thank you for your help!
Kind regards Johan
Apr 10 2020 11:34 AM
I cant really see a way to block phonecalls but keep SMS if since like Microsoft said, this is by design.
I would suggest that you remove the Phonecall/SMS as a method and just use the app/Verification code as a method.
Or maybe poke around in Conditional access policies to see if it's possible to control it from there.
Spoofing/forwardning numbers is a big issue really, but hard to protect against.
One security setting we've done is to only allow SSPR and MFA registration from inside our country, this to avoide spoofed/forwarded numbers etc.
Hope this helps.