openscap HTML report redesign

Trey Henefield trey.henefield at ultra-ats.com
Thu Jul 17 18:54:08 UTC 2014


I definitely like the new layout.

I am not sure if it has been mentioned, but I personally would find it useful to include details on the results.

For instance, considering a check that ensures all libraries meet certain permissions, it would be useful to identify all entries that are non-compliant, if failed.

The SCC scanner does this, sort of. Well it lists every item verified, which in some cases can make it difficult to identify just the failed items (needle in the haystack).

In some cases, the simplicity of the result details in OpenSCAP reports are desirable. In other cases, the verbosity in the SCC reports are useful.

It would be ideal if OpenSCAP could offer both.

More specifically, it would be ideal if an option could be specified when generating the report to dictate the verbosity of the report details.

I would consider the following three verbosity levels most useful:

LOW - No details, just the overall outcome for each check (the current OpenSCAP report scheme).

MEDIUM - Includes all (and only) failed items for each check that fails.

HIGH - Includes all items verified (both pass and fail items) for every check.

Best regards,
 

Trey Henefield, CISSP
Senior IAVA Engineer

Ultra Electronics
Advanced Tactical Systems, Inc.
4101 Smith School Road
Building IV, Suite 100
Austin, TX 78744 USA

Trey.Henefield at ultra-ats.com
Tel: +1 512 327 6795 ext. 647
Fax: +1 512 327 8043
Mobile: +1 512 541 6450

www.ultra-ats.com

-----Original Message-----
From: scap-workbench-bounces at lists.fedorahosted.org [mailto:scap-workbench-bounces at lists.fedorahosted.org] On Behalf Of Martin Preisler
Sent: Thursday, July 17, 2014 1:34 PM
To: open-scap-list; SCAP Security Guide; scap-workbench at lists.fedorahosted.org
Subject: Re: openscap HTML report redesign

----- Original Message -----
> From: "Martin Preisler" <mpreisle at redhat.com>
> To: "open-scap-list" <open-scap-list at redhat.com>, "SCAP Security Guide" <scap-security-guide at lists.fedorahosted.org>,
> scap-workbench at lists.fedorahosted.org
> Sent: Friday, July 11, 2014 4:09:33 PM
> Subject: openscap HTML report redesign
> 
> Hi,
> I wrote a blog post about the ongoing HTML report redesign.
> 
> http://martin.preisler.me/2014/07/openscap-html-report-redesign/
> 
> Please give it a look and consider providing feedback.

A new blog post with more progress on the HTML report redesign. Things are shaping up in rule overview, I will focus on result details next.

http://martin.preisler.me/2014/07/openscap-html-report-redesign-part-2/

I humbly ask for more feedback :-)

-- 
Martin Preisler
_______________________________________________
scap-workbench mailing list
scap-workbench at lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/scap-workbench

Disclaimer
The information contained in this communication from trey.henefield at ultra-ats.com sent at 2014-07-17 14:54:15 is confidential and may be legally privileged.
It is intended solely for use by scap-security-guide at lists.fedorahosted.org and others authorized to receive it. If you are not scap-security-guide at lists.fedorahosted.org you are hereby notified that
any disclosure, copying, distribution or taking action in reliance of the contents of this information is strictly prohibited and may be unlawful.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/scap-security-guide/attachments/20140717/79ab37d0/attachment.html>


More information about the scap-security-guide mailing list