[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AS2VDWNA5Z6MWCXQWHY72":3,"skill-same:01M71AS2VDWNA5Z6MWCXQWHY72":77},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":62,"updatedAt":63,"install":64,"resources":76},"01M71AS2VDWNA5Z6MWCXQWHY72","cyber-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","nexuslinkproductions\u002Fyuri-os","nexuslinkproductions","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273246263?v=4","01M718YX9NZRCW50B59B8ZVDKN","Marcel Spatz","01M718YXAQ7530F4B1VKN6SFQV",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-configuring-host-based-intrusion-detection\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"configuring host based intrusion detection","intrusion","detection","cyber configuring host based intrusion detection","host","OSSEC","Wazuh","endpoint","security","integrity","change detection","file integrity monitoring","change","monitoring","fim","when","false","cybersecurity","HIDS","intrusion-detection","2026-11-10 10:12:30",false,"---\nname: cyber-configuring-host-based-intrusion-detection\ndescription: \"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 \"\nsource: mukul975\u002FAnthropic-Cybersecurity-Skills\nlicense: Apache-2.0\nauthorized_lab: false\norigin_frontmatter: \"name: configuring-host-based-intrusion-detection | description: '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, |   OSS\"\nhide: true\n---\n\n> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\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","> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\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",{"hide":52,"name":5,"source":53,"license":15,"description":54,"authorized_lab":48,"origin_frontmatter":55},true,"mukul975\u002FAnthropic-Cybersecurity-Skills","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 ","name: configuring-host-based-intrusion-detection | description: '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, |   OSS","main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794",".claude\u002Fskills\u002Fcyber-configuring-host-based-intrusion-detection",0,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions","Building deterministic AI governance and continuity systems. Workflow architect + visual storyteller","2026-11-14 03:05:17",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":52},[66,69,72],{"tool":67,"command":68},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-configuring-host-based-intrusion-detection",{"tool":70,"command":71},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-configuring-host-based-intrusion-detection",{"tool":73,"command":74},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-configuring-host-based-intrusion-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-configuring-host-based-intrusion-detection\u002FSKILL.md",[],[78,101,125,155,182,201],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":47},"01M71CG1AME5WC0A79AE65WT0X","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","MIT","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[86,87,88,89,90,91,92,93,94,95,96,42,97,98,99,100],"zoom out","zoom","with","harness","how","section","re","true","understand","use","perspective","you","code","it","context",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":47},"01M71CFY9ATD0BAXV6B14HFG7C","yuri-shura","6-perspective adversarial review for high-stakes turns (architecture decisions, refactor planning, deployment review) — fans out architect, adversary (7-vector attack), maintainer, ops, product, and security perspectives in parallel, then consolidates. Use when user says 'review this decision', '\u002Fshura', 'adversarial review', 'what could go wrong', 'architecture review', or 'deployment review'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-shura\u002FSKILL.md",[],[108,109,89,110,111,112,113,114,115,116,117,95,118,42,119,120,121,122,123,124],"yuri shura","parallel","architecture review","planning","for","deployment","vector","strategic review","decision","strategic","ops","workflow","decisions","architecture","review","perspectives","adversarial",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":136,"publishedAt":47},"01M71CFTTYW1HA2MNX38EV1GJ5","yuri-sales-intelligence","Unified sales and outreach skill generating cold outreach openers, social selling sequences, objection rebuttals, and ad creative for any paid platform — multi-persona aware, adapting tone and offer frame to buyer type. Use when user says 'write a cold email', 'outreach sequence', 'objection handling', 'ad copy', or 'sales pitch'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-sales-intelligence\u002FSKILL.md",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[137,138,139,140,141,142,143,144,145,42,146,147,148,149,150,151,152,112,153,154],"intelligence","sales intelligence","yuri sales intelligence","sales","cold","paid","social","persona","pitch","cold email","ad creative","write","sequences","sequence","platform","email","cold outreach","frame",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":167,"publishedAt":47},"01M71CFQMBFTFADJNGP0Z2WCYK","yuri-code-intelligence","Unified code quality intelligence layer that diagnoses code smells (Long Method, Feature Envy, design pattern issues), prescribes targeted Fowler refactoring techniques, and reviews code for security, performance, and clarity. Use when user says 'review this code', 'refactor this', 'what's wrong with this method', 'code smells', or 'clean this up'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-code-intelligence\u002FSKILL.md",[161,164],{"categoryNo":162,"categoryName":163,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[168,98,169,137,89,170,171,172,112,173,174,175,176,177,178,179,180,181,95,42],"yuri code intelligence","code intelligence","reviews","code quality","feature","performance","code review","long","up","issues","clean","techniques","improve","design",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":47},"01M71CFP32RT6GD3GKNHCJP8VP","yuri-adw","Invoke when user asks to run the ADW loop \u002F agentic engineering loop \u002F software factory workflow.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-adw\u002FSKILL.md",[],[189,190,191,192,193,194,195,196,197,42,198,119,199,200],"yuri adw","run","engineering loop","software factory","software","agentic engineering","factory","loop","invoke","engineering","agentic","user",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":219,"publishedAt":47},"01M71CFK4VPEKY6A73237P7RSN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[207,210,213,216],{"categoryNo":208,"categoryName":209,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":211,"categoryName":212,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":214,"categoryName":215,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":217,"categoryName":218,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[220,221,222,42,119,223,89,224,113,95,225],"writing","writing skills","new","work","editing","Existing"]