From: Blibbet <blibbet@gmail.com>
To: chipsec@lists.01.org
Subject: SCAP reporting support for CHIPSEC
Date: Mon, 27 Jul 2015 10:37:35 -0700 [thread overview]
Message-ID: <55B66C5F.6060809@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]
Hijacking one of John's comments on Debian packaging:
> [...] we should probably print some shorter and more friendly output.
Perhaps
> something more like "Protection Found"/"Possible
Vulnerability"/"Manual Assessment
> Needed"?
>
> BIOS Write Protection: Possible Vulnerability
> SMI Suppression: Possible Vulnerability
> Compatibility SMRAM Lock: Protection Found
> SMM Cache Poisoning: Protection Found
> UEFI Variables: Manual Assessment Needed
>
> How would others like to view/use this sort of information?
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.
Currently, SCAP is not too useful for searching for firmware. Today, if
you want to look for BIOS or UEFI (or EFI 1.x) vulnerabilities in NVD,
it's only via full-text search, and hoping reporting of error happens to
include UEFI. Thus the need for SCAP OVAL definitions. (Then UEFI Forum
could not only report vulnerabilities as PDFs -- hosted on SourceForge's
reliable CDN :-) -- but also as CVEs in the NVD (which has also gone
down like SF, but XML content is mirrored by multiple orgs. CHIPSEC --
or Copernicus, if MITRE is maintaining it -- would be needed to fix
SCAP, as there aren't any other vulnerability reporting tools to
generate the needed ARF reports. Maybe -- I've not studied it closely
yet -- the BIOS profile by DMTF's SMASH-and-DASH team might be helpful
for SCAP OVAL starting point?
I presume Intel could make good marketing use of this improved
enterprise security feature. If/when Linaro ports CHIPSEC to AArch64, I
presume some of the anticipated green Linux server market will also like
to have this feature. :-)
Thanks,
Lee
RSS: http://firmwaresecurity.com/feed
next reply other threads:[~2015-07-27 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 17:37 Blibbet [this message]
2015-07-31 16:07 ` SCAP reporting support for CHIPSEC Blibbet
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=55B66C5F.6060809@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).