Closed mrabe142 closed 5 years ago
DISA's fix text is wrong and needs to be updated. Docs can be found here: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/blacklisting_a_module
Specifically:
The |blacklist/<module_name>/| command, however, does not prevent the module from being loaded manually, or from being loaded as a dependency for another kernel module that is not blacklisted. To ensure that a module cannot be loaded on the system at all, modify the specified configuration file in the |/etc/modprobe.d/| directory as root with the following line: |install /<module_name>//bin/true| Bash
This has been explained to DISA several times, and keeps getting reintroduced.
DISA fix text does in fact include the line "install dccp /bin/true" - as stated when the issue was opened. The line is put into the file /etc/modprobe.d/dccp.conf. It also lists the module in blacklist.conf - no harm putting it there.
Closing this issue.
As part of the latest RHEL 7 STIG update referenced in https://github.com/ComplianceAsCode/content/issues/3370, a rule has been updated in the current version. Information about the rule change is outlined below:
Rule Metadata
New Rule Title
Previous Fix Content
New Fix Content
Noted Differences
Related Tickets This update may address the following issues: https://github.com/ComplianceAsCode/content/issues/3342