From: Steve Grubb <sgrubb@redhat.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>, linux-audit@redhat.com
Subject: Re: Repository of audit events
Date: Fri, 11 Apr 2014 10:07:20 -0400 [thread overview]
Message-ID: <1667762.7KL3TunczQ@x2> (raw)
In-Reply-To: <1397187375.21461.2.camel@dhcp-9-2-203-236.watson.ibm.com>
Hi Mimi,
On Thursday, April 10, 2014 11:36:15 PM Mimi Zohar wrote:
> On Wed, 2014-04-09 at 18:26 -0700, Peter Moody wrote:
> > On Wed, Apr 09 2014 at 10:19, Steve Grubb wrote:
> > > Missing INTEGRITY_RULE
> >
> > IMA with an 'audit' rule generates INTEGRITY_RULE messages.
For those of us not really up on IMA and just want to generate the event to
add to our collection, any tips on doing this?
> > Missing INTEGRITY_DATA
>
> Failure to collect or appraise file data.
> (Requires the filesystem to be labeled w/security.ima and integrity
> appraisal enabled.)
How would I cause this event to be generated if I wanted to see it?
> > Missing INTEGRITY_HASH
>
> Not used.
OK, I'll mark that deprecated.
> > Missing INTEGRITY_METADATA
>
> Before updating/removing 'security.evm' the xattr or modifying file
> metadata included in the HMAC calculation(eg. i_ino, i_uid, i_gid,
> i_mode, FSUUID, i_generation), EVM verifies the existing value.
> (Requires the filesystem to be labeled w/security.evm and integrity
> appraisal enabled.)
How to get it?
> > Missing INTEGRITY_STATUS
>
> Errors related to the IMA policy.
How to get it?
Thanks,
-Steve
next prev parent reply other threads:[~2014-04-11 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 6:25 Repository of audit events Burn Alting
2014-04-09 16:32 ` Eric Paris
2014-04-09 16:33 ` lists_todd
2014-04-09 17:19 ` Steve Grubb
2014-04-10 0:16 ` Burn Alting
2014-04-10 1:26 ` Peter Moody
2014-04-11 3:36 ` Mimi Zohar
2014-04-11 14:07 ` Steve Grubb [this message]
2014-04-11 15:26 ` Mimi Zohar
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=1667762.7KL3TunczQ@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=zohar@linux.vnet.ibm.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