Add RHCOS STIG content and enable for NIST#6046
Add RHCOS STIG content and enable for NIST#6046carlosmmatos merged 4 commits intoComplianceAsCode:masterfrom
Conversation
|
Changes identified: Recommended tests to execute: |
b95a649 to
6c5c3aa
Compare
|
Moving this out of draft mode as the content builds correctly. |
| @@ -0,0 +1,23 @@ | |||
| documentation_complete: true | |||
There was a problem hiding this comment.
if this is a draft, why not set documentation_complete: false?
There was a problem hiding this comment.
@JAORMX Need it to build so that updated transmission to DISA can happen.
| - var_ssh_client_rekey_limit_size=1G | ||
| - var_ssh_client_rekey_limit_time=1hour | ||
|
|
||
| # zIPl specific rules |
There was a problem hiding this comment.
Need the rules enabled so that updated transmission to DISA can easily happen without having to enable/disable rules. Can they be enabled and updated later when completed?
| - configure_crypto_policy | ||
| - configure_ssh_crypto_policy | ||
| - configure_openssl_crypto_policy | ||
| - configure_libreswan_crypto_policy |
There was a problem hiding this comment.
Let's comment this out for now since libreswan is not available in RHCOS
There was a problem hiding this comment.
Currently, no. But it was submitted as part of the draft STIG. Need the rules enabled so that updated transmission to DISA can easily happen without having to enable/disable rules.
| - grub2_vsyscall_argument | ||
| - grub2_vsyscall_argument.role=unscored | ||
| - grub2_vsyscall_argument.severity=info | ||
| - grub2_pti_argument |
There was a problem hiding this comment.
Need the rules enabled so that updated transmission to DISA can easily happen without having to enable/disable rules. Can they be enabled and updated later when completed?
| - selinux_policytype | ||
|
|
||
| ### Application Whitelisting (RHEL 8) | ||
| - package_fapolicyd_installed |
There was a problem hiding this comment.
Are these rules relevant since fapolicyd is not part of RHCOS?
There was a problem hiding this comment.
It is a requirement for STIG, yes.
| ### Configure USBGuard | ||
| - service_usbguard_enabled | ||
| - configure_usbguard_auditbackend | ||
| - usbguard_allow_hid_and_hub |
There was a problem hiding this comment.
Are these rules relevant since usbguard is not part of RHCOS?
There was a problem hiding this comment.
We gotta research the extension mechanism in RHCOS [1], we could install usbguard nowadays with that.
| ## Disable Unauthenticated Login (such as Guest Accounts) | ||
| ## FIA_UAU.1 | ||
| - require_singleuser_auth | ||
| - grub2_disable_interactive_boot |
There was a problem hiding this comment.
Do we know if these rules work with the RHCOS bootloader?
There was a problem hiding this comment.
That's a good question. Something we gotta research.
| - accounts_tmout | ||
| - sudo_remove_no_authenticate | ||
| - sudo_remove_nopasswd | ||
| - sudo_require_authentication |
There was a problem hiding this comment.
By default the core user is a member of the sudo group which has %sudo ALL=(ALL) NOPASSWD: ALL set in sudoers, this likely clash with the sudo rules above. Just saying.
There was a problem hiding this comment.
Right, however it is a problem to just sudo without password. Also, I believe that the recommended guidance that we are going to also give is to remove the core user.
|
On Wed, Sep 30, 2020 at 09:15:50AM -0700, Gabe Alford wrote:
@redhatrises commented on this pull request.
> + - accounts_umask_etc_bashrc
+ - accounts_umask_etc_csh_cshrc
+
+ ### Software update
+ - ensure_redhat_gpgkey_installed
+
+ ### Kernel Config
+ ## Boot prompt
+ - grub2_audit_argument
+ - grub2_audit_backlog_limit_argument
+ - grub2_slub_debug_argument
+ - grub2_page_poison_argument
+ - grub2_vsyscall_argument
+ - grub2_vsyscall_argument.role=unscored
+ - grub2_vsyscall_argument.severity=info
+ - grub2_pti_argument
Need the rules enabled so that updated transmission to DISA can easily happen without having to enable/disable rules. Can they be enabled and updated later when completed?
I guess? I haven't tested the rules, but I guess at worst the grub
config file wouldn't be there and the result wouldn't be compliant.
|
True. Equally, we aren't testing it yet either in CI/CD, but since this is draft and under review, which not only are there bound to be errors, but it the draft could change as well too. |
|
@redhatrises: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
/retest |
|
@openscap-ci test this please |
|
Changes identified: Show detailsProfile ospp on rhcos4: Recommended tests to execute: |
|
Might wanna rebase this |
Yeah... I was just wanting fresh tests. |
32fab46 to
4bd1be1
Compare
4bd1be1 to
ec1c354
Compare
Description: