-
Notifications
You must be signed in to change notification settings - Fork 766
Update SRG-OS-000096-GPOS-00050 for RHEL 9 STIG #8497
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
Update SRG-OS-000096-GPOS-00050 for RHEL 9 STIG #8497
Conversation
|
This datastream diff is auto generated by the check Click here to see the full diffNew datastream is missing OVAL for rule 'xccdf_org.ssgproject.content_rule_configure_firewalld_ports'.
New datastream is missing bash remediation for rule 'xccdf_org.ssgproject.content_rule_configure_firewalld_ports'.
OCIL for rule 'xccdf_org.ssgproject.content_rule_chronyd_client_only' differs:
--- old datastream
+++ new datastream
@@ -2,5 +2,5 @@
$ grep '\bport\b' /etc/chrony.conf
The output should return
port 0
- Is it the case that it does not exist or port is set to non-zero value?
+ Is it the case that port is not set or port is set to non-zero value?
New datastream adds ansible remediation for rule 'xccdf_org.ssgproject.content_rule_chronyd_client_only'.
OCIL for rule 'xccdf_org.ssgproject.content_rule_chronyd_no_chronyc_network' differs:
--- old datastream
+++ new datastream
@@ -2,5 +2,5 @@
$ grep '\bcmdport\b' /etc/chrony.conf
The output should return
cmdport 0
- Is it the case that it does not exist or port is set to non-zero value?
+ Is it the case that cmdport is not set or cmdport is set to non-zero value?
New datastream adds ansible remediation for rule 'xccdf_org.ssgproject.content_rule_chronyd_no_chronyc_network'.
OCIL for rule 'xccdf_org.ssgproject.content_rule_firewalld_sshd_port_enabled' differs:
--- old datastream
+++ new datastream
@@ -17,5 +17,5 @@
If it is a port:
22/tcp
- Is it the case that ?
+ Is it the case that sshd service is disabled by firewall?
New datastream adds bash remediation for rule 'xccdf_org.ssgproject.content_rule_firewalld_sshd_port_enabled'. |
|
/retest |
…enabled During our work on SRG-OS-000096-GPOS-00050 we have discovered the following: - The requirement "The firewall should be configured sanely" isn't possible to be automated by SCAP because services and ports differ on different systems. - At the same time there is rule "configure_firewalld_ports" that tries to implement it. - The rule "configure_firewalld_ports" is internally inconsistent - its rationale and description are about generic firewall configuration, but OVAL and bash check and configure that sshd service is enabled in firewall. - But we also have rule firewalld_sshd_port_enabled which checks that sshd service is enabled in firewall. - Our STIG workflow recommends us that OCIL and fix should be aligned with bash and OVAL which means if we create OCIL and fix for rule configure_firewalld_ports according to this rule's existing bash and OVAL the rule would be even more internally inconsistent - it would be basically a copy of firewalld_sshd_port_enabled with a misleading generic title. Therefore, in this commit, we make the rule configure_firewalld_ports generic, remove everything related to sshd from this rule, remove OVAL and bash because of non-automated character of this rule, and instead update rule firewalld_sshd_port_enabled with the remediation. See discussion in the pull request: ComplianceAsCode#8497
|
/retest |
|
@jan-cerny looks like this PR needs a rebase. Not sure why the boot hasn't told you about that. |
…enabled During our work on SRG-OS-000096-GPOS-00050 we have discovered the following: - The requirement "The firewall should be configured sanely" isn't possible to be automated by SCAP because services and ports differ on different systems. - At the same time there is rule "configure_firewalld_ports" that tries to implement it. - The rule "configure_firewalld_ports" is internally inconsistent - its rationale and description are about generic firewall configuration, but OVAL and bash check and configure that sshd service is enabled in firewall. - But we also have rule firewalld_sshd_port_enabled which checks that sshd service is enabled in firewall. - Our STIG workflow recommends us that OCIL and fix should be aligned with bash and OVAL which means if we create OCIL and fix for rule configure_firewalld_ports according to this rule's existing bash and OVAL the rule would be even more internally inconsistent - it would be basically a copy of firewalld_sshd_port_enabled with a misleading generic title. Therefore, in this commit, we make the rule configure_firewalld_ports generic, remove everything related to sshd from this rule, remove OVAL and bash because of non-automated character of this rule, and instead update rule firewalld_sshd_port_enabled with the remediation. See discussion in the pull request: ComplianceAsCode#8497
0d7fea8 to
0e27fe0
Compare
|
I have rebased this pull request on the top of the current upstream master branch and I have changed fix to fixtext. |
…enabled During our work on SRG-OS-000096-GPOS-00050 we have discovered the following: - The requirement "The firewall should be configured sanely" isn't possible to be automated by SCAP because services and ports differ on different systems. - At the same time there is rule "configure_firewalld_ports" that tries to implement it. - The rule "configure_firewalld_ports" is internally inconsistent - its rationale and description are about generic firewall configuration, but OVAL and bash check and configure that sshd service is enabled in firewall. - But we also have rule firewalld_sshd_port_enabled which checks that sshd service is enabled in firewall. - Our STIG workflow recommends us that OCIL and fix should be aligned with bash and OVAL which means if we create OCIL and fix for rule configure_firewalld_ports according to this rule's existing bash and OVAL the rule would be even more internally inconsistent - it would be basically a copy of firewalld_sshd_port_enabled with a misleading generic title. Therefore, in this commit, we make the rule configure_firewalld_ports generic, remove everything related to sshd from this rule, remove OVAL and bash because of non-automated character of this rule, and instead update rule firewalld_sshd_port_enabled with the remediation. See discussion in the pull request: ComplianceAsCode#8497
0e27fe0 to
e5af623
Compare
...de/system/network/network-firewalld/ruleset_modifications/configure_firewalld_ports/rule.yml
Show resolved
Hide resolved
|
I have add fixtext to configure_firewalld_ports |
This will make the macro text aligned with the bash remediation in the template shared/templates/kernel_module_disabled/bash.template.
…enabled During our work on SRG-OS-000096-GPOS-00050 we have discovered the following: - The requirement "The firewall should be configured sanely" isn't possible to be automated by SCAP because services and ports differ on different systems. - At the same time there is rule "configure_firewalld_ports" that tries to implement it. - The rule "configure_firewalld_ports" is internally inconsistent - its rationale and description are about generic firewall configuration, but OVAL and bash check and configure that sshd service is enabled in firewall. - But we also have rule firewalld_sshd_port_enabled which checks that sshd service is enabled in firewall. - Our STIG workflow recommends us that OCIL and fix should be aligned with bash and OVAL which means if we create OCIL and fix for rule configure_firewalld_ports according to this rule's existing bash and OVAL the rule would be even more internally inconsistent - it would be basically a copy of firewalld_sshd_port_enabled with a misleading generic title. Therefore, in this commit, we make the rule configure_firewalld_ports generic, remove everything related to sshd from this rule, remove OVAL and bash because of non-automated character of this rule, and instead update rule firewalld_sshd_port_enabled with the remediation. See discussion in the pull request: ComplianceAsCode#8497
Originally, check and remediation for enabling sshd ports were a part of rule configure_firewalld_ports, but that rule was meant to be generic. We moved these checks and remediations to firewalld_sshd_port_enabled. So we add firewalld_sshd_port_enabled to this control to keep the original intent.
35388d2 to
44697ba
Compare
|
/retest |
...de/system/network/network-firewalld/ruleset_modifications/configure_firewalld_ports/rule.yml
Outdated
Show resolved
Hide resolved
...de/system/network/network-firewalld/ruleset_modifications/configure_firewalld_ports/rule.yml
Show resolved
Hide resolved
|
I have Fix firewalld command for adding services |
|
@jan-cerny: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
marcusburghardt
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@Mab879 , I didn't merge so you also have opportunity to update your last review. Thanks |
|
Tests pass locally. |
…enabled During our work on SRG-OS-000096-GPOS-00050 we have discovered the following: - The requirement "The firewall should be configured sanely" isn't possible to be automated by SCAP because services and ports differ on different systems. - At the same time there is rule "configure_firewalld_ports" that tries to implement it. - The rule "configure_firewalld_ports" is internally inconsistent - its rationale and description are about generic firewall configuration, but OVAL and bash check and configure that sshd service is enabled in firewall. - But we also have rule firewalld_sshd_port_enabled which checks that sshd service is enabled in firewall. - Our STIG workflow recommends us that OCIL and fix should be aligned with bash and OVAL which means if we create OCIL and fix for rule configure_firewalld_ports according to this rule's existing bash and OVAL the rule would be even more internally inconsistent - it would be basically a copy of firewalld_sshd_port_enabled with a misleading generic title. Therefore, in this commit, we make the rule configure_firewalld_ports generic, remove everything related to sshd from this rule, remove OVAL and bash because of non-automated character of this rule, and instead update rule firewalld_sshd_port_enabled with the remediation. See discussion in the pull request: ComplianceAsCode#8497
…enabled During our work on SRG-OS-000096-GPOS-00050 we have discovered the following: - The requirement "The firewall should be configured sanely" isn't possible to be automated by SCAP because services and ports differ on different systems. - At the same time there is rule "configure_firewalld_ports" that tries to implement it. - The rule "configure_firewalld_ports" is internally inconsistent - its rationale and description are about generic firewall configuration, but OVAL and bash check and configure that sshd service is enabled in firewall. - But we also have rule firewalld_sshd_port_enabled which checks that sshd service is enabled in firewall. - Our STIG workflow recommends us that OCIL and fix should be aligned with bash and OVAL which means if we create OCIL and fix for rule configure_firewalld_ports according to this rule's existing bash and OVAL the rule would be even more internally inconsistent - it would be basically a copy of firewalld_sshd_port_enabled with a misleading generic title. Therefore, in this commit, we make the rule configure_firewalld_ports generic, remove everything related to sshd from this rule, remove OVAL and bash because of non-automated character of this rule, and instead update rule firewalld_sshd_port_enabled with the remediation. See discussion in the pull request: ComplianceAsCode#8497
Description:
add missing fix texts, missing Ansible, improve OCIL
Rationale:
RHEL 9 STIG