CNF-23448: RAN Hardening (5.0) - Audit Kernel Modules (M5)

[sebrandon1]

Summary

Adds MachineConfig to deploy audit rules for kernel module loading and unloading events on both master and worker nodes.

This addresses MEDIUM severity findings from the ACSC Essential Eight compliance profile — auditing init_module, finit_module, and delete_module syscalls to ensure all kernel module operations are recorded.

Remediation Group

• M5: Audit Kernel Modules

Files

• 75-audit-kernel-modules-master.yaml
• 75-audit-kernel-modules-worker.yaml

Verification

After applying to a cluster, verify with:

oc debug node/<node> -- chroot /host auditctl -l | grep -E "init_module|delete_module"
# Expected: audit rules for module syscalls

Jira

• Story: CNF-23448
• Epic: CNF-22573 (RAN Hardening for 5.0)

Supersedes #738 — migrated from compliance/4.22/* to compliance/5.0/* branch naming.

OCP 5.0 Verification (2026-06-22)

Cluster: cnfdt16 — OCP 5.0.0-0.nightly-2026-06-18-000016, RHCOS 10.2

Finding: Hardening still needed. Stock RHCOS 10 ships no kernel module audit rules.

$ cat /etc/audit/rules.d/audit.rules
## First rule - delete all
-D
## Increase the buffers to survive stress events.
-b 8192
## This determine how long to wait in burst of events
--backlog_wait_time 60000
## Set failure mode to syslog
-f 1

The default audit.rules only has basic buffer/backlog setup. No rules for init_module, finit_module, or delete_module syscalls exist by default. The only other rules file is mco-audit-quiet-containers.rules (NETFILTER_CFG and ANOM_PROMISCUOUS suppressions).

[openshift-ci-robot]

@sebrandon1: This pull request references CNF-23448 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Adds MachineConfig to deploy audit rules for kernel module loading and unloading events on both master and worker nodes.

This addresses MEDIUM severity E8 compliance checks for auditing init_module, finit_module, and delete_module syscalls, ensuring all kernel module operations are recorded.

Remediation Group

• M5: Audit Kernel Modules

Files

• 75-audit-kernel-modules-master.yaml
• 75-audit-kernel-modules-worker.yaml

Verification

After applying to a cluster, verify with:

oc debug node/<node> -- chroot /host auditctl -l | grep -E "init_module|delete_module"
# Expected: audit rules for module syscalls

Jira

• Story: CNF-23448
• Epic: CNF-22573 (RAN Hardening for 5.0)

Supersedes #738 — migrated from compliance/4.22/* to compliance/5.0/* branch naming.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sebrandon1
Once this PR has been reviewed and has the lgtm label, please assign marsik for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

Warning

Review limit reached

@sebrandon1, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 5e3be425-2d6f-4219-b79c-25df069432c6

📥 Commits

Reviewing files that changed from the base of the PR and between 78962de and 3bf88ea.

📒 Files selected for processing (2)

• telco-ran/configuration/kube-compare-reference/informational/hardening/75-audit-kernel-modules-master.yaml
• telco-ran/configuration/kube-compare-reference/informational/hardening/75-audit-kernel-modules-worker.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci-robot]

@sebrandon1: This pull request references CNF-23448 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Adds MachineConfig to deploy audit rules for kernel module loading and unloading events on both master and worker nodes.

This addresses MEDIUM severity E8 compliance checks for auditing init_module, finit_module, and delete_module syscalls, ensuring all kernel module operations are recorded.

Remediation Group

• M5: Audit Kernel Modules

Files

• 75-audit-kernel-modules-master.yaml
• 75-audit-kernel-modules-worker.yaml

Verification

After applying to a cluster, verify with:

oc debug node/<node> -- chroot /host auditctl -l | grep -E "init_module|delete_module"
# Expected: audit rules for module syscalls

Jira

• Story: CNF-23448
• Epic: CNF-22573 (RAN Hardening for 5.0)

Supersedes #738 — migrated from compliance/4.22/* to compliance/5.0/* branch naming.

OCP 5.0 Verification (2026-06-22)

Cluster: cnfdt16 — OCP 5.0.0-0.nightly-2026-06-18-000016, RHCOS 10.2

Finding: Hardening still needed. Stock RHCOS 10 ships no kernel module audit rules.

$ cat /etc/audit/rules.d/audit.rules
## First rule - delete all
-D
## Increase the buffers to survive stress events.
-b 8192
## This determine how long to wait in burst of events
--backlog_wait_time 60000
## Set failure mode to syslog
-f 1

The default audit.rules only has basic buffer/backlog setup. No rules for init_module, finit_module, or delete_module syscalls exist by default. The only other rules file is mco-audit-quiet-containers.rules (NETFILTER_CFG and ANOM_PROMISCUOUS suppressions).

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@sebrandon1: This pull request references CNF-23448 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Adds MachineConfig to deploy audit rules for kernel module loading and unloading events on both master and worker nodes.

This addresses MEDIUM severity findings from the ACSC Essential Eight compliance profile — auditing init_module, finit_module, and delete_module syscalls to ensure all kernel module operations are recorded.

Remediation Group

• M5: Audit Kernel Modules

Files

• 75-audit-kernel-modules-master.yaml
• 75-audit-kernel-modules-worker.yaml

Verification

After applying to a cluster, verify with:

oc debug node/<node> -- chroot /host auditctl -l | grep -E "init_module|delete_module"
# Expected: audit rules for module syscalls

Jira

• Story: CNF-23448
• Epic: CNF-22573 (RAN Hardening for 5.0)

Supersedes #738 — migrated from compliance/4.22/* to compliance/5.0/* branch naming.

OCP 5.0 Verification (2026-06-22)

Cluster: cnfdt16 — OCP 5.0.0-0.nightly-2026-06-18-000016, RHCOS 10.2

Finding: Hardening still needed. Stock RHCOS 10 ships no kernel module audit rules.

$ cat /etc/audit/rules.d/audit.rules
## First rule - delete all
-D
## Increase the buffers to survive stress events.
-b 8192
## This determine how long to wait in burst of events
--backlog_wait_time 60000
## Set failure mode to syslog
-f 1

The default audit.rules only has basic buffer/backlog setup. No rules for init_module, finit_module, or delete_module syscalls exist by default. The only other rules file is mco-audit-quiet-containers.rules (NETFILTER_CFG and ANOM_PROMISCUOUS suppressions).

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 openshift-eng/jira-lifecycle-plugin repository.