Our startup has something like 100 usernames and passwords to keep track of, and we can't keep track of all of them. Would putting all of them in a Google spreadsheet shared amongst ourselves be a bad idea? It feels like a security problem, but I can't articulate why I think that.
|
migrated from programmers.stackexchange.com Dec 24 '11 at 23:03
|
I have a colleague who consulted for a company that was doing something this colossally dumb - same thing, with bank passwords. You want something like http://enterprise.lastpass.com/ ! (I'm just a happy (non-enterprise) customer.) With that, NONE of your staff need direct access to the passwords to use them. < sic > |
|||
|
|
|
Wait --you are thinking of sharing amongst yourselves the list of all your usernames and passwords? That's not just spectacularly, that's a monumentally bad idea regardless of whether you store it as a google spreadsheet or post-it notes! And, of course, a google spreadsheet has the additional disadvantage of being publishable to the entire planet with a couple of clicks. The rule about passwords should be: "Your password is very strictly personal. If we find out that someone other than you knows your password, you are both fired." |
|||||||||||
|
|
Without wanting to pick on Google, you should read the article by James Fallows in the November Atlantic Monthly. In brief, Fallows's wife's GMail account was compromised by a scammer. The scammer used her mailing list and old emails to generate a "Help, I've been mugged in foreign city and need money!" scam. On top of that, the miscreant deleted all of her documents and old email before she regained control of the account. Consider: your shared document is no more secure then the Google account of your most careless team member. While Google's security may be generally better than yours in theory, it's also a more prominent target, and can easily be undermined by carelessness on the part of a user. You may incorporate the Google cloud into your infrastructure, but you can't just assume that Google is going to take on all the responsibility for your security. Nobody will care about your data as much as you do. |
|||||
|
|
It depends on your required level of security. In that case the data should be in an excel spreadsheet on a USB key that is left on a train. (in the US, where the left on a train loophole has been effecively blocked it should be left in a cab) |
|||||
|
|
In a targeted attack, an unprotected list of users and passwords is one of the first things scanned for. Once you have that, you have the keys to the kingdom. The next thing in line is to look for an organizational chart to find which user names would be most likely to have access to the data you wish to steal. If this is for access to infrastructure like routers and servers, it's particularly useful if the admin accounts have access to any files you wish to read, unencumbered by user account permissions. Keep this stuff under lock and key, even if it's something as simple as Roboform's encrypted notes. Don't ever even think of sending this file anywhere else into the outside world, you have no idea as to where it will get sent or who it will be shared with. In your scenario as a shared Google spreadsheet, you have no idea who will share it out. Your security model needs to be rethunk as you really have no security when you're sharing passwords like this. Quis custodiet ipsos custodes? |
|||
|
|
|
Use a secure password management system. They are easy to set up and fairly inexpensive. Here's one I've had recommended to me by a colleague: http://www.thycotic.com/ And yes, putting all your passwords into a shared spreadsheet is a bad idea for at least 2 reasons:
|
|||||||
|
