Auditd event cache

Operating Systems Linux Red Hat Auditd event cache

08-12-2010

Registered User

1, 0

Join Date: Aug 2010

Last Activity: 12 August 2010, 5:04 PM EDT

Posts: 1

Thanks Given: 0

Thanked 0 Times in 0 Posts

Auditd event cache

I'm writing an auditd plugin. In my testing, I enabled pam_tty_audit.

After running test data through it, I notice that when logged in as root, the tty events are sent in real time, and not cached in the event queue.

When running as a user, the events are only spit out by the dispatcher (and presumably downstream in the auditd daemon) much later - presumably when the cache is full.

The other difference is the root tty events are sent as individual events, whereas the user events are collected and sent as a single compound event. I've tried various configuration changes, but this behavior seems to be set in stone. Is there a way of forcing the system to send tty events to the plugin in near real time as with root?

tahoekid

View Public Profile for tahoekid

Find all posts by tahoekid

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Trying to customize auditd.cron

Hello all, I'm trying to update auditd.cron to force rotate daily and gzip audit.log.1. I will probably then remove anything older that 3 months. The part I don't like about my script right now is the sleep command. It seems that the "/sbin/service auditd rotate" command must use a different...

2. UNIX for Dummies Questions & Answers

Auditd (How to disable)

I'm running CentOS 5.x and want to disable this daemon as it's crashing my server daily! I didn't install that and don't know why it's started magically for some reason. Please enlighten me to the answer to this question, I've read the man pages on this and found something that stops it...

3. Cybersecurity

Events done on the serial console does not get recorded via the auditd

the events done on the serial console does not get logged. I am using BSM audit. I have enabled all audit flags. Is there anything that im missing? Please help!!

4. Linux

File cache /Page cache Linux

Hi All, could any one point out any open source test-suites for "File cache" testing and as well as performance test suites for the same. Currently my system is up with Linux/ext4. Regards Manish

5. Linux

getting info on Cache Size, Data Cache etc..

Hi all I saw in Microsoft web site www.SysInternals.com a tool called CoreInfo from able to print out on screen the size of the Data and Instruction caches of your processor, the Locigal to Physical Processor mapping, the number of the CPU sockets. etc.. Do you know if in Linux is available a...

6. UNIX for Dummies Questions & Answers

Auditd problem

Hi, I have the following my logs: Nov 20 04:02:04 mail-07 kernel: audit: audit_backlog=326 > audit_backlog_limit=320 Nov 20 04:02:04 mail-07 kernel: audit: audit_lost=4272 audit_rate_limit=0 audit_backlog_limit=320 Nov 20 04:02:04 mail-07 kernel: audit: backlog limit exceeded Nov 20...

7. Red Hat

auditd

Has anyone used, or set up auditd? I want to use it to audit critical system files. Will this be hard, how would I start setting this up? :eek:

8. UNIX for Dummies Questions & Answers

how to disable auditd daemon

I want to disable the auditd daemon on my unix server. Running this daemon on the server causes to system to crash afer every two month. Could any one let me know step by step how to disable it and is there any implication of doing it?

9. UNIX for Advanced & Expert Users

UBC cache vs. Metadata cache

hi, What is the difference between UBC cache and Metadata cache ? where can i find UBC cache Hits and Metadata cache Hits in hp-ux? Advanced thanx for the help.

LEARN ABOUT CENTOS

auditd

AUDITD(8)						  System Administration Utilities						 AUDITD(8)

NAME

       auditd - The Linux Audit daemon

SYNOPSIS

       auditd [-f] [-l] [-n] [-s disable|enable|nochange]

DESCRIPTION

       auditd is the userspace component to the Linux Auditing System. It's responsible for writing audit records to the disk. Viewing the logs is
       done with the ausearch or aureport utilities. Configuring the audit rules is done with the auditctl utility. During startup, the  rules	in
       /etc/audit/audit.rules  are  read  by auditctl and loaded into the kernel. Alterately, there is also an augenrules program that reads rules
       located in /etc/audit/rules.d/ and compiles them into an audit.rules file. The audit daemon itself has some configuration options that  the
       admin may wish to customize. They are found in the auditd.conf file.

OPTIONS

       -f     leave the audit daemon in the foreground for debugging. Messages also go to stderr rather than the audit log.

       -l     allow the audit daemon to follow symlinks for config files.

       -n     no fork. This is useful for running off of inittab or systemd.

       -s=ENABLE_STATE
	      specify when starting if auditd should change the current value for the kernel enabled flag. Valid values for ENABLE_STATE are "dis-
	      able", "enable" or "nochange". The default is to enable (and disable when auditd terminates). The value of the enabled flag  may	be
	      changed during the lifetime of auditd using 'auditctl -e'.

SIGNALS

       SIGHUP causes auditd to reconfigure. This means that auditd re-reads the configuration file. If there are no syntax errors, it will proceed
	      to implement the requested changes. If the reconfigure is successful, a DAEMON_CONFIG event is recorded in the logs. If not success-
	      ful,  error handling is controlled by space_left_action, admin_space_left_action, disk_full_action, and disk_error_action parameters
	      in auditd.conf.

       SIGTERM
	      caused auditd to discontinue processing audit events, write a shutdown audit event, and exit.

       SIGUSR1
	      causes auditd to immediately rotate the logs. It will consult the max_log_size_action to see if it should keep the logs or not.

       SIGUSR2
	      causes auditd to attempt to resume logging. This is usually needed after logging has been suspended.

FILES

       /etc/audit/auditd.conf - configuration file for audit daemon

       /etc/audit/audit.rules - audit rules to be loaded at startup

       /etc/audit/rules.d/ - directory holding individual sets of rules to be compiled into one file by augenrules.

NOTES

       A boot param of audit=1 should be added to ensure that all processes that run before the audit daemon starts is marked as auditable by  the
       kernel. Not doing that will make a few processes impossible to properly audit.

       The  audit  daemon  can	receive audit events from other audit daemons via the audisp-remote audispd plugin. The audit daemon may be linked
       with tcp_wrappers to control which machines can connect. If this is the case, you can add an entry to hosts.allow and deny.

SEE ALSO

       auditd.conf(5), audispd(8), ausearch(8), aureport(8), auditctl(8), augenrules(8), audit.rules(7).

AUTHOR

       Steve Grubb

Red Hat 							     Sept 2013								 AUDITD(8)

Red Hat