From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Maupertuis Philippe <philippe.maupertuis@equensworldline.com>
Subject: Re: anom messages
Date: Thu, 24 May 2018 12:35:18 -0400 [thread overview]
Message-ID: <10392411.QvQxEpX8uf@x2> (raw)
In-Reply-To: <3D2AB1326AB2974190FCE3F69401F790010BADD2C461@FRVDX103.fr01.awl.atosorigin.net>
Hello,
On Thursday, May 24, 2018 11:06:11 AM EDT Maupertuis Philippe wrote:
> The redhat security guide in annex B2 reads :
> All Audit event types prepended with ANOM are intended to be processed by
> an intrusion detection program. All Audit event types prepended with RESP
> are intended responses of an intrusion detection system in case it detects
> malicious activity on the system.
>
> Can you point me towards an intrusion detection program able to manage
> these audit records.
It is in development but not ready to merge into the audit-userspace repo.
This is why I added some more event types in this area a couple months ago.
It is targeted for the audit-3.1 release along with a bunch of new audit
rules to assist in its job. Audit 3.1 should be late summer or fall of this
year.
-Steve
prev parent reply other threads:[~2018-05-24 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 15:06 anom messages Maupertuis Philippe
2018-05-24 16:35 ` Steve Grubb [this message]
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=10392411.QvQxEpX8uf@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