From: Steve Grubb <sgrubb@redhat.com>
To: Warron S French <warron.s.french@aero.org>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: audit-tools and SUDO
Date: Tue, 10 May 2016 10:31:03 -0400 [thread overview]
Message-ID: <2247443.0y4SDndMu0@x2> (raw)
In-Reply-To: <BY1PR09MB088792A33B5B6AAFF5D8AE48C7710@BY1PR09MB0887.namprd09.prod.outlook.com>
On Tuesday, May 10, 2016 01:44:50 PM Warron S French wrote:
> > > I have two problems though; and they seem somewhat minor:
> > >
> > > 1. The audit events being captured don’t seem to be tied to any
> > > given node (so that I can perform ausearch --node hostName, or
> > > aureport), that’s the first issue.
> >
> >
> > What have you set the configuration parameter 'name_format'
> > in /etc/audit/auditd.conf to?
> >
> > One assumes you may want to set
> > name_format = fqd
> > or
> > name_format = hostname
> >
> > After the change on each host, don't forget to reload the
> > configuration with either a sighup on the auditd process or just restart
> > the service.
>
> On the lab-clients ends:
> In, and ONLY IN, my /etc/audisp/audispd.conf file have I set
> name_format=hostname, where hostname is a literal string of 'hostname' not
> THE hostname;
This is correct. Did you set remote_server in /etc/audisp/audisp-remote.conf?
> there is no name_format reference in any other file on my
> lab-client machines under the directory /etc/audisp/ anywhere. Also on my
> lab-client machines in the /etc/audit/auditd.conf file the name_format
> variable is set to NONE.
>
> On the lab-server end:
> In the only file that I modified, /etc/audit/auditd.conf, the only variables
> that I altered were:
> tcp_listen_port = 60
> tcp_client_ports = 60
> use_libwrap = no (because I am using iptables)
You would want to set name_format. This way the local events on the
aggregating server have the same format.
> The lab works as expected, but my production environment does not. %-/
I would start by checking that events are coming out of the remote systems.
You can use tcpdump port 60 on the clients. After confirming that, do the same
on the server to see if events are getting there. Then look in syslog for
anything that might give a clue. And then you can also tail -f
/var/log/audit/audit.log to see if things are getting written to disk.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2016-05-10 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 12:31 audit-tools and SUDO Warron S French
2016-05-10 12:52 ` Burn Alting
2016-05-10 13:07 ` Warron S French
2016-05-10 13:25 ` Steve Grubb
2016-05-10 13:44 ` Warron S French
2016-05-10 14:31 ` Steve Grubb [this message]
2016-05-10 15:25 ` Warron S French
2016-05-10 15:45 ` Steve Grubb
2016-05-10 17:46 ` Warron S French
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2247443.0y4SDndMu0@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=warron.s.french@aero.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox