Earlier quoted context omitted.
When calling my bank I have to enter my entire CC number AND my PIN code. Talk about training people to give away sensitive data.
What is the issue? That's literally just your account number and the password. That's what you're supposed to do. That's what security is. That's the sensitive data that ensures it's not a rando calling who stole your card. I'm not sure what alternative you are looking for? You're the one calling them, so it's fine.
Why are banks still getting authentication so wrong?
361–370 of 375 posts
Re: Why are banks still getting authentication so wrong?
#362Earlier quoted context omitted.
> When calling my bank I have to enter my entire CC number AND my PIN code. YOU calling THEM is not an issue. That's the secure connection. There's not (afaik) a way to hijack the receiving phone number. The issue is when somebody calls YOU. Faking the originating number of a phone call is easy, happens all of the time. That's the scammer route.
There are absolutely ways to intercept a call from a targeted user that would be viable to use to gain access to a mid to high value user's funds. SS7 call routing and rogue 2G base stations are some potential approaches. In terms of banking security, a good (ideal) architecture would treat the user PIN as a credential which is not transmitted over insecure means. Unfortunately many banks don't do this right, and sti…
Re: Why are banks still getting authentication so wrong?
#363Earlier quoted context omitted.
> I don’t have a good way to authenticate someone is calling from the bank on my end. You could ask them to list your last 3 transactions, and their exact amounts. Easy to cross-reference by looking at your banking website / app.
Unless the system you use the check that balance is compromised on your end or their end. If you have malware, they can be looking at the same numbers you’re looking at, so that isn’t fool-proof. If your account is already compromised, they may just be phishing for 2fa tokens to initiate some kind of account change, like the kind that would complete their total account takeover, at least until you or the bank notices…
Re: Why are banks still getting authentication so wrong?
#364Earlier quoted context omitted.
Password manager ftw
This is fine for services you can easily access on a phone or computer. My employer requires I change my laptop password every 60 days, it stores the last 2 years of passwords to prevent reuse. I am not opening up LastPass and plugging in a 32 character random string every time I want to start my computer up. My password at any given point is either a few random words and a number, or a short (8-12 character) alphanu…
How do these people get these jobs?
I have 25 years of enterprise-level web application development experience. I passed the CISSP on my first try with minimal study. I read RFCs for fun.
And yet I can't even get a screening interview with an actual human (although my one AI interview asked surprisingly competent follow-up questions).
Re: Why are banks still getting authentication so wrong?
#365Earlier quoted context omitted.
I think it’s valid to question the wisdom of a CISO using misguided password guidelines. I don’t think it’s valid to respond to guidelines you disagree with by willfully sabatoging security. You relinquish your righteous position on password security when you put your password on a post-it in your laptop.
Reads like you are trying to argue for abstinence only education here. The reality security must operate in is that the best security policies are those that people don't circumvent. If people have to resort to sticky notes, sharing credentials, scripts that automatically update a file containing a plaintext credential, or what have you, odds are that security has massively fumbled the ball. Keep in mind this is alre…
Re: Why are banks still getting authentication so wrong?
#366Earlier quoted context omitted.
I think it’s valid to question the wisdom of a CISO using misguided password guidelines. I don’t think it’s valid to respond to guidelines you disagree with by willfully sabatoging security. You relinquish your righteous position on password security when you put your password on a post-it in your laptop.
You call it "willfully [sabotaging] security," I call it "the best alternative that doesn't leave me with a 30% chance of forgetting my password every 60 days." 1Password is smart enough to let me have a secure, non-leaked password of high complexity that I have memorized , then let me go years without resetting it. I started there and the policies have made my laptop progressively less secure over time.
Re: Why are banks still getting authentication so wrong?
#367Can we get rid of the password expiration too? Requiring that users change their perfectly secure password every 6 months is absurd and gives the impression of security when in reality it only makes things worse.
One hundred percent. I’d be interested to see how many people resort to having weaker passwords just to try to remember the new password every 6 months. I know many folks are proud of their password ‘system’ of using the same word and adding different numbers every time they need to change it. Not helpful.
Re: Why are banks still getting authentication so wrong?
#368Re: Why are banks still getting authentication so wrong?
#369Earlier quoted context omitted.
Be careful what you wish for. This problem is solved in China — you can contact many government agencies and major companies over WeChat and be sure that you're talking to the real entity, but the downside is that WeChat has a copy of your passport and knows everything about you.
>This problem is solved in China It isn't. China is the best example that draconian identity verification / KYC processes don't stop scammers.
Re: Why are banks still getting authentication so wrong?
#370> TOTP Support: Let users use any standard authenticator How many of them allow to generate a code related to specific operation (provide a context for what is being "confirmed")? This is the EU requirement that killed everything but SMS and bank mobile apps.
Still better than in-house crap.