From: Matt Anderson <mra@hp.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Auditing the TPM
Date: Thu, 03 Jan 2008 18:22:39 -0500 [thread overview]
Message-ID: <477D6E3F.3070209@hp.com> (raw)
In-Reply-To: <200801031639.00244.sgrubb@redhat.com>
Steve Grubb wrote:
> On Thursday 03 January 2008 14:22:45 Matt Anderson wrote:
>> Has anyone in this community begun looking at what TPM events are
>> interesting from an audit perspective?
>
> Not that I know of. No one has contacted me for event types. Are there any
> standards that define what is supposed to be audited?
The Trusted Computing Group spec 1.2 allow for auditing events that the
TPM processes, but it only says that the owner should be able to set
which events get audited and which shouldn't, suggesting "There will be
a very limited number of audited commands, most likely those commands
that provide identities and control of the TPM. Commands such as unseal
would not be audited, they would use the logging functions of a
transport session."
Other than that spec I am unaware of other standards that might be
applicable. I will investigate that further, but if anyone can think of
any please let me know.
-matt
prev parent reply other threads:[~2008-01-03 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 19:22 Auditing the TPM Matt Anderson
2008-01-03 21:39 ` Steve Grubb
2008-01-03 23:22 ` Matt Anderson [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=477D6E3F.3070209@hp.com \
--to=mra@hp.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox