From: Gabriel Alford <ralford@redhat.com>
To: linux-audit@redhat.com, Juan Osorio Robles <josorior@redhat.com>
Subject: auditing audispd vs kubernetes daemonsets
Date: Fri, 10 Apr 2020 14:39:37 -0600 [thread overview]
Message-ID: <CAOxyEpno-VdVb3sqX8q7hGX7L3fgEOLpf9j25u_o+mcezZ+EBg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 835 bytes --]
Hello,
In the midst of discussing sending audit logs from a Red Hat CoreOS node to
some central audit collection and evaluation tool, the question came up
about using audispd instead of Daemonsets. Daemonsets are what is planned
for OpenShift. As I understand it, the general principle is to allow
auditing to flow through the subsystem, but does it need to flow through
the entire auditing workflow? Can a Daemonset be used instead of audispd,
or are there reasons audispd should be used over a Daemonset that some of
us just aren't aware of?
Thanks,
Gabriel Alford
Member of the technical staff
office of the chief technologist
red hat Public Sector
Red Hat
<https://www.redhat.com>
ralford@redhat.com T: 972-707-6483 <650-254-4391> M: 303-550-7234
<https://red.ht/sig> <https://red.ht/sig>
[-- Attachment #1.2: Type: text/html, Size: 2744 bytes --]
[-- Attachment #2: Type: text/plain, Size: 102 bytes --]
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next reply other threads:[~2020-04-13 2:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 20:39 Gabriel Alford [this message]
2020-04-13 13:57 ` auditing audispd vs kubernetes daemonsets Steve Grubb
2020-04-13 16:00 ` Lenny Bruzenak
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=CAOxyEpno-VdVb3sqX8q7hGX7L3fgEOLpf9j25u_o+mcezZ+EBg@mail.gmail.com \
--to=ralford@redhat.com \
--cc=josorior@redhat.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;
as well as URLs for NNTP newsgroup(s).