Connectors

Connectors are how Shield360 attaches to external systems. Each connector is an atomic integration: one backend, one credential set, and a clear set of actions (test connection, validate signals, bind telemetry, browse memories, and more).

Open Connectors from the sidebar under Settings → Integrations → Connectors (/connectors). Always select the correct project and environment first — connectors belong to the project, not the organization root.

Note

Connectors share one registry model across categories. Data-source connectors route telemetry reads; memory connectors connect Shield360 to agent memory stores; scanner connectors run Trustabl jobs against GitHub repositories; document connectors give agents governed read access to files; identity and device connectors sync people and computers; spend connectors import what AI and cloud vendors actually billed.

Connector categories

Data-source connectors

ClickHouse, Tempo, Loki, Prometheus, and Jaeger — read traces, logs, and metrics with per-signal routing.

Memory connectors

Claude, LangGraph, Mem0, memmesh, and Zep — browse, search, write, and copy agent memories from the Memory page and Otter.

Scanner connectors

Trustabl — scan GitHub repositories for agent SDK, MCP, and policy findings.

Document connectors

SharePoint, OneDrive, OneNote, and Google Drive — files agents may read, granted per folder.

Identity and device connectors

Entra ID and Intune, Okta, Google Workspace, Defender, CrowdStrike, SentinelOne, Jamf, Kandji, Rapid7, and Datadog.

Spend and cloud cost connectors

OpenAI, Anthropic, GitHub Copilot, Cursor, ChatGPT Enterprise, Microsoft 365 Copilot, Azure, AWS, and Google Cloud billing.

Base316 (your customers' billing)

Name your customers, import their MRR for margin, and push AI usage per customer to a Base316 meter.

Setup guides

Every connector form in the app has a How to set this up link that opens the matching guide below, and a short What you’ll need checklist. Each guide lists the exact permissions, scopes, or roles Shield360 uses — nothing more — and how to test the connection.

Category	Connector	Setup guide
Data source	ClickHouse	Set up ClickHouse
Data source	Grafana Tempo	Set up Grafana Tempo
Data source	Grafana Loki	Set up Grafana Loki
Data source	Prometheus	Set up Prometheus
Data source	Jaeger	Add a Jaeger connector
Memory	Claude	Set up Claude memory
Memory	Mem0	Set up Mem0
Memory	memmesh	Set up memmesh
Memory	Zep	Set up Zep
Memory	LangGraph	Set up LangGraph
Scanner	Trustabl	Add a Trustabl scanner
Sensitive data	Built-in detector	Built-in detector
Documents	SharePoint	SharePoint
Documents	OneDrive	OneDrive
Documents	OneNote	OneNote
Documents	Google Drive	Google Drive
Identity	Microsoft Entra ID + Intune	Microsoft Entra ID
Identity	Okta	Okta
Identity	Google Workspace	Google Workspace
Devices	Microsoft Defender for Endpoint	Microsoft Defender for Endpoint
Devices	CrowdStrike Falcon	CrowdStrike Falcon
Devices	SentinelOne	SentinelOne
Devices	Jamf Pro	Jamf Pro
Devices	Kandji	Kandji
Devices	Rapid7 InsightVM	Rapid7 InsightVM
Devices	Datadog	Datadog
AI spend	OpenAI API costs	OpenAI API costs
AI spend	Anthropic API costs	Anthropic API costs
AI spend limits and costs	Claude Enterprise	Claude Enterprise spend limits and costs
AI spend limits	LiteLLM budgets	LiteLLM budgets
AI spend limits	OpenRouter key limits	OpenRouter key limits
AI spend	GitHub Copilot	GitHub Copilot
AI spend	Cursor	Cursor
AI spend	ChatGPT Enterprise	ChatGPT Enterprise
AI spend	Microsoft 365 Copilot	Microsoft 365 Copilot
AI spend	Azure OpenAI	Azure OpenAI
AI spend	Amazon Bedrock	Amazon Bedrock
Cloud costs	AWS (all services)	AWS Cost Explorer
Cloud costs	Azure (all services)	Azure Cost Management
Cloud costs	Google Cloud	Google Cloud billing export

Mental model

flowchart LR
  subgraph org [Organisation]
    proj[Project]
  end
  subgraph env [Environment]
    bindT[traces binding]
    bindL[logs binding]
    bindM[metrics binding]
    mem[memory connectors]
    scan[scanner connectors]
  end
  proj --> env
  bindT --> DS1[Tempo]
  bindL --> DS2[Loki]
  bindM --> DS3[Prometheus]
  mem --> M1[Mem0]
  mem --> M2[Zep]
  mem --> M3[LangGraph]
  scan --> S1[Trustabl]

• Atomic connectors — one backend per connector instance. Never a multi-backend blob.
• Project scope — connectors are created on a project and partitioned by environment.
• Data-source bindings — traces, logs, and metrics bind independently. See Signal routing.
• Memory usage — memory connectors power the Memory page (/memory) and Otter memory tools; they do not replace telemetry routing.
• Scanner usage — scanner connectors power the Scanner page (/scanner) and Otter get_scanner_findings; they do not replace telemetry routing.

Common actions

Action	Data-source	Memory	Scanner
Add / edit connector	Yes	Yes	Yes
Store credentials	Vault (ClickHouse) or connector secret	Encrypted on connector	Encrypted on connector
Health check / test connection	Yes	Yes	Yes (CLI installed)
Validate AI signal	Yes (gen_ai.* markers)	—	—
Bind signal	traces / logs / metrics	—	—
Browse / search / write memories	—	Yes (capability-dependent)	—
Run scan / list findings	—	—	Yes

Enterprise audit logs record connector create, update, delete, test, bind, and unbind events. RBAC permissions are connectors:read|create|update|delete|test|bind (owner/admin by default).

Related

Organization overview

How projects and environments scope connectors.

Signal routing

Bind traces, logs, and metrics to data-source connectors.

Database Config

ClickHouse app store and built-in connector.

Environments

Partition connectors by environment.