Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: HTML guide -- consider ability to filter the list of displayed rules per requirement #247

Closed
iankko opened this issue Dec 1, 2015 · 2 comments
Milestone

Comments

@iankko
Copy link

iankko commented Dec 1, 2015

HTML report in current OpenSCAP can filter out the displayed rules depending on the result (PASS, FAIL, NOTCHECKED) and display only rules having one concrete result.

It would be nice (RFE) if the generated HTML guide for particular profile and benchmark could also filter out only rules e.g.:

  • per concrete PCI DSS identifier, DISA STIG / NIST identifier etc.

Example use case: Show me only rules in the guide mapping to PCI DSS Req #5.

The author of this idea is Zbynek (proper attribution is important). I just formatted the idea into a ticket.

Thank you for your consideration, Jan.

@shawndwells
Copy link
Member

On 12/1/15 5:40 AM, iankko wrote:

HTML report in current OpenSCAP can filter out the displayed rules
depending on the result (PASS, FAIL, NOTCHECKED) and display only
rules having one concrete result.

It would be nice (RFE) if the generated HTML guide for particular
profile and benchmark could also filter out only rules e.g.:

  • per concrete PCI DSS identifier, DISA STIG / NIST identifier etc.

Example use case: Show me only rules in the guide mapping to PCI DSS
Req #5 #5.

The author of this idea is Zbynek (proper attribution is important). I
just formatted the idea into a ticket.

Thank you for your consideration, Jan.

+1. Having a simpler table, e.g. like below, would be great!

CCE | NIST Refs | XCCDF Rule Title | Pass/Fail

@isimluk isimluk added this to the 1.2.10 milestone Feb 3, 2016
@jan-cerny jan-cerny modified the milestones: 1.2.11, 1.2.10 Jun 22, 2016
@jan-cerny jan-cerny modified the milestones: 1.2.12, 1.2.11 Oct 14, 2016
@mpreisler mpreisler modified the milestones: 1.2.7, 1.2.12 Nov 15, 2016
@mpreisler
Copy link
Member

Implemented in #188, fixed in #357

If you don't agree please reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants