The audit logs were clean—too clean. Somewhere in the database, a few silent fields carried more power than any admin login. These were the privilege escalation sensitive columns, and they were the hidden choke points of control.
A privilege escalation sensitive column is any field in your database whose value can grant or expand user permissions. Change it, and an ordinary account might gain admin rights, cross tenant boundaries, or unlock restricted data. Think role, is_admin, account_type, tenant_id, group_id, or permissions_mask. These columns are few, but they are dangerous.
Attackers target them because they bypass the front door. They don’t need to trigger a login vulnerability—they just flip a value in the right place. Internal threats do it for convenience. External threats do it for domination. Without proper controls, one update query is all it takes.
Identifying privilege escalation sensitive columns must be part of every security review. Start with mapping every table that stores authentication or authorization data. Include join tables and reference columns. Trace relationships: a column outside your users table can still dictate access levels.