mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 16:40:24 +00:00
24f816b6a3
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):
- brain/ LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
dispatch, A51 channels, and the OSINT cluster
- knowledge/ LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
MITRE ATT&CK data
- reference/ defensive threat-reference (C3, shhbruh doc) + AdaYaml parser
License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.
Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.
https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
67 lines
2.0 KiB
Markdown
67 lines
2.0 KiB
Markdown
---
|
|
name: implementing-endpoint-detection-with-wazuh
|
|
description: Deploy and configure Wazuh SIEM/XDR for endpoint detection including agent management, custom decoder and rule
|
|
XML creation, alert querying via the Wazuh REST API, and automated response actions.
|
|
domain: cybersecurity
|
|
subdomain: security-operations
|
|
tags:
|
|
- siem
|
|
- xdr
|
|
- wazuh
|
|
- endpoint-detection
|
|
- custom-rules
|
|
- incident-response
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_ai_rmf:
|
|
- GOVERN-1.1
|
|
- MEASURE-2.7
|
|
- MANAGE-3.1
|
|
- MANAGE-2.4
|
|
- MEASURE-3.1
|
|
nist_csf:
|
|
- DE.CM-01
|
|
- RS.MA-01
|
|
- GV.OV-01
|
|
- DE.AE-02
|
|
---
|
|
# Implementing Endpoint Detection with Wazuh
|
|
|
|
## Overview
|
|
|
|
Wazuh is an open-source SIEM and XDR platform for endpoint monitoring, threat detection, and compliance. This skill covers managing agents via the Wazuh REST API, creating custom decoders and rules in XML for organization-specific detections, querying alerts, and testing rule logic using the logtest endpoint.
|
|
|
|
|
|
## When to Use
|
|
|
|
- When deploying or configuring implementing endpoint detection with wazuh capabilities in your environment
|
|
- When establishing security controls aligned to compliance requirements
|
|
- When building or improving security architecture for this domain
|
|
- When conducting security assessments that require this implementation
|
|
|
|
## Prerequisites
|
|
|
|
- Wazuh Manager 4.x deployed with API enabled
|
|
- Python 3.9+ with `requests` library
|
|
- API credentials (username/password for JWT authentication)
|
|
- Understanding of Wazuh decoder and rule XML syntax
|
|
|
|
## Steps
|
|
|
|
### Step 1: Authenticate to Wazuh API
|
|
Obtain JWT token via POST to /security/user/authenticate.
|
|
|
|
### Step 2: List and Monitor Agents
|
|
Query agent status, versions, and last keep-alive via /agents endpoint.
|
|
|
|
### Step 3: Query Security Alerts
|
|
Search alerts by rule ID, severity, agent, or time range.
|
|
|
|
### Step 4: Test Custom Rules with Logtest
|
|
Use the /logtest endpoint to validate decoder and rule logic against sample log lines.
|
|
|
|
## Expected Output
|
|
|
|
JSON report with agent inventory, alert statistics, rule coverage, and logtest validation results.
|