Couple comments on the report layout.
- Rules result breakdown - while the color bar breakdown is nice, it doesn't present precise information at first glance. The user will see 86 passed, 131 failed, and left guessing what that remaining 6 rules are. It'll be nice to see the total number of
rules as well.
- Failed rules by severity breakdown – similar to rules results, the severity description got cut off even though it’s easy to assume that the two failed rules refer to High severity.
- Score – it’ll be nice to have a brief explanation or reference to how the scoring is done for those not familiar with the scoring system.
- Section heading – I think the number of “not checked” should also be included in the section heading along with fail and unknown. For example, I could’ve easily missed “Ensure Software Patches Installed” since it was collapsed within Updating Software
section.
Regards,
Wei
----- Original Message -----
> Sent: Thursday, August 28, 2014 7:49:23 PM
> Subject: New report and guide in openscap 1.1.0
>
> Hi,
>
> as you may know I have been working on a complete rewrite of HTML
> report and guide for the upcoming openscap 1.1.0 release. It's a
> feature that will touch almost every user of openscap. I would like to
> gather feedback from the scap-security-guide community so that we can
> make sure there aren't any blocker issues in the release. It is
> natural that there will be small issues that we will iron out in minor
> releases. Basically we would just like to make sure the new report and
> guide aren't missing anything crucial that would prevent adoption.
>
> HTML report and guide from SSG for RHEL6.
>
> Looking forward to feedback.
>
> --
> Martin Preisler
> --
> SCAP Security Guide mailing list