Connect sources to KAIDAN

A source is a system that can supply event metadata relevant to an AI or LLM investigation. Examples include a model runtime, guardrail, cloud audit log, vector database, observability tool, or SIEM.

KAIDAN has 16 signed compatibility packages today. Every package is compatible but unverified, not vendor-certified. Some have authenticated self-hosted field receipts; a self-hosted receipt does not prove a vendor-managed service.

Before connecting any source

Ask the source owner to answer:

1. Why is this source needed for incident response?
2. Who owns it?
3. What exact events and fields will be read?
4. What content and identifiers are excluded?
5. What is the least-privilege permission?
6. Where will the credential live?
7. Which network destination is required?
8. How will success, outage, throttling, replay, and schema change be tested?
9. What is the source’s maximum visibility?
10. How will access be removed and the credential rotated?

If any answer is unknown, record the gap and defer the connection.

Visibility levels in ordinary language

• L0 — discovery: KAIDAN can show that a product or runtime appears to exist.
• L1 — activity: KAIDAN can show approved activity or audit metadata.
• L2 — correlation: KAIDAN can connect privacy-reduced events across a request or trace when the source supports it.
• Higher semantic claims require stronger, separately approved evidence. A transport alone does not create visibility.

The screen must never imply L2 merely because a connector uses a modern protocol.

Current source packages

Package	Source family	Maximum designed visibility	Important limit
aws-ai-audit	AWS Bedrock and CloudTrail	L1	Provider field receipt remains separate
azure-ai-audit	Microsoft AI diagnostics	L1	Field receipt remains separate
datadog-agent-observability	Datadog Agent Observability	L2	Managed field receipt remains separate
elasticsearch-vector-audit	Elasticsearch audit logs	L1	Self-hosted proof is not Elastic Cloud certification
google-ai-audit	Vertex AI audit and pipeline logs	L1	Provider field receipt remains separate
google-model-armor	Model Armor logs	L2	Provider field receipt remains separate
kafka-ocsf	OCSF events transported by Kafka	L1	Transported assertions remain source assertions
milvus-audit	Milvus access logs	L2	Native logs prove L1; L2 needs approved correlation
ocsf-https	Generic OCSF HTTPS source	L1	Semantics limited to the accepted OCSF record
opensearch-vector-audit	OpenSearch audit logs	L1	Managed-service proof is separate
otlp-genai	OpenTelemetry GenAI spans	L2	Only approved privacy-reduced attributes
pgvector-audit	Instrumented pgvector retrieval	L2	No SQL, vectors, values, or documents
pinecone-audit	Pinecone control-plane audit	L1	Control-plane logs do not prove query semantics
prisma-airs	Prisma AIRS decisions	L2	Detector decisions are source assertions
qdrant-audit	Qdrant audit activity	L2	Native logs prove L1; L2 needs approved correlation
weaviate-audit	Weaviate authorization logs	L2	Native logs prove L1; L2 needs approved correlation

Check the KAIDAN console’s signed catalog for the exact installed package version and current proof state. Do not rely on this documentation page as a live connector-health display.

Choose a delivery boundary

External gRPC adapter

Use this for a dedicated source adapter. The adapter runs as a separate mutual-TLS workload. The vendor credential stays with the adapter and is not placed in the KAIDAN relay.

HTTPS pull

KAIDAN polls a bounded authenticated HTTPS source, tracks a checkpoint, and accepts only a named normalizer’s schema.

HTTPS webhook

The source pushes a bounded signed request. Verify authentication, replay protection, timestamp bounds, schema, rate handling, and dead-letter recovery.

Direct telemetry

Approved SDK or OpenTelemetry metadata can be observed directly. Instrumentation must allowlist fields and remove prompt, response, file, secret, and customer-content values before transmission.

Create the credential safely

1. Ask the source owner to create a dedicated service identity.
2. Grant only the documented read actions.
3. Restrict the identity to the required account, project, tenant, topic, or audit endpoint.
4. Set an expiration or rotation date.
5. Store the secret, certificate, or key in the approved secret manager.
6. Put only the secret reference in the setup plan.
7. Deny the credential to the browser and to components that do not need it.
8. Record the owner and emergency revocation procedure.

Never paste a token into Briard-AI, a support ticket, chat, source control, a deployment values file, or a command line.

Test the source

A credible source test covers:

• unauthenticated access is denied;
• authenticated collection succeeds;
• only allowlisted fields cross the boundary;
• pagination or checkpoint restart resumes correctly;
• replay is idempotent;
• throttling and outage backoff recover;
• schema drift fails closed;
• rejected records enter a controlled dead-letter path;
• an authorized replay resolves the rejected record;
• credential rotation works and the retired credential is denied;
• privacy canaries are rejected; and
• KAIDAN displays the correct capability ceiling and evidence gaps.

Retain the signed test receipt. “Connected” means this test passed against the intended environment; it does not mean the provider certified KAIDAN.

Understand operational states

A source can be:

• proposed;
• awaiting owner approval;
• configured;
• testing;
• healthy;
• degraded;
• failed;
• disabled; or
• revoked.

A last-success timestamp is not enough. Review checkpoint age, error class, backoff, dead-letter count, schema version, credential age, and the visibility ceiling.

Remove a source

1. Disable intake.
2. Confirm no new events arrive.
3. Revoke the source credential.
4. Remove the secret-manager entry according to policy.
5. Record the final checkpoint and revocation receipt.
6. Update the setup plan and expected visibility.
7. Preserve prior evidence according to retention and legal-hold rules.
8. Tell investigators that future coverage changed.

Removing a connector does not rewrite prior custody history.