Glossary. Least privilege.
What is least privilege for data access?
Least privilege means each identity holds only the permissions its job needs, on only the data that job touches.
By Dipal Panchal, co-founder and CEO · Updated November 8, 2026
Only the verbs the job needs
Least privilege is the principle that each user, service account or process holds only the permissions its job needs, on only the data that job touches. Unlike need to know, which decides whether an identity may see specific information at all, least privilege also limits what it can do with it: read, change, export, delete or grant. A review that asks only who has access misses the second half, because an over-powered account still looks legitimate.
NIST SP 800-53 control AC-6 puts it as allowing only the access “necessary to accomplish assigned organizational tasks.”
Six identities, sized against their jobs
Identities across four systems, each compared with the one job it does; (restricted) marks restricted data. Last used comes from login auditing, a usage report or a log; where none is on, the cell says not measured.
| Identity | Role or group | Object | Privilege | Last used | Decision |
|---|---|---|---|---|---|
| svc_invoice_loader (SQL Server) | db_datareader, db_datawriter | Every table in the billing database (restricted) | Read and write on all of them | November 6, 2026 | Downgrade: drop both role memberships, then grant INSERT on dbo.Invoices, the one table the job loads |
| reporting_ro (PostgreSQL) | reporting_ro | Every table in the sales schema, including sales.customer_pii (restricted) | SELECT | October 29, 2026 | Narrow: the dashboards need SELECT on the reporting views; the PII table leaves the role |
| app_crm (PostgreSQL login) | Owner of the crm schema and its tables | Every crm table (restricted) | Ownership: ALTER, DROP and GRANT on its own tables | November 7, 2026 | Move ownership to a role that can’t log in; the app reads and writes customer records, so it keeps USAGE and those verbs |
| ds-readers (AWS IAM role) | Data science team | s3://lake/raw/, including raw/hr/ (restricted) | Read on every object under the prefix | Not measured: object-level logging is off | Narrow to raw/sales/, the data the models train on; HR data leaves the grant |
| HR business partners, UK (SharePoint) | Members of the HR site | Investigations library (restricted) | Edit, inherited from the site | October 22, 2026 | Break inheritance: the two investigators keep edit; other members lose access, and site owners keep theirs |
| j.rao@example.com (PostgreSQL), India | finance_ro | finance.gl_entries | SELECT | November 5, 2026 | Excluded from changes: the job is reconciling ledger entries, and SELECT already matches it |
Where excess hides in each system
In SQL Server, the fixed database roles db_datareader and db_datawriter reach every user table in the database, so a loader that needs one table holds them all (row 1). In PostgreSQL, a table’s owner can alter, drop and grant on it whatever its grants say, which is why an application login shouldn’t own its tables or their schema (row 3).
In Amazon S3, a policy on a key prefix covers every object under it, including objects written later (row 4). In SharePoint, a library inherits the site’s permissions until someone breaks inheritance, so every site member can edit a sensitive library (row 5).
Remove the verbs first
Sylox’s suggested order on restricted data: ownership and the right to grant, held by application logins, come off first. Write and delete rights beyond the job go next, then read rights beyond the job, and everything else waits for the next review. That puts row 3 first, rows 1 and 5 next, and rows 2 and 4 after them.
The order needs the data classified first. Dipal Panchal, Sylox’s co-founder and CEO, described the alternative in an April 2026 interview. Without knowing what a warehouse holds, “I will blindly give access to the entire finance database, and I don’t even know whether they really need it.”
Questions only the job’s owner can answer
A privilege review can’t say what the job needs; only the job’s owner can, which is why every decision in the table names a job. It can’t see inside an application either, where the app’s own role model decides which of its users see which rows.
A grant sized correctly in March drifts by October as jobs change, so least privilege needs a check over time as well as a review at grant time.
IRIS links users, service accounts, roles and groups to the sensitive data they can reach, where the source exposes permission data. Capabilities vary by edition.
Admin, owner and write rights on sensitive data flagged: IRIS produces part of this, in supported sources that expose permission data.
Service accounts that can change sensitive tables: IRIS produces part of this, one of the excessive-access rules IRIS applies, in supported sources that expose permission data.
The owner’s decision on what each job needs: Not produced by IRIS.
The narrower grant in the source system: Not produced by IRIS.
Explore access mappingList the write rights on one restricted table
Pick your most sensitive table and list every identity that can change it, own it or grant on it. Include access through nested roles and groups, PUBLIC, and built-in admin roles such as db_owner or a superuser. Write the job beside each one. An identity without a job you can name loses its write rights before any other.
Stale access catches the grants a job no longer uses. For the full review on one database, see how to run a database access review.
Vendor documentation behind the table
- SQL Server documentation: database-level roles (db_datareader, db_datawriter, db_owner), Microsoft Learn. Opened November 8, 2026.
- PostgreSQL documentation: privileges and object ownership, PostgreSQL Global Development Group. Opened November 8, 2026.
- AWS IAM documentation: IAM user groups, Amazon Web Services. Opened November 8, 2026.
The principle in practice
What is data classification?
The step before least privilege: knowing which tables are restricted, so you know where excess matters.
What is data access governance?
Tracing every path to a table, so each path can be tested against the job it serves.
What is stale access?
The next step: grants the job has stopped using, judged against a period you wrote down.
What admins ask about least privilege
No. Least privilege is a principle. Zero trust is a set of principles, and tenet 3 of NIST SP 800-207 says access “should also be granted with the least privileges needed to complete the task.”
Yes. In SQL Server and PostgreSQL the built-in admin roles, db_owner and superuser, can read every table, so give administrators narrower admin roles where the job allows. We’d keep their data access on a separate account (AC-6(2)) points the same way) and log privileged functions under NIST control AC-6(9)).
Count the identities that hold write, owner or grant rights on restricted data, and how many of them have a recorded job and reason. Track both at every review.
Protect your brand. Start with your data.
Pick a supported database with unreviewed service accounts. We’ll show what they reach where permission data is exposed.