this post was submitted on 10 Apr 2026
5 points (100.0% liked)

Cybersecurity

9810 readers
33 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 !securitynews@infosec.pub !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 2 years ago
MODERATORS
 

My company has an external auth provider for the whole organization, and MFA is required (push notification to a phone app). This all works well and I agree with it, BUT they have configured the credentials to expire in 20 minutes. In practice this means everyone in the company is typing their password and fiddling with their phone dozens of times per day to work with any application except for email (somehow it gets away with caching the credentials).

Timeouts for credentials are good, but does this aggressively low setting actually provide increased security?

you are viewing a single comment's thread
view the rest of the comments
[–] blarth@thelemmy.club 1 points 1 day ago

In my opinion, somewhat. Tokens that expire can’t be used persistently for exploitation, but if an attacker was able to obtain said token, why wouldn’t they be able to continue obtaining new ones?

Passkeys are the perfect antidote, but their adoption has been hindered by a lack of understanding of how they work, where they’re stored, and a renewed SSO tax, among over factors.