Skip to content

Add rules for disabling nfs to Ubuntu 22.04 STIG#14418

Merged
dodys merged 1 commit intoComplianceAsCode:masterfrom
mpurg:ubuntu_stig_UBTU-22-215040
Feb 20, 2026
Merged

Add rules for disabling nfs to Ubuntu 22.04 STIG#14418
dodys merged 1 commit intoComplianceAsCode:masterfrom
mpurg:ubuntu_stig_UBTU-22-215040

Conversation

@mpurg
Copy link
Copy Markdown
Contributor

@mpurg mpurg commented Feb 18, 2026

Description:

Add rules for disabling nfs to Ubuntu 22.04 STIG

Rationale:

Aligns with STIG V2R7 rule UBTU-22-215040
(Ubuntu 22.04 LTS must not have the nfs-kernel-server package installed).

Aligns with STIG V2R7 rule UBTU-22-215040
(Ubuntu 22.04 LTS must not have the nfs-kernel-server package
installed).
@mpurg mpurg added the Ubuntu Ubuntu product related. label Feb 18, 2026
@github-actions
Copy link
Copy Markdown

This datastream diff is auto generated by the check Compare DS/Generate Diff

Click here to see the full diff
New content has different text for rule 'xccdf_org.ssgproject.content_rule_package_nfs-kernel-server_removed'.
--- xccdf_org.ssgproject.content_rule_package_nfs-kernel-server_removed
+++ xccdf_org.ssgproject.content_rule_package_nfs-kernel-server_removed
@@ -10,6 +10,9 @@
 [reference]:
 2.1.9
 
+[reference]:
+UBTU-22-215040
+
 [rationale]:
 If the system does not export NFS shares or act as an NFS client, it is
 recommended that these services be removed to reduce the remote attack

ansible remediation for rule 'xccdf_org.ssgproject.content_rule_package_nfs-kernel-server_removed' differs.
--- xccdf_org.ssgproject.content_rule_package_nfs-kernel-server_removed
+++ xccdf_org.ssgproject.content_rule_package_nfs-kernel-server_removed
@@ -3,6 +3,7 @@
     name: nfs-kernel-server
     state: absent
   tags:
+  - DISA-STIG-UBTU-22-215040
   - disable_strategy
   - low_complexity
   - low_disruption

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Feb 18, 2026

@mpurg: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-openshift-node-compliance b4abd59 link true /test e2e-aws-openshift-node-compliance
ci/prow/e2e-aws-openshift-platform-compliance b4abd59 link true /test e2e-aws-openshift-platform-compliance

Full PR test history. Your PR dashboard.

Details

Instructions 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.

@mpurg mpurg added the STIG STIG Benchmark related. label Feb 19, 2026
@mpurg mpurg requested a review from dodys February 19, 2026 12:25
@mpurg mpurg added this to the 0.1.81 milestone Feb 19, 2026
@dodys dodys self-assigned this Feb 20, 2026
Copy link
Copy Markdown
Contributor

@dodys dodys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thanks!

@dodys dodys merged commit 11f54d1 into ComplianceAsCode:master Feb 20, 2026
59 of 65 checks passed
hdean3 added a commit to hdean3/content that referenced this pull request Feb 26, 2026
All V2R7 control PRs (ComplianceAsCode#14427, ComplianceAsCode#14418, ComplianceAsCode#14415, ComplianceAsCode#14416, ComplianceAsCode#14433) were
merged without updating the version metadata fields. This causes STIG
Viewer imports and auditor reports to display V2R3 while the actual
content reflects V2R7 rules.

Updated files:
- controls/stig_ubuntu2204.yml: version V2R3 → V2R7
- products/ubuntu2204/profiles/stig.profile: version, title, and
  description strings V2R3 → V2R7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

STIG STIG Benchmark related. Ubuntu Ubuntu product related.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants