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 [email protected] Tel: +1 512 327 6795 ext. 647 Fax: +1 512 327 8043 Mobile: +1 512 541 6450 www.ultra-ats.com -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Martin Preisler Sent: Thursday, July 17, 2014 1:34 PM To: open-scap-list; SCAP Security Guide; [email protected] Subject: Re: openscap HTML report redesign ----- Original Message ----- > From: "Martin Preisler" <[email protected]> > To: "open-scap-list" <[email protected]>, "SCAP Security Guide" > <[email protected]>, > [email protected] > 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 [email protected] https://lists.fedorahosted.org/mailman/listinfo/scap-workbench Disclaimer The information contained in this communication from [email protected] sent at 2014-07-17 14:54:15 is confidential and may be legally privileged. It is intended solely for use by [email protected] and others authorized to receive it. If you are not [email protected] 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.
-- SCAP Security Guide mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide https://github.com/OpenSCAP/scap-security-guide/
