Blog. Access governance.
Data owners, not data teams, should sign off on sensitive data
Co-founder and CEO · November 6, 2026 · 3 min read

On this page
Access to sensitive data should be approved by the person accountable for that data in the business. The team that runs a platform can say who has access. Only the data owner can say who should. Data teams make the grants, keep the systems running and know where things are, and they can’t know whether a given person needs a given column to do the job.
The finance analyst shows where the decision belongs
A new analyst joins the finance team and asks for access to the finance database. Their work is reporting: aggregating figures and building summaries. Do they need full client IDs, phone numbers and other personal details? Probably not.
If nobody has classified what is in that database, there is no basis for a narrower grant. The analyst gets the whole database, and nobody knows whether they needed it. The person who knows what the analyst needs is the finance data owner. The data team can make the grant, and the owner should decide it.
| Request | Data touched | Decision | Reason | Decided by | Change made and checked by |
|---|---|---|---|---|---|
| Finance analyst, whole finance database | Client IDs, phone numbers, ledgers | Downgrade to the aggregate views | Reporting needs totals, not client detail | Finance data owner | Database administrator, checked by the security lead |
| Finance analyst, ledger tables | Ledgers | Keep | Needed for month-end reconciliation | Finance data owner | No change needed |
| Payroll clerk, payroll table | Salary and bank details | Time-limit to the pay run | Access needed only on pay days | HR data owner | Database administrator, checked by the security lead |
| Intern, payroll table | Salary and bank details | Revoke | No business need stated | HR data owner | Database administrator, checked by the security lead |
| Contractor, billing archive | Client IDs | Rejected: request withdrawn | Project ended | Finance data owner | Not applicable |
Three roles split the work
Here are the working definitions for this piece. The data owner is accountable for the data in a domain, including its classification and its approved uses. The data steward supports day-to-day governance under the owner. The data custodian handles technical management, including applying the access the owner approved.
NIST’s Cybersecurity Framework 2.0 asks for the same clarity in general terms: roles, responsibilities and authorities for cybersecurity risk management should be established, communicated and understood (GV.RR-02). The owner decides, and the custodian carries it out.
Data-team sign-off turns into a stamp
The IDPro Body of Knowledge describes reviewers who face long lists of access without context. They approve “without proper validation,” a practice it calls ‘rubber-stamping.’ A data team reviewing access to a finance table is in that position by design: it knows the grant and doesn’t know the job.
The same article says privilege owner certification is primarily used for sensitive privileges. For sensitive data, the data owner is that privilege owner.
An owner needs five facts to decide
- What the data is, and how sensitive it is.
- Where it sits, including copies outside the main system.
- Who can reach it today, and how they got that access.
- Why each person or account needs it.
- What changed since the last review.
Without that context an owner signs whatever is in front of them, and the stamp moves from one desk to another. A sign-off record then holds the decision (keep, revoke, downgrade or time-limit), the reason in one line, who decided and when, who made the change and who checked it. The last two lines matter as much as the first, because an approval nobody carries out is a note.
Where the source exposes permission data, IRIS shows who can reach each sensitive dataset and flags broad rights on it.
Reviewers record keep, revoke, downgrade or time-limit for a grant, with a reason; a second approver signs off. The owner decides; the source system makes the change. Capabilities vary by edition.
See access review with IRIS and the access mapping page.
Name one owner for the domain that would hurt most
You don’t need an operating model for the whole company to begin. Start with the data domain that would hurt most if it leaked, such as customer identity data or payroll.
- Name one owner for that domain, by role, and write down what they approve.
- Route new requests for access to that data through the owner, with the context above.
- Ask the owner to review existing access to it, starting with the widest grants.
- Set how often the review repeats, based on how sensitive the data is.
IDPro suggests reviewing high-risk or privileged access more often than low-risk access, usually quarterly. Sensitive data belongs in the higher group. The glossary entry on access certification defines the review, and the database access review guide gives the queries behind step 3.
Sources
- NIST: The NIST Cybersecurity Framework (CSF) 2.0, subcategory GV.RR-02 (February 26, 2024; opened November 9, 2026)
- IDPro Body of Knowledge: Optimizing Access Recertifications (2025; opened November 9, 2026)
Start with a free assessment of one database you choose.
Get a free assessmentProtect your brand. Start with your data.
Book a demo, or start with a free assessment of one database.


