From: Mimi Zohar <zohar@linux.ibm.com>
To: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
stephen.smalley.work@gmail.com, casey@schaufler-ca.com
Cc: tyhicks@linux.microsoft.com, sashal@kernel.org,
jmorris@namei.org, linux-integrity@vger.kernel.org,
selinux@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/4] LSM: Measure security module data
Date: Wed, 05 Aug 2020 08:00:33 -0400 [thread overview]
Message-ID: <1624d016e4110cf903e4b3d22f253edc34c6b39c.camel@linux.ibm.com> (raw)
In-Reply-To: <20200805004331.20652-1-nramas@linux.microsoft.com>
On Tue, 2020-08-04 at 17:43 -0700, Lakshmi Ramasubramanian wrote:
> Critical data structures of security modules are currently not measured.
> Therefore an attestation service, for instance, would not be able to
> attest whether the security modules are always operating with the policies
> and configuration that the system administrator had setup. The policies
> and configuration for the security modules could be tampered with by
> malware by exploiting kernel vulnerabilities or modified through some
> inadvertent actions on the system. Measuring such critical data would
> enable an attestation service to better assess the state of the system.
From a high level review, "Critical data structures" should be the
focus of this patch set. Measuring "critical data structures" should
be independent of measuring the "policy" being loaded. The in memory
policy hash could be an example of data included in the "critical data
structures".
Keep this patch set simple.
Mimi
prev parent reply other threads:[~2020-08-05 19:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 0:43 [PATCH v6 0/4] LSM: Measure security module data Lakshmi Ramasubramanian
2020-08-05 0:43 ` [PATCH v6 1/4] IMA: Add func to measure LSM state and policy Lakshmi Ramasubramanian
2020-08-05 3:25 ` Mimi Zohar
2020-08-05 12:46 ` Stephen Smalley
2020-08-05 12:56 ` Mimi Zohar
2020-08-05 13:03 ` Stephen Smalley
2020-08-05 13:19 ` Mimi Zohar
2020-08-05 14:27 ` Stephen Smalley
2020-08-05 15:07 ` Tyler Hicks
2020-08-05 15:43 ` Stephen Smalley
2020-08-05 16:45 ` John Johansen
2020-08-05 15:17 ` Mimi Zohar
2020-08-05 0:43 ` [PATCH v6 2/4] IMA: Define IMA hooks " Lakshmi Ramasubramanian
2020-08-05 0:43 ` [PATCH v6 3/4] LSM: Define SELinux function to measure " Lakshmi Ramasubramanian
2020-08-05 0:43 ` [PATCH v6 4/4] IMA: Handle early boot data measurement Lakshmi Ramasubramanian
2020-08-05 1:04 ` [PATCH v6 0/4] LSM: Measure security module data Casey Schaufler
2020-08-05 1:14 ` Lakshmi Ramasubramanian
2020-08-05 15:36 ` Casey Schaufler
2020-08-05 15:45 ` Tyler Hicks
2020-08-05 16:07 ` Lakshmi Ramasubramanian
2020-08-05 16:14 ` Tyler Hicks
2020-08-05 16:21 ` Lakshmi Ramasubramanian
2020-08-05 16:32 ` Tyler Hicks
2020-08-05 17:31 ` Casey Schaufler
2020-08-05 17:03 ` Mimi Zohar
2020-08-05 17:25 ` Lakshmi Ramasubramanian
2020-08-05 17:57 ` Casey Schaufler
2020-08-05 18:08 ` Lakshmi Ramasubramanian
2020-08-05 18:25 ` Casey Schaufler
2020-08-12 20:37 ` Lakshmi Ramasubramanian
2020-08-05 12:37 ` Mimi Zohar
2020-08-05 12:00 ` Mimi Zohar [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=1624d016e4110cf903e4b3d22f253edc34c6b39c.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nramas@linux.microsoft.com \
--cc=sashal@kernel.org \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=tyhicks@linux.microsoft.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).