[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74VJBZPDYTNR3K515FS7Z1G":3,"skill-same:01M74VJBZPDYTNR3K515FS7Z1G":91},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":37,"commitSha":38,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M74VJBZPDYTNR3K515FS7Z1G","configuring-host-based-intrusion-detection",null,"Configures host-based intrusion detection systems (HIDS) to monitor endpoint file integrity, system calls, and configuration changes for security violations. Use when deploying OSSEC, Wazuh, or AIDE for endpoint monitoring, building file integrity monitoring (FIM) policies, or meeting compliance requirements for change detection. Activates for requests involving HIDS configuration, file integrity monitoring, OSSEC\u002FWazuh deployment, or host-based detection.","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fconfiguring-host-based-intrusion-detection\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fconfiguring-host-based-intrusion-detection\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: configuring-host-based-intrusion-detection\ndescription: >\n  Configures host-based intrusion detection systems (HIDS) to monitor endpoint file integrity,\n  system calls, and configuration changes for security violations. Use when deploying OSSEC,\n  Wazuh, or AIDE for endpoint monitoring, building file integrity monitoring (FIM) policies, or\n  meeting compliance requirements for change detection. Activates for requests involving HIDS\n  configuration, file integrity monitoring, OSSEC\u002FWazuh deployment, or host-based detection.\ndomain: cybersecurity\nsubdomain: endpoint-security\ntags: [endpoint, HIDS, Wazuh, OSSEC, file-integrity-monitoring, intrusion-detection]\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\n---\n# Configuring Host-Based Intrusion Detection\n\n## When to Use\n\nUse this skill when:\n- Deploying HIDS agents (Wazuh, OSSEC, AIDE) across Windows and Linux endpoints\n- Configuring file integrity monitoring (FIM) for compliance (PCI DSS 11.5, NIST SI-7)\n- Monitoring system configuration changes, rootkit detection, and security policy violations\n- Integrating HIDS alerts with SIEM platforms for centralized monitoring\n\n**Do not use** this skill for network-based IDS (Suricata, Snort) or for EDR deployment.\n\n## Prerequisites\n\n- Wazuh server (manager) deployed and accessible from endpoints\n- Administrative access to target endpoints\n- Network connectivity: agents to Wazuh manager on port 1514 (TCP\u002FUDP) and 1515 (TCP enrollment)\n- Wazuh dashboard (OpenSearch Dashboards) for alert visualization\n- Understanding of critical files\u002Fdirectories to monitor per OS\n\n## Workflow\n\n### Step 1: Install Wazuh Agent\n\n**Windows**:\n```powershell\n# Download and install Wazuh agent\nInvoke-WebRequest -Uri \"https:\u002F\u002Fpackages.wazuh.com\u002F4.x\u002Fwindows\u002Fwazuh-agent-4.9.0-1.msi\" `\n  -OutFile \"wazuh-agent.msi\"\nmsiexec \u002Fi wazuh-agent.msi \u002Fq WAZUH_MANAGER=\"wazuh-manager.corp.com\" `\n  WAZUH_REGISTRATION_SERVER=\"wazuh-manager.corp.com\" WAZUH_AGENT_GROUP=\"windows-workstations\"\nnet start WazuhSvc\n```\n\n**Linux (Debian\u002FUbuntu)**:\n```bash\ncurl -s https:\u002F\u002Fpackages.wazuh.com\u002Fkey\u002FGPG-KEY-WAZUH | gpg --dearmor -o \u002Fusr\u002Fshare\u002Fkeyrings\u002Fwazuh.gpg\necho \"deb [signed-by=\u002Fusr\u002Fshare\u002Fkeyrings\u002Fwazuh.gpg] https:\u002F\u002Fpackages.wazuh.com\u002F4.x\u002Fapt\u002F stable main\" \\\n  > \u002Fetc\u002Fapt\u002Fsources.list.d\u002Fwazuh.list\napt-get update && apt-get install wazuh-agent -y\nsed -i 's\u002FMANAGER_IP\u002Fwazuh-manager.corp.com\u002F' \u002Fvar\u002Fossec\u002Fetc\u002Fossec.conf\nsystemctl daemon-reload && systemctl enable --now wazuh-agent\n```\n\n### Step 2: Configure File Integrity Monitoring (FIM)\n\nEdit agent configuration (`\u002Fvar\u002Fossec\u002Fetc\u002Fossec.conf` or `C:\\Program Files (x86)\\ossec-agent\\ossec.conf`):\n\n```xml\n\u003Csyscheck>\n  \u003C!-- Scan frequency: every 12 hours -->\n  \u003Cfrequency>43200\u003C\u002Ffrequency>\n  \u003Cscan_on_start>yes\u003C\u002Fscan_on_start>\n  \u003Calert_new_files>yes\u003C\u002Falert_new_files>\n\n  \u003C!-- Linux critical directories -->\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">\u002Fetc\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">\u002Fusr\u002Fbin\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">\u002Fusr\u002Fsbin\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">\u002Fbin\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">\u002Fsbin\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\">\u002Fboot\u003C\u002Fdirectories>\n\n  \u003C!-- Windows critical directories -->\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">C:\\Windows\\System32\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">C:\\Windows\\SysWOW64\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">%PROGRAMFILES%\u003C\u002Fdirectories>\n\n  \u003C!-- Windows registry monitoring -->\n  \u003Cwindows_registry>HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\u003C\u002Fwindows_registry>\n  \u003Cwindows_registry>HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\u003C\u002Fwindows_registry>\n  \u003Cwindows_registry>HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\u003C\u002Fwindows_registry>\n\n  \u003C!-- Ignore frequently changing files -->\n  \u003Cignore>\u002Fetc\u002Fmtab\u003C\u002Fignore>\n  \u003Cignore>\u002Fetc\u002Fresolv.conf\u003C\u002Fignore>\n  \u003Cignore type=\"sregex\">.log$\u003C\u002Fignore>\n\u003C\u002Fsyscheck>\n```\n\n### Step 3: Configure Rootkit Detection\n\n```xml\n\u003Crootcheck>\n  \u003Cdisabled>no\u003C\u002Fdisabled>\n  \u003Cfrequency>43200\u003C\u002Ffrequency>\n  \u003Crootkit_files>\u002Fvar\u002Fossec\u002Fetc\u002Fshared\u002Frootkit_files.txt\u003C\u002Frootkit_files>\n  \u003Crootkit_trojans>\u002Fvar\u002Fossec\u002Fetc\u002Fshared\u002Frootkit_trojans.txt\u003C\u002Frootkit_trojans>\n  \u003Csystem_audit>\u002Fvar\u002Fossec\u002Fetc\u002Fshared\u002Fsystem_audit_rcl.txt\u003C\u002Fsystem_audit>\n  \u003Ccheck_dev>yes\u003C\u002Fcheck_dev>\n  \u003Ccheck_files>yes\u003C\u002Fcheck_files>\n  \u003Ccheck_if>yes\u003C\u002Fcheck_if>\n  \u003Ccheck_pids>yes\u003C\u002Fcheck_pids>\n  \u003Ccheck_ports>yes\u003C\u002Fcheck_ports>\n  \u003Ccheck_sys>yes\u003C\u002Fcheck_sys>\n  \u003Ccheck_trojans>yes\u003C\u002Fcheck_trojans>\n  \u003Ccheck_unixaudit>yes\u003C\u002Fcheck_unixaudit>\n\u003C\u002Frootcheck>\n```\n\n### Step 4: Configure Log Analysis Rules\n\n```xml\n\u003C!-- Custom rules in \u002Fvar\u002Fossec\u002Fetc\u002Frules\u002Flocal_rules.xml -->\n\u003Cgroup name=\"local,syscheck,\">\n  \u003C!-- Alert on critical binary modifications -->\n  \u003Crule id=\"100001\" level=\"12\">\n    \u003Cif_sid>550\u003C\u002Fif_sid>\n    \u003Cmatch>\u002Fusr\u002Fbin\u002F|\u002Fusr\u002Fsbin\u002F|\u002Fbin\u002F|\u002Fsbin\u002F\u003C\u002Fmatch>\n    \u003Cdescription>Critical system binary modified: $(file)\u003C\u002Fdescription>\n    \u003Cgroup>syscheck,pci_dss_11.5,\u003C\u002Fgroup>\n  \u003C\u002Frule>\n\n  \u003C!-- Alert on new executable in temp directories -->\n  \u003Crule id=\"100002\" level=\"10\">\n    \u003Cif_sid>554\u003C\u002Fif_sid>\n    \u003Cmatch>\u002Ftmp\u002F|\u002Fvar\u002Ftmp\u002F\u003C\u002Fmatch>\n    \u003Cdescription>New file created in temp directory: $(file)\u003C\u002Fdescription>\n    \u003Cgroup>syscheck,malware,\u003C\u002Fgroup>\n  \u003C\u002Frule>\n\n  \u003C!-- Alert on SSH configuration changes -->\n  \u003Crule id=\"100003\" level=\"10\">\n    \u003Cif_sid>550\u003C\u002Fif_sid>\n    \u003Cmatch>\u002Fetc\u002Fssh\u002Fsshd_config\u003C\u002Fmatch>\n    \u003Cdescription>SSH configuration modified\u003C\u002Fdescription>\n    \u003Cgroup>syscheck,authentication,\u003C\u002Fgroup>\n  \u003C\u002Frule>\n\u003C\u002Fgroup>\n```\n\n### Step 5: Configure Active Response\n\n```xml\n\u003C!-- Auto-block IP after repeated authentication failures -->\n\u003Cactive-response>\n  \u003Ccommand>firewall-drop\u003C\u002Fcommand>\n  \u003Clocation>local\u003C\u002Flocation>\n  \u003Crules_id>5712\u003C\u002Frules_id>\n  \u003Ctimeout>600\u003C\u002Ftimeout>\n\u003C\u002Factive-response>\n\n\u003C!-- Disable account after brute force detection -->\n\u003Cactive-response>\n  \u003Cdisabled>no\u003C\u002Fdisabled>\n  \u003Ccommand>disable-account\u003C\u002Fcommand>\n  \u003Clocation>local\u003C\u002Flocation>\n  \u003Crules_id>100100\u003C\u002Frules_id>\n  \u003Ctimeout>3600\u003C\u002Ftimeout>\n\u003C\u002Factive-response>\n```\n\n### Step 6: Integrate with SIEM\n\n```\n# Wazuh to Splunk via Filebeat\n# Edit \u002Fetc\u002Ffilebeat\u002Ffilebeat.yml:\nfilebeat.inputs:\n  - type: log\n    paths:\n      - \u002Fvar\u002Fossec\u002Flogs\u002Falerts\u002Falerts.json\n    json.keys_under_root: true\noutput.elasticsearch:\n  hosts: [\"https:\u002F\u002Fsplunk-hec:8088\"]\n\n# Wazuh to Elastic via direct integration\n# Wazuh indexer feeds directly into OpenSearch\u002FElasticsearch\n# Dashboard: https:\u002F\u002Fwazuh-dashboard:5601\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **HIDS** | Host-based Intrusion Detection System; monitors individual endpoints for malicious activity |\n| **FIM** | File Integrity Monitoring; detects unauthorized changes to files by comparing cryptographic hashes |\n| **Syscheck** | Wazuh\u002FOSSEC module for file integrity monitoring and registry monitoring |\n| **Rootcheck** | Wazuh\u002FOSSEC module for rootkit and malware detection |\n| **Active Response** | Automated defensive action triggered by HIDS alert (IP block, account disable) |\n| **CDB List** | Constant Database list used for custom lookups in Wazuh rules |\n\n## Tools & Systems\n\n- **Wazuh**: Open-source HIDS platform (fork of OSSEC) with manager, agent, and dashboard\n- **OSSEC**: Original open-source HIDS (predecessor to Wazuh)\n- **AIDE (Advanced Intrusion Detection Environment)**: Standalone file integrity checker for Linux\n- **Tripwire**: Commercial file integrity monitoring solution\n- **Samhain**: Open-source HIDS focused on file integrity and log monitoring\n\n## Common Pitfalls\n\n- **Monitoring too many directories**: FIM on entire filesystems generates excessive alerts. Focus on critical system binaries, configuration files, and web roots.\n- **Not excluding noisy files**: Frequently changing files (logs, temp, caches) generate false positive FIM alerts. Maintain exclusion lists.\n- **Ignoring baseline establishment**: First FIM scan creates a baseline. Changes detected before baseline stabilization are noise, not threats. Allow 48 hours for baseline.\n- **Active response without testing**: Auto-blocking IPs or disabling accounts can cause outages. Test active response rules in a non-production environment first.\n- **Agent enrollment failures**: Agents must successfully enroll with the manager before monitoring begins. Verify firewall rules allow port 1514 and 1515 traffic.\n","# Configuring Host-Based Intrusion Detection\n\n## When to Use\n\nUse this skill when:\n- Deploying HIDS agents (Wazuh, OSSEC, AIDE) across Windows and Linux endpoints\n- Configuring file integrity monitoring (FIM) for compliance (PCI DSS 11.5, NIST SI-7)\n- Monitoring system configuration changes, rootkit detection, and security policy violations\n- Integrating HIDS alerts with SIEM platforms for centralized monitoring\n\n**Do not use** this skill for network-based IDS (Suricata, Snort) or for EDR deployment.\n\n## Prerequisites\n\n- Wazuh server (manager) deployed and accessible from endpoints\n- Administrative access to target endpoints\n- Network connectivity: agents to Wazuh manager on port 1514 (TCP\u002FUDP) and 1515 (TCP enrollment)\n- Wazuh dashboard (OpenSearch Dashboards) for alert visualization\n- Understanding of critical files\u002Fdirectories to monitor per OS\n\n## Workflow\n\n### Step 1: Install Wazuh Agent\n\n**Windows**:\n```powershell\n# Download and install Wazuh agent\nInvoke-WebRequest -Uri \"https:\u002F\u002Fpackages.wazuh.com\u002F4.x\u002Fwindows\u002Fwazuh-agent-4.9.0-1.msi\" `\n  -OutFile \"wazuh-agent.msi\"\nmsiexec \u002Fi wazuh-agent.msi \u002Fq WAZUH_MANAGER=\"wazuh-manager.corp.com\" `\n  WAZUH_REGISTRATION_SERVER=\"wazuh-manager.corp.com\" WAZUH_AGENT_GROUP=\"windows-workstations\"\nnet start WazuhSvc\n```\n\n**Linux (Debian\u002FUbuntu)**:\n```bash\ncurl -s https:\u002F\u002Fpackages.wazuh.com\u002Fkey\u002FGPG-KEY-WAZUH | gpg --dearmor -o \u002Fusr\u002Fshare\u002Fkeyrings\u002Fwazuh.gpg\necho \"deb [signed-by=\u002Fusr\u002Fshare\u002Fkeyrings\u002Fwazuh.gpg] https:\u002F\u002Fpackages.wazuh.com\u002F4.x\u002Fapt\u002F stable main\" \\\n  > \u002Fetc\u002Fapt\u002Fsources.list.d\u002Fwazuh.list\napt-get update && apt-get install wazuh-agent -y\nsed -i 's\u002FMANAGER_IP\u002Fwazuh-manager.corp.com\u002F' \u002Fvar\u002Fossec\u002Fetc\u002Fossec.conf\nsystemctl daemon-reload && systemctl enable --now wazuh-agent\n```\n\n### Step 2: Configure File Integrity Monitoring (FIM)\n\nEdit agent configuration (`\u002Fvar\u002Fossec\u002Fetc\u002Fossec.conf` or `C:\\Program Files (x86)\\ossec-agent\\ossec.conf`):\n\n```xml\n\u003Csyscheck>\n  \u003C!-- Scan frequency: every 12 hours -->\n  \u003Cfrequency>43200\u003C\u002Ffrequency>\n  \u003Cscan_on_start>yes\u003C\u002Fscan_on_start>\n  \u003Calert_new_files>yes\u003C\u002Falert_new_files>\n\n  \u003C!-- Linux critical directories -->\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">\u002Fetc\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">\u002Fusr\u002Fbin\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">\u002Fusr\u002Fsbin\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">\u002Fbin\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">\u002Fsbin\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\">\u002Fboot\u003C\u002Fdirectories>\n\n  \u003C!-- Windows critical directories -->\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">C:\\Windows\\System32\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">C:\\Windows\\SysWOW64\u003C\u002Fdirectories>\n  \u003Cdirectories check_all=\"yes\" realtime=\"yes\">%PROGRAMFILES%\u003C\u002Fdirectories>\n\n  \u003C!-- Windows registry monitoring -->\n  \u003Cwindows_registry>HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\u003C\u002Fwindows_registry>\n  \u003Cwindows_registry>HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\u003C\u002Fwindows_registry>\n  \u003Cwindows_registry>HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\u003C\u002Fwindows_registry>\n\n  \u003C!-- Ignore frequently changing files -->\n  \u003Cignore>\u002Fetc\u002Fmtab\u003C\u002Fignore>\n  \u003Cignore>\u002Fetc\u002Fresolv.conf\u003C\u002Fignore>\n  \u003Cignore type=\"sregex\">.log$\u003C\u002Fignore>\n\u003C\u002Fsyscheck>\n```\n\n### Step 3: Configure Rootkit Detection\n\n```xml\n\u003Crootcheck>\n  \u003Cdisabled>no\u003C\u002Fdisabled>\n  \u003Cfrequency>43200\u003C\u002Ffrequency>\n  \u003Crootkit_files>\u002Fvar\u002Fossec\u002Fetc\u002Fshared\u002Frootkit_files.txt\u003C\u002Frootkit_files>\n  \u003Crootkit_trojans>\u002Fvar\u002Fossec\u002Fetc\u002Fshared\u002Frootkit_trojans.txt\u003C\u002Frootkit_trojans>\n  \u003Csystem_audit>\u002Fvar\u002Fossec\u002Fetc\u002Fshared\u002Fsystem_audit_rcl.txt\u003C\u002Fsystem_audit>\n  \u003Ccheck_dev>yes\u003C\u002Fcheck_dev>\n  \u003Ccheck_files>yes\u003C\u002Fcheck_files>\n  \u003Ccheck_if>yes\u003C\u002Fcheck_if>\n  \u003Ccheck_pids>yes\u003C\u002Fcheck_pids>\n  \u003Ccheck_ports>yes\u003C\u002Fcheck_ports>\n  \u003Ccheck_sys>yes\u003C\u002Fcheck_sys>\n  \u003Ccheck_trojans>yes\u003C\u002Fcheck_trojans>\n  \u003Ccheck_unixaudit>yes\u003C\u002Fcheck_unixaudit>\n\u003C\u002Frootcheck>\n```\n\n### Step 4: Configure Log Analysis Rules\n\n```xml\n\u003C!-- Custom rules in \u002Fvar\u002Fossec\u002Fetc\u002Frules\u002Flocal_rules.xml -->\n\u003Cgroup name=\"local,syscheck,\">\n  \u003C!-- Alert on critical binary modifications -->\n  \u003Crule id=\"100001\" level=\"12\">\n    \u003Cif_sid>550\u003C\u002Fif_sid>\n    \u003Cmatch>\u002Fusr\u002Fbin\u002F|\u002Fusr\u002Fsbin\u002F|\u002Fbin\u002F|\u002Fsbin\u002F\u003C\u002Fmatch>\n    \u003Cdescription>Critical system binary modified: $(file)\u003C\u002Fdescription>\n    \u003Cgroup>syscheck,pci_dss_11.5,\u003C\u002Fgroup>\n  \u003C\u002Frule>\n\n  \u003C!-- Alert on new executable in temp directories -->\n  \u003Crule id=\"100002\" level=\"10\">\n    \u003Cif_sid>554\u003C\u002Fif_sid>\n    \u003Cmatch>\u002Ftmp\u002F|\u002Fvar\u002Ftmp\u002F\u003C\u002Fmatch>\n    \u003Cdescription>New file created in temp directory: $(file)\u003C\u002Fdescription>\n    \u003Cgroup>syscheck,malware,\u003C\u002Fgroup>\n  \u003C\u002Frule>\n\n  \u003C!-- Alert on SSH configuration changes -->\n  \u003Crule id=\"100003\" level=\"10\">\n    \u003Cif_sid>550\u003C\u002Fif_sid>\n    \u003Cmatch>\u002Fetc\u002Fssh\u002Fsshd_config\u003C\u002Fmatch>\n    \u003Cdescription>SSH configuration modified\u003C\u002Fdescription>\n    \u003Cgroup>syscheck,authentication,\u003C\u002Fgroup>\n  \u003C\u002Frule>\n\u003C\u002Fgroup>\n```\n\n### Step 5: Configure Active Response\n\n```xml\n\u003C!-- Auto-block IP after repeated authentication failures -->\n\u003Cactive-response>\n  \u003Ccommand>firewall-drop\u003C\u002Fcommand>\n  \u003Clocation>local\u003C\u002Flocation>\n  \u003Crules_id>5712\u003C\u002Frules_id>\n  \u003Ctimeout>600\u003C\u002Ftimeout>\n\u003C\u002Factive-response>\n\n\u003C!-- Disable account after brute force detection -->\n\u003Cactive-response>\n  \u003Cdisabled>no\u003C\u002Fdisabled>\n  \u003Ccommand>disable-account\u003C\u002Fcommand>\n  \u003Clocation>local\u003C\u002Flocation>\n  \u003Crules_id>100100\u003C\u002Frules_id>\n  \u003Ctimeout>3600\u003C\u002Ftimeout>\n\u003C\u002Factive-response>\n```\n\n### Step 6: Integrate with SIEM\n\n```\n# Wazuh to Splunk via Filebeat\n# Edit \u002Fetc\u002Ffilebeat\u002Ffilebeat.yml:\nfilebeat.inputs:\n  - type: log\n    paths:\n      - \u002Fvar\u002Fossec\u002Flogs\u002Falerts\u002Falerts.json\n    json.keys_under_root: true\noutput.elasticsearch:\n  hosts: [\"https:\u002F\u002Fsplunk-hec:8088\"]\n\n# Wazuh to Elastic via direct integration\n# Wazuh indexer feeds directly into OpenSearch\u002FElasticsearch\n# Dashboard: https:\u002F\u002Fwazuh-dashboard:5601\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **HIDS** | Host-based Intrusion Detection System; monitors individual endpoints for malicious activity |\n| **FIM** | File Integrity Monitoring; detects unauthorized changes to files by comparing cryptographic hashes |\n| **Syscheck** | Wazuh\u002FOSSEC module for file integrity monitoring and registry monitoring |\n| **Rootcheck** | Wazuh\u002FOSSEC module for rootkit and malware detection |\n| **Active Response** | Automated defensive action triggered by HIDS alert (IP block, account disable) |\n| **CDB List** | Constant Database list used for custom lookups in Wazuh rules |\n\n## Tools & Systems\n\n- **Wazuh**: Open-source HIDS platform (fork of OSSEC) with manager, agent, and dashboard\n- **OSSEC**: Original open-source HIDS (predecessor to Wazuh)\n- **AIDE (Advanced Intrusion Detection Environment)**: Standalone file integrity checker for Linux\n- **Tripwire**: Commercial file integrity monitoring solution\n- **Samhain**: Open-source HIDS focused on file integrity and log monitoring\n\n## Common Pitfalls\n\n- **Monitoring too many directories**: FIM on entire filesystems generates excessive alerts. Focus on critical system binaries, configuration files, and web roots.\n- **Not excluding noisy files**: Frequently changing files (logs, temp, caches) generate false positive FIM alerts. Maintain exclusion lists.\n- **Ignoring baseline establishment**: First FIM scan creates a baseline. Changes detected before baseline stabilization are noise, not threats. Allow 48 hours for baseline.\n- **Active response without testing**: Auto-blocking IPs or disabling accounts can cause outages. Test active response rules in a non-production environment first.\n- **Agent enrollment failures**: Agents must successfully enroll with the manager before monitoring begins. Verify firewall rules allow port 1514 and 1515 traffic.\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"subdomain":35,"description":36},[26,27,28,29,30,31],"endpoint","HIDS","Wazuh","OSSEC","file-integrity-monitoring","intrusion-detection","mahipal","cybersecurity","1.0.0","endpoint-security","Configures host-based intrusion detection systems (HIDS) to monitor endpoint file integrity, system calls, and configuration changes for security violations. Use when deploying OSSEC, Wazuh, or AIDE for endpoint monitoring, building file integrity monitoring (FIM) policies, or meeting compliance requirements for change detection. Activates for requests involving HIDS configuration, file integrity monitoring, OSSEC\u002FWazuh deployment, or host-based detection.\n","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill configuring-host-based-intrusion-detection",{"tool":49,"command":50},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill configuring-host-based-intrusion-detection",{"tool":52,"command":53},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill configuring-host-based-intrusion-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fconfiguring-host-based-intrusion-detection\u002FSKILL.md",true,[57,63,67,73,77,81,87],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002Ftemplate.md","ASSET","资产文件",998,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fconfiguring-host-based-intrusion-detection\u002Fassets\u002Ftemplate.md",{"path":64,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fapi-reference.md","REFERENCE","参考文档",1571,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fconfiguring-host-based-intrusion-detection\u002Freferences\u002Fapi-reference.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fstandards.md",1520,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fconfiguring-host-based-intrusion-detection\u002Freferences\u002Fstandards.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fworkflows.md",1301,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fconfiguring-host-based-intrusion-detection\u002Freferences\u002Fworkflows.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fagent.py","SCRIPT","脚本",5409,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fconfiguring-host-based-intrusion-detection\u002Fscripts\u002Fagent.py",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fprocess.py",5677,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fconfiguring-host-based-intrusion-detection\u002Fscripts\u002Fprocess.py",[92,100,107,114,121,128],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":20},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]