From: Steve Grubb <sgrubb@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: zohar@linux.vnet.ibm.com, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-audit@redhat.com
Subject: Re: [PATCH 8/8] ima: Differentiate auditing policy rules from "audit" actions
Date: Wed, 30 May 2018 11:15:29 -0400 [thread overview]
Message-ID: <15281606.YptaXzsEVL@x2> (raw)
In-Reply-To: <2d5baf73-755b-dc82-a778-25a3cd22989a@linux.vnet.ibm.com>
On Wednesday, May 30, 2018 9:54:00 AM EDT Stefan Berger wrote:
> On 05/29/2018 05:30 PM, Steve Grubb wrote:
> > Hello,
> >
> > On Thursday, May 24, 2018 4:11:05 PM EDT Stefan Berger wrote:
> >> The AUDIT_INTEGRITY_RULE is used for auditing IMA policy rules and
> >> the IMA "audit" policy action. This patch defines
> >> AUDIT_INTEGRITY_POLICY_RULE to reflect the IMA policy rules.
> >>
> >> With this change we now call integrity_audit_msg_common() to get
> >> common integrity auditing fields. This now produces the following
> >> record when parsing an IMA policy rule:
> >>
> >> type=UNKNOWN[1806] msg=audit(1527004216.690:311): action=dont_measure \
> >>
> >> fsmagic=0x9fa0 pid=1613 uid=0 auid=0 ses=2 \
> >> subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 \
> >> op=policy_update cause=parse_rule comm="echo" exe="/usr/bin/echo" \
> >> tty=tty2 res=1
> >
> > Since this is a new event, do you mind moving the tty field to be between
> > auid= and ses= ? That is the more natural place for it.
>
> 6/8 refactors the code so that the integrity audit records produced by
> IMA follow one format in terms of ordering of the fields, with fields
> like inode optional, though, and AUDIT_INTEGRITY_RULE in the end being
> the only one with a different format. Do we really want to change that
> order just for 1806?
>
> 5/8 now produces the following:
>
> type=INTEGRITY_PCR msg=audit(1527685075.941:502): pid=2431 \
> uid=0 auid=1000 ses=5 \
> subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 \
> op=invalid_pcr cause=open_writers comm="grep" \
> name="/var/log/audit/audit.log" dev="dm-0" ino=1962494 \
> exe="/usr/bin/grep" tty=pts0 res=1
>
> Comparing the two:
>
> 1806: action, fsmagic, pid, uid, auid, ses, subj, op, cause,
> comm, exe, tty, res
> INTEGRITY_PCR: pid, uid, auid, ses, subj, op, cause,
> comm, name, dev, ino, exe, tty, res
OK. I guess go with it as is. It passes testing.
-Steve
> > Also, it might be more natural for the op= and cause= fields to be before
> > the pid= portion. This doesn't matter as much to me because those are
> > not searchable fields and they are skipped right over. But moving the
> > tty field is the main comment from me.
>
> With the refactoring in 6/8 we at least have consistency among the
> INTEGRITY_* records, with the only exception being AUDIT_INTEGRITY_RULE
> that has its own format:
>
> https://elixir.bootlin.com/linux/latest/source/security/integrity/ima/ima_a
> pi.c#L324
>
> The other ones currently all format using integrity_audit_msg().
>
> > Thanks,
> > -Steve
> >
> >> Signed-off-by: Stefan Berger<stefanb@linux.vnet.ibm.com>
> >> ---
> >>
> >> include/uapi/linux/audit.h | 3 ++-
> >> security/integrity/ima/ima_policy.c | 5 +++--
> >> 2 files changed, 5 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/include/uapi/linux/audit.h b/include/uapi/linux/audit.h
> >> index 4e61a9e05132..776e0abd35cf 100644
> >> --- a/include/uapi/linux/audit.h
> >> +++ b/include/uapi/linux/audit.h
> >> @@ -146,7 +146,8 @@
> >>
> >> #define AUDIT_INTEGRITY_STATUS 1802 /* Integrity enable status */
> >> #define AUDIT_INTEGRITY_HASH 1803 /* Integrity HASH type */
> >> #define AUDIT_INTEGRITY_PCR 1804 /* PCR invalidation msgs */
> >>
> >> -#define AUDIT_INTEGRITY_RULE 1805 /* policy rule */
> >> +#define AUDIT_INTEGRITY_RULE 1805 /* IMA "audit" action policy msgs
> >> */ +#define AUDIT_INTEGRITY_POLICY_RULE 1806 /* IMA policy rules */
> >>
> >> #define AUDIT_KERNEL 2000 /* Asynchronous audit record. NOT A
> >
> > REQUEST. */
> >
> >> diff --git a/security/integrity/ima/ima_policy.c
> >> b/security/integrity/ima/ima_policy.c index 3aed25a7178a..a8ae47a386b4
> >> 100644
> >> --- a/security/integrity/ima/ima_policy.c
> >> +++ b/security/integrity/ima/ima_policy.c
> >> @@ -634,7 +634,7 @@ static int ima_parse_rule(char *rule, struct
> >> ima_rule_entry *entry) int result = 0;
> >>
> >> ab = integrity_audit_log_start(NULL, GFP_KERNEL,
> >>
> >> - AUDIT_INTEGRITY_RULE);
> >> + AUDIT_INTEGRITY_POLICY_RULE);
> >>
> >> entry->uid = INVALID_UID;
> >> entry->fowner = INVALID_UID;
> >>
> >> @@ -926,7 +926,8 @@ static int ima_parse_rule(char *rule, struct
> >> ima_rule_entry *entry) temp_ima_appraise |= IMA_APPRAISE_FIRMWARE;
> >>
> >> else if (entry->func == POLICY_CHECK)
> >>
> >> temp_ima_appraise |= IMA_APPRAISE_POLICY;
> >>
> >> - audit_log_format(ab, "res=%d", !result);
> >> + integrity_audit_msg_common(ab, NULL, NULL,
> >> + "policy_update", "parse_rule", result);
> >>
> >> audit_log_end(ab);
> >> return result;
> >>
> >> }
next prev parent reply other threads:[~2018-05-30 15:15 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 20:10 [PATCH 0/8] IMA: work on audit records produced by IMA Stefan Berger
2018-05-24 20:10 ` [PATCH 1/8] ima: Call audit_log_string() rather than logging it untrusted Stefan Berger
2018-05-29 20:29 ` Paul Moore
2018-05-24 20:10 ` [PATCH 2/8] ima: Use audit_log_format() rather than audit_log_string() Stefan Berger
2018-05-29 20:31 ` Paul Moore
2018-05-24 20:11 ` [PATCH 3/8] audit: Implement audit_log_tty() Stefan Berger
2018-05-29 21:07 ` Paul Moore
2018-05-30 19:46 ` Stefan Berger
2018-05-24 20:11 ` [PATCH 4/8] audit: Allow others to call audit_log_d_path_exe() Stefan Berger
2018-05-29 21:18 ` Paul Moore
2018-05-24 20:11 ` [PATCH 5/8] integrity: Add exe= and tty= before res= to integrity audits Stefan Berger
2018-05-29 21:19 ` Paul Moore
2018-05-29 21:35 ` Steve Grubb
2018-05-29 21:47 ` Paul Moore
2018-05-29 22:58 ` Mimi Zohar
2018-05-30 13:04 ` Mimi Zohar
2018-05-30 21:15 ` Paul Moore
2018-05-30 12:17 ` Stefan Berger
2018-05-30 21:14 ` Paul Moore
2018-05-24 20:11 ` [PATCH 6/8] integrity: Factor out common part of integrity_audit_msg() Stefan Berger
2018-05-29 21:32 ` Steve Grubb
2018-05-30 13:04 ` Stefan Berger
2018-05-24 20:11 ` [PATCH 7/8] ima: Do not audit if CONFIG_INTEGRITY_AUDIT is not set Stefan Berger
2018-05-24 20:11 ` [PATCH 8/8] ima: Differentiate auditing policy rules from "audit" actions Stefan Berger
2018-05-29 21:30 ` Steve Grubb
[not found] ` <2d5baf73-755b-dc82-a778-25a3cd22989a@linux.vnet.ibm.com>
2018-05-30 15:15 ` Steve Grubb [this message]
2018-05-30 15:25 ` Stefan Berger
2018-05-30 16:27 ` Steve Grubb
2018-05-30 19:54 ` Stefan Berger
2018-05-30 21:24 ` Paul Moore
2018-05-30 21:49 ` Stefan Berger
2018-05-30 22:00 ` Mimi Zohar
2018-05-30 22:15 ` Stefan Berger
2018-05-30 22:41 ` Mimi Zohar
2018-05-30 23:54 ` Paul Moore
2018-05-30 12:49 ` Richard Guy Briggs
2018-05-30 12:55 ` Steve Grubb
2018-05-30 13:08 ` Stefan Berger
2018-05-30 21:22 ` Paul Moore
2018-05-30 21:38 ` Stefan Berger
2018-05-30 23:34 ` Richard Guy Briggs
2018-06-01 20:00 ` Stefan Berger
2018-06-01 20:13 ` Paul Moore
2018-06-01 20:21 ` Paul Moore
2018-06-01 20:50 ` Stefan Berger
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=15281606.YptaXzsEVL@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanb@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).