this post was submitted on 16 Sep 2024
27 points (100.0% liked)

Cybersecurity

5687 readers
67 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Community Rules

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !cybersecurity@lemmy.capebreton.social !securitynews@infosec.pub !netsec@links.hackliberty.org !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] sugar_in_your_tea@sh.itjust.works 1 points 2 months ago (1 children)

Eh, it's about validating credentials match the records of the user account, it's not about validating that the person using those credentials is who they say they are. In other words, it doesn't mean "the person logging in is John Smith," it means "the person logging in has John Smith's credentials." If you want to prove that the user is who they say they are, you'll need a lot more than a password (biometrics are a start).

[–] YodaDaCoda@aussie.zone 1 points 2 months ago* (last edited 2 months ago) (1 children)

I imagine this process is more about ensuring the employee is the one entering the new password, rather than the malicious actor - which would easily be possible if a simple password reset email was sent out.

I guess that's possible, but then that user would be locked out of their account and they'd quickly figure out whose account was compromised when the employee can't access things anymore.