RAN Hardening: Low Severity (dmesg restrict)#358
Closed
sebrandon1 wants to merge 1 commit intoopenshift-kni:mainfrom
Closed
RAN Hardening: Low Severity (dmesg restrict)#358sebrandon1 wants to merge 1 commit intoopenshift-kni:mainfrom
sebrandon1 wants to merge 1 commit intoopenshift-kni:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: sebrandon1 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
sebrandon1
force-pushed
the
compliance_low_level_only
branch
from
0a19e32 to
ab44b01
Compare
sebrandon1
force-pushed
the
compliance_low_level_only
branch
from
ab44b01 to
91c01f9
Compare
sebrandon1
changed the title
Contributor
Author
|
Closing in favor of: #466 |
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
1 participant
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.
This is the only low level compliance failure I'm seeing in the compliance operator that stands alone in its own
path:/etc/sysctl.d/75-sysctl_kernel_dmesg_restrict.confEnabling
kernel.dmesg_restrict=1is safe for Kubernetes and OpenShift because neither the control plane components nor workloads rely on direct access to dmesg for logging or operations. These platforms use systemd journals, CRI runtimes, and container stdout/stderr for log collection, so blocking user access to the kernel ring buffer has no functional impact.Restricting dmesg prevents unprivileged users or compromised pods from gathering sensitive kernel information such as memory addresses or driver details, which could aid in exploits. Including this setting strengthens node-level security and aligns with common hardening practices in production clusters.