implementing-file-integrity-monitoring-with-aide

Configure AIDE (Advanced Intrusion Detection Environment) for file integrity monitoring including baseline creation, scheduled integrity checks, change detection, and alerting

跳到安装

仓库: xalgord/xalgorix
最近来源活动: 2026年6月6日 16:41
检测到的 SKILL.md 语言: 英语
星标: 813
分支: 146

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/xalgord/xalgorix --skill implementing-file-integrity-monitoring-with-aide

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

exploiting-http-request-smuggling

Detecting and exploiting HTTP request smuggling vulnerabilities caused by Content-Length and Transfer-Encoding parsing discrepancies between front-end and back-end servers.

2026-07-20

exploiting-oauth-misconfiguration

Identifying and exploiting OAuth 2.0 and OpenID Connect misconfigurations including redirect URI manipulation, token leakage, and authorization code theft during security assessments.

2026-07-20

exploiting-subdomain-takeover-vulnerabilities

Identifying and exploiting dangling DNS records pointing to unclaimed cloud services, enabling subdomain takeover for phishing, cookie stealing, and authentication bypass during authorized penetration tests.

2026-06-19

查看这个仓库的全部 Skills

Implementing File Integrity Monitoring with AIDE

Overview

AIDE (Advanced Intrusion Detection Environment) is a host-based intrusion detection system that monitors file and directory integrity using cryptographic checksums. This skill covers generating AIDE configuration files, initializing baseline databases, running integrity checks, parsing change reports, and setting up automated cron-based monitoring with alerting.

When to Use

When deploying or configuring implementing file integrity monitoring with aide 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

Common Misconfigurations & Verification

Baseline DB stored on the host: if aide.db.gz lives at its default /var/lib/aide/aide.db.gz on the monitored system, an attacker with root simply re-runs aide --init and copies aide.db.new.gz over it, erasing evidence. Store the baseline (and aide.conf) read-only off-host or on signed/immutable media, and compare against that copy.

DB never updated after legit changes: after patching, admins run aide --update and blindly promote aide.db.new.gz to the baseline, masking any malicious change made in the same window. Diff the report before promoting, and update the DB out-of-band.

Weak rule selection: lines using p+i only (perms/inode) miss content tampering. Confirm critical paths use a hashing ruleset (e.g., Checksums = sha256+sha512) and that /etc, /bin, /sbin, /usr/bin, /boot are actually in scope and not shadowed by a later !exclude.

Check not scheduled / output unread: a cron job that writes to a local file no one reads is not monitoring. Verify the cron entry exists and routes results to a SIEM or mailbox.

Verification: touch a canary change (chmod o+w /etc/passwd or add a file under /usr/bin), run aide --check, and confirm it reports the added/changed entry with a checksum mismatch; then revert. A clean report after a known change means the rules or DB path are wrong.

Prerequisites