STUB. This is retrieval infrastructure, not a governance control. The governance-critical part of retrieval is entitlement-aware-rag — read that page. A vector store with no permission enforcement is exactly how a RAG system surfaces documents a user was never allowed to see.

Business objective

The AI’s card catalog: turns documents into searchable “meaning” (embeddings) so the model finds the right snippet to ground its answer. Semantic search and retrieval infrastructure — the index layer between your content-sources and the enterprise-ai-assistant.

When you need it

Day-1 if you are doing RAG; otherwise N/A. It is a build choice (which vector database / search service), not a security control. Many assistants ship their own retrieval and you never touch a standalone vector store. The governance question is not “which vector DB” but “does retrieval respect the user’s permissions” — and that lives in entitlement-aware-rag.

Security role

A sensitive-data store, not a control. A vector index is a copy of your sensitive content, often stripped of the source system’s ACLs — which is the classic RAG failure mode: the permissions lived on the SharePoint folder, not on the embedding. Whether the index re-checks entitlements at query time is the whole game. Lives in the yellow/green zone.

Vendors

Infrastructure choices, not a competitive survey shortlist:

• azure-ai-search — Azure’s managed search/vector service; default for Microsoft-stack RAG, supports security-trimming via document-level ACLs.
• pinecone — managed vector database; popular standalone choice for custom RAG builds.
• weaviate — open-source / managed vector database.
• opensearch — open-source search engine with vector support; the self-hosted option.

Consolidation / M&A dynamics

N/A — mix of cloud-platform services (Azure) and independent infra vendors; not a seed-flagged M&A category.

Adjacent categories

• entitlement-aware-rag — the layer that makes retrieval permission-aware; the part that matters for governance.
• content-sources — the systems of record this index is built from.
• enterprise-ai-assistant — the consumer of retrieved snippets.

Survey

No standalone survey question. Vector database choice is an engineering decision, not a CTO governance survey item. Where it matters, it is captured under entitlement-aware-rag and enterprise-ai-assistant.

Open taxonomy questions

• Like content-sources, this is infra rather than a buying-decision category. Kept as a stub to preserve the layer-cake row; the security-relevant content all routes to entitlement-aware-rag.