How fine-grained is DeltaForge access control?

Standard SQL GRANT and REVOKE down to the column. Privilege types are SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, ALTER, and ADMIN. REVOKE takes effect immediately.

Where are storage credentials kept?

In your vaults, never in config files. On desktop, credentials live in the OS Keychain; in production, in Azure Key Vault. The catalog stores references only.

Is traffic between components encrypted?

Yes. All connections between components run over TLS: desktop GUI to control plane, ODBC and ADBC drivers to compute, compute to object storage.

What ends up in the audit log?

Authentication events, every ALLOW and DENY decision, data access, DDL operations, permission changes, and configuration changes. The log exports cleanly to a SIEM.

How are AI agents and automation governed?

Service accounts are named identities for automation, with scoped tokens and explicit tool allow-lists for MCP agent sessions. MCP tool calls land in the same audit log as human queries.

Does DeltaForge send data outside my network?

No. DeltaForge is software you install on your own infrastructure. Your existing VPC isolation, firewall rules, and private endpoints apply directly.

Security: RBAC, Audit Log, Key Management for Delta Lake

Your network, your posture

Because DeltaForge runs on infrastructure you control, it inherits the network controls you already have in place. VPC isolation, firewall rules, private endpoints: these apply to DeltaForge the same way they apply to anything else in your environment.

No external control plane

The control plane runs on your VMs or on-premises. No traffic leaves your network to reach a DeltaForge-managed service. You operate the software; you control the perimeter.

Credentials stay in your vaults

Storage credentials and connection secrets are stored in OS Keychain (for desktop) or Azure Key Vault (for production). The catalog stores references only. The GUI never touches credentials directly; all operations go through the control plane HTTP API.

TLS on every connection

All connections between components (GUI to control plane, ODBC driver to compute node, compute node to object storage) run over TLS. There is no plaintext path.

RBAC: GRANT and REVOKE

Standard SQL access control enforced by the engine before any read or write reaches the data.

Privilege types

SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, ALTER, ADMIN. Granted per object at zone, schema, table, view, or column granularity. REVOKE takes effect immediately.

Roles

Built-in administrative roles plus custom roles you define. Role hierarchy with inheritance. Multiple roles per identity. Grants cascade downward: a schema grant covers all tables in that schema.

Service accounts

Named identities for automation and pipeline runs. Scoped tokens with explicit tool allow-lists for MCP agent sessions. Token expiry and revocation from the control plane.

One enforcement point

The same RBAC engine governs SQL queries, ODBC connections, MCP tool calls, and the desktop GUI. There is no second permission system to keep aligned with the first.

Audit log

Every authorization decision, every query, every schema change: all recorded with identity, timestamp, and outcome.

What is logged

Authentication events, ALLOW and DENY decisions, data access (read/write), DDL operations (CREATE, ALTER, DROP), permission changes (GRANT, REVOKE), and configuration changes.

What each entry contains

Timestamp with timezone, user identity and session, source IP, action and resource, success or failure status, and the SQL or API call that triggered the entry.

Export and retention

Configurable retention policies. Log export for SIEM integration. MCP tool calls from AI agents land in the same log as human queries so you have a unified record of all access.

Security that runs inside your network