configuring-host-based-intrusion-detection

Configures Wazuh and OSSEC agents for file integrity monitoring and host-based intrusion detection.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill configuring-host-based-intrusion-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configuring-host-based-intrusion-detection
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/endpoint-security/configuring-host-based-intrusion-detection
Command: npx skills add https://github.com/xalgord/xalgorix --skill configuring-host-based-intrusion-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying host-based intrusion detection across Windows and Linux endpoints is error-prone: agents enroll but never connect, realtime FIM silently falls back to scheduled scans, and custom rules sit below the alert threshold. This Skill provides a verified, end-to-end workflow for deploying Wazuh/OSSEC HIDS with file integrity monitoring, rootkit detection, and SIEM integration.

Core Features & Use Cases

  • Agent Deployment: Step-by-step Wazuh agent installation for Windows (MSI) and Linux (APT) with manager enrollment on ports 1514/1515.
  • FIM & Rootkit Configuration: Ready-to-adapt syscheck and rootcheck XML covering critical directories, Windows registry keys, and exclusion lists for noisy files.
  • Custom Detection Rules & Active Response: Local rules for binary modification, temp-directory executables, and SSH config changes, plus automated IP blocking and account disabling.
  • Use Case: A security engineer needs PCI DSS 11.5 file integrity monitoring across a mixed fleet; this Skill walks through agent rollout, FIM policy, alert verification with Atomic Red Team tests, and forwarding alerts to Splunk or OpenSearch.

Quick Start

Ask the AI to configure Wazuh file integrity monitoring with realtime alerts on /etc and Windows registry Run keys, then verify alerts reach the SIEM.

Frequently Asked Questions about configuring-host-based-intrusion-detection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure file integrity monitoring with Wazuh?

Configure FIM in the agent's ossec.conf syscheck block by listing directories with check_all and realtime attributes, setting a scan frequency, and adding ignore rules for noisy files like logs. Critical paths include /etc, /usr/bin, and Windows System32 plus registry Run keys.

How to deploy Wazuh agents on Windows and Linux endpoints?

On Windows, install the MSI with WAZUH_MANAGER and WAZUH_AGENT_GROUP parameters, then start WazuhSvc. On Debian/Ubuntu, add the Wazuh APT repository, install wazuh-agent, set the manager IP in ossec.conf, and enable the systemd service.

Wazuh vs OSSEC vs AIDE for host-based intrusion detection?

Wazuh is an actively maintained OSSEC fork adding a manager, dashboard, and SIEM integration, making it suited for centralized fleets. OSSEC is the original HIDS, while AIDE is a standalone file integrity checker for single Linux hosts without agent-manager architecture.

Why is Wazuh realtime FIM not alerting on file changes?

Realtime monitoring only works with inotify on Linux or the USN journal on Windows; on NFS or overlay mounts it silently falls back to the scheduled 12-hour scan. Verify by touching a watched file and confirming a rule 550 or 554 alert fires within seconds.

Why does my Wazuh agent show registered but send no alerts?

A registered agent may be disconnected; check agent_control -l for Active status rather than Never connected. Also confirm local rule levels meet the manager's log_alert_level threshold and that ports 1514 and 1515 are open.

When should I not use host-based intrusion detection?

Do not use HIDS for network traffic analysis; that requires network-based IDS like Suricata or Snort. HIDS also does not replace EDR platforms, which provide deeper behavioral telemetry and response capabilities beyond file integrity and log monitoring.