Skip to main content

Risk Matrix

Every OpenClaw integration that handles credentials has been assessed for security risk. This matrix covers channels, model providers, and plugin packages, evaluating each on risk level, secret scope, rotation difficulty, blast radius, and recommended hardening measures.


Risk Level Distribution

Risk LevelCountDescription
High9Persistent sessions, user-delegated OAuth scopes, or local host access. Compromise has severe consequences.
Medium-High32Service/account API scope or plugin permissions. Broad access, moderate blast radius.
Medium12Provider/channel scoped access. Impact is limited to one integration.
Low1No cloud secret (local runtime only).

Channels

High Risk

These channels involve persistent sessions, local host access, or user-delegated OAuth scopes with high blast radius.

ChannelAuth PatternSecret ScopeBlast RadiusHardening
WhatsAppQR pairing sessionPersistent messaging identity/sessionHighProtect session files at rest, isolate host, use allowlists, re-pair on compromise
SignalLinked account/sessionLocal account/session + host permissionsHighHarden host OS, dedicated service user, strict filesystem permissions, monitor bridge processes
iMessage (legacy)Local macOS permissionsLocal account/session + host permissionsHighHarden host OS, dedicated service user, strict filesystem permissions
TwitchOAuth tokenUser delegated scopes / refresh tokensHighMinimize OAuth scopes, enforce re-consent/revocation playbooks, separate auth profiles
Zalo PersonalQR sessionPersistent messaging identity/sessionHighProtect session files at rest, isolate host, use allowlists, re-pair on compromise

Medium-High Risk

Service or account-level API scopes with moderate-to-high blast radius.

ChannelAuth PatternBlast RadiusHardening
DiscordBot tokenMedium-HighDedicated keys per integration, set rate limits, rotate regularly
LINEChannel token/secretMedium-HighDedicated keys per integration, set rate limits, rotate regularly
MatrixToken/password loginMedium-HighDedicated keys per integration, set rate limits, rotate regularly
MattermostBot token + base URLMedium-HighDedicated keys per integration, set rate limits, rotate regularly
SlackappToken + botTokenMedium-HighDedicated keys per integration, set rate limits, rotate regularly
TelegramBot tokenMedium-HighDedicated keys per integration, set rate limits, rotate regularly
WebChatGateway auth tokenMedium-HighDedicated keys per integration, set rate limits, rotate regularly
Zalo Bot APIApp creds/tokenMedium-HighDedicated keys per integration, set rate limits, rotate regularly

Medium Risk

Provider or channel-scoped access with contained blast radius.

ChannelAuth PatternHardening
BlueBubblesServer credsLeast-privilege, isolate per integration, rotate every 60-90 days
FeishuApp credentialsLeast-privilege, isolate per integration, rotate every 60-90 days
Google ChatService account credentialsLeast-privilege, isolate per integration, rotate every 60-90 days
Microsoft TeamsBot app credentialsLeast-privilege, isolate per integration, rotate every 60-90 days
Nextcloud TalkBot secretLeast-privilege, isolate per integration, rotate every 60-90 days
NostrPrivate keyLeast-privilege, isolate per integration, rotate every 60-90 days
Tlon (Urbit)URL + login codeLeast-privilege, isolate per integration, rotate every 60-90 days

Model Providers

High Risk

OAuth-based providers where compromise exposes user-delegated scopes and refresh tokens.

ProviderAuth PatternBlast RadiusHardening
Google AntigravityOAuth loginHighMinimize scopes, enforce re-consent/revocation, separate auth profiles per agent
Google Gemini CLIOAuth loginHighMinimize scopes, enforce re-consent/revocation, separate auth profiles per agent
OpenAI Code (Codex)OAuth loginHighMinimize scopes, enforce re-consent/revocation, separate auth profiles per agent
Qwen PortalOAuth device-codeHighMinimize scopes, enforce re-consent/revocation, separate auth profiles per agent

Medium-High Risk

API-key-based providers with service/account scope.

ProviderAuth PatternHardening
AnthropicAPI key / setup-tokenDedicated keys, spend/rate limits, rotate regularly
CerebrasAPI keyDedicated keys, spend/rate limits, rotate regularly
GitHub CopilotTokenDedicated keys, spend/rate limits, rotate regularly
Google Gemini (API)API keyDedicated keys, spend/rate limits, rotate regularly
GroqAPI keyDedicated keys, spend/rate limits, rotate regularly
MistralAPI keyDedicated keys, spend/rate limits, rotate regularly
OpenAIAPI keyDedicated keys, spend/rate limits, rotate regularly
OpenCode ZenAPI keyDedicated keys, spend/rate limits, rotate regularly
OpenRouterAPI keyDedicated keys, spend/rate limits, rotate regularly
Vercel AI GatewayAPI keyDedicated keys, spend/rate limits, rotate regularly
xAIAPI keyDedicated keys, spend/rate limits, rotate regularly
Z.AI (GLM)API keyDedicated keys, spend/rate limits, rotate regularly

Medium Risk

ProviderAuth PatternHardening
Amazon BedrockAWS authLeast-privilege IAM, isolate per integration, rotate every 60-90 days
GLM ModelsProvider authLeast-privilege, isolate per integration
Google VertexADC / gcloud authLeast-privilege, isolate per integration, rotate every 60-90 days
MiniMaxProvider authLeast-privilege, isolate per integration
QianfanProvider authLeast-privilege, isolate per integration

Low Risk

ProviderAuth PatternHardening
OllamaNo key (local server)Bind to localhost, patch regularly, restrict local access

Plugin Packages

All published @openclaw/* plugins are assessed at medium-high risk due to their ability to register tools, channels, and hooks that execute with runtime-configured credentials.

Hardening Recommendation
Pin versions and verify provenance
Review permissions and code before installation
Run with least privilege
Audit plugin-registered tools and hooks

Applies to: @openclaw/bluebubbles, @openclaw/diagnostics-otel, @openclaw/discord, @openclaw/feishu, @openclaw/lobster, @openclaw/matrix, @openclaw/msteams, @openclaw/nextcloud-talk, @openclaw/nostr, @openclaw/voice-call, @openclaw/zalo, @openclaw/zalouser.


Universal Hardening Checklist

warning

These recommendations apply across all integration types.

  1. Least privilege: Grant only the scopes and permissions the agent actually needs.
  2. Credential isolation: Use separate credentials per integration and per agent.
  3. Rotation schedule: Rotate API keys every 60-90 days; revoke immediately on compromise.
  4. Audit logging: Enable audit logs for all credential access and API calls.
  5. Host hardening: For local integrations (Signal, iMessage, WhatsApp), harden the host OS with dedicated service users and strict filesystem permissions.
  6. Network restriction: Bind local runtimes (Ollama, Sonos, Hue) to localhost.
  7. Plugin hygiene: Pin plugin versions, verify provenance, review code.
  8. Session protection: For QR-paired sessions (WhatsApp, Zalo Personal), protect session files at rest and re-pair on compromise.

Download

For the complete dataset with all fields (risk profiles, rotation difficulty scores, source documentation links):