From: Joe Wulf <joe_wulf@yahoo.com>
To: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: New draft standards
Date: Mon, 14 Dec 2015 16:38:23 +0000 (UTC) [thread overview]
Message-ID: <1459913744.767260.1450111103969.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <1736195.o09BuzvBta@x2>
[-- Attachment #1.1: Type: text/plain, Size: 795 bytes --]
Steve,
The last place I was at heavily used Splunk and then transitioned to dual-routing a substantial portion of the logs from across the infrastructure to ELK, as well.
-Joe
From: Steve Grubb <sgrubb@redhat.com>
To: F Rafi <farhanible@gmail.com>; "linux-audit@redhat.com" <linux-audit@redhat.com>
Sent: Monday, December 14, 2015 10:34 AM
Subject: Re: New draft standards
But I guess this gives me an opportunity to ask the community what tools they
are using for audit log collection and viewing? Its been a couple years since
e had this discussion on the mail list and I think some things have changed.
Do people use ELK?
Apache Flume?
Something else?
It might be possible to write a plugin to translate the audit logs into the
native format of these tools.
-Steve
[-- Attachment #1.2: Type: text/html, Size: 2813 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-12-14 16:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 19:22 New draft standards Steve Grubb
2015-12-08 19:58 ` Paul Moore
2015-12-08 20:25 ` Steve Grubb
2015-12-09 0:28 ` Paul Moore
2015-12-09 1:43 ` Burn Alting
2015-12-10 22:49 ` Steve Grubb
2015-12-10 22:59 ` Paul Moore
2015-12-15 5:11 ` Richard Guy Briggs
2015-12-10 4:35 ` Steve Grubb
2015-12-10 16:50 ` Paul Moore
2015-12-10 17:40 ` F Rafi
2015-12-14 15:34 ` Steve Grubb
2015-12-14 16:38 ` Joe Wulf [this message]
2015-12-14 17:01 ` Kevin.Dienst
2015-12-14 22:12 ` Burn Alting
2015-12-15 13:46 ` Steve Grubb
2015-12-18 5:12 ` Burn Alting
2015-12-23 22:44 ` Burn Alting
2015-12-26 16:38 ` Steve Grubb
2015-12-27 0:30 ` Burn Alting
2015-12-27 15:06 ` Steve Grubb
2015-12-28 7:24 ` Burn Alting
2015-12-29 19:28 ` LC Bruzenak
2015-12-08 20:49 ` Richard Guy Briggs
2015-12-08 21:28 ` Steve Grubb
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=1459913744.767260.1450111103969.JavaMail.yahoo@mail.yahoo.com \
--to=joe_wulf@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.