Hello Martin,

----- Original Message -----

From: "Simon Lukasik" isimluk@fedoraproject.org To: "SCAP Security Guide" scap-security-guide@lists.fedorahosted.org, "open-scap-list" open-scap-list@redhat.com, scap-workbench@lists.fedorahosted.org Sent: Tuesday, July 15, 2014 3:24:16 PM Subject: Re: openscap HTML report redesign

On 07/11/2014 04:09 PM, Martin Preisler wrote:

...

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.

Thank you for this effort. Generally looks very nice (I would even say more professional than the actual version). Though couple of personal observations / preferences:

* there are kinda too much colours for me for the first image / example: http://martin.preisler.me/wp-content/uploads/2014/07/screenshot1.png

But maybe just question of personal preferences.

* for the first image yet. Noticed "header line" like 'Characteristics', 'Compliance and Scoring' ...

would be nice (if having longer page to display) these to have / be HTML anchors to simplify page navigation.

* for the Requested features section: -- "Rule filtering – for example to hide all passed rules" - would be very nice to have 'selected / group by views' - e.g. ability to display only rules ending / finishing with failed, notchecked, unknown, error result,

-- Rule sorting – for example by severity, to form a remediation priority queue

+1 Basically I would say it should be possible to sort (in descending/ascending order) according to each table column header listed (e.g. to put into context the first example possibility to sort by Title, Identifiers, Severity, Result).

-- Custom display of columns -- related with previous one. Is there a chance there might be more columns added in the future? If so, would it be possible (via setting / configuring scap-workbench preferences dialog) to specify, which columns should be shown in the report? Understand this is more feature request for scap-workbench than for openscap now, but would be good to think at it in the future.

-- "Rule full-text search – type CVEs, CCEs, titles, parts of descriptions, filter rules by them" +1 Would it be possible to add searching by rule IDs? Rule IDs are unique, and often the most quicker way how to find a specific rule (many rules belonging to same section, e.g. PAM one share common prefix, differing just by couple of words)

-- speaking about groups, SSG benchmark content is organized into groups (System Settings, Services, etc.). Would it be possible to display something like treeview (tree item headers having labels matching to group name, expandable tree items matching particular rules)?

-- "Custom branding – allow downstreams to insert their own logo" + 1, another nice feature

-- "Generate guide just for the chosen profile – as opposed to generating guide for the default profile" again +1 for this feature

...

Martin, I do like what where this is heading.

Thank You!

Thank you && Regards, Jan. -- Jan iankko Lieskovsky / Red Hat Security Technologies Team

-- Simon Lukasik Security Technologies -- SCAP Security Guide mailing list scap-security-guide@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide https://github.com/OpenSCAP/scap-security-guide/

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@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@lists.fedorahosted.org [mailto:scap-workbench-bounces@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@lists.fedorahosted.org Subject: Re: openscap HTML report redesign

----- Original Message -----

From: "Martin Preisler" mpreisle@redhat.com To: "open-scap-list" open-scap-list@redhat.com, "SCAP Security Guide" scap-security-guide@lists.fedorahosted.org, scap-workbench@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 :-)