Wazuh-MCP-Server MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

48 tools across alerts, agents, vulnerabilities, active response, compliance
Output sanitization — redacts credentials before they reach the LLM
Rate limiting + circuit breakers to protect Wazuh Manager
RBAC per tool; audit logs for destructive actions
Deploys via Docker Compose; supports Wazuh 4.8–4.14

라이브 데모

실제 사용 모습

wazuh.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "wazuh": {
      "command": "uvx",
      "args": [
        "Wazuh-MCP-Server"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "wazuh": {
      "command": "uvx",
      "args": [
        "Wazuh-MCP-Server"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "wazuh": {
      "command": "uvx",
      "args": [
        "Wazuh-MCP-Server"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "wazuh": {
      "command": "uvx",
      "args": [
        "Wazuh-MCP-Server"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "wazuh",
      "command": "uvx",
      "args": [
        "Wazuh-MCP-Server"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "wazuh": {
      "command": {
        "path": "uvx",
        "args": [
          "Wazuh-MCP-Server"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add wazuh -- uvx Wazuh-MCP-Server

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: Wazuh-MCP-Server

Triage overnight alerts in 10 minutes instead of 2 hours

👤 SOC analysts ⏱ ~20 min advanced

언제 쓸까: Shift start. Hundreds of alerts overnight. You need to find the real ones without reading every row.

사전 조건

Wazuh Manager API creds — Wazuh UI > API credentials

흐름

Summarize

For last 12 hours: group alerts by rule group, count severity 10+ per group, top 5 agents with most high-sev alerts.✓ 복사됨

→ Ranked summary
Investigate

For top agent, pull the 10 most recent high-sev alerts with full details.✓ 복사됨

→ Detailed events
Determine action

Based on these events, is this a true positive? If yes, propose response: isolate agent / disable account / create ticket.✓ 복사됨

→ Verdict + action plan

결과: Faster MTTD/MTTR without more eyeballs.

함정

Auto-triggering active response before confirming — Keep active response tools behind a confirmation gate

Weekly vulnerability posture report

👤 Security managers ⏱ ~30 min intermediate

언제 쓸까: Friday report for leadership. How many CVEs open? Where? Trend vs last week?

흐름

Pull vulnerabilities

From Wazuh vulnerability module: total open CVEs by severity, top 10 agents by critical CVE count.✓ 복사됨

→ Numbers + top agents
Compare to last week

Compare counts to last Friday's report [paste]. What improved, what regressed?✓ 복사됨

→ Delta analysis
Prioritize

List the 5 critical CVEs affecting most hosts that should be patched this weekend.✓ 복사됨

→ Actionable patch list

결과: Board-ready security posture summary.

함정

Vuln data only as fresh as last scan — Check scan timestamps before drawing conclusions

함께 쓰기: notion

Isolate a compromised host on confirmation

👤 SOC on-call ⏱ ~10 min advanced

언제 쓸까: Alert fires: unambiguous malware on endpoint. You need to isolate fast.

흐름

Confirm scope

For agent 'ws-4412': show active processes with parent PID, recent listening ports, and last 20 alerts. Is this clearly compromised?✓ 복사됨

→ Risk assessment
Isolate

Isolate agent ws-4412 via active response. Require my explicit confirm first.✓ 복사됨

→ Confirmation prompt, then isolation + audit log entry

결과: Compromised host isolated within minutes.

함정

False-positive isolation of prod server — Double-check agent ID and classification before confirming; keep an out-of-band way to re-enable

조합

다른 MCP와 조합해 10배 효율

wazuh + notion

Weekly security digest to exec

Compose a weekly Wazuh summary and create a Notion page in 'Security Weekly'.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
list_alerts	filter: obj, from, to, limit	Investigate by time/severity/rule	1 API call
get_agent	agent_id	Profile a specific endpoint	1 API call
list_vulnerabilities	agent_id?, severity?	Vuln posture checks	1 API call
trigger_active_response	agent_id, command, arguments?	Isolate / kill process / disable account — destructive; confirm	1 API call + physical effect
compliance_report	framework: 'pci'\|'hipaa'\|'nist', scope	Audit readiness	1 API call

비용 및 제한

운영 비용

API 쿼터: Bounded by Wazuh Manager API limits
호출당 토큰: Alert listings can be huge — always filter by time + severity
금액: Free. Wazuh itself is open-source.
팁: Use limit aggressively. Don't list a week's alerts without grouping.

보안

권한, 시크릿, 파급범위

최소 스코프: Wazuh API user scoped read-only for inspection; elevate for active response

자격 증명 저장: Wazuh API creds in env or Docker secrets

데이터 외부 송신: Alert/event data goes to your LLM provider

절대 부여 금지: Active-response scope to a dev/eval instance

Active response tools cause real actions on endpoints. Gate behind human confirmation.
Alert payloads may contain sensitive info (filenames, users); consider Presidio-style redaction upstream.

문제 해결

자주 발생하는 오류와 해결

401 from Wazuh API

Creds wrong, or JWT expired. Server auto-rotates; if persistent, check ENV.

Empty alert list despite known alerts

Indexer (Elasticsearch) not reachable from MCP container. Check docker-compose networks.

Active response failed / no effect

Confirm the active-response script is enabled on that agent (ossec.conf). Some actions are agent-side only.

대안

Wazuh-MCP-Server 다른 것과 비교

대안	언제 쓰나	단점/장점
Splunk / Sentinel MCPs	You use Splunk or Sentinel instead	Different SIEM
Wazuh UI directly	Single-alert deep dive	Slower; no LLM synthesis

Wazuh-MCP-Server