Repository navigation
Closed
Labels
needs-infoWaiting on reporter for more informationWaiting on reporter for more information
Description
Findings from running the v0.1.1 one-liner (curl -fsSL .../get.sh | sudo sh) in guided mode on two test hosts:
- Rocky Linux 10.2 with the
heavyprofile. It installed, and every verify check passed. - Ubuntu 22.04 with auditd 3.0.7 and a Wazuh agent, choosing
mediumand UDP forwarding. It was refused.
Ubuntu 22.04: refused only after every question
- Guided mode asks every question before it checks for refusals. The host runs a Wazuh agent. Install asked for the profile, the syslog server, the port, the protocol, and the existing rule files, then refused with
refuse=agent_conflict:wazuhand threw the answers away. Guided mode should run the preflight checks first. Then it can stop before the questions, or offer the override as a question, e.g. "Wazuh is installed and may manage audit rules. Install anyway? [y/N]". - The override text doesn't say how to pass it.
override=akit_accept_agentsnames the setting, but not the flag (--accept-agents wazuh) or the value. Someone using the one-liner has to guesssh -s -- --accept-agents wazuh. - Check whether the host is a container. The host reported a Proxmox kernel (
7.0.14-14-pve), and a guest VM runs its own kernel, so this suggests an LXC container. auditd can't load rules in a container. If that's what this was, survey saidsupport_tier=supported, and install would have failed or rolled back after the refusal was overridden. Survey should report container hosts (for example withsystemd-detect-virt --container), and preflight should refuse them. - Find out why Ubuntu's
audit.ruleswas offered for keep or replace. On Rocky, the distro's defaults-onlyaudit.rulesis moved without asking. On this host the question came up, so survey didn't see the file as control lines only. Wazuh may have added rules to it, or Ubuntu's default file may hold more than control lines. Check which.
Rocky Linux 10: installed, but the output needs work
- The output floods the screen.
augenrules --loadprinted 114 lines of "Old style watch rules are slower" and "perm used without an arch is slower".auditctl -swas printed three times, plus a "No rules" line, so the result lines were easy to miss. Send all of that to the log file under/var/log/auditd-kit/, and print one summary line instead. - The plan prints about 400 lines of diff before "Apply these N changes?" The change list scrolls out of sight before the question. In guided mode, show only the change lines and point to
--dry-runfor the full diff. - Guided mode doesn't ask about immutable mode for
heavy. CIS and STIG expect-e 2, andheavyis the compliance profile. Whenheavyis chosen, ask whether to lock the rules until reboot, and say that any later rule change, including rollback, then needs a reboot. - The render drops aren't shown. Render dropped 12 rules on the Rocky host, all correctly: Ubuntu-only paths, programs that aren't installed, and the
yumsymlink. They're listed only in/var/lib/auditd-kit/render-report.txt. Print one line with the count and the report path. - Measure the cost of watch rules and path rules without an arch. auditctl's warnings point at a real cost.
-wwatches and-F path=/-F dir=rules without-F arch=are checked on more syscalls than rules that name an arch. audit-userspace recommends-a always,exit -F arch=b64 -F path=... -F perm=wa. Converting would roughly double the rule count and change every rule file, so time a syscall-heavy workload with both forms before deciding. - Document the
node=prefix. Install setsname_format = hostname, so every audit log line starts withnode=<hostname>. That's on purpose, but a SIEM parser that expects lines to start withtype=needs to allow for it. Add a line to the README.
What worked
On Rocky, install loaded 172 rules for heavy. Every verify check passed (rule count, files, canary, lost), no events were lost, and an idle minute logged 63 events.
Metadata
Metadata
Assignees
Labels
needs-infoWaiting on reporter for more informationWaiting on reporter for more information
Activity
fix: make guided install output short, and ask about immutable for he…
spydisec commentedon Oct 21, 2026
Items 5 to 8 are fixed in #46 and released in v0.1.2: command output goes to the install log, guided mode shows a short plan,
heavyasks about immutable mode, and install prints a count of the rules render left out. Items 1 to 4 (Ubuntu) and 9 and 10 are still open.spydisec commentedon Oct 21, 2026
Triage: items 5 to 8 are fixed in v0.1.2. Items 1, 2, 9, and 10 are clear enough to build. Items 3 and 4 need output from the Ubuntu 22.04 host:
fix: ask about other agents first in guided mode, and name the flag (#50
spydisec commentedon Nov 11, 2026
Checked each open item against v0.5.1. Closing.
akit_acceptsettings were removed, and a refusal printsrefuse=<code> detail=<what to do>.auditctl -sfails there. The text only spoke of the kernel setting, so fix: say that a container can't load audit rules #90 makes it name the container case.audit.ruleswas asked about: no longer a question. Since 0.4.0 install keeps every file it didn't write.-wlines. Nobody has reported a slow host, so this is dropped until someone does.node=prefix: documented indocs/integrations/send-audit-log.md,azure-ama.mdandwazuh.md.fix: say that a container can't load audit rules (#90)