Hey everyone, lets look at what is wrong with passwords and regular MFA! Please make sure to read the description for the chapters and key information about this video and others. ⚠ P L E A S E N O T E ⚠ 🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there! 🕰 I don't discuss future content nor take requests for future content so please don't ask 😇 🤔 Due to the channel growth and number of people wanting help I no longer can answer or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc. 👂 Translate the captions to your native language via the auto-translate feature in settings! ruclips.net/video/v5b53-PgEmI/видео.html for a demo of using this feature. Thanks for watching! 🤙
John: Excellent content as always. Thank you for everything you do! Can this 'proximity' control work if we give our users the flexibility to access 'some' of our apps via their phones or their personal devices? Wondering how the use of say a 'bluetooth', would work in that scenario? Or perhaps this is a perfect use-case for someone with an 'admin' role?
I'm on to you!! You try to trick us by saying your password is 'password' but later in the video you say you use a unique password for each login. So, obviously, its 'password1', 'password2', etc.. Seriously, though. When a hacker gets a user's password, one of the first thing they will do is see where else that password can work. Don't re-use passwords. Thanks for the video, John!
If the user falls for a AITM attack their account can still be bypassed since the session gets captured correct? What can we do prevent an AITM from working? Enabling sign ons from trusted locations isn’t always feasible for some clients.
![SiVi CODE | Xây dựng website bán hàng với ReactJS. [FE - Bài 28]](http://i.ytimg.com/vi/XCSEsr3lTc0/mqdefault.jpg)
Hey everyone, lets look at what is wrong with passwords and regular MFA! Please make sure to read the description for the chapters and key information about this video and others.
⚠ P L E A S E N O T E ⚠
🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there!
🕰 I don't discuss future content nor take requests for future content so please don't ask 😇
🤔 Due to the channel growth and number of people wanting help I no longer can answer or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc.
👂 Translate the captions to your native language via the auto-translate feature in settings! ruclips.net/video/v5b53-PgEmI/видео.html for a demo of using this feature.
Thanks for watching!
🤙
Perfect timing for this! Thanks for reliably engaging and relevant content
MFA: Something old, something new, something borrowed, something blue, and a sixpence in your shoe.
John: Excellent content as always. Thank you for everything you do! Can this 'proximity' control work if we give our users the flexibility to access 'some' of our apps via their phones or their personal devices? Wondering how the use of say a 'bluetooth', would work in that scenario? Or perhaps this is a perfect use-case for someone with an 'admin' role?
💯%, couldn't agree more, only use anti-phishing auth options 🙂
Thanks John. Great Content one again 👏
My pleasure!
Now I only have to convince people at work that we should implement this... it's an up hill battle!!
enjoying this video for today learning, thanks a lot!
"As you can see this is me, there's no hair there whatsoever"
Gold.
I'm on to you!! You try to trick us by saying your password is 'password' but later in the video you say you use a unique password for each login. So, obviously, its 'password1', 'password2', etc..
Seriously, though. When a hacker gets a user's password, one of the first thing they will do is see where else that password can work. Don't re-use passwords.
Thanks for the video, John!
Damnit, you got me :)
Very useful.
At i put my foot down MFA enable for all users now just need to configure the Phishing-resistant MFA policy.
If the user falls for a AITM attack their account can still be bypassed since the session gets captured correct? What can we do prevent an AITM from working? Enabling sign ons from trusted locations isn’t always feasible for some clients.
I did a separate video talking about token theft.
Thank you
You're welcome
Thanks for the video!