Hello all,

I would like to propose a new Github issue template which should make requesting a new SCAP rule easier. It should guide the issue reporter and answer questions which are important for content authors right away. Here is the list of questions I would like to have in the template. Please feel free to give any feedback, ideally until Monday November 16.

~~~

##Which products does the rule apply to?

##Describe the configuration setting enforced by this rule.

##Why is the configuration security relevant?

##How to check the configuration?

###Is it order dependent? (does it need to be at certain place in the file?

###What is correct and incorrect syntax?

##How to remediate

###Does any command need to be run?

##Are there going to be other rules like (similar configuration) this in the future? (is it worth creating template?)

##Are there any caveats to be considered when testing?

##Is the configuration loaded directly by the <software> or is it stored in some intermediate database (similar to dconf)? (We want to edit the lowest level possible, if appropriate)

##Is it possible to check / remediate this configuration in offline mode? (scanning containers or offline systems)

## Please provide security policy references if possible e.g. STIG

~~~

Have a nice weekend,

--

Vojtech Polasek

Software engineer, security compliance

Red Hat

vpolasek@redhat.com   

_______________________________________________
scap-security-guide mailing list -- scap-security-guide@lists.fedorahosted.org
To unsubscribe send an email to scap-security-guide-leave@lists.fedorahosted.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedorahosted.org/archives/list/scap-security-guide@lists.fedorahosted.org