public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Dan Gruhn <Dan.Gruhn@groupw.com>
Cc: linux-audit@redhat.com
Subject: Re: Central Audit Server with Prelude and Prewikka - RHEL5
Date: Fri, 13 Feb 2009 16:45:38 -0500	[thread overview]
Message-ID: <4995EA02.8060200@groupw.com> (raw)
In-Reply-To: <200902131527.31766.sgrubb@redhat.com>

Steve,

Thanks for the advice.  I was wondering about duplicating those 
information streams and needed the encouragement to go ahead.

One thing that did come up, I changed a lot of "localhost" references in 
the "Audit + Prelude HOWTO" and in the /etc/prelude/default/client.conf 
files to my actual server name (master) and I also changed a line in 
/etc/prelude-manager/prelude-manager.conf from

listen = 127.0.0.1

to

listen = master

All of these changes required me to revoke my old prelude-manager 
registrations under "localhost" and re-register all of the sensors to 
"master".  Perhaps I didn't need all of this but it is all working now 
(except for my 5.2 SELinux problem).

I'm running prelude-lml on the master and I'll be figuring out if I 
should run it on each node or it will pick up everything from the 
master's /var/log/messages file.  I'm thinking it would be better to 
keep things separate but I'll be testing.

If anyone can tell me if some of those "localhost" changes were not 
necessary it would be helpful to know for future reference.  I could 
update the "Audit + Prelude HOWTO" with what I've found and send it to 
back to Steve if that would be useful.

Dan


Steve Grubb wrote:
> On Friday 13 February 2009 03:11:26 pm Dan Gruhn wrote:
>   
>> I'm using Prelude and Prewikka to view events and I see the master as a
>> sensor/source and its events, but I don't see the node.  I thought that
>> once the audit/syslog information was making it to the central files the
>> rest would also work but that doesn't seem to be the case.
>>     
>
> Prelude has its own messaging protocol. It picks things out of its 
> configuration files to fill in various fields in its data packets. So, if you 
> have the audit-prelude sensor reading aggregated logs, it won't know these 
> are coming from all over the place.
>
> To use prelude the way it wants to be setup, you would have the audisp-prelude 
> sensor on each machine sending to a central prelude-manager. Let audit send 
> its data to its aggregator and prelude send its own data to its aggregator. 
> Yes, there will be duplication...but it will work better.
>
> -Steve
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
>   

-- 
Dan Gruhn
Group W Inc.
8315 Lee Hwy, Suite 303
Fairfax, VA, 22031
PH: (703) 752-5831
FX: (703) 752-5851

  reply	other threads:[~2009-02-13 21:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 17:01 Remote audit clients on RHEL 5.2 Dan Gruhn
2009-02-12 17:43 ` Steve Grubb
2009-02-12 17:48   ` Dan Gruhn
2009-02-13 20:11     ` Central Audit Server with Prelude and Prewikka - RHEL5 Dan Gruhn
2009-02-13 20:27       ` Steve Grubb
2009-02-13 21:45         ` Dan Gruhn [this message]
     [not found]     ` <200902121338.50329.sgrubb@redhat.com>
2009-02-17 18:43       ` Remote audit clients on RHEL 5.2 Dan Gruhn

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=4995EA02.8060200@groupw.com \
    --to=dan.gruhn@groupw.com \
    --cc=linux-audit@redhat.com \
    /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