mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-07-25 13:50:59 +03:00
mukul975
cb8d79e068
- Add validated mitre_attack frontmatter to all 754 skills (286 distinct techniques), verified against MITRE ATT&CK v19.1 via the official mitreattack-python library: 0 revoked, deprecated, or invalid IDs - Curate precise per-skill technique IDs for forensics, malware-analysis, threat-intel, and red-team skills (e.g. DCSync -> T1003.006, Kerberoasting -> T1558.003, Pass-the-Ticket -> T1550.003) - Reconcile v19.1 tactic restructuring: Defense Evasion split into Stealth (TA0005) and Defense Impairment (TA0112); revoked T1562.* family and T1070.001/.002 remapped to active equivalents (T1685.*) - Normalize word-split tags across 35 skills (remove filename-derived stopword tags, add semantic cybersecurity tags) - Add api-reference.md for 3 skills that were missing it - Update README ATT&CK section with accurate v19.1 tactic distribution
74 lines
2.1 KiB
Markdown
74 lines
2.1 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
|
|
mitre_attack:
|
|
- T1078
|
|
- T1190
|
|
- T1059
|
|
- T1685.002
|
|
- T1685.005
|
|
---
|
|
# 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.
|