Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-5197

Audit rules for /proc are not loaded on boot

    • audit-3.1.5-1.el9
    • None
    • Important
    • 2
    • rhel-sst-security-special-projects
    • ssg_security
    • 26
    • None
    • QE ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • SECENGSP Cycle 6, SECENGSP Cycle 7
    • Bug Fix
    • Hide
      .Audit rules for `/proc` are now correctly loaded during the boot

      Before this update, the system failed to load Audit watch rules for the `/proc` directory during the boot phase. Consequently, the administrator had to load the rules manually later, and the rules were not applied during the boot. The bug has been fixed, and the system now loads the Audit rules related to `/proc` during the boot phase.
      Show
      .Audit rules for `/proc` are now correctly loaded during the boot Before this update, the system failed to load Audit watch rules for the `/proc` directory during the boot phase. Consequently, the administrator had to load the rules manually later, and the rules were not applied during the boot. The bug has been fixed, and the system now loads the Audit rules related to `/proc` during the boot phase.
    • Done
    • None

      Description of problem:

      Audit rules for "-F dir=/proc" fails to load on boot, the rules works if loaded manually later.
      This behavior differs from RHEL 7 (the rules for /proc are loaded correctly on boot)

      Version-Release number of selected component (if applicable):

      audit-3.0.7-101.el9_0.2.x86_64

      How reproducible:

      Always

      Steps to Reproduce:
      1. # vi /etc/audit/rules.d/test.rules
      -a never,exit -F arch=b32 -F dir=/proc -S fchmodat
      2. # reboot
      3. # auditctl -l

      Actual results:

      1. auditctl -l
        No rules.

      Expected results:

      1. auditctl -l
        -a never,exit -F arch=b32 -S fchmodat -F dir=/proc

      Additional info:

      The list of syscalls is actually quite extensive, the same behavior occurs with any syscall we tested, it does not occur if we use a different "-F dir=" value, this behavior is only present on /proc so far.
      Another detail, if we run auditd with -f, we can see below log record on system boot's journal:

      auditd[xxx]: type=CONFIG_CHANGE msg=audit(xxxxxxxxxx.xxx:xxx): op=remove_rule dir="/proc" key=(null) list=4 res=1

      Juan Gamba
      Principal Technical Support Engineer
      Red Hat - Support Delivery

              rh-ee-alakatos Attila Lakatos
              rhn-support-jgamba Juan Gamba
              Sergio Correia Sergio Correia
              Natália Bubáková Natália Bubáková
              Mirek Jahoda Mirek Jahoda
              Votes:
              0 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: