Fichaloto

Blog Security

The access list nobody maintains and everybody needs

8 min read

The uncomfortable question is not what they had access to. It is how they could still get back in, and almost nobody can answer that with confidence.

The scene

Someone who has been working with you for eighteen months moves on. You sit down to close their access and start pulling the thread. Email, yes. Project tool, yes. Hosting panel — hang on. Did they get FTP? Probably, for that deployment thing. Was the design tool account theirs or the shared one? And what about the token they generated for that script?

Fifteen minutes in you realise you are not revoking access. You are trying to reconstruct eighteen months of decisions made on the fly, most of them over chat, none of them written down.

This is not a story about disorganised firms. It is the default state of any organisation that did not build the register before it needed one, because access gets granted in a hurry and forgotten in the same minute.

Four layers, and which one bites

A person's access does not live in one place, and that is exactly why it cannot be closed in one action.

  • Corporate identity. Email and everything federated behind it. This is the easy layer: disable the account and it cascades. It is also the only one everybody remembers.
  • Local accounts in third-party tools. Services they signed up to with their work address but which hold their own password. Killing the mailbox does not close these — it only stops password recovery, which is not the same thing.
  • Technical credentials. FTP, hosting panels, API keys, database logins, SSH keys. These hang off no identity, expire on their own never, and appear in no user list anywhere. This is the layer that bites.
  • Shared accounts. The single login four people use. Revoking here means rotating the password and telling the other three, which is why it gets postponed indefinitely.

Why contractors make it worse

With an employee there is at least a process: a leaving date, someone in HR, a person to notify. With a contractor there is none of that. The engagement does not end on a particular day — it fades. You run out of work, three months pass, and their access sits exactly as it did on day one.

And it is precisely the most technical, hardest-to-reconstruct access, because it was granted piece by piece as needed, with no plan behind it.

The extreme case, which happens more often than people admit, is the supplier relationship that ended badly. At that point the question stops being administrative.

The register that actually works

The fix is not a longer exit checklist. A checklist gets filled in from memory and inherits the same flaw. What works is recording access at the moment you grant it, when it costs thirty seconds, instead of reconstructing it at the end, when it costs an afternoon and comes out wrong.

Five fields are enough: which system, what kind of credential, who authorised it, when, and until when. The fifth is the one almost nobody fills in and the one that saves the most. Access with an expiry date closes itself, or at least warns you. Open-ended access is the access still live three years later.

And it has to sit alongside the person's record, not in a separate document. An access inventory in a standalone sheet stops being updated in month two. On the record of someone you work with, you see it every time you open the record.

Frequently asked questions

Does single sign-on not solve this?

It solves the first layer and part of the second, which is genuinely a lot. It does not touch technical credentials or shared accounts, because those never pass through a federated identity. Centralising identity shrinks the problem; it does not close it.

How often should it be reviewed?

A quarterly review of live access is enough for most small firms, and takes under half an hour if the register is current. What does not work is reviewing only when somebody leaves — by then you are reconstructing again.

Is this the same as an audit log?

No. An audit log records what was done inside the product: who changed what and when. An access register records which doors are open right now, facing outward. They complement each other, but they answer different questions and neither substitutes for the other.

All of this is built into Fichaloto. See how it works.

Keep reading