Skip to content

Guided install: findings from v0.1.1 tests on Rocky 10 and Ubuntu 22.04 #45

Closed

Description

@spydisec

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 heavy profile. It installed, and every verify check passed.
  • Ubuntu 22.04 with auditd 3.0.7 and a Wazuh agent, choosing medium and UDP forwarding. It was refused.

Ubuntu 22.04: refused only after every question

  1. 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:wazuh and 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]".
  2. The override text doesn't say how to pass it. override=akit_accept_agents names the setting, but not the flag (--accept-agents wazuh) or the value. Someone using the one-liner has to guess sh -s -- --accept-agents wazuh.
  3. 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 said support_tier=supported, and install would have failed or rolled back after the refusal was overridden. Survey should report container hosts (for example with systemd-detect-virt --container), and preflight should refuse them.
  4. Find out why Ubuntu's audit.rules was offered for keep or replace. On Rocky, the distro's defaults-only audit.rules is 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

  1. The output floods the screen. augenrules --load printed 114 lines of "Old style watch rules are slower" and "perm used without an arch is slower". auditctl -s was 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.
  2. 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-run for the full diff.
  3. Guided mode doesn't ask about immutable mode for heavy. CIS and STIG expect -e 2, and heavy is the compliance profile. When heavy is chosen, ask whether to lock the rules until reboot, and say that any later rule change, including rollback, then needs a reboot.
  4. 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 yum symlink. They're listed only in /var/lib/auditd-kit/render-report.txt. Print one line with the count and the report path.
  5. Measure the cost of watch rules and path rules without an arch. auditctl's warnings point at a real cost. -w watches 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.
  6. Document the node= prefix. Install sets name_format = hostname, so every audit log line starts with node=<hostname>. That's on purpose, but a SIEM parser that expects lines to start with type= 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.

Activity

  1. spydisec commented on Oct 21, 2026

    @spydisec
    OwnerAuthor

    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, heavy asks 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.

  2. added
    needs-infoWaiting on reporter for more information
    and removed
    needs-triageMaintainer needs to evaluate this issue
    on Oct 21, 2026
  3. spydisec commented on Oct 21, 2026

    @spydisec
    OwnerAuthor

    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:

    systemd-detect-virt; systemd-detect-virt --container   # item 3: VM or container?
    cat /etc/audit/rules.d/audit.rules                      # item 4: why it was asked about
    grep -n whodata /var/ossec/etc/ossec.conf               # does Wazuh use auditd (see #47)?
    auditctl -l | grep -ci wazuh
  4. spydisec commented on Nov 11, 2026

    @spydisec
    OwnerAuthor

    Checked each open item against v0.5.1. Closing.

    • 1, refusals after the questions: fixed in 0.4.0 (feat!: replace the survey with a host check #74). Guided mode runs the host check first and stops before any question.
    • 2, the override text: gone in 0.4.0. The akit_accept settings were removed, and a refusal prints refuse=<code> detail=<what to do>.
    • 3, containers: install already refuses a container, because auditctl -s fails 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.
    • 4, Ubuntu's audit.rules was asked about: no longer a question. Since 0.4.0 install keeps every file it didn't write.
    • 5 to 8: fixed in v0.1.2 (fix: make guided install output short, and ask about immutable for heavy #46).
    • 9, the cost of watch rules without an arch: not done. The rules still hold 86 -w lines. Nobody has reported a slow host, so this is dropped until someone does.
    • 10, the node= prefix: documented in docs/integrations/send-audit-log.md, azure-ama.md and wazuh.md.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-infoWaiting on reporter for more information

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions