Wardengate
Protocol guide

Database access

DBAs and support engineers need production query access — but shared SQL logins and vault checkout workflows produce weak evidence. Wardengate brokers database sessions with identity attribution and inline query capture.

Beyond vault checkout

Checking out a database password proves someone retrieved a secret — not what they queried or changed. Gateway brokering injects credentials at connect time and logs every statement in the session stream, bound to the operator's identity and approval record.

Supported access patterns

Broker sessions for PostgreSQL, MySQL, Microsoft SQL Server, and Oracle through native clients and web SQL consoles. Read-only and read-write grants are separate policy objects. Production write access typically requires JIT approval with shorter TTLs.

Query and command control

Apply deny rules for DDL and destructive DML — DROP, TRUNCATE, DELETE without WHERE — or route matches through approval. Sensitive column masking can redact PII in recorded sessions while still allowing support workflows.

Compliance and SIEM

Session metadata includes database user mapping, client IP, policy version, and approver. Structured exports feed Splunk, Sentinel, and GRC tools. PCI and HIPAA reviewers get query-level evidence without enabling verbose database auditing on every instance.

Operational docs

Ready to deploy? Continue in documentation

Ready to evaluate?

See the platform on your architecture

Walk through gateway brokering, recording, and audit exports in a working session — or start with the interactive demo.