Skip to content

Verified cloud accounts across 14 providers

Why root credentials should never be used for daily work

The top level account credential is a single point of total failure. Using it routinely removes the only clean signal you have that something is wrong.

Every cloud account has one identity that sits above the permission system rather than inside it. Depending on the provider it is called the root user, the account owner or the global administrator. What they share is that the usual controls do not fully apply to it: it can change billing, alter or remove other identities, and in most cases close the account entirely.

Three reasons routine use is a problem

Permissions cannot be reduced

For normal identities, the answer to “this process only needs to read one storage bucket” is a narrow policy. For the top level credential there is no such answer, because it is not constrained by policy in the ordinary way. Any task performed with it is performed with the ability to do everything else as well.

Attribution disappears

If several people share one credential, the audit log records the credential, not the person. Every entry becomes ambiguous at exactly the moment ambiguity is most expensive. Named identities per person, or short lived credentials issued through an identity provider, keep the log answerable.

You lose a free alarm

This is the benefit most teams overlook. If the top level credential is genuinely unused, then any use of it is anomalous by definition, and an alert on it is a high quality signal with almost no false positives. Use it daily and that signal is gone permanently, buried in ordinary activity.

What it should be reserved for

A small set of tasks genuinely requires it, and they are all rare: initial account setup, changing billing or payment details, modifying account level settings that no other identity can reach, recovering access when the normal identity path is broken, and closing the account. Everything else, including all deployment and operational work, should run as something narrower.

Handling it well

  • Store it in a vault, not a person’s head or notes. A shared secrets manager with access logging is the right home.
  • Enable multi-factor authentication, and treat the second factor carefully. A hardware key in a known physical location, or a software token in the vault, both work. What matters is that it is not tied to one individual’s personal device.
  • Alert on its use. Send a notification on every sign-in and every action taken by it.
  • Remove any access keys attached to it. Programmatic access at this level is almost never needed and is a standing risk.
  • Record the recovery path. Who can reach the recovery email, who holds the second factor, and what happens if that person is unavailable.

When an account changes hands

If an account was created by someone other than its current operator, the top level credential must be rotated before the account is trusted, along with its password, its multi-factor configuration and its recovery contacts. Until that is done, the account’s security depends on a party you cannot audit. This is the single most important step when taking over any existing cloud account, and it should happen before the first workload is deployed rather than after.

Chat on Telegram
Scroll to Top