Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Maupertuis Philippe <philippe.maupertuis@equensworldline.com>
Subject: Re: Auditing console access
Date: Wed, 06 Sep 2017 14:12:44 -0400	[thread overview]
Message-ID: <1987898.q18JgGjdTj@x2> (raw)
In-Reply-To: <3D2AB1326AB2974190FCE3F69401F7900102F358B6BA@FRVDX103.fr01.awl.atosorigin.net>

On Wednesday, September 6, 2017 9:42:53 AM EDT Maupertuis Philippe wrote:
> Hi,
> The examples found in the audit documentation mention that to work it is
> assumed that no direct root login is allowed. This very sensible and not a
> big problem except for console access.

Why is it a problem for console access?  :-)

> What would be the best way to monitor what is done through this access ?

If you need to know the commands & changes made by root, then you probably 
need to use pam_tty_audit to enable tty auditing for su and sudo.

> Would you recommend to forbid root access even in console ?

Yes. Who is root? Who was root 4 years ago? By logging in with your account 
and then changing to root, the audit system can track who root is. The only 
time I can think of where you wouldn't want this tracking is when the system 
is in single user mode. (Because auditd doesn't normally start in single user 
mode.)
 
-Steve

> !!!*************************************************************************
> ************ "Ce message et les pi?ces jointes sont confidentiels et
> r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre
> prot?g? par le secret professionnel. Si vous recevez ce message par erreur,
> merci d'en avertir imm?diatement l'exp?diteur et de le d?truire.
> L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la
> responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de
> ce message. Bien que les meilleurs efforts soient faits pour maintenir
> cette transmission exempte de tout virus, l'exp?diteur ne donne aucune
> garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour
> tout dommage r?sultant d'un virus transmis.
> 
> This e-mail and the documents attached are confidential and intended solely
> for the addressee; it may also be privileged. If you receive this e-mail in
> error, please notify the sender immediately and destroy it. As its
> integrity cannot be secured on the Internet, the Worldline liability cannot
> be triggered for the message content. Although the sender endeavours to
> maintain a computer virus-free network, the sender does not warrant that
> this transmission is virus-free and will not be liable for any damages
> resulting from any virus transmitted.!!!"

  reply	other threads:[~2017-09-06 18:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-06 13:42 Auditing console access Maupertuis Philippe
2017-09-06 18:12 ` Steve Grubb [this message]
2017-09-07  8:04   ` Maupertuis Philippe
2017-09-07 18:23     ` 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=1987898.q18JgGjdTj@x2 \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=philippe.maupertuis@equensworldline.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