Nice way of talking about boring subjects, and on top of that, the first video is really funny!
The only way it could get better is having two people working in tandem on a single keyboard for extra speediness
The world's biggest brands have benefited from influencer marketing for years – now the UK's National Cyber Security Centre (NCSC) has hopped on the bandwagon to preach two-factor authentication (2FA) to the masses. It's the latest effort to improve the nation's cyber resilience as part of the Stop! Think Fraud campaign …
Nice way of talking about boring subjects, and on top of that, the first video is really funny!
The only way it could get better is having two people working in tandem on a single keyboard for extra speediness
Nah, asymmetric public / private keys are the better solution.
Reaching for your stupid mobile just to log in is tedious and masks the real problem... You keep having to "log in".
Imagine you instead simply upload your public key to sites as you create an account. Never need to log in again. Web browsers could make this even more simple by acting as an agent for your private key.
Well, in that case, I have good news for you - this is exactly how WebAuthn works! Whether it's the 2nd factor or the only factor depends on the website, and depending on your platform you might be using a physical security key or (as you suggested!) a platform authenticator like a phone, OS or browser, but in any case, the website just gets a public key and you use your private key to log in, sometimes with as little as a fingerprint scan (again, depending on your desired security level).
Imagine trying to educate the public about how to generate a keypair, upload their public key to every single Web site they want to access, and how to keep their private key private.
Imagine someone phishing the user's private key or compromising the user's browser and thus being able to log into any Web site the user has ever used without any other authentication.
Imagine the user needing to log in from disparate devices and having to generate a new static key for each device (or for there to be a secure private key distribution mechanism among devices).
Not to say that symmetric key authentication is a bad idea, but it's hardly a simple panacea for the problem of compromised credentials. MFA using a TOTP authenticator has its own problems (e.g. credential recovery if the device is lost), but it's better than what a lot of people have, which is either nothing or SMS-based MFA.
"...Imagine you instead simply upload your public key to sites as you create an account. Never need to log in again. Web browsers could make this even more simple by acting as an agent for your private key..."
How is that different from logging in with a GooFaceGramX account, which most sites already support, and how does it increase security ?
I genuinely don't know what uploading a public key is, but from the short sentence describing it - it sounds like a comfort feature to ease logging in, rather than a security one. If someone gets on my computer and my public key is uploaded, how do I prevent them from getting on these sites where I'll never need to log in again ?
And if the answer is "enter your private key" - I'll refer to my first question ?
Thanks
ISO standard for password complexity ?
Of course not. So everyone+dog has their own idea of what is acceptable.
ISO standard for MFA implementation ?
(Spits coffee out) Are you kidding ? We need another century on that.
This is better than nothing. But that's only because we literally have nothing to compare it to.
"ISO standard for password complexity ..."
Having worked on ISO infosec standards for years, I'm not at all sure that would help at present, for two reasons: [1] the revision cycle is very long compared with the speed at which the threat space evolves; [2] the content of the standards is based on a majority consensus of current practice, so it's a very slow process to amend existing core material, because they can only reflect what is being done rather than what necessarily should be done. And as everyone follows the standard, practice has little chance of getting changed. This is not a fault specific to ISO -- it's inherent in development of any standard based on the average of current practice. A more effective way forward might be to rigorously redefine practitioner training to emphasise teaching of first principles rather than just rules, so the individual would, for example, be aware of the actual range of threats to passwords and how to protect against each -- understanding that it's not all 'fixed' by 'complexity' (whatever that really means). And the results of such training would to some extent feed usefully into standards development by improving the 'current practice' on which they are based.
National Cyber Security Centre (NCSC) --> Promotes cyber security and recommended use of E2EE.
MI5 and UK Plod --> We want backdoors into everything, including E2EE (and you can trust us to only go after terrorists and paedophiles, even though the Regulation of Investigatory Powers Act was used simply to catch people not picking up their dogs shit, as reported by El Reg many moons ago)