If you asked whoever looks after your systems, in-house or outsourced, how many people in total hold top-level administrator access to your website and your server, could you have a list with names and email addresses within the hour?
Many owners have never asked, on the grounds that they do not write code, so what would they do with a list of accounts? But top-level access is the master key to the company's vault and front door — the owner certainly does not have to turn the key every day, but the owner cannot afford not to know how many copies of that master key exist and whose pocket each one is in. This is the eleventh piece in our security basics series. Following Security Basics 01|An advisory just landed: how do you know whether it affects you and the two previous pieces on closing accounts for leavers and not sharing accounts, this one gets back a list that should have been yours all along: who has top-level access to your system.
Why a top-level access list gets messier as time passes
No company sets out to make a mess of its permissions. The problem is always the small conveniences that accumulate: a few years ago a marketing agency needed to install a tracking script, so they were given a website administrator account; later a senior employee helped test a new feature, and their account was raised to top level too; then the maintenance supplier changed, and nobody ever deleted the old supplier's engineer account.
The UK's National Cyber Security Centre (NCSC) sets out a clear principle for highly privileged accounts in its 10 Steps to Cyber Security: Identity and access management guidance: an organisation should manage administrator accounts in tiers and use fully privileged top-level administrator accounts (such as a domain administrator, global administrator or cloud administrator) only where genuinely necessary; and it must regularly review all user accounts and systems to find excessive privileges that are no longer needed and revoke them immediately, including temporary accounts created to test a process at the time.
Without a regular look at the list laid out in full, these historical top-level accounts simply go on lying there quietly. The email password of any one of those people leaking is enough for an attacker to take over your entire system as a top-level administrator.
Not just the website back office: the four places that genuinely hold life and death
If you ask your technical people for a top-level access list and they send you one screenshot of the website admin area, three more critical pieces are missing. As set out in Your Engineer Left and the System's Still Running: 12 Things to Get Back First and Don't Let Handover Become a Black Box: A Minimal Documentation Set to Leave Behind, top-level control of a system sits in four places:
- The first: the domain registrar (decides where the address points): whoever can sign in to the registrar can point your company address somewhere else, taking the whole website and the company email down instantly.
- The second: the cloud server console (decides machines and billing): top-level access here can delete an entire server, read every backup, or run up an enormous cloud computing bill.
- The third: the source code repository (decides who can change code and add or remove engineers): as Your Engineer Left and the System's Still Running: 12 Things to Get Back First stresses, you need "administrator rights on the repository, or there is nowhere to put changes and nobody can be added".
- The fourth: the website and business system admin areas (decide who can see user data and change settings): this is the layer people touch most, able to export a whole list, change product prices or alter permission settings.
Three checks an owner can do unaided once the list arrives
You do not need to know how to operate the interface of each technical platform. You only need to ask whoever is responsible for the system to put the currently active administrators for those four places onto a single one-page table — which is exactly one of the five documents listed in Don't Let Handover Become a Black Box: A Minimal Documentation Set to Leave Behind: "who can sign in: which accounts exist, what each can do, and where to get the passwords". With the table in hand, you only have to look at three things:
| What the owner looks for | What the table should show | Ask immediately if you see this |
| 1. Who the top-level owner is | The top-level owner of all four places is tied to the company's own official email address | The top-level owner is a departed engineer's personal email, or the outside supplier's own account |
| 2. Whether you recognise everyone on the list | Every account is identified as a specific current colleague or a supplier inside a current contract | Initialled accounts nobody can name, test accounts, or old suppliers whose projects closed long ago |
| 3. Whether anyone holds top-level access they do not need | Only the people running the underlying operations have top-level server access; admin and marketing have ordinary back-office rights | Colleagues who normally only edit copy or read reports are listed as administrators who could delete the system |
How often should this list be reviewed?
This list does not need looking at weekly. The practical approach is the rhythm suggested in Don't Let Handover Become a Black Box: A Minimal Documentation Set to Leave Behind: turn it over once a quarter, tied to the security updates. Each quarter, when the routine security updates are done, ask whoever is responsible to refresh that one-page who-can-sign-in list at the same time and pass it to you to read; anyone you do not recognise or who is no longer involved gets closed off that same week.
Nerd Technic is a systems software company that came out of custom development, and what we do now is the long-term maintenance of AI systems. Long-term maintenance means security updates run to a fixed rhythm, and when an engagement ends every document and record stays with you. If you cannot produce a top-level access list for your own system right now, a system health check is a place to start: Book a system health check