new rule sysctl_use_max_user_namespaces_no_remediation#13351
Merged
jan-cerny merged 3 commits intoApr 17, 2025
Merged
Conversation
This rule is almost the same as syscl_user_max_user_namespaces, but it does not contain any remediation
… references as it is no longer part of stig also add warning pointing to the alternative rule without a remediation
|
This datastream diff is auto generated by the check Click here to see the full diffNew content has different text for rule 'xccdf_org.ssgproject.content_rule_sysctl_user_max_user_namespaces'.
--- xccdf_org.ssgproject.content_rule_sysctl_user_max_user_namespaces
+++ xccdf_org.ssgproject.content_rule_sysctl_user_max_user_namespaces
@@ -14,9 +14,11 @@
to large non-zero value.
[warning]:
-This configuration baseline was created to deploy the base operating system for general purpose
-workloads. When the operating system is configured for certain purposes, such as to host Linux Containers,
-it is expected that user.max_user_namespaces will be enabled.
+Remediation of this rule might impair or prevent functionality of certain applications.
+This stands especially for general container usage and for certain desktop applications.
+There is an alternative rule which performs the same check but it intentionally lacks the remediation part.
+If needed, you can use the rule sysctl_user_max_user_namespaces_no_remediation.
+In that case, ensure that such use case is properly documented.
[reference]:
CCI-000366
@@ -33,12 +35,6 @@
[reference]:
SRG-OS-000480-GPOS-00227
-[reference]:
-RHEL-08-040284
-
-[reference]:
-SV-230548r1017310_rule
-
[rationale]:
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or system objectives.
These unnecessary capabilities or services are often overlooked and therefore may remain unsecured.
ansible remediation for rule 'xccdf_org.ssgproject.content_rule_sysctl_user_max_user_namespaces' differs.
--- xccdf_org.ssgproject.content_rule_sysctl_user_max_user_namespaces
+++ xccdf_org.ssgproject.content_rule_sysctl_user_max_user_namespaces
@@ -3,7 +3,6 @@
manager: auto
tags:
- CCE-82211-4
- - DISA-STIG-RHEL-08-040284
- NIST-800-53-CM-6(a)
- NIST-800-53-SC-39
- disable_strategy
@@ -26,7 +25,6 @@
when: '"kernel" in ansible_facts.packages'
tags:
- CCE-82211-4
- - DISA-STIG-RHEL-08-040284
- NIST-800-53-CM-6(a)
- NIST-800-53-SC-39
- disable_strategy
@@ -45,7 +43,6 @@
when: '"kernel" in ansible_facts.packages'
tags:
- CCE-82211-4
- - DISA-STIG-RHEL-08-040284
- NIST-800-53-CM-6(a)
- NIST-800-53-SC-39
- disable_strategy
@@ -65,7 +62,6 @@
when: '"kernel" in ansible_facts.packages'
tags:
- CCE-82211-4
- - DISA-STIG-RHEL-08-040284
- NIST-800-53-CM-6(a)
- NIST-800-53-SC-39
- disable_strategy |
|
@vojtapolasek: 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-sigs/prow repository. I understand the commands that are listed here. |
|
Code Climate has analyzed commit ea4907e and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 61.9% (0.0% change). View more on Code Climate. |
jan-cerny
approved these changes
Apr 17, 2025
Collaborator
jan-cerny
left a comment
There was a problem hiding this comment.
I have run test scenarios. Also, I have verified that the removed rule is still part of RHEL 8 and 9 data streams because it's part of OSPP and CUI profiles.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Rationale:
Review Hints: