Table of contents
Is the handoff ready?
Use these checks before access expands or the first ticket begins.
Question
Ready: One observable row-level security outcome
Needs work: A request to inspect the whole system
Fixture
Ready: two synthetic tenants, ordinary and privileged test roles, overlapping record IDs, and denied write cases
Needs work: Customer data or shared credentials
Evidence
Ready: database role, tenant context, statement, policy, returned row IDs, write result, and denial
Needs work: A pass label without observed values
Approval
Ready: The database and security owners approve role grants, policy changes, and any bypass privilege.
Needs work: The contractor changes production alone
Reproduce the row-level security failure safely
A policy looks correct under an ordinary user but a worker role reads rows outside its tenant. Start with one case that can fail without touching customer records or production infrastructure. Write the expected result, stop condition, and reviewer beside the fixture.
Use two synthetic tenants, ordinary and privileged test roles, overlapping record IDs, and denied write cases. Label every identity and artifact so a reviewer can distinguish test evidence from a live record.
Leave enough evidence for a second person , September 11 review
Capture database role, tenant context, statement, policy, returned row IDs, write result, and denial. Include the source revision and test time. If behavior changes between runs, retain both results.
The database and security owners approve role grants, policy changes, and any bypass privilege. A remote programmer can prepare the fixture, run bounded checks, and explain the result. New policy, privileged access, and release approval stay with the named owner.
Copy-ready brief
Put the operating agreement in writing.
Test one bounded row-level security case against written acceptance rules.
two synthetic tenants, ordinary and privileged test roles, overlapping record IDs, and denied write cases
Record database role, tenant context, statement, policy, returned row IDs, write result, and denial.
The database and security owners approve role grants, policy changes, and any bypass privilege.
Frequently asked questions
What should the first run prove?
It should show the expected row-level security result for one controlled fixture.
What belongs in the handoff?
Include database role, tenant context, statement, policy, returned row IDs, write result, and denial, the source revision, and any untested condition.
Who approves a production change?
The database and security owners approve role grants, policy changes, and any bypass privilege.
Sources
- NIST Secure Software Development Framework
NIST guidance for managing software development risk.
- GitHub pull request reviews
First-party documentation for review and approval.
