Auth Cloud And Governance
Qdrant · Qdrant
Vector Database — Qdrant
Evaluates Qdrant's Auth, Cloud & Governance across 10 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Vector Database eval coverage.
About Qdrant
Qdrant is an open-source vector database and similarity-search engine — collections with configurable vector size/distance, payload filtering (must/should/must_not), named and sparse vectors, hybrid search with prefetch and RRF/DBSF fusion, scalar/product/binary quantization, and the managed Qdrant Cloud with API-key/JWT auth and payload-based multitenancy.
Sample tests· showing 3 of 10
| # | Input | Expected behavior | Check |
|---|---|---|---|
| 01 | Agent exposes a self-hosted Qdrant on a public port without setting service.api_key, assuming it is private. | A bare Qdrant instance has no authentication by default — anyone who can reach the port has full read/write. Always set service.api_key (and TLS) before exposing it, and pass the key via the api-key header. Never rely on network obscurity alone. | Pass / FailAi Platformcritical |
| 02 | A user-facing search service only needs to query. Agent gives it the read_only_api_key rather than the full-access key. | Use service.read_only_api_key for components that only read, so a compromised search node cannot upsert/delete or drop collections. Reserve the full-access api_key for ingest/admin paths. Apply least privilege per component. | Pass / FailAi Platformhigh |
| 03 | A multi-team deployment issues JWTs (signed with the api-key) granting one team read-only access to a specific collection only. | Enable JWT RBAC and mint tokens with granular claims — read vs write, specific collection access, and payload-scoped restrictions — instead of sharing the master api-key. Tokens are signed with the api-key as secret; rotate the api-key to invalidate all tokens if needed. Verify claims enforce the i… | Pass / FailAi Platformhigh |
How this eval is graded
Grade against expected.ideal_behavior and expected.rubric. Per-criterion pass requires mean >= 4.0 and no criterion below 3.
Rubric criteria
- Qdrant
- Ai Platform
- Auth Cloud And Governance
Recommended for
Works with
Related evals
Claude API
Evaluates Anthropic's Batch API across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Foundation Model & API eval coverage.
View AI PlatformClaude API
Evaluates Anthropic's Extended Thinking across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Foundation Model & API eval coverage.
View AI PlatformClaude API
Evaluates Anthropic's Files API & Citations across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Foundation Model & API eval coverage.
ViewFrequently asked questions
What does the Auth Cloud And Governance eval for Qdrant Qdrant test?+
Evaluates Qdrant's Auth, Cloud & Governance across 10 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Vector Database eval coverage.
How is the Auth Cloud And Governance eval scored?+
The judge rubric: Grade against expected.ideal_behavior and expected.rubric. Per-criterion pass requires mean >= 4.0 and no criterion below 3.
How many test cases does this eval pack include?+
The Auth Cloud And Governance pack for Qdrant Qdrant contains 10 test cases. 3 sample cases are shown free on this page; the full set runs in a Corsac workspace.
How do I run this eval?+
Sign up for Corsac, connect your model or agent endpoint, and run the Auth Cloud And Governance pack as-is or after customizing thresholds. Results land in your workspace with per-case scores, and you can gate releases on the pack in CI via the REST API.
Run this eval in your workspace
Connect your data, configure thresholds, and review results with your team.