Our own access review's top row was me, since March 2023, reason column blank. Privilege creep is incident sediment — here's the sudo -l career audit, the break-glass script with a witness and a sunset, the privilege diary, and the witnessed self-review.
The question came from our own access review: list every identity with standing production admin. The sheet came back short, which felt like success, until I read the top row.
Me. Since March 2023. Reason column: blank.
I remembered the weekend instantly — the incident, the 2 a.m. scramble, "just grant me admin for now, we'll clean up after." We cleaned up after. Everyone else got revoked at the Monday postmortem; me I forgot, because revoking yourself feels like locking your keys inside the house. For three years, the most overprivileged account in the company was the one writing the security posts.
Privilege creep is incident sediment
Every emergency deposits a layer of access on the people who show up. The incident grants admin; the migration grants DB owner; the stuck pipeline grants CI admin "to rerun one job"; the domain move grants the DNS seat. Each grant is correct at the moment it's made — that's what makes it dangerous. Correctness at grant time is not correctness at rest.
And the access review skips one employee by construction: the reviewer. I reviewed teams, contractors, bots. I never looked for my own name, because my own access felt like equipment, not privilege.
The career audit (sudo -l, but for your life)
# machine-level: what does my everyday account actually hold?
sudo -l # sudoers, expanded — the fossil record
id # groups = invisible privilege nobody reviews
ls -la ~/.ssh/ && cat ~/.ssh/config # keys + habitual hops
# cloud-level: which contexts exist, and what am I right now?
krova context list # every saved scope I ever created
krova whoami # current context, space, key — the mirror
Then the SaaS layer, by hand: billing seats, DNS providers, CI admin, registry orgs — every "granted for one thing" seat, cross-referenced against incidents. My list: prod admin (2023 incident, used four times since), billing admin ("check one invoice," 2024), the DNS wheel from a migration I don't touch quarterly, CI admin for one rerun eighteen months ago, and root on a box that "was staging back then."
Five standing elevations. One surviving justification. Four fossils of Fridays.
Break-glass with a witness and a sunset
My everyday account reads, deploys, debugs. Destructive actions live behind an elevation I fetch deliberately:
#!/bin/bash
# break-glass.sh <reason> — speed with a witness, not speed with amnesia
set -euo pipefail
TICKET=$(itsm create "break-glass: $1" --priority sev3)
page oncall "break-glass opened by $USER — $TICKET" # use is loud, always
krova auth login --api-key "$(vault kv get -field=key sec/glass)" \
--context glass # destructive scope, fetched not worn
( sleep 4h && krova context delete glass \
&& itsm close "$TICKET" "auto-sunset" ) & # the glass closes itself
A ceremony you can't skip is the only ceremony that works at 2 a.m. — because it's the system doing the remembering, not you.
The privilege diary + witnessed review
Every standing right I keep gets one row, reviewed quarterly out loud, with a second human in the room:
| right | opens | why standing | incident that justifies again |
|------------------|----------------|---------------------|-------------------------------|
| on-call prod ro | dashboards, ssh| rotation needs 3am | any sev1 |
| billing read | invoices | finance asks weekly | none — revoke candidate |
Solo self-review is a mirror; witnessed self-review is an audit. A right that can't write its own biography gets revoked. And project ends revoke their seats in the same sitting — graveyard rules, people-shaped: when a project dies, its grants die with it.
On the platform side, the friction is architectural: my everyday Krova context is scoped to create, wake, and SSH; destructive operations need the glass key above. Keys are scoped per space with idempotency on mutations, so even automation runs on a leash. The architecture enforces the habit my memory never could.
The honest part
- Break-glass has a real cost mid-incident. When everything is on fire, a ceremony is seconds you don't have — which is why the glass pages instead of blocking.
- Some standing access is honest. On-call needs keys at 3 a.m.; pretending otherwise writes checks the incident will cash. The goal isn't zero privilege — it's explained privilege, every line with a biography.
- This isn't confession as marketing. Your sheet has the same top row, wearing your name, with a blank reason column. That's the point of publishing mine.
Audit the auditor
Privilege doesn't creep because people are careless; it creeps because emergencies are generous, memories are short, and the one account nobody schedules for review is the one holding the review.
Go run sudo -l on your own career. Not the team's — yours. Count how many biographies come back empty. Mine was four out of five; the fifth was the incident I'm still cleaning up after: this one.
Confession booth: what's your oldest standing elevation, and which bad weekend born it? Ours includes a billing seat for an invoice nobody can find and a DNS wheel I haven't touched in quarters. Comments open; the mirror is facing you.
I'm Dhruv Malaviya, CEO of Krova Cloud, Shoptimity & DraftRank: API keys are scoped per space with idempotency on mutations, so automation acts without standing crown-jewel credentials. A scoped key still opens exactly what it opens — scoping is a leash, not a conscience.
Top comments (2)
The sudo -l career audit framing really landed.
Glad it landed and it came from a real moment: the top row of our own access review was me, reason column blank. Every grant was correct on the day it was made and wrong by default ever since; sudo -l just made the sediment legible.
Did you run the audit on yourself? Mine turned up a billing seat for an invoice nobody can find anymore.😄