GRC Oversight

QuestDB

Audit QuestDB table durability (WAL), partitioning hygiene, and server configuration through read-only HTTP query endpoints.

Generic connector
Evidence coverage

What this connector audits

Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.

  • WAL durability on user tables
  • Partitioning on time-series tables
  • Server parameters (best-effort, version-dependent)
  • Connector auth configuration
Least privilege

What we need

Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.

Required

  • QuestDB base URL

Optional

  • Username
  • Password(secret credential)
Where this evidence goes

Which frameworks this evidence supports

QuestDB evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.

Don't see your system?

Tell us what you use and what it needs to prove. We'll follow up about adding a connector.

Wire in QuestDB evidence

Get a guided demo, or start by scanning any domain for free.