Picture a mid-sized logistics firm in Coimbatore. Call it Kaveri Freight; the company and everyone in it are invented for this walkthrough. Its IT team of six shares a single domain administrator password, kept in a spreadsheet on a shared drive called “IT_misc”. Two people who knew it have since left. A backup tool runs under an account called svc-backup whose password was set in 2019 and never changed, because nobody dares to break the nightly job.

Nothing has gone wrong yet. That is the uncomfortable part. Let us walk through what happens when something does, and what privileged access management (PAM) would change at each step.

Day one: a clerk opens an attachment

A billing clerk’s laptop is compromised. The clerk has ordinary rights, so the attacker can read what the clerk can read and not much more. Annoying, but contained. Then the attacker looks around. On that laptop, a helpdesk engineer once logged in to fix a printer driver, using a domain admin account. Windows kept the engineer’s credential material in memory or cached it. The attacker lifts it.

The attacker is now a domain admin without breaking any password. This is the heart of the problem: privileged credentials leave traces wherever they are used, so every machine an admin touches becomes part of the path to the top.

The PAM answer is separation. Admins get a normal account for email and browsing and a different account used only for administrative tasks, and those admin accounts are barred from logging in to ordinary workstations at all. Better still, administration is done from dedicated, locked-down machines, often called privileged access workstations. If the admin credential never touches the clerk’s laptop, it cannot be stolen from there.

Day three: the quiet service account

Suppose the attacker did not find an admin credential. They might instead go after svc-backup. Service accounts are attractive because their passwords never change, nobody gets a login alert about them, they often have far more rights than needed (backup software typically wants to read everything), and no human notices when they behave oddly.

PAM tools tackle this with a vault. The password for the account lives in the vault, is long and random, and is rotated automatically on a schedule, with the application fetching it as needed rather than a person knowing it. Where the platform supports it, managed service accounts or workload identities remove the stored password entirely. Rights get trimmed too: backup needs read access to data, not the ability to create new users.

The vendor who needs access for an hour

Kaveri’s ERP vendor needs to log in to a server to apply a fix. Today, someone gives them a VPN account and a server password, and both stay active for the next two years. The PAM pattern is called just-in-time access. The vendor requests access, a named internal person approves, a time-limited credential is issued, the session goes through a gateway that records what was typed or clicked, and the access expires by itself. Nothing standing, nothing forgotten.

The same idea applies to your own staff. A database administrator does not need production superuser rights at 3 p.m. on a Tuesday for routine work. They elevate when a task requires it, with a reason attached, and drop back after. The security benefit is a smaller window; the audit benefit is a clear trail of who did what and why.

Pieces of a PAM programme

  • An inventory of privileged accounts: human admins, service accounts, shared accounts, cloud root or owner accounts, and API keys. You cannot protect what you have not listed, and the first inventory is usually humbling.
  • A credential vault with rotation, and a way to break glass: an emergency account whose use triggers an alert to several people.
  • Session brokering and recording for the most sensitive systems.
  • Least privilege and time limits as defaults, not favours.
  • Strong authentication, ideally phishing-resistant, on every privileged login.
  • Regular reviews, because roles drift and people change teams.

Honest limits

PAM products are expensive and a vault does not fix a culture where everyone wants permanent admin “just in case”. Start small. Remove shared passwords, move the ten most powerful accounts into a vault, and make the cloud owner account unusable for daily work. A spreadsheet-replacement that is actually used beats a fully licensed platform that is half deployed.

Also, PAM reduces damage; it does not prevent the initial compromise. It is the difference between a clerk’s laptop being a bad afternoon and being the end of the company’s year. Kaveri Freight, after some uncomfortable meetings, would rank “separate admin accounts” and “rotate the old service account” as the two jobs for next week, and neither costs a rupee in licences.

Figures and names in the examples are illustrative.

Leave a Reply

Trending