Skip to content

[Ubuntu 22.04] Bump STIG profile metadata from V2R3 to V2R7#14459

Merged
mpurg merged 1 commit intoComplianceAsCode:masterfrom
hdean3:fix/ubuntu2204-stig-v2r3-to-v2r7-metadata
Feb 27, 2026
Merged

[Ubuntu 22.04] Bump STIG profile metadata from V2R3 to V2R7#14459
mpurg merged 1 commit intoComplianceAsCode:masterfrom
hdean3:fix/ubuntu2204-stig-v2r3-to-v2r7-metadata

Conversation

@hdean3
Copy link
Copy Markdown
Contributor

@hdean3 hdean3 commented Feb 26, 2026

Summary

PRs #14427, #14418, #14415, #14416, and #14433 merged V2R7 STIG rules for Ubuntu 22.04 LTS but the version metadata fields were not updated. This causes a mismatch where:

  • STIG Viewer imports report V2R3 in the header
  • Auditors performing ATO reviews see V2R3 in scan reports
  • The actual content reflects V2R7 rules

Changes

File Change
controls/stig_ubuntu2204.yml version: V2R3version: V2R7
products/ubuntu2204/profiles/stig.profile version, title, and description strings V2R3 → V2R7

Testing

This is a metadata-only change with no functional impact on rule evaluation. No build or test infrastructure required to verify correctness — the change is a string substitution aligning version labels to match the content already merged.

References

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
@hdean3 hdean3 requested a review from a team as a code owner February 26, 2026 11:34
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Feb 26, 2026

Hi @hdean3. Thanks for your PR.

I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@openshift-ci openshift-ci Bot added the needs-ok-to-test Used by openshift-ci bot. label Feb 26, 2026
@mpurg mpurg self-assigned this Feb 26, 2026
@mpurg mpurg added Ubuntu Ubuntu product related. STIG STIG Benchmark related. labels Feb 26, 2026
@mpurg mpurg added this to the 0.1.81 milestone Feb 26, 2026
Copy link
Copy Markdown
Contributor

@mpurg mpurg left a comment

Choose a reason for hiding this comment

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

Thanks for fixing this @hdean3 !

@mpurg mpurg merged commit 7965ebd into ComplianceAsCode:master Feb 27, 2026
51 of 52 checks passed
@hdean3 hdean3 deleted the fix/ubuntu2204-stig-v2r3-to-v2r7-metadata branch February 27, 2026 22:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-ok-to-test Used by openshift-ci bot. STIG STIG Benchmark related. Ubuntu Ubuntu product related.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants