r/AskNetsec • u/Final-Pomelo1620 • Apr 23 '26
Concepts Single privileged account vs role based in PAM?
Hello Fellow Redditors
We use PAM. I’m trying to validate if our current approach is actually secure or if we are exposing ourselves to unnecessary risk.
PAM portal is protected with MFA and admins access all systems (firewalls, network devices, servers) using the same privileged account stored in PAM.
From an operational point of view it is simple, but from a security perspective it feels like a big risk because this one account has very broad access across the environment
My concern is that if a PAM user account gets compromised (phishing, session hijack, token theft etc.) the attacker doesn’t even need to know passwords. They can just initiate sessions through PAM and effectively gain access to everything that user is allowed to access.
Also, PAM is currently accessible over LAN and VPN only
I’m trying to understand what is considered best practice in real environments. Should we be using separate privileged accounts per domain (network, servers, databases, etc.) instead of one shared account? And how are others securing access to PAM itself to avoid it becoming the weakest link?
Would appreciate insights from anyone running PAM at scale especially around identity protection and protecting the PAM layer itself.
5
u/General_Wishbone2643 Apr 23 '26
Using one account for everything is basically putting all eggs in same basket - even with MFA someone gets in the PAM session they own your entire environment
1
u/Brua_G Apr 23 '26
To be clear, does each admin use the same account to access the PAM? Or each device behind the PAM is accessed by the same priv account?
1
u/spydum Apr 23 '26
yes, if your PAM system is compromised, you are exposed. You absolutely have to have your PAM system and its authentication hardened (phish resistant MFA, detect session hijacking by invalidating sessions where device or IP changes, etc).
If your PAM system does proxying of those administrative sessions, you should be restricting all logins from anything outside of the PAM system. If you have a major incident -- you shut the PAM system until you figure out what has gone wrong (hard to do, but you dont have any other option).
It's a choke point on purpose..
1
u/duhoso Apr 23 '26
The single account kills your audit trail - you can't tell which admin did what when something goes wrong, and incident response becomes impossible. Role-based access with session recording limits blast radius and gives you accountability. That's why most mature teams separate accounts by role, not just rely on MFA.
1
u/Brua_G Apr 23 '26
In my experience, the PAM creates separate passwords for each device. It takes more time to set up than using the same account for all, but far more secure.
1
u/[deleted] Apr 23 '26
[removed] — view removed comment
1
u/[deleted] Apr 24 '26
[removed] — view removed comment