Safe naming conventions for personal privilege accounts help

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Safe naming conventions for personal privilege accounts help

L1 Bithead

Was hoping I could get some inspiration/help for reformatting our safe naming policy for personal privileged accounts. Right now, its very barebones

EG DOMAINACRONYM-FIRST-LAST

 

Our enterprise environment is such that we have ~14 different domains with varying levels of trust. So we have a lot of people who have multiple PP safes, as one is needed per domain in its own trust. I dont see any way around that since the CPM is tied to the safe. And the domains wont ever be centralized

 

I want to future proof as we mature the product by adding a prefix that denotes it as PP , and perhaps dept name?

eg DOMAINACRONYM-PPA-DEPT-FIRST-LAST

 

Pushing against the character limit. i could also add the account type

WIN-DOMAINACRONYM-PPA-DEPT-FIRST-LAST

  • that would cover accounts outside of the windows OS environment. EG Azure/Entra, but leaving little space for people's actual names.

 

Thoughts?

 

 

 

1 accepted solution

Accepted Solutions

L7 Applicator

Have you thought about using employee id or similar unique identifier in the organisation and the domain identifier?

Using departments is tricky as people do move around.

Many people share the same first and last names too.

​

View solution in original post

6 REPLIES 6

L7 Applicator

Have you thought about using employee id or similar unique identifier in the organisation and the domain identifier?

Using departments is tricky as people do move around.

Many people share the same first and last names too.

​

L7 Applicator

Hi @Schon Fazio​ 

 

I agree with your approach track to define Personal Privileged Account safe naming convention to be scalable and future-proof, especially given your multi-domain setup. The challenge is balancing clarity, uniqueness, and brevity 

 

I would think one of the following naming convention might be useful.

 

 

DOMAIN-PPA-ACCTYPE-USER

 

DOMAIN-PPA-DEPT-ACCTYPE-USER

 

DOMAIN-PPA-DPT-AT-USER

 

 

Hope it helps !

 

 

This is the answer. People will move departments and departments will change names. Keep it simple and stick to something like an employee ID in the safe name.

 

Regarding the safe per domain for CPM management, I would see if PlatformsToManage could help you consolidate the safes. Yes, it is for PAM self-hosted but being that the Priv Cloud and PAM self-hosted CPMs are (for the time being) still pretty similar, this could be a setting that you could convince support to help you define, maybe with some encouragement from your account manager/customer success manager.

Sadly Platforms To Manage isn't exposed in PCloud to end users either by configuration in pvwa or rest as far as I know.

It's an omission that I hope they resolve shortly as it is very handy in use cases like this.

I believe support can modify it, but not sure if they want to...

I was on the fence about the department. this is good enough reason to axe it

something like an employee ID from our HR system would be interesting.

Thanks for the response. At the very least placing domain first is a safe bet (pun intended). probably going to forgo the department though

  • 1 accepted solution
  • 237 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!