linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Gabriel Alford <ralford@redhat.com>,
	Juan Osorio Robles <josorior@redhat.com>
Subject: Re: auditing audispd vs kubernetes daemonsets
Date: Mon, 13 Apr 2020 09:57:58 -0400	[thread overview]
Message-ID: <4644525.9UYIb4EAcv@x2> (raw)
In-Reply-To: <CAOxyEpno-VdVb3sqX8q7hGX7L3fgEOLpf9j25u_o+mcezZ+EBg@mail.gmail.com>

On Friday, April 10, 2020 4:39:37 PM EDT Gabriel Alford wrote:
> 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? 

I'd say that if you ask 10 people on this list, you may find 10 different ways 
they are doing it. It really depends on your requirements. Some places care 
that you don't mix security officer and system admin roles. (Security Officer may 
have a system admin under investigation.) In that case, you have to keep the 
logs separate and this is likely to a MLS system. Other, less demanding 
sites, don't care because they are one in the same. They send audit logs into 
syslog and then pick it apart later. And then there are some tools that have 
their own audisp plugin and transport the logs themselves.

> 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?

Entirely up to the system architect and their security requirements.

-Steve


--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit


  reply	other threads:[~2020-04-13 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 20:39 auditing audispd vs kubernetes daemonsets Gabriel Alford
2020-04-13 13:57 ` Steve Grubb [this message]
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=4644525.9UYIb4EAcv@x2 \
    --to=sgrubb@redhat.com \
    --cc=josorior@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=ralford@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).