WEBVTT 00:00:00.080 --> 00:00:08.320 honestly we all suck at passwords and yeah maybe you personally use unique 00:00:05.680 --> 00:00:12.000 impossible to guess 50 character randomized passwords for all your 00:00:10.080 --> 00:00:15.440 accounts but unfortunately you'd be the exception rather than the rule you 00:00:13.519 --> 00:00:20.000 special little person you according to a 2019 google study about a quarter of 00:00:17.760 --> 00:00:23.600 americans used some absurdly unsecured passwords like one two three four five 00:00:21.920 --> 00:00:27.599 six and according to a different study from the same year around three quarters 00:00:25.519 --> 00:00:32.800 of users in the us and canada reused passwords while around half only change 00:00:30.960 --> 00:00:36.960 one character when they're forced to update their passwords and to be fair a 00:00:35.120 --> 00:00:40.960 big part of the reason this happens is that the average person has so many 00:00:39.120 --> 00:00:44.640 online accounts now that they can't keep their password straight and many people 00:00:42.879 --> 00:00:48.879 aren't even aware that password management software even exists then you 00:00:47.280 --> 00:00:52.879 have the fact that passwords sometimes aren't even stored on the servers 00:00:50.719 --> 00:00:56.079 themselves in a secure manner all you need is to take one look at the 00:00:54.079 --> 00:01:00.719 headlines about password dumps to see that but do we even need passwords at 00:00:59.680 --> 00:01:05.439 all even though we're all still used to punching in passwords people in the 00:01:03.680 --> 00:01:10.159 computer industry have been discussing eliminating them for quite a while now 00:01:07.600 --> 00:01:14.240 back in 2004 bill gates himself pointed out that the whole idea of a password 00:01:12.240 --> 00:01:18.479 was flawed for situations where a high level of security was needed 00:01:16.400 --> 00:01:22.240 but if this is true what would we use instead microsoft 00:01:20.799 --> 00:01:25.680 seems to think they've got it all figured out if you have a microsoft 00:01:24.080 --> 00:01:30.159 account you can actually go into your settings right now and choose to convert 00:01:27.920 --> 00:01:34.240 your account to password lists instead of using a password you can use the 00:01:32.159 --> 00:01:38.079 microsoft authenticator app to secure your account each time you want to log 00:01:36.159 --> 00:01:43.280 in you'll either get a verification code from the app or through sms or email get 00:01:40.960 --> 00:01:47.759 prompted for a physical security key or use biometrics like Windows hello face 00:01:45.920 --> 00:01:51.200 scan i'll tell you a little more after this message from our sponsor pulseway 00:01:49.680 --> 00:01:54.159 pulseway is an all-in-one platform management tool that can help protect 00:01:52.720 --> 00:01:57.920 your business for things like phishing and ransomware pulsar's got features 00:01:55.920 --> 00:02:01.600 like automated patching and central user and system management they also offer 00:01:59.840 --> 00:02:04.880 disaster recovery backup and stolen credential monitoring so protect your 00:02:02.960 --> 00:02:08.959 business today and try pulseway for free through the link below the password list 00:02:06.960 --> 00:02:12.160 isn't just something microsoft is doing though it has stolen the headlines 00:02:10.479 --> 00:02:15.599 considering it means you can go entirely passwordless on Windows many mobile apps 00:02:14.400 --> 00:02:20.000 have allowed you to log in with a fingerprint after just a first-time 00:02:17.440 --> 00:02:23.920 setup and the signs also point to google moving to a passwordless model with 00:02:21.840 --> 00:02:28.239 those one-tap authentication prompts that show up on your phone possibly 00:02:26.000 --> 00:02:32.239 being the way of the future in fact google builds security keys directly 00:02:30.160 --> 00:02:36.560 into Android phones themselves in order to verify that it's actually you trying 00:02:34.239 --> 00:02:39.920 to get into your own account of course even though none of this will sound 00:02:38.080 --> 00:02:44.400 super novel to anyone who's ever used two-factor authentication as all of you 00:02:42.160 --> 00:02:48.720 should be we probably still have a ways to go before passwords really become a 00:02:46.480 --> 00:02:52.959 thing of the past while large firms like google and microsoft will probably lead 00:02:50.480 --> 00:02:57.360 the way in implementing it it won't be trivial for smaller organizations to 00:02:55.360 --> 00:03:01.760 switch all of their infrastructure over to passwordless especially as users 00:02:59.200 --> 00:03:05.680 often have to log into multiple services that might not automatically play nice 00:03:04.080 --> 00:03:09.840 with each other it's for this reason that it departments might be looking 00:03:07.360 --> 00:03:13.519 more at a concept called the federated login which essentially means that one 00:03:11.840 --> 00:03:17.840 login will get the user into all the services they need but this takes work 00:03:15.760 --> 00:03:21.440 to implement and this isn't the only barrier to ditching our passwords if all 00:03:20.239 --> 00:03:25.519 this sounds like two-factor authentication with you know one less 00:03:23.280 --> 00:03:29.200 factor you'd be right although not having a password sounds super 00:03:26.879 --> 00:03:33.440 convenient it has the potential to make things a massive headache if a user 00:03:31.599 --> 00:03:37.760 loses their phone or their physical access token so cyber security workers 00:03:35.920 --> 00:03:42.319 face a challenge in figuring out a practical way to verify a person's 00:03:39.760 --> 00:03:47.840 identity if the worst happens personally i'm a fan of good 00:03:44.000 --> 00:03:47.840 old-fashioned secret handshakes 00:03:51.519 --> 00:03:56.239 so thanks for watching guys if you like this video hit like hit subscribe and 00:03:54.560 --> 00:04:00.959 hit us up in the comments section with your suggestions for topics that we 00:03:57.680 --> 00:04:00.959 should cover in the future