001 Access

The shared password nobody can change

One login everybody uses, and nobody knows what it opens. Why it never gets changed, what a password manager fixes, and what it does not.

Somebody leaves on a Friday. The password to the shared account is in their head, in a spreadsheet, and in a chat message from 2023.

Nobody changes it. Not out of carelessness — because nobody can say what it opens, and changing something that might be wired into a payment job or a nightly export is a worse Monday than leaving it alone.

The shared login was never a decision

One account gets created because a service charges per user and three people need it twice a year. The login gets passed on when somebody joins. Five years later it is in four places, two of them searchable, and the list of what depends on it exists only as things people remember breaking once.

The cost is not the password itself. It is that you cannot answer a question you will eventually be asked: who had access to this, and when did that stop?

What a password manager actually fixes

A password manager is a shared vault. Each person gets their own login to it, and the credentials that genuinely have to be shared are shared inside the tool rather than forwarded in a message.

It fixes the dull half of the problem, which is most of it:

  • Each person has their own login, so removing one person removes one login.
  • Shared items are shared by reference. Nobody needs a copy of their own.
  • The tool records who holds what, so the question above has an answer.

Then somebody leaving is a checkbox rather than an afternoon of archaeology.

What it does not fix

Credentials that live inside the software itself.

A password written into a file goes wherever that file goes — laptops, backups, every copy anybody ever made. No vault reaches those. Only reissuing the value closes it, and that part waits on whichever outside provider issued it, which is why it is the half that gets left unfinished. We wrote up what that looks like in practice, including the part that was still open when we published it.

Treat them as two separate jobs. The vault is an afternoon. The credentials inside the code are a week, most of it spent waiting on somebody else.

The trigger to watch for

None of this is urgent until the week somebody leaves badly, which is exactly why it never gets scheduled.

You do not need a security review to find out where you stand. The next time somebody asks which accounts a departing person could still reach, notice how long it takes to answer. If the answer is “we would have to work that out”, that is the finding, and you have it for free.

If somebody has told you your system isn’t secure, this is usually one of the things they meant. Tell us what you are dealing with and the reply will say honestly whether you need us for it.

Recognise any of this in your own system? Describe what breaks and a person replies within one business day. Free, and a person is what’s at the other end.

Write to us  ·  The work  ·  What things cost  ·  All writing