News for hackers. Stuff that matters.
Re:Capsudo: Rethinking Sudo with Object Capabilities by esseph on Friday December 12, 2025 @09:41PM (#46251513)
You should read over NIST 800-53 AC-2 and AC-6. They go over why privileged accounts are important, why they are used, and how they protect users and organizations.

JIT access should be the goal.

Scroll down to: Implementation Guidance

https://csf.tools/reference/cloud-controls-matrix/v4-0/iam/i...

Re:Capsudo: Rethinking Sudo with Object Capabilities by charcircuit on Friday December 12, 2025 @11:46PM (#46252062)
>JIT access should be the goal.

Individual privileges for specific things should be given access to instead of giving god access to a system.

Re:Capsudo: Rethinking Sudo with Object Capabilities by esseph on Saturday December 13, 2025 @12:22AM (#46252237)
I hear what you are saying but many, many people who have dedicated their life to this topic disagree with you. Onions have layers for a reason.

RBAC by nature requires a Creator. ZeroTrust networks still require gateways.

Re:Capsudo: Rethinking Sudo with Object Capabilities by charcircuit on Saturday December 13, 2025 @06:11PM (#46259146)
I'm not saying there can't be an admin who can create roles, or do some extra authentication to gain that privilege. I am saying that it shouldn't require assuming an all powerful user to do it. You should be able to do it from your actual account. This is good for keeping accurate records too since all actions are done by the users themselves. Yes, technically sudo can be logged, but it's bypassable by starting a shell.
Re:Capsudo: Rethinking Sudo with Object Capabilities by esseph on Saturday December 13, 2025 @08:42PM (#46260099)
Elevated credentials for said users segment access while still allowing the same user to access more administrative function.

Proper group / sudoers mappings can go a long way, but you still want that administrative break between access levels.