Re:Robinhood announces data security incident
by nijave on Monday November 08, 2021 @05:02PM
(#29154853)
2FA with hard tokens seems common. There's also authenticating gateways/proxies and SASE products
[ Parent
| on HN ]
Re:Robinhood announces data security incident
by jimmydorry on Monday November 08, 2021 @05:15PM
(#29154977)
2FA doesn't seem like a golden bullet here, where if I understand the attack vector correctly, the malicious party convinced support to grant them access (presumably since they claimed to be working from home).
If they issued 2FA hard tokens, the attacker would have to wait a few days for them to arrive, but they would be allowed in all the same.
Re:Robinhood announces data security incident
by omegalulw on Tuesday November 09, 2021 @01:19PM
(#29165257)
> If they issued 2FA hard tokens, the attacker would have to wait a few days for them to arrive, but they would be allowed in all the same.
Nope. You won't ship keys to some random address - you will do it to the address on file. Presumably, changing address on file would be guarded by rigorous processes.
Re:Robinhood announces data security incident
by jimmydorry on Sunday November 14, 2021 @10:06AM
(#29217567)
Much like giving keys to the kingdom (access to internal systems) was guarded by a rigorous process. xD
Re:Robinhood announces data security incident
by doubled112 on Monday November 08, 2021 @06:18PM
(#29155616)
I'm mostly playing devil's advocate, but there could definitely be a process around that 2FA token that isn't there for a password reset.
Verifying the employee's mailing address vs just replying to them over the phone or email sounds like a hurdle. Might not be the same person shipping out the token, so now you have to prove it to two people. Blockers like that.