All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Auditing Logons/Logoffs
Date: Fri, 14 Jul 2017 16:46:16 -0400	[thread overview]
Message-ID: <3128112.AezCZUyPye@x2> (raw)
In-Reply-To: <CAJdJdQ=1MK7wiJSY7zZirKkhye63RccFwXf7v=YqFJP5kkQMLg@mail.gmail.com>

On Friday, July 14, 2017 3:51:16 PM EDT warron.french wrote:
> Back to this again, as I thought my coworker had addressed it months ago,
> but he did not as I cannot find anything.
> 
> *THE_SUBJECT*: Auditing Logons and Logoffs (success/failures)
>
> I am aware of the following files:
> /var/log/faillog, and
> /var/log/lastlog
> 
> The following link is relevant to RHEL5 (maybe 6 and 7??):
> https://www.stigviewer.com/stig/oracle_linux_5/2015-12-07/finding/V-818
> 
> Is there an appropriate syscall for handling *THE_SUBJECT*?

Nope. This is hardwired into the applications. There is a specification here:

https://github.com/linux-audit/audit-documentation/wiki/SPEC-User-Login-Lifecycle-Events

That explains each event that is part of the login and logout and its meaning.

> Do I use the syntax as advised in the link provided at stigviewer.com?

Nope. Its hardwired. As long as audit is enabled, you'll get them.

-Steve

> We are dealing with systems that do tie into IPA, but have to ensure
> *THE_SUBJECT* is being addressed and forwarded.
> 
> I have to support both RHEL6 and RHEL7.
> 
> 
> Thanks in advance,
> --------------------------
> Warron French

  reply	other threads:[~2017-07-14 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 19:51 Auditing Logons/Logoffs warron.french
2017-07-14 20:46 ` Steve Grubb [this message]
     [not found]   ` <CAJdJdQmJb44ZwCWYxR9Cry9XddsqwR5_F5cbLyjTeDF7iVs0mQ@mail.gmail.com>
2017-07-17 15:26     ` 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=3128112.AezCZUyPye@x2 \
    --to=sgrubb@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 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.