Skip to content

🔄 NIST 800-53 CIS Reference Update (2026-06-07)#14784

Closed
github-actions[bot] wants to merge 1 commit into
masterfrom
auto-update-nist-800-53-20260607-144403
Closed

🔄 NIST 800-53 CIS Reference Update (2026-06-07)#14784
github-actions[bot] wants to merge 1 commit into
masterfrom
auto-update-nist-800-53-20260607-144403

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions Bot commented Jun 7, 2026

Summary

This automated PR updates the CIS reference file showing the
latest CIS→NIST mappings.

⚠️ MANUAL ACTION REQUIRED

Review changes and update product control files accordingly:

  1. Review the diff to see what changed in CIS mappings
  2. Apply changes to products/{p}/controls/nist_800_53/*.yml
  3. Preserve human-added rules or notes in the real files
  4. Commit manual updates to the real control files in this PR

Changes

  • +342/-321 lines modified in CIS reference files
  • Reference files in shared/references/controls/

File Roles

File Purpose By
shared/references/.../{p}.yml Ref metadata 🤖
shared/references/.../{p}/*.yml Ref families 🤖
products/{p}/controls/nist_800_53.yml Product metadata 👤
products/{p}/controls/nist_800_53/*.yml Product families 👤

Details

  • Triggered by: Weekly scheduled workflow
  • Date: 2026-06-07 14:44:05 UTC
  • OSCAL: NIST SP 800-53 Revision 5

🤖 Generated by weekly sync workflow

This automated update regenerates the CIS→NIST reference file from
the latest OSCAL catalog and CIS benchmark mappings.

Changes: +342/-321 lines in CIS reference files

⚠️  MANUAL ACTION REQUIRED:
Review the diff and manually update the product control files.

Generated by: Weekly NIST 800-53 Sync Workflow
Co-Authored-By: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown
Author

github-actions Bot commented Jun 7, 2026

Detailed Changes in CIS Reference Files

Changed Family Files

None
📁 Family files diff

Tip: Family files (ac.yml, au.yml, cm.yml, etc.) make it
easier to review changes by control area.

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Jun 7, 2026

Hi @github-actions[bot]. 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.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant