You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+27-5Lines changed: 27 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,13 @@ The Wazuh MCP Server provides direct access to Wazuh security data through natur
57
57
58
58
### Threat Intelligence Gathering and Response
59
59
60
-
For enhanced threat intelligence capabilities, the Wazuh MCP Server can be combined with the **[Cortex MCP Server](https://github.com/gbrigandi/mcp-server-cortex/)** to create a powerful security analysis ecosystem.
60
+
For enhanced threat intelligence and incident response capabilities, the Wazuh MCP Server can be combined with complementary security MCP servers:
61
+
62
+
| Server | Description |
63
+
|--------|-------------|
64
+
|**[Cortex MCP Server](https://github.com/gbrigandi/mcp-server-cortex/)**| Artifact analysis and IOC enrichment via 140+ analyzers |
65
+
|**[TheHive MCP Server](https://github.com/gbrigandi/mcp-server-thehive/)**| Case management and incident response orchestration |
66
+
|**[MISP MCP Server](https://github.com/gbrigandi/mcp-server-misp/)**| Threat intelligence sharing and IOC lookup |
61
67
62
68
**Enhanced Capabilities with Cortex Integration:**
63
69
***Artifact Analysis:** Automatically analyze suspicious files, URLs, domains, and IP addresses found in Wazuh alerts using Cortex's 140+ analyzers
@@ -66,12 +72,28 @@ For enhanced threat intelligence capabilities, the Wazuh MCP Server can be combi
66
72
***Multi-Source Intelligence:** Leverage analyzers for reputation checks, malware analysis, domain analysis, and behavioral analysis
67
73
***Response Orchestration:** Use analysis results to inform automated response actions and alert prioritization
68
74
75
+
**Enhanced Capabilities with TheHive Integration:**
76
+
***Case Creation:** Automatically create cases in TheHive from Wazuh alerts for structured incident tracking
77
+
***Alert Correlation:** Link related Wazuh alerts to existing cases for comprehensive incident timelines
78
+
***Task Management:** Create and track investigation tasks based on alert severity and type
79
+
***Observable Management:** Extract and manage IOCs as observables within case investigations
80
+
***Collaboration:** Enable security team collaboration on incidents detected by Wazuh
81
+
82
+
**Enhanced Capabilities with MISP Integration:**
83
+
***IOC Lookup:** Check if indicators from Wazuh alerts are known in your threat intelligence database
84
+
***Threat Context:** Retrieve event context, threat actor attribution, and MITRE ATT&CK mappings for IOCs
85
+
***False Positive Reduction:** Validate IOCs against MISP warninglists to reduce false positives
86
+
***Sighting Tracking:** Record and query sighting history to assess IOC prevalence
87
+
***Galaxy Exploration:** Access threat actor profiles, malware families, and attack patterns
88
+
69
89
**Example Workflow:**
70
90
1. Wazuh detects a suspicious file hash or network connection in an alert
71
-
2. The AI assistant automatically queries the Cortex MCP Server to analyze the artifact using multiple analyzers
72
-
3. Results from VirusTotal, hybrid analysis, domain reputation, and other sources are correlated
73
-
4. The combined intelligence provides context for incident response decisions
74
-
5. Findings can be used to update Wazuh rules or trigger additional monitoring
91
+
2. The AI assistant queries the MISP MCP Server to check if the IOC is known in threat intelligence
92
+
3. If unknown, the Cortex MCP Server analyzes the artifact using multiple analyzers
93
+
4. Results from VirusTotal, hybrid analysis, domain reputation, and other sources are correlated
94
+
5. A case is created in TheHive via the TheHive MCP Server to track the investigation
95
+
6. The combined intelligence provides context for incident response decisions
96
+
7. Findings can be used to update Wazuh rules or trigger additional monitoring
0 commit comments