From: Blibbet <blibbet@gmail.com>
To: chipsec@lists.01.org
Subject: Re: SCAP reporting support for CHIPSEC
Date: Fri, 31 Jul 2015 09:07:30 -0700 [thread overview]
Message-ID: <55BB9D42.6030608@gmail.com> (raw)
In-Reply-To: <55B66C5F.6060809@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
On 07/27/2015 10:37 AM, Blibbet wrote:
...
> I'd like to use this sort of information as machine-readable SCAP XML,
> so CHIPSEC output can be fed into current enterprise CM/SIEM solutions.
> Then, the question of what format is more of needing SCAP OVAL
> definitions for Intel HW/FW assets, and then SCAP ARF-based report
> plugin for CHIPSEC.
>
> SCAP isn't needed for security researcher usage of CHIPSEC. BUT IMO,
> SCAP would be very useful for system administrator's use of CHIPSEC, but
> I'm not sure anyone is asking yet.
Ah, they *ARE* asking:
http://security.stackexchange.com/questions/46941/can-a-vulnerability-management-tool-highlight-bios-and-driver-level-vulnerabilit
prev parent reply other threads:[~2015-07-31 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 17:37 SCAP reporting support for CHIPSEC Blibbet
2015-07-31 16:07 ` Blibbet [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=55BB9D42.6030608@gmail.com \
--to=blibbet@gmail.com \
--cc=chipsec@lists.01.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).