SurrealDB
Audit SurrealDB namespace/database configuration and table permissions through read-only SurrealQL introspection queries.
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.
- Namespace-level auth methods defined
- Database table permissions (flags open/FULL permissions)
- Root-level user inventory (best-effort)
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.
- SurrealDB base URL
- Namespace
- Database
- Username
- Password(secret credential)
- Token(secret credential)
Required
Optional
Where this evidence goes
Which frameworks this evidence supports
SurrealDB 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 SurrealDB evidence
Get a guided demo, or start by scanning any domain for free.