Quick Thoughts on Password Managers for IT Team Use

I'm by no means an absolute source for security wisdom, but after working in a handful of different environments, I've learned about using Password Managers in an IT environment. I generally recommend Keepass, but I'd like to expound on that recommendation a bit.
Keepass usually gets my recommendation for it's simplicity and it's price (free). However, it does have some limitations. Let's look at some of those.
  • Shared Login - You can access a Keepass DB with a password/passphrase, a key-file, or using a Windows Account. That third option at a glance makes one think it can auth against AD. What it actually entails is that you can only login using that specific Windows Account, and it's not just that username and password. If your computer gets wiped & reloaded, you can't simply create a new user account with the same username and password. Most commonly, a Keepass DB is locked with a master password or a key-file. For a small team this is usually sufficient, but if you need auditing, or better multi-user functionality, Keepass is a no-go. More info on how Keepass locks it's DB can be found here
  • Auditing - because there's no real multi-user functionality to Keepass DBs, there's no logging of who used what password when, or who modified a record, etc. I've worked in an environment where this functionality was deemed crucial
If individual accounts and activity auditing are features you need from a password manager, then you can look at Secret Server from Thycotic Software. It's not cheap, but it definitely has more features than KeePass. 

Comments

Popular posts from this blog

Installing CentOS 7 on a Raspberry Pi 3

Modifying the Zebra F-701 & F-402 pens

How to fix DPM Auto-Protection failures of SQL servers