Guides
Jun 4, 2026
Just-in-Time Database Access
Grant database access on request, expire it automatically
What standing database access costs you
The access never goes away
A grant made for one task outlives it by months. Permissions pile up, nobody remembers who has what, and the attack surface is every credential ever issued — not the few in use today.
Shared credentials, no attribution
When a team shares `admin@prod`, every query is untraceable. An auditor asks who ran a destructive statement and the honest answer is 'anyone on the team'.
Access requests stall in tickets
Getting into a database means a ticket, a Slack thread, and a wait. Developers are blocked, the DBA is the bottleneck, and the workaround is to over-grant 'just in case'.
How Bytebase grants access just in time
Request, approve, expire
Access is issued for a specific database, a specific reason, and a bounded window — then revoked automatically when the window closes.
Self-service request
A developer asks for access to a database in-product, with a reason and a duration — no ticket queue, no shared password.
Approval that fits the risk
A peer, a DBA, or an automated policy grants it; high-risk targets route to a human, routine ones can auto-approve.
Auto-expiring by default
The grant ends on its own when the window closes, so access reflects what's in use now, not what was ever issued.
Scoped to the task, not the whole database
Each grant is least-privilege — bounded to the databases, schemas, and actions a task needs, with masking and review still in force.
Least-privilege scope
Grant query, export, or change rights on specific databases and tables — not blanket access to the instance.
Masking still applies
Sensitive columns stay masked under a temporary grant, so on-demand access never means raw PII in the result grid.
Break-glass with a trail
Emergency access is possible, but it routes through approval and lands in the audit log — never a silent backdoor.
Every grant on the record
Who asked, who approved, what they could touch, and when it expired — captured as an audit trail you can hand an auditor.
Full request-to-revoke trail
Each access lifecycle is logged end to end: request, reason, approver, scope, and expiry.
Mapped to frameworks
Least privilege and time-bound access are the controls SOC 2, HIPAA, and ISO 27001 check for.
Tied to a real identity
Access binds to an SSO identity, so a grant names the person — never a shared service account.
One access workflow, controls for every team
Integrations
Designed to integrate across modern enterprise environments
Bytebase connects to databases, developer tooling, and collaboration platforms to fit naturally into complex, multi-tool enterprise ecosystems.
Resources
