Dne 11. 11. 20 v 20:50 Gabe Alford napsal(a):
Looks good. I assume that this is going to be in addition to and not a
replacement of the existing template? Having more than one issue
template that GH creates a menu for you to choose is kinda nice.
Correct, this will be an additional template, the existing one for
reporting issues whill stay there.
Vojta
On Fri, Nov 6, 2020 at 8:54 AM Vojtech Polasek <[email protected]
<mailto:[email protected]>> wrote:
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 <https://www.redhat.com>
[email protected] <mailto:[email protected]>
<https://www.redhat.com>
_______________________________________________
scap-security-guide mailing list --
[email protected]
<mailto:[email protected]>
To unsubscribe send an email to
[email protected]
<mailto:[email protected]>
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
<https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
<https://fedoraproject.org/wiki/Mailing_list_guidelines>
List Archives:
https://lists.fedorahosted.org/archives/list/[email protected]
<https://lists.fedorahosted.org/archives/list/[email protected]>
_______________________________________________
scap-security-guide mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
_______________________________________________
scap-security-guide mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
