Google GitGoogle Git
Sign in
cos/third_party/localtoast/refs/heads/cos/release-R133/./configs/defs/cos.textproto
blob: 1056932e053b973b9e62c43079808d16f2f67c4d [file] [edit]
# Checks exclusive to COS. These are either completely new checks or versions of
# the generic Linux checks with COS-specific modifications added.
benchmark_configs: {
id: "tmp-configured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure /tmp is configured"
description:
"The /tmp directory is a world-writable directory used for temporary "
"storage by all users and some applications."
rationale:
"Making /tmp its own file system allows an administrator to set the "
"noexec option on the mount, making /tmp useless for an attacker to "
"install executable code. It would also prevent an attacker from "
"establishing a hardlink to a system setuid program and wait for it to "
"be updated. Once the program was updated, the hardlink would be "
"broken and the attacker would have his own copy of the program. If "
"the program happened to have a security vulnerability, the attacker "
"could continue to exploit the known flaw. This can be accomplished "
"by either mounting tmpfs to /tmp, or creating a separate partition "
"for /tmp."
remediation:
"Configure /etc/fstab as appropriate.\n"
"example:\n"
"```\n"
"tmpfs /tmp tmpfs defaults,rw,nosuid,nodev,noexec,relatime 0 0\n"
"```\n"
"OR\n"
"Run the following commands to enable systemd /tmp mounting:\n"
"```\n"
"systemctl unmask tmp.mount\n"
"systemctl enable tmp.mount\n"
"```\n"
"Edit /usr/lib/systemd/system/tmp.mount to configure "
"the /tmp mount:\n"
"```\n"
"[Mount]\n"
"What=tmpfs\n"
"Where=/tmp\n"
"Type=tmpfs\n"
"Options=mode=1777,strictatime,noexec,nodev,nosuid\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".* /tmp .*- .*\""
" expected_regex: \".* /tmp .*- tmpfs tmpfs.*\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/lib/systemd/system/tmp.mount\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"Type=.*\""
" expected_regex: \"Type=tmpfs\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/lib/systemd/system/tmp.mount\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"Type=.*\""
" expected_regex: \"Type=tmpfs\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "var-nodev-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure nodev option set on /var partition"
description:
"The nodev mount option specifies that the filesystem cannot contain "
"special devices."
rationale:
"Since the /var filesystem is not intended to support devices, set "
"this option to ensure that users cannot attempt to create block or "
"character special devices in /var."
remediation:
"Run the following command to remount /var:\n"
"```\n"
"# mount -o remount,nodev /var\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".* /var .* - .*\""
" expected_regex: \".* /var .*nodev.* - .*\""
" }"
" }"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".* /var .* - .*\""
" expected_regex: \".* /var .* - .*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "var-nosuid-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure nosuid option set on /var partition"
description:
"The nosuid mount option specifies that the filesystem cannot contain "
"setuid files."
rationale:
"Since the /var filesystem is only intended for temporary file "
"storage, set this option to ensure that users cannot create setuid "
"files in /var."
remediation:
"Run the following command to remount /var:\n"
"```\n"
"# mount -o remount,nosuid /var\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".* /var .* - .*\""
" expected_regex: \".* /var .*nosuid.* - .*\""
" }"
" }"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".* /var .* - .*\""
" expected_regex: \".* /var .* - .*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "var-noexec-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure noexec option set on /var partition"
description:
"The noexec mount option specifies that the filesystem cannot contain "
"executable binaries."
rationale:
"Since the /var filesystem is only intended for temporary file "
"storage, set this option to ensure that users cannot run executable "
"binaries from /var."
remediation:
"Run the following command to remount /var:\n"
"```\n"
"# mount -o remount,noexec /var\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".* /var .* - .*\""
" expected_regex: \".* /var .*noexec.* - .*\""
" }"
" }"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".* /var .* - .*\""
" expected_regex: \".* /var .* - .*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "tmp-nodev-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure nodev option set on /tmp partition"
description:
"The nodev mount option specifies that the filesystem cannot contain "
"special devices."
rationale:
"Since the /tmp filesystem is not intended to support devices, set "
"this option to ensure that users cannot attempt to create block or "
"character special devices in /tmp ."
remediation:
"Edit the /etc/fstab file and add nodev to the fourth field (mounting "
"options) for the /tmp partition. See the fstab(5) manual page for "
"more information.\n"
"Run the following command to remount /tmp:\n"
"```\n"
"# mount -o remount,nodev /tmp\n"
"```\n"
"or\n"
"Edit the config file in /usr/lib/systemd/system/tmp.mount.d to add "
"nodev to the /tmp mount options:\n"
"```\n"
"[Mount]\n"
"Options=mode=1777,strictatime,noexec,nodev,nosuid\n"
"Run the following command to remount /tmp:\n"
"# mount -o remount,nodev /tmp\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".* /tmp .* - .*\""
" expected_regex: \".* /tmp .*nodev.* - .*\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/lib/systemd/system/tmp.mount.d\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"Options=.*\""
" expected_regex: \"Options=.*nodev.*\""
" }"
" }"
" }"
" }"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".* /tmp .* - .*\""
" expected_regex: \".* /tmp .* - .*\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/lib/systemd/system/tmp.mount.d\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"Options=.*\""
" expected_regex: \"Options=.*nodev.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "tmp-nosuid-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure nosuid option set on /tmp partition"
description:
"The nosuid mount option specifies that the filesystem cannot contain "
"setuid files."
rationale:
"Since the /tmp filesystem is only intended for temporary file "
"storage, set this option to ensure that users cannot create setuid "
"files in /tmp ."
remediation:
"Edit the /etc/fstab file and add nosuid to the fourth field (mounting "
"options) for the /tmp partition. See the fstab(5) manual page for "
"more information."
"Run the following command to remount /tmp:\n"
"```\n"
"# mount -o remount,nosuid /tmp\n"
"```\n"
"or\n"
"Edit the config file in /usr/lib/systemd/system/tmp.mount.d to add "
"nosuid to the /tmp mount options:\n"
"```\n"
"[Mount]\n"
"Options=mode=1777,strictatime,noexec,nodev,nosuid\n"
"```\n"
"Run the following command to remount /tmp:\n"
"```\n"
"# mount -o remount,nosuid /tmp\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".* /tmp .* - .*\""
" expected_regex: \".* /tmp .*nosuid.* - .*\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/lib/systemd/system/tmp.mount.d\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"Options=.*\""
" expected_regex: \"Options=.*nosuid.*\""
" }"
" }"
" }"
" }"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".* /tmp .* - .*\""
" expected_regex: \".* /tmp .* - .*\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/lib/systemd/system/tmp.mount.d\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"Options=.*\""
" expected_regex: \"Options=.*nosuid.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "tmp-noexec-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure noexec option set on /tmp partition"
description:
"The noexec mount option specifies that the filesystem cannot contain "
"executable binaries."
rationale:
"Since the /tmp filesystem is only intended for temporary file "
"storage, set this option to ensure that users cannot run executable "
"binaries from /tmp ."
remediation:
"Edit the /etc/fstab file and add noexec to the fourth field (mounting "
"options) for the /tmp partition. See the fstab(5) manual page for "
"more information.\n"
"Run the following command to remount /tmp:\n"
"```\n"
"# mount -o remount,noexec /tmp\n"
"```\n"
"or\n"
"Edit the config file in /usr/lib/systemd/system/tmp.mount.d to add "
"noexec to the /tmp mount options:\n"
"```\n"
"[Mount]\n"
"Options=mode=1777,strictatime,noexec,nodev,nosuid\n"
"```\n"
"Run the following command to remount /tmp:\n"
"```\n"
"# mount -o remount,noexec /tmp\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".* /tmp .* - .*\""
" expected_regex: \".* /tmp .*noexec.* - .*\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/lib/systemd/system/tmp.mount.d\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"Options=.*\""
" expected_regex: \"Options=.*noexec.*\""
" }"
" }"
" }"
" }"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".* /tmp .* - .*\""
" expected_regex: \".* /tmp .* - .*\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/lib/systemd/system/tmp.mount.d\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"Options=.*\""
" expected_regex: \"Options=.*noexec.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "home-nodev-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure nodev option set on /home partition"
description:
"The nodev mount option specifies that the filesystem cannot contain "
"special devices."
rationale:
"Since the user partitions are not intended to support devices, set "
"this option to ensure that users cannot attempt to create block or "
"character special devices."
remediation:
"Edit the /etc/fstab file and add nodev to the fourth field (mounting "
"options) for the /home partition. See the fstab(5) manual page for "
"more information.\n"
"# mount -o remount,nodev /home\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".* /home .* - .*\""
" expected_regex: \".* /home .*nodev.* - .*\""
" }"
" }"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".* /home .* - .*\""
" expected_regex: \".* /home .* - .*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "shm-nodev-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure nodev option set on /dev/shm partition"
description:
"The nodev mount option specifies that the filesystem cannot contain "
"special devices."
rationale:
"Since the /dev/shm filesystem is not intended to support devices, set "
"this option to ensure that users cannot attempt to create special "
"devices in /dev/shm partitions."
remediation:
"Edit the /etc/fstab file and add nodev to the fourth field (mounting "
"options) for the /dev/shm partition. See the fstab(5) manual page for "
"more information.\n"
"Run the following command to remount /dev/shm:\n"
"```\n"
"# mount -o remount,nodev /dev/shm\n\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".* /dev/shm .* - .*\""
" expected_regex: \".* /dev/shm .*nodev.* - .*\""
" }"
" }"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".* /dev/shm .* - .*\""
" expected_regex: \".* /dev/shm .* - .*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "shm-nosuid-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure nosuid option set on /dev/shm partition"
description:
"The nosuid mount option specifies that the filesystem cannot contain "
"setuid files."
rationale:
"Setting this option on a file system prevents users from introducing "
"privileged programs onto the system and allowing non-root users to "
"execute them."
remediation:
"Edit the /etc/fstab file and add nosuid to the fourth field (mounting "
"options) for the /dev/shm partition. See the fstab(5) manual page for "
"more information.\n"
"Run the following command to remount /dev/shm:\n"
"```\n"
"# mount -o remount,nosuid /dev/shm\n\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".* /dev/shm .* - .*\""
" expected_regex: \".* /dev/shm .*nosuid.* - .*\""
" }"
" }"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".* /dev/shm .* - .*\""
" expected_regex: \".* /dev/shm .* - .*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "shm-noexec-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure noexec option set on /dev/shm partition"
description:
"The noexec mount option specifies that the filesystem cannot contain "
"executable binaries."
rationale:
"Setting this option on a file system prevents users from executing "
"programs from shared memory. This deters users from introducing "
"potentially malicious software on the system."
remediation:
"Make sure the /usr/lib/systemd/system/dev-shm-remount.service file "
"remounts the /dev/shm partition with noexec:\n"
"```\n"
"ExecStart=/bin/mount -o remount,noexec /dev/shm\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".* /dev/shm .* - .*\""
" expected_regex: \".* /dev/shm .*noexec.* - .*\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/lib/systemd/system/dev-shm-remount.service\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"ExecStart=.*\""
" expected_regex: \"ExecStart=/bin/mount -o remount.*noexec.* /dev/shm\""
" }"
" }"
" }"
" }"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".* /dev/shm .* - .*\""
" expected_regex: \".* /dev/shm .* - .*\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/lib/systemd/system/dev-shm-remount.service\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"ExecStart=.*\""
" expected_regex: \"ExecStart=/bin/mount -o remount.*noexec.* /dev/shm\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "dm-verity-installed-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:89" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure dm-verity is enabled"
description:
"device-mapper-verity (dm-verity) kernel feature provides transparent "
"integrity checking of block devices using a cryptographic digest "
"provided by the kernel crypto API."
rationale:
"The Container-Optimized OS root filesystem is always mounted as "
"read-only. Additionally, its checksum is computed at build time and "
"verified by the kernel on each boot. This mechanism prevents against "
"attackers from \"owning\" the machine through permanent local changes."
remediation: "An OS image update that has the dm-verity enabled kernel is required."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/config.gz\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"CONFIG_DM_VERITY=.*\""
" expected_regex: \"CONFIG_DM_VERITY=y\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "dm-verity-installed-cos-93"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure dm-verity is enabled"
description:
"device-mapper-verity (dm-verity) kernel feature provides transparent "
"integrity checking of block devices using a cryptographic digest "
"provided by the kernel crypto API."
rationale:
"The Container-Optimized OS root filesystem is always mounted as "
"read-only. Additionally, its checksum is computed at build time and "
"verified by the kernel on each boot. This mechanism prevents against "
"attackers from \"owning\" the machine through permanent local changes."
remediation: "An OS image update that has the dm-verity enabled kernel is required."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/boot\""
" recursive: false"
" filename_regex: \"config-.*\""
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"CONFIG_DM_VERITY=.*\""
" expected_regex: \"CONFIG_DM_VERITY=y\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "bootloader-permissions-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure permissions on bootloader config are configured"
description:
"The grub configuration file contains information on boot settings and "
"passwords for unlocking boot options. The grub configuration is usually "
"grub.cfg stored in /boot/grub2/ or /boot/grub/."
rationale:
"Setting the permissions to read and write for root only prevents "
"non-root users from seeing the boot parameters or changing them. "
"Non-root users who read the boot parameters may be able to identify "
"weaknesses in security upon boot and be able to exploit them."
remediation:
"Changing the permissions on grub configuration is not possible because "
"rootfs is read-only file system. An image update with the correct grub "
"configuration is required."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/boot/efi/boot/grub.cfg\"}}"
" permission:{"
" clear_bits: 0077"
" user: {name: \"root\" should_own: true}"
" group: {name: \"root\" should_own: true}"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "auth-for-single-user-required-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:89" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure authentication required for single user mode"
description:
"Single user mode is used for recovery when the system detects an "
"issue during boot or by manual selection from the bootloader."
rationale:
"Requiring authentication in single user mode prevents an unauthorized "
"user from rebooting the system into single user to gain root "
"privileges without credentials."
remediation:
"Rootfs is read-only file system. Therefore, update to an OS image "
"which requires single user mode authentication."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/lib/systemd/system/rescue.service\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"ExecStart=-/usr/lib/systemd/systemd-sulogin-shell.*\""
" expected_regex: \"ExecStart=-/usr/lib/systemd/systemd-sulogin-shell rescue\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/lib/systemd/system/emergency.service\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"ExecStart=-/usr/lib/systemd/systemd-sulogin-shell.*\""
" expected_regex: \"ExecStart=-/usr/lib/systemd/systemd-sulogin-shell emergency\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "core-dumps-restricted-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure core dumps are restricted"
description:
"A core dump is the memory of an executable program. It is generally "
"used to determine why a program aborted. It can also be used to glean "
"confidential information from a core file. The system provides the "
"ability to set a soft limit for core dumps, but this can be overridden "
"by the user."
rationale:
"Setting a hard limit on core dumps prevents users from overriding the "
"soft variable. If core dumps are required, consider setting limits for "
"user groups (see limits.conf(5) ). In addition, setting the "
"fs.suid_dumpable variable to 0 will prevent setuid programs from "
"dumping core."
remediation:
"Add the following line to /etc/security/limits.conf or a "
"/etc/security/limits.d/* file\n:"
"* hard core 0\n"
"Run the following command to set the active kernel parameter:\n"
"```\n"
"# sysctl -w fs.suid_dumpable=0\n"
"```\n"
"If systemd-coredump@ is installed:\n"
"edit /etc/systemd/coredump.conf and add/modify the following lines:\n"
"```\n"
"Storage=none\n"
"ProcessSizeMax=0\n"
"```\n"
"Run the command:\n"
"```\n"
"systemctl daemon-reload\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/security/limits.conf\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".*hard core.*\""
" expected_regex: \"\\\\* hard core 0\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/fs/suid_dumpable\"}}"
" content:{content:\"0\\n\"}"
" }"
" file_checks:{"
" files_to_check:{"
" files_in_dir:{"
" dir_path:\"/usr/lib/systemd/system\""
" recursive: true"
" filename_regex: \"systemd-coredump@.service\""
" }"
" }"
" existence:{should_exist: true}"
" }"
" file_checks:{"
" files_to_check:{"
" files_in_dir:{"
" dir_path:\"/usr/lib/systemd/system\""
" recursive: true"
" filename_regex: \"systemd-coredump.socket\""
" }"
" }"
" existence:{should_exist: true}"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*echo .* /etc/security/limits.conf.*\""
" expected_regex: \".*echo \\\"\\\\* hard core 0\\\" >> /etc/security/limits.conf.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "motd-configured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure message of the day is configured properly"
description:
"The contents of the /etc/motd file are displayed to users after login "
"and function as a message of the day for authenticated users.\n"
"Unix-based systems have typically displayed information about the OS "
"release and patch level upon logging in to the system. This information "
"can be useful to developers who are developing software for a "
"particular OS platform. If mingetty(8) supports the following options, "
"they display operating system information: \\m - machine architecture "
"\\r - operating system release \\s - operating system name \\v - "
"operating system version"
rationale:
"Warning messages inform users who are attempting to login to the "
"system of their legal status regarding the system and must include the "
"name of the organization that owns the system and any monitoring "
"policies that are in place. Displaying OS and patch level information "
"in login banners also has the side effect of providing detailed system "
"information to attackers attempting to target specific exploits of a "
"system. Authorized users can easily get this information by running "
"the \"uname -a\" command once they have logged in."
remediation:
"Edit the /etc/motd file with the appropriate contents according to "
"your site policy, remove any instances of \\m , \\r , \\s , \\v or "
"references to the OS platform\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/motd\"}}"
# The scan instructions don't support substituting in values of e.g.
# "uname -r" so for now we use the hard-coded system values specific to
# the COS release.
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".*Container-Optimized OS.*\""
" expected_regex: \".*Container-Optimized OS.*\""
" }"
# Architectures COS is currently running on.
" match_criteria: {"
" filter_regex: \".*(^|\\\\s+)x86_64($|\\\\s+).*\""
" expected_regex: \".*(^|\\\\s+)x86_64($|\\\\s+).*\""
" }"
" match_criteria: {"
" filter_regex: \".*(^|\\\\s+)arm($|\\\\s+).*\""
" expected_regex: \".*(^|\\\\s+)arm($|\\\\s+).*\""
" }"
# Kernel version.
" match_criteria: {"
" filter_regex: \".*[0-9]+\\\\.[0-9]+\\\\.[0-9]+($|\\\\s+).*\""
" expected_regex: \".*[0-9]+\\\\.[0-9]+\\\\.[0-9]+($|\\\\s+).*\""
" }"
" }"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/motd\"}}"
" existence:{should_exist:false}"
" }"
"}}"
}
}
benchmark_configs: {
id: "local-login-warning-configured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure local login warning banner is configured properly"
description:
"The contents of the /etc/issue file are displayed to users prior to "
"login for local terminals. Unix-based systems have typically "
"displayed information about the OS release and patch level upon "
"logging in to the system. This information can be useful to "
"developers who are developing software for a particular OS platform. "
"If mingetty(8) supports the following options, they display operating "
"system information: \\m - machine architecture \\r - operating system "
"release \\s - operating system name \\v - operating system version - or "
"the operating system's name"
rationale:
"Warning messages inform users who are attempting to login to the "
"system of their legal status regarding the system and must include "
"the name of the organization that owns the system and any monitoring "
"policies that are in place. Displaying OS and patch level information "
"in login banners also has the side effect of providing detailed "
"system information to attackers attempting to target specific "
"exploits of a system. Authorized users can easily get this "
"information by running the \" uname -a \" command once they have logged in."
remediation:
"Make sure the /etc/issue file is empty. Alternatively, edit the /etc/issue "
"file with the appropriate contents according to your site policy, remove "
"any instances of \\m , \\r , \\s , \\v or references to the OS platform, "
"and (when applicable) opt the file out from scanning to prevent further "
"compliance reports.\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/issue\"}}"
" content:{content:\"\"}"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/issue\"}}"
" existence:{should_exist:false}"
" }"
"}}"
}
}
benchmark_configs: {
id: "remote-login-warning-configured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure remote login warning banner is configured properly"
description:
"The contents of the /etc/issue.net file are displayed to users prior to "
"login for remote connections from configured services."
"Unix-based systems have typically displayed information about the OS "
"release and patch level upon logging in to the system. This "
"information can be useful to developers who are developing software "
"for a particular OS platform. If mingetty(8) supports the following "
"options, they display operating system information: \\m - machine "
"architecture \\r - operating system release \\s - operating system "
"name \\v - operating system version"
rationale:
"Warning messages inform users who are attempting to login to the "
"system of their legal status regarding the system and must include "
"the name of the organization that owns the system and any monitoring "
"policies that are in place. Displaying OS and patch level information "
"in login banners also has the side effect of providing detailed "
"system information to attackers attempting to target specific "
"exploits of a system. Authorized users can easily get this "
"information by running the \" uname -a \" command once they have logged "
"in."
remediation:
"Make sure the /etc/issue.net file is empty or deleted. Alternatively, "
"edit the /etc/issue.net file with the appropriate contents according "
"to your site policy, remove any instances of \\m , \\r , \\s , \\v "
"or references to the OS platform and (when applicable) opt the file "
"out from scanning to prevent further compliance reports.\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/issue.net\"}}"
" content:{content:\"\"}"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/issue.net\"}}"
" existence:{should_exist:false}"
" }"
"}}"
}
}
benchmark_configs: {
id: "motd-permissions-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure permissions on /etc/motd are configured"
description:
"The contents of the /etc/motd file are displayed to users after login "
"and function as a message of the day for authenticated users."
rationale:
"If the /etc/motd file does not have the correct ownership it could be "
"modified by unauthorized users with incorrect or misleading information."
remediation:
"Run the following commands to set permissions on /etc/motd:\n"
"```\n"
"# chown root:root /etc/motd\n"
"# chmod 644 /etc/motd\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/motd\"}}"
" permission:{"
" set_bits: 0444"
" clear_bits: 0133"
" bits_should_match: BOTH_SET_AND_CLEAR"
" user: {name: \"root\" should_own: true}"
" group: {name: \"root\" should_own: true}"
" }"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/motd\"}}"
" existence:{should_exist:false}"
" }"
"}}"
}
}
benchmark_configs: {
id: "etc-issue-permissions-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure permissions on /etc/issue are configured"
description:
"The contents of the /etc/issue file are displayed to users prior to "
"login for local terminals."
rationale:
"If the /etc/issue file does not have the correct ownership it could "
"be modified by unauthorized users with incorrect or misleading "
"information."
remediation:
"Run the following commands to set permissions on /etc/issue:\n"
"```\n"
"# chown root:root /etc/issue\n"
"# chmod 644 /etc/issue\n\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/issue\"}}"
" permission:{"
" set_bits: 0444"
" clear_bits: 0133"
" bits_should_match: BOTH_SET_AND_CLEAR"
" user: {name: \"root\" should_own: true}"
" group: {name: \"root\" should_own: true}"
" }"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/issue\"}}"
" existence:{should_exist:false}"
" }"
"}}"
}
}
benchmark_configs: {
id: "etc-issue-net-permissions-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure permissions on /etc/issue.net are configured"
description:
"The contents of the /etc/issue.net file are displayed to users prior "
"to login for remote connections from configured services."
rationale:
"If the /etc/issue.net file does not have the correct ownership it "
"could be modified by unauthorized users with incorrect or misleading "
"information."
remediation:
"Run the following commands to set permissions on /etc/issue.net:\n"
"```\n"
"# chown root:root /etc/issue.net\n"
"# chmod 644 /etc/issue.net\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/issue.net\"}}"
" permission:{"
" set_bits: 0444"
" clear_bits: 0133"
" bits_should_match: BOTH_SET_AND_CLEAR"
" user: {name: \"root\" should_own: true}"
" group: {name: \"root\" should_own: true}"
" }"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/issue.net\"}}"
" existence:{should_exist:false}"
" }"
"}}"
}
}
benchmark_configs: {
id: "chrony-installed-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:89" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure time synchronization is in use"
description:
"System time should be synchronized between all systems in an environment. This\n"
"is typically done by establishing an authoritative time server or set of\n"
"servers and having all systems synchronize their clocks to them."
rationale:
"Time synchronization is important to support time sensitive security\n"
"mechanisms like Kerberos and also ensures log files have consistent time\n"
"records across the enterprise, which aids in forensic investigations."
remediation:
"On physical systems or virtual systems where host based time "
"synchronization is not available update to an image that comes with "
"chrony package installed.\n"
"On virtual systems where host based time synchronization is available "
"consult your virtualization software documentation and setup host "
"based synchronization."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/cos-package-info.json\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".*\\\"name\\\": \\\"chrony\\\".*\""
" expected_regex: \".*\\\"name\\\": \\\"chrony\\\".*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "chrony-configured-cos-89"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:89" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure chrony is configured"
description:
"chrony is a daemon which implements the Network Time Protocol (NTP) is\n"
"designed to synchronize system clocks across a variety of systems and use a\n"
"source that is highly accurate. More information on chrony can be found at\n"
"http://chrony.tuxfamily.org/. chrony can be configured to be a client and/or a\n"
"server."
rationale:
"If chrony is in use on the system proper configuration is vital to ensuring\n"
"time synchronization is working properly. This recommendation only applies if\n"
"chrony is in use on the system."
remediation:
"Add or edit server or pool lines to /etc/chrony.conf as appropriate:\n"
"```\n"
"server <remote-server>\n"
"```\n"
"Configure chrony to run as the chrony user by configuring the appropriate\n"
"startup script for your distribution. Startup scripts are typically stored in \n"
"/etc/init.d or /etc/systemd"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/chrony/chrony.conf\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"server|pool .*\""
" expected_regex: \"server|pool .*\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/chrony/chrony.conf\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"server|pool .*\""
" expected_regex: \"server|pool .*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "chrony-configured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure chrony is configured"
description:
"chrony is a daemon which implements the Network Time Protocol (NTP) is\n"
"designed to synchronize system clocks across a variety of systems and use a\n"
"source that is highly accurate. More information on chrony can be found at\n"
"http://chrony.tuxfamily.org/. chrony can be configured to be a client and/or a\n"
"server."
rationale:
"If chrony is in use on the system proper configuration is vital to ensuring\n"
"time synchronization is working properly. This recommendation only applies if\n"
"chrony is in use on the system."
remediation:
"Add or edit server or pool lines to /etc/chrony.conf as appropriate:\n"
"```\n"
"server <remote-server>\n"
"```\n"
"Configure chrony to run as the chrony user by configuring the appropriate\n"
"startup script for your distribution. Startup scripts are typically stored in\n"
"etc/init.d or /etc/systemd"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/chrony/chrony.conf\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"server|pool .*\""
" expected_regex: \"server|pool .*\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{process_path:{proc_name:\"chronyd\"}}"
" permission:{user: {name: \"ntp\" should_own: true}}"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/chrony/chrony.conf\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"server|pool .*\""
" expected_regex: \"server|pool .*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "x-window-system-not-installed-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:89" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure X Window System is not installed"
description:
"The X Window System provides a Graphical User Interface (GUI) where users can\n"
"have multiple windows in which to run programs and various add on. The X\n"
"Windows system is typically used on workstations where users login, but not on\n"
"servers where users typically do not login."
rationale:
"Unless your organization specifically requires graphical login access via X\n"
"Windows, remove it to reduce the potential attack surface."
remediation: "An OS image update that does not include X Window System is required."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/cos-package-info.json\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".*\\\"name\\\": \\\".*xorg.*\\\".*\""
" expected_regex: \".*\\\"name\\\": \\\".*xorg.*\\\".*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "nfs-rpc-disabled-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:89" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure NFS and RPC are not enabled"
description:
"The Network File System (NFS) is one of the first and most widely distributed\n"
"file systems in the UNIX environment. It provides the ability for systems to\n"
"mount file systems of other servers through the network."
rationale:
"If the system does not export NFS shares or act as an NFS client, it is\n"
"recommended that these services be disabled to reduce the remote attack\n"
"surface."
remediation:
"Run one of the following commands to disable nfs and rpcbind:\n"
"```\n"
"# chkconfig nfs off\n"
"# chkconfig rpcbind off\n"
"# systemctl disable nfs\n"
"# systemctl disable rpcbind\n"
"# update-rc.d nfs disable\n"
"# update-rc.d rpcbind disable\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{"
" files_in_dir:{"
" dir_path:\"/etc/systemd/system\""
" recursive: true"
" filename_regex: \"nfs.service\""
" }"
" }"
" files_to_check:{"
" files_in_dir:{"
" dir_path:\"/etc/systemd/system\""
" recursive: true"
" filename_regex: \"rpcbind.service\""
" }"
" }"
" existence:{should_exist: false}"
" non_compliance_msg: \"a config file in /etc/systemd/system enables nfs or rpcbind\""
" file_display_command: \"find /etc/systemd/system -name 'nfs.service'; find /etc/systemd/system -name 'rpcbind.service'\""
" }"
"}}"
}
}
benchmark_configs: {
id: "rsync-disabled-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:89" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure rsync service is not enabled"
description:
"The rsyncd service can be used to synchronize files between systems over\n"
"network links."
rationale:
"The rsyncd service presents a security risk as it uses unencrypted protocols\n"
"for communication."
remediation:
"Run the following command to disable rsyncd:\n"
"```\n"
"# systemctl --now disable rsyncd\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/systemd/system\""
" recursive: true"
" filename_regex: \"rsyncd.service\""
" }}"
" existence:{should_exist: false}"
" non_compliance_msg: \"a config file in /etc/systemd/system enables rsyncd\""
" file_display_command: \"find /etc/systemd/system -name rsyncd.service\""
" }"
"}}"
}
}
benchmark_configs: {
id: "packet-redirect-sending-disabled-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure packet redirect sending is disabled"
description:
"ICMP Redirects are used to send routing information to other hosts. As a host\n"
"itself does not act as a router (in a host only configuration), there is no\n"
"need to send redirects."
rationale:
"An attacker could use a compromised host to send invalid ICMP redirects to\n"
"other router devices in an attempt to corrupt routing and have users access a\n"
"system set up by the attacker as opposed to a valid system."
remediation:
"Set the following parameters in /etc/sysctl.conf or a /etc/sysctl.d/* file:\n"
"```\n"
"net.ipv4.conf.all.send_redirects = 0\n"
"net.ipv4.conf.default.send_redirects = 0\n"
"```\n"
"Run the following commands to set the active kernel parameters:\n"
"```\n"
"# sysctl -w net.ipv4.conf.all.send_redirects=0\n"
"# sysctl -w net.ipv4.conf.default.send_redirects=0\n"
"# sysctl -w net.ipv4.route.flush=1\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/all/send_redirects\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/default/send_redirects\"}}"
" content:{content:\"0\\n\"}"
" }"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/sysctl.d\""
" recursive: true"
" }}"
" content_entry: {"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"net.ipv4.conf.all.send_redirects *=.*\""
" expected_regex: \"net.ipv4.conf.all.send_redirects *= *0\""
" }"
" match_criteria: {"
" filter_regex: \"net.ipv4.conf.default.send_redirects *=.*\""
" expected_regex: \"net.ipv4.conf.default.send_redirects *= *0\""
" }"
" }"
" non_compliance_msg: \"a config file in /etc/sysctl.d/ enables send_redirects\""
" file_display_command: \"grep -l 'send_redirects' /etc/sysctl.d/*\""
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/sysctl.d\""
" recursive: true"
" }}"
" content_entry: {"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"net.ipv4.conf.all.send_redirects *=.*\""
" expected_regex: \"net.ipv4.conf.all.send_redirects *= *0\""
" }"
" match_criteria: {"
" filter_regex: \"net.ipv4.conf.default.send_redirects *=.*\""
" expected_regex: \"net.ipv4.conf.default.send_redirects *= *0\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "source-routed-packets-not-accepted-cos-89"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:89" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure source routed packets are not accepted"
description:
"In networking, source routing allows a sender to partially or fully specify\n"
"the route packets take through a network. In contrast, non-source routed\n"
"packets travel a path determined by routers in the network. In some cases,\n"
"systems may not be routable or reachable from some locations (e.g. private\n"
"addresses vs. Internet routable), and so source routed packets would need to\n"
"be used."
rationale:
"Setting net.ipv4.conf.all.accept_source_route, and \n"
"net.ipv4.conf.default.accept_source_route to 0 disables the system from \n"
"accepting source routed packets. Assume this system was capable of routing \n"
"packets to Internet routable addresses on one interface and private addresses \n"
"on another interface. Assume that the private addresses were not routable to \n"
"the Internet routable addresses and vice versa. Under normal routing \n"
"circumstances, an attacker from the Internet routable addresses could not use \n"
"the system as a way to reach the private address systems. If, however, source \n"
"routed packets were allowed, they could be used to gain access to the private \n"
"address systems as the route could be specified, rather than rely on routing \n"
"protocols that did not allow this routing."
remediation:
"Run the following commands to set the active kernel parameters:\n"
"```\n"
"# sysctl -w net.ipv4.conf.all.accept_source_route=0\n"
"# sysctl -w net.ipv4.conf.default.accept_source_route=0\n"
"# sysctl -w net.ipv4.route.flush=1\n"
"```\n"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/all/accept_source_route\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/default/accept_source_route\"}}"
" content:{content:\"0\\n\"}"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/sysctl.d/\""
" recursive: true"
" }}"
" content_entry: {"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"net.ipv4.conf.all.accept_source_route *=.*\""
" expected_regex: \"net.ipv4.conf.all.accept_source_route *= *0\""
" }"
" match_criteria: {"
" filter_regex: \"net.ipv4.conf.default.accept_source_route *=.*\""
" expected_regex: \"net.ipv4.conf.default.accept_source_route *= *0\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "source-routed-packets-not-accepted-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure source routed packets are not accepted"
description:
"In networking, source routing allows a sender to partially or fully specify\n"
"the route packets take through a network. In contrast, non-source routed\n"
"packets travel a path determined by routers in the network. In some cases,\n"
"systems may not be routable or reachable from some locations (e.g. private\n"
"addresses vs. Internet routable), and so source routed packets would need to\n"
"be used."
rationale:
"Setting net.ipv4.conf.all.accept_source_route, and \n"
"net.ipv4.conf.default.accept_source_route to 0 disables the system from \n"
"accepting source routed packets. Assume this system was capable of routing \n"
"packets to Internet routable addresses on one interface and private addresses \n"
"on another interface. Assume that the private addresses were not routable to \n"
"the Internet routable addresses and vice versa. Under normal routing \n"
"circumstances, an attacker from the Internet routable addresses could not use \n"
"the system as a way to reach the private address systems. If, however, source \n"
"routed packets were allowed, they could be used to gain access to the private \n"
"address systems as the route could be specified, rather than rely on routing \n"
"protocols that did not allow this routing."
remediation:
"Run the following commands to set the active kernel parameters:\n"
"```\n"
"# sysctl -w net.ipv4.conf.all.accept_source_route=0\n"
"# sysctl -w net.ipv4.conf.default.accept_source_route=0\n"
"# sysctl -w net.ipv6.conf.all.accept_source_route=0\n"
"# sysctl -w net.ipv6.conf.default.accept_source_route=0\n"
"# sysctl -w net.ipv4.route.flush=1\n"
"# sysctl -w net.ipv6.route.flush=1\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/all/accept_source_route\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/default/accept_source_route\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv6/conf/all/accept_source_route\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv6/conf/default/accept_source_route\"}}"
" content:{content:\"0\\n\"}"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/sysctl.d/\""
" recursive: true"
" }}"
" content_entry: {"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"net.ipv4.conf.all.accept_source_route *=.*\""
" expected_regex: \"net.ipv4.conf.all.accept_source_route *= *0\""
" }"
" match_criteria: {"
" filter_regex: \"net.ipv4.conf.default.accept_source_route *=.*\""
" expected_regex: \"net.ipv4.conf.default.accept_source_route *= *0\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "icmp-redirects-not-accepted-cos-89"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:89" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure ICMP redirects are not accepted"
description:
"ICMP redirect messages are packets that convey routing information and tell\n"
"your host (acting as a router) to send packets via an alternate path. It is a\n"
"way of allowing an outside routing device to update your system routing\n"
"tables. By setting net.ipv4.conf.all.accept_redirects to 0, the system will\n"
"not accept any ICMP redirect messages, and therefore, won't allow outsiders\n"
"to update the system's routing tables."
rationale:
"Attackers could use bogus ICMP redirect messages to maliciously alter the\n"
"system routing tables and get them to send packets to incorrect networks and\n"
"allow your system packets to be captured."
remediation:
"Run the following commands to set the active kernel parameters:\n"
"```\n"
"# sysctl -w net.ipv4.conf.all.accept_redirects=0\n"
"# sysctl -w net.ipv4.conf.default.accept_redirects=0\n"
"# sysctl -w net.ipv4.route.flush=1\n"
"```\n"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/all/accept_redirects\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/default/accept_redirects\"}}"
" content:{content:\"0\\n\"}"
" }"
"}}"
}
}
benchmark_configs: {
id: "icmp-redirects-not-accepted-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure ICMP redirects are not accepted"
description:
"ICMP redirect messages are packets that convey routing information and tell\n"
"your host (acting as a router) to send packets via an alternate path. It is a\n"
"way of allowing an outside routing device to update your system routing\n"
"tables. By setting net.ipv4.conf.all.accept_redirects and net.ipv6.conf.all\n"
"accept_redirects to 0, the system will not accept any ICMP redirect messages,\n"
"and therefore, won't allow outsiders to update the system's routing tables."
rationale:
"Attackers could use bogus ICMP redirect messages to maliciously alter the\n"
"system routing tables and get them to send packets to incorrect networks and\n"
"allow your system packets to be captured."
remediation:
"Run the following commands to set the active kernel parameters:\n"
"```\n"
"# sysctl -w net.ipv4.conf.all.accept_redirects=0\n"
"# sysctl -w net.ipv4.conf.default.accept_redirects=0\n"
"# sysctl -w net.ipv6.conf.all.accept_redirects=0\n"
"# sysctl -w net.ipv6.conf.default.accept_redirects=0\n"
"# sysctl -w net.ipv4.route.flush=1\n"
"# sysctl -w net.ipv6.route.flush=1\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/all/accept_redirects\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/default/accept_redirects\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv6/conf/all/accept_redirects\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv6/conf/default/accept_redirects\"}}"
" content:{content:\"0\\n\"}"
" }"
"}}"
}
}
benchmark_configs: {
id: "secure-icmp-redirects-not-accepted-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure secure ICMP redirects are not accepted"
description:
"Secure ICMP redirects are the same as ICMP redirects, except they come "
"from gateways listed on the default gateway list. It is assumed that "
"these gateways are known to your system, and that they are likely to "
"be secure."
rationale:
"It is still possible for even known gateways to be compromised. "
"Setting net.ipv4.conf.all.secure_redirects to 0 protects the system "
"from routing table updates by possibly compromised known gateways."
remediation:
"Run the following commands to set the active kernel parameters:\n"
"```\n"
"# sysctl -w net.ipv4.conf.all.secure_redirects=0\n"
"# sysctl -w net.ipv4.conf.default.secure_redirects=0\n"
"# sysctl -w net.ipv4.route.flush=1\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/all/secure_redirects\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/default/secure_redirects\"}}"
" content:{content:\"0\\n\"}"
" }"
"}}"
}
}
benchmark_configs: {
id: "suspicious-packets-logged-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure suspicious packets are logged"
description:
"When enabled, this feature logs packets with un-routable source "
"addresses to the kernel log."
rationale:
"Enabling this feature and logging these packets allows an administrator "
"to investigate the possibility that an attacker is sending spoofed "
"packets to their system."
remediation:
"Run the following commands to set the active kernel parameters:\n"
"```\n"
"# sysctl -w net.ipv4.conf.all.log_martians=1\n"
"# sysctl -w net.ipv4.conf.default.log_martians=1\n"
"# sysctl -w net.ipv4.route.flush=1\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/all/log_martians\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/default/log_martians\"}}"
" content:{content:\"1\\n\"}"
" }"
"}}"
}
}
benchmark_configs: {
id: "broadcast-icmp-requests-ignored-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure broadcast ICMP requests are ignored"
description:
"Setting net.ipv4.icmp_echo_ignore_broadcasts to 1 will cause the system to\n"
"ignore all ICMP echo and timestamp requests to broadcast and multicast\n"
"addresses."
rationale:
"Accepting ICMP echo and timestamp requests with broadcast or multicast\n"
"destinations for your network could be used to trick your host into starting\n"
"or participating) in a Smurf attack. A Smurf attack relies on an attacker\n"
"sending large amounts of ICMP broadcast messages with a spoofed source\n"
"address. All hosts receiving this message and responding would send echo-reply\n"
"messages back to the spoofed address, which is probably not routable. If many\n"
"hosts respond to the packets, the amount of traffic on the network could be\n"
"significantly multiplied."
remediation:
"Set the following parameters in /etc/sysctl.conf or a /etc/sysctl.d/* file:\n"
"```\n"
"net.ipv4.icmp_echo_ignore_broadcasts = 1\n"
"```\n"
"Run the following commands to set the active kernel parameters:\n"
"```\n"
"# sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1\n"
"# sysctl -w net.ipv4.route.flush=1\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/icmp_echo_ignore_broadcasts\"}}"
" content:{content:\"1\\n\"}"
" }"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/sysctl.d/\""
" recursive: true"
" }}"
" content_entry: {"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"net.ipv4.icmp_echo_ignore_broadcasts *=.*\""
" expected_regex: \"net.ipv4.icmp_echo_ignore_broadcasts *= *1\""
" }"
" }"
" non_compliance_msg: \"config files in /etc/sysctl.d/ do not enable echo_ignore_broadcasts\""
" file_display_command: \"grep -l 'echo_ignore_broadcasts' /etc/sysctl.d/*\""
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/sysctl.d/\""
" recursive: true"
" }}"
" content_entry: {"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"net.ipv4.icmp_echo_ignore_broadcasts *=.*\""
" expected_regex: \"net.ipv4.icmp_echo_ignore_broadcasts *= *1\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "bogus-icmp-responses-ignored-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure bogus ICMP responses are ignored"
description:
"Setting icmp_ignore_bogus_error_responses to 1 prevents the kernel from\n"
"logging bogus responses (RFC-1122 non-compliant) from broadcast reframes,\n"
"keeping file systems from filling up with useless log messages."
rationale:
"Some routers (and some attackers) will send responses that violate RFC-1122\n"
"and attempt to fill up a log file system with many useless error messages."
remediation:
"Set the following parameter in /etc/sysctl.conf or a /etc/sysctl.d/* file:\n"
"```\n"
"net.ipv4.icmp_ignore_bogus_error_responses = 1\n"
"```\n"
"Run the following commands to set the active kernel parameters:\n"
"```\n"
"# sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1\n"
"# sysctl -w net.ipv4.route.flush=1\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/icmp_ignore_bogus_error_responses\"}}"
" content:{content:\"1\\n\"}"
" }"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/sysctl.d/\""
" recursive: true"
" }}"
" content_entry: {"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"net.ipv4.icmp_ignore_bogus_error_responses *=.*\""
" expected_regex: \"net.ipv4.icmp_ignore_bogus_error_responses *= *1\""
" }"
" }"
" non_compliance_msg: \"config files in /etc/sysctl.d/ do not enable icmp_ignore_bogus_error_responses\""
" file_display_command: \"grep -l 'icmp_ignore_bogus_error_responses' /etc/sysctl.d/*\""
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/sysctl.d/\""
" recursive: true"
" }}"
" content_entry: {"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"net.ipv4.icmp_ignore_bogus_error_responses *=.*\""
" expected_regex: \"net.ipv4.icmp_ignore_bogus_error_responses *= *1\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "reverse-path-filtering-enabled-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure Reverse Path Filtering is enabled"
description:
"Setting net.ipv4.conf.all.rp_filter and net.ipv4.conf.default.rp_filter to 1\n"
"forces the Linux kernel to utilize reverse path filtering on a received packet\n"
"to determine if the packet was valid. Essentially, with reverse path\n"
"filtering, if the return packet does not go out the same interface that the\n"
"corresponding source packet came from, the packet is dropped (and logged if\n"
"log_martians is set)."
rationale:
"Setting these flags is a good way to deter attackers from sending your system\n"
"bogus packets that cannot be responded to. One instance where this feature\n"
"breaks down is if asymmetrical routing is employed. This would occur when\n"
"using dynamic routing protocols (bgp, ospf, etc) on your system. If you are\n"
"using asymmetrical routing on your system, you will not be able to enable this\n"
"feature without breaking the routing."
remediation:
"Set the following parameters in /etc/sysctl.conf or a /etc/sysctl.d/* file:\n"
"```\n"
"net.ipv4.conf.all.rp_filter = 1\n"
"net.ipv4.conf.default.rp_filter = 1\n"
"```\n"
"Run the following commands to set the active kernel parameters:\n"
"```\n"
"# sysctl -w net.ipv4.conf.all.rp_filter=1\n"
"# sysctl -w net.ipv4.conf.default.rp_filter=1\n"
"# sysctl -w net.ipv4.route.flush=1\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/all/rp_filter\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/conf/default/rp_filter\"}}"
" content:{content:\"1\\n\"}"
" }"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/sysctl.d/\""
" recursive: true"
" }}"
" content_entry: {"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"net.ipv4.conf.all.rp_filter *=.*\""
" expected_regex: \"net.ipv4.conf.all.rp_filter *= *1\""
" }"
" match_criteria: {"
" filter_regex: \"net.ipv4.conf.default.rp_filter *=.*\""
" expected_regex: \"net.ipv4.conf.default.rp_filter *= *1\""
" }"
" }"
" non_compliance_msg: \"config files in /etc/sysctl.d/ do not enable rp_filter\""
" file_display_command: \"grep -l 'rp_filter' /etc/sysctl.d/*\""
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/sysctl.d/\""
" recursive: true"
" }}"
" content_entry: {"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"net.ipv4.conf.all.rp_filter *=.*\""
" expected_regex: \"net.ipv4.conf.all.rp_filter *= *1\""
" }"
" match_criteria: {"
" filter_regex: \"net.ipv4.conf.default.rp_filter *=.*\""
" expected_regex: \"net.ipv4.conf.default.rp_filter *= *1\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "tcp-syn-cookies-enabled-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure TCP SYN Cookies is enabled"
description:
"When tcp_syncookies is set, the kernel will handle TCP SYN packets normally\n"
"until the half-open connection queue is full, at which time, the SYN cookie\n"
"functionality kicks in. SYN cookies work by not using the SYN queue at all.\n"
"Instead, the kernel simply replies to the SYN with a SYN|ACK, but will include\n"
"a specially crafted TCP sequence number that encodes the source and\n"
"destination IP address and port number and the time the packet was sent. A\n"
"legitimate connection would send the ACK packet of the three way handshake\n"
"with the specially crafted sequence number. This allows the system to verify\n"
"that it has received a valid response to a SYN cookie and allow the\n"
"connection, even though there is no corresponding SYN in the queue."
rationale:
"Attackers use SYN flood attacks to perform a denial of service attacked on a\n"
"system by sending many SYN packets without completing the three way handshake.\n"
"This will quickly use up slots in the kernel's half-open connection queue and\n"
"prevent legitimate connections from succeeding. SYN cookies allow the system\n"
"to keep accepting valid connections, even if under a denial of service attack."
remediation:
"Set the following parameters in /etc/sysctl.conf or a /etc/sysctl.d/* file:\n"
"```\n"
"net.ipv4.tcp_syncookies = 1\n"
"```\n"
"Run the following commands to set the active kernel parameters:\n"
"```\n"
"# sysctl -w net.ipv4.tcp_syncookies=1\n"
"# sysctl -w net.ipv4.route.flush=1\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv4/tcp_syncookies\"}}"
" content:{content:\"1\\n\"}"
" }"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/sysctl.d/\""
" recursive: true"
" }}"
" content_entry: {"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"net.ipv4.tcp_syncookies *=.*\""
" expected_regex: \"net.ipv4.tcp_syncookies *= *1\""
" }"
" }"
" non_compliance_msg: \"config files in /etc/sysctl.d/ do not enable tcp_syncookies\""
" file_display_command: \"grep -l 'tcp_syncookies' /etc/sysctl.d/*\""
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/sysctl.d/\""
" recursive: true"
" }}"
" content_entry: {"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"net.ipv4.tcp_syncookies *=.*\""
" expected_regex: \"net.ipv4.tcp_syncookies *= *1\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "ipv6-router-advertisements-not-accepted-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure IPv6 router advertisements are not accepted"
description:
"This setting disables the system's ability to accept IPv6 router "
"advertisements."
rationale:
"It is recommended that systems do not accept router advertisements as "
"they could be tricked into routing traffic to compromised machines. "
"Setting hard routes within the system (usually a single default route "
"to a trusted router) protects the system from bad routes."
remediation:
"Run the following commands to set the active kernel parameters:\n"
"```\n"
"# sysctl -w net.ipv6.conf.all.accept_ra=0\n"
"# sysctl -w net.ipv6.conf.default.accept_ra=0\n"
"# sysctl -w net.ipv6.route.flush=1\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv6/conf/all/accept_ra\"}}"
" files_to_check:{single_file:{path:\"/proc/sys/net/ipv6/conf/default/accept_ra\"}}"
" content:{content:\"0\\n\"}"
" }"
"}}"
}
}
benchmark_configs: {
id: "iptables-installed-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:89" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure iptables is installed"
description:
"iptables allows configuration of the IPv4 and IPv6 tables in the linux kernel\n"
"and the rules stored within them. Most firewall configuration utilities\n"
"operate as a front end to iptables."
rationale: "iptables is required for firewall management and configuration."
remediation: "An OS image update is required."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/cos-package-info.json\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".*\\\"name\\\": \\\"iptables\\\".*\""
" expected_regex: \".*\\\"name\\\": \\\"iptables\\\".*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "stackdriver-correct-container"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure correct container image is set for stackdriver logging agent"
description:
"stackdriver-logging service runs stackdriver container image to export "
"logs to Cloud Logging."
rationale:
"If the logging agent is not set correctly, the logs cannot be exported "
"to Cloud Logging."
remediation:
"Edit the LOGGING_AGENT_DOCKER_IMAGE variable in the "
"/etc/stackdriver/env_vars file to set the correct logging agent.\n"
"Run the following command to restart stackdriver-logging service:\n"
"```\n"
"# systemctl restart stackdriver-logging\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/stackdriver/env_vars\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"LOGGING_AGENT_DOCKER_IMAGE=.*\""
" expected_regex: \"LOGGING_AGENT_DOCKER_IMAGE=\\\"gcr.io/stackdriver-agents/stackdriver-logging-agent:.*\\\"\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "logging-service-running"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure logging Service is running"
description:
"Stackdriver-logging agent or fluent-bit logging agent needs "
"to be activated in order to export logs to Cloud Logging."
rationale:
"If neither stackdriver-logging nor fluent-bit service is running, "
"the logs will not be exported to Cloud Logging."
remediation:
"Stackdriver-logging Agent \n"
"Run the following command to enable stackdriver-logging : \n"
"```# systemctl start stackdriver-logging```\n "
"Fluent-bit Logging \n"
"Run the following command to enable fluent-bit : \n"
"```# systemctl start fluent-bit```\n "
"Works for Both \n"
"Simply update the instance metadata to enable logging as follows: \n"
"```# gcloud compute instances add-metadata <instance-name> \\ --zone <compute-zone> \\ --metadata google-logging-enabled=true```"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{"
" files_in_dir:{"
" dir_path:\"/run/systemd/units\""
" recursive: true"
" filename_regex: \"invocation:stackdriver-logging.service\""
" }"
" }"
" existence:{should_exist: true}"
" }"
"} check_alternatives:{"
" file_checks:{"
" files_to_check:{"
" files_in_dir:{"
" dir_path:\"/run/systemd/units\""
" recursive: true"
" filename_regex: \"invocation:fluent-bit.service\""
" }"
" }"
" existence:{should_exist: true}"
" }"
"}}"
}
}
benchmark_configs: {
id: "logging-configured"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure logging is configured"
description:
"For AMD, the /etc/stackdriver/logging.config.d/*.conf files specifies rules "
"for logging and which files are to be used to log certain classes of "
"messages. ARM uses /usr/share/fluent-bit/fluent-bit.conf for the same"
"purpose."
rationale:
"A great deal of important security-related information is sent via "
"logging (e.g., successful and failed su attempts, failed "
"login attempts, root login attempts, etc.)."
remediation:
"Review the contents of the /etc/stackdriver/logging.config.d/*.conf for AMD"
"and /usr/share/fluent-bit/fluent-bit.conf for ARM to ensure appropriate"
"logging is set. In addition, run the following command and verify that"
"the log files are logging information:\n"
"```\n"
"# ls -l /var/log/\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above need to be performed after every boot for AMD. This"
"is not the case for ARM as the logging agent is in /usr/share/ which"
"isn't stateless so changes will be persistent across reboots."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/stackdriver/logging.config.d\""
" recursive: true"
" filename_regex: \".*\\\\.conf\""
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
# Expect some kind of logging config in the file (i.e. not just comments).
" filter_regex: \"[^#].*\""
" expected_regex: \"[^#].*\""
" }"
" }"
" }"
"}"
# ARM images use fluent-bit instead of fluentd for logging.
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/share/fluent-bit/fluent-bit.conf\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"[^#].*\""
" expected_regex: \"[^#].*\""
" }"
" }"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/fluent-bit/fluent-bit.conf\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"[^#].*\""
" expected_regex: \"[^#].*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "journald-compress-large-log-files-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure journald is configured to compress large log files"
description:
"The journald system includes the capability of compressing overly "
"large files to avoid filling up the system with logs or making the "
"logs unmanageably large."
rationale:
"Uncompressed large files may unexpectedly fill a filesystem leading to "
"resource unavailability. Compressing logs prior to write can prevent "
"sudden, unexpected filesystem impacts."
remediation:
"Edit the /etc/systemd/journald.conf file and add the following line:\n"
"```\n"
"Compress=yes\n"
"```\n"
"Reload the configuration to be effective.\n"
"```\n"
"# systemctl force-reload systemd-journald\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/systemd/journald.conf\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"Compress=.*\""
" expected_regex: \"Compress=yes\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*sed -i 's/\\\\^#Compress=.*/Compress=.*/' /etc/systemd/journald.conf.*\""
" expected_regex: \".*sed -i 's/\\\\^#Compress=.*/Compress=yes/' /etc/systemd/journald.conf.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "journald-write-to-persistent-disk-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure journald is configured to write logfiles to persistent disk"
description:
"Data from journald may be stored in volatile memory or persisted locally on\n"
"the server. Logs in memory will be lost upon a system reboot. By persisting\n"
"logs to local disk on the server they are protected from loss."
rationale:
"Writing log data to disk will provide the ability to forensically reconstruct\n"
"events which may have impacted the operations or security of a system even\n"
"after a system crash or reboot."
remediation:
"Edit the /etc/systemd/journald.conf file and add the following line:\n"
"```\n"
"Storage=persistent\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/systemd/journald.conf\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"Storage=.*\""
" expected_regex: \"Storage=persistent\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "logfile-permissions-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure permissions on all logfiles are configured"
description:
"Log files stored in /var/log/ contain logged information from many "
"services on the system, or on log hosts others as well."
rationale:
"It is important to ensure that log files have the correct permissions "
"to ensure that sensitive data is archived and protected."
remediation:
"Run the following commands to set permissions on all existing log files:\n"
"```\n"
"find /var/log -type f -exec chmod g-wx,o-rwx \"{}\" + -o -type d -exec chmod gw,o-rwx \"{}\" +\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*sudo find /var/log.*\""
" expected_regex: \".*sudo find /var/log -type f -exec chmod g-wx,o-rwx \\\"{}\\\" \\\\+ -o .* -type d -exec chmod g-w,o-rwx \\\"{}\\\" +.*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "logrotate-configured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure logrotate is configured"
description:
"The system includes the capability of rotating log files regularly to "
"avoid filling up the system with logs or making the logs unmanageably "
"large. The file /etc/logrotate.d/syslog is the configuration file used "
"to rotate log files created by syslog or rsyslog."
rationale:
"By keeping the log files smaller and more manageable, a system "
"administrator can easily archive these files to another system and "
"spend less time looking through inordinately large log files."
remediation:
"Edit /etc/logrotate.conf and /etc/logrotate.d/* to ensure logs are "
"rotated according to site policy.\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/logrotate.conf\"}}"
" existence:{should_exist: true}"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/logrotate.d\"}}"
" existence:{should_exist: true}"
" }"
"}}"
}
}
benchmark_configs: {
id: "password-creation-reqs-configured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure password creation requirements are configured"
description:
"The pam_passwdqc.so module checks the strength of passwords. It "
"performs checks such as making sure a password is not a dictionary "
"word, it is a certain length, contains a mix of characters (e.g. "
"alphabet, numeric, other) and more based on the following options set "
"in the /etc/security/passwdqc.conf:\n"
"min=disabled,disabled,disabled,disabled,14 - The password must be 14 "
"characters or more and consists of four character classes.\n"
"max=40 - The maximum allowed password length is 40.\n"
"passphrase=3 - The number of words required for a passphrase is at "
"least 3.\n"
"match=4 - The length of common substring required to conclude that a "
"password is at least partially based on information found in a "
"character string is 4.\n"
"similar=deny - The password that is similar to the old one is going to "
"be denied.\n"
"random=47 - The size of randomly-generated passphrases in bits is 47.\n"
"enforce=everyone - Warn everyone for weak passwords.\n"
"retry=3 - Let the user provide a password 3 times if the user fails to "
"provide a sufficiently strong password and enter it twice the first "
"time.\n"
"For more details, refer to pam_passwdqc module documentation. The "
"settings shown above are one possible policy. Alter these values to "
"conform to your own organization's password policies.\n"
rationale:
"Strong passwords protect systems from being hacked through brute force "
"methods."
remediation:
"Edit the file /etc/security/passwdqc.conf and add or modify the "
"following lines for password length and complexity to conform to site "
"policy:\n"
"```\n"
"min=disabled,disabled,disabled,disabled,14\n"
"max=40\n"
"passphrase=3\n"
"match=4\n"
"similar=deny\n"
"random=47\n"
"enforce=everyone\n"
"retry=3\n"
"```\n"
"Edit the /etc/pam.d/system-auth files to include the appropriate "
"options for pam_passwdqc.so and to conform to site policy:\n"
"```\n"
"password required pam_passwdqc.so config=/etc/security/passwdqc.conf\n"
"```\n"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/security/passwdqc.conf\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"min=.*\""
" expected_regex: \"min=disabled,disabled,disabled,disabled,(\\\\d+)\""
" group_criteria: {"
" group_index: 1"
" type: GREATER_THAN"
" const: 13"
" }"
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/pam.d\""
" filename_regex: \"(system-auth)|(common-password)\""
" recursive: false"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".*pam_passwdqc.so.*\""
" expected_regex: \"password\\\\s+required\\\\s+pam_passwdqc.so\\\\s+config=/etc/security/passwdqc.conf\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "default-user-umask-027-or-more-restrictive-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure default user umask is 027 or more restrictive"
description:
"The default umask determines the permissions of files created by "
"users. The user creating the file has the discretion of making their "
"files and directories readable by others via the chmod command. Users "
"who wish to allow their files and directories to be readable by others "
"by default may choose a different default umask by inserting the umask "
"command into the standard shell configuration files (.profile, .bashrc"
", etc.) in their home directories."
rationale:
"Setting a very secure default value for umask ensures that users make "
"a conscious choice about their file permissions. A default umask "
"setting of 077 causes files and directories created by users to not be "
"readable by any other user on the system. A umask of 027 would make "
"files and directories readable by users in the same Unix group, while "
"a umask of 022 would make files readable by every user on the system."
remediation:
"Edit the /etc/bash/bashrc, /etc/profile and /etc/profile.d/*.sh files "
"(and the appropriate files for any other shell supported on your "
"system) and add or edit any umask parameters as follows:\n"
"```\n"
"umask 027\n"
"```\n"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/bash/bashrc\"}}"
" files_to_check:{single_file:{path:\"/etc/profile\"}}"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/profile.d\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"umask .*\""
" expected_regex: \"umask (\\\\d+)\""
" group_criteria: {"
" group_index: 1"
" type: NO_LESS_RESTRICTIVE_UMASK"
" const: 027"
" }"
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*sed.*umask.*/etc/profile.*\""
" expected_regex: \".*sed -i 's/\\\\^umask \\\\.\\\\*\\\\$/umask 027/' /etc/profile.*\""
" }"
" match_criteria: {"
" filter_regex: \".*echo.*umask.*/etc/profile.d/\\\\*.*\""
" expected_regex: \".*echo \\\"umask 027\\\" \\\\| tee -a /etc/profile.d/\\\\*.*\""
" }"
" match_criteria: {"
" filter_regex: \".*echo.*umask.*/etc/bash/bashrc.*\""
" expected_regex: \".*echo \\\"umask 027\\\" >> /etc/bash/bashrc.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "access-to-su-restricted-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure access to the su command is restricted"
description:
"The su command allows a user to run a command or shell as another user. The\n"
"program has been superseded by sudo , which allows for more granular control\n"
"over privileged access. Normally, the su command can be executed by any user.\n"
"By uncommenting the pam_wheel.so statement in /etc/pam.d/su , the su command\n"
"will only allow users in the wheel group to execute su."
rationale:
"Restricting the use of su , and using sudo in its place, provides system\n"
"administrators better control of the escalation of user privileges to execute\n"
"privileged commands. The sudo utility also provides a better logging and audit\n"
"mechanism, as it can log each command executed via sudo, whereas su can only\n"
"record that a user executed the su program."
remediation:
"Add the following line to the /etc/pam.d/su file:\n"
"```\n"
"auth required pam_wheel.so use_uid\n"
"```\n"
"Create a comma separated list of users in the wheel statement in the "
"/etc/group file:\n"
"```\n"
"wheel:!:10:root,<user list>\n"
"```\n"
"`/etc` is stateless on Container-Optimized OS. Therefore, `/etc` "
"cannot be used to make these changes persistent across reboots. The "
"steps mentioned above needs to be performed after every boot."
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/pam.d/su\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"auth.*\\\\spam_wheel.so\\\\s.*\""
" expected_regex: \"auth\\\\s*required\\\\s*pam_wheel.so\\\\s*use_uid\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/group\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"wheel:.*\""
" expected_regex: \"wheel:.*:.*:(.*,)?root(,|$).*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "etc-passwd-dash-permissions-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure permissions on /etc/passwd- are configured"
description: "The /etc/passwd- file contains backup user account information."
rationale:
"It is critical to ensure that the /etc/passwd- file is protected from "
"unauthorized access. Although it is protected by default, the file "
"permissions could be changed either inadvertently or through malicious "
"actions."
remediation:
"Run the following command to set permissions on /etc/passwd-:\n"
"```\n"
"# chown root:root /etc/passwd-\n"
"# chmod u-x,go-wx /etc/passwd-\n"
"```\n"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/passwd-\"}}"
" existence:{should_exist:false}"
" }"
"}"
"check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/passwd-\"}}"
" permission:{"
" clear_bits: 0133"
" user: {name: \"root\" should_own: true}"
" group: {name: \"root\" should_own: true}"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "root-path-integrity-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure root PATH Integrity"
description:
"The root user can execute any command on the system and could be fooled "
"into executing programs unintentionally if the PATH is not set correctly"
rationale:
"Including the current working directory (.) or other writable directory "
"in root's executable path makes it likely that an attacker can gain "
"superuser access by forcing an administrator operating as root to execute "
"a Trojan horse program."
remediation: "Correct or justify any items discovered by the CIS document's Audit step."
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
# Check the env vars of the scanner process's user. This assumes that the
# scanner is running as root.
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/environ\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" delimiter: \"\\0\""
# No empty dirs.
" match_criteria: {"
" filter_regex: \"PATH=.*\""
" expected_regex: \"PATH=.*::\""
" }"
# No trailing ':'.
" match_criteria: {"
" filter_regex: \"PATH=.*\""
" expected_regex: \"PATH=.*:$\""
" }"
" }"
" }"
# Directories have restricted permissions.
" file_checks:{"
" files_to_check:{unix_env_var_paths:{"
" var_name: \"PATH\""
" dirs_only: true"
" }}"
" permission:{"
" clear_bits: 0022"
" user: {name: \"root\" should_own: true}"
" }"
" }"
# No files among paths.
" file_checks:{"
" files_to_check:{unix_env_var_paths:{"
" var_name: \"PATH\""
" files_only: true"
" }}"
" existence:{should_exist: false}"
" }"
# Base dir of /opt/bin and /usr/local/(s)bin are readonly.
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/self/mountinfo\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \".* / / .*- .*\""
" expected_regex: \".* / .*ro*\""
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "udf-mounting-disabled-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure mounting of udf filesystems is disabled"
description:
"The udf filesystem type is the universal disk format used to implement "
"ISO/IEC 13346 and ECMA-167 specifications. This is an open vendor "
"filesystem type for data storage on a broad range of media. This "
"filesystem type is necessary to support writing DVDs and newer optical "
"disc formats."
rationale:
"Removing support for unneeded filesystem types reduces the local "
"attack surface of the system. If this filesystem type is not needed, "
"disable it."
remediation:
"Edit or create a file in the /etc/modprobe.d/ directory ending in .conf\n"
"Example: vim /etc/modprobe.d/udf.conf\n"
"and add the following line:\n"
"```\n"
"install udf /bin/true\n"
"```\n"
"Run the following command to unload the udf module:\n"
"```\n"
"# rmmod udf\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/proc/modules\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \"udf .*\""
" expected_regex: \"udf .*\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/modprobe.d\""
" filename_regex: \".*\\\\.conf\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"install udf .*\""
" expected_regex: \"install udf /bin/true\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*echo \\\"install udf .*\""
" expected_regex: \".*echo \\\"install udf /bin/true\\\" > /etc/modprobe.d/udf.conf.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "strong-mac-algorithms-used-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure only strong MAC algorithms are used"
description: "This variable limits the types of MAC algorithms that SSH can use during communication."
rationale:
"MD5 and 96-bit MAC algorithms are considered weak and have been shown "
"to increase exploitability in SSH downgrade attacks. Weak algorithms "
"continue to have a great deal of attention as a weak spot that can be "
"exploited with expanded computing power. An attacker that breaks the "
"algorithm could take advantage of a MiTM position to decrypt the SSH "
"tunnel and capture credentials and information"
remediation:
"Edit the /etc/ssh/sshd_config file and add/modify the MACs line to "
"contain a comma separated list of the site approved MACs\n"
"Example:\n"
"```\n"
"MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/ssh/sshd_config\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*hmac-md5(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*hmac-md5-96(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*hmac-ripemd160(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*hmac-sha1(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*hmac-sha1-96(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*umac-64@openssh.com(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*umac-128@openssh.com(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*hmac-md5-etm@openssh.com(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*hmac-md5-96-etm@openssh.com(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*hmac-ripemd160-etm@openssh.com(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*hmac-sha1-etm@openssh.com(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*hmac-sha1-96-etm@openssh.com(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*umac-64-etm@openssh.com(,|$).*\""
" }"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*umac-128-etm@openssh.com(,|$).*\""
" }"
" }"
" }"
# The default values are also insecure so check that they're overridden.
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/ssh/sshd_config\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"MACs .*\""
" expected_regex: \"MACs .*\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*echo .*MACs.* /etc/ssh/sshd_config.*\""
" expected_regex: \".*echo \\\"MACs hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,[^a-z]*hmac-sha2-256,hmac-sha2-512\\\" >> /etc/ssh/sshd_config.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "ssh-idle-timeout-interval-configured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure SSH Idle Timeout Interval is configured"
description:
"The two options ClientAliveInterval and ClientAliveCountMax control the "
"timeout of ssh sessions. When the ClientAliveInterval variable is set, "
"ssh sessions that have no activity for the specified length of time are "
"terminated. When the ClientAliveCountMax variable is set, sshd will "
"send client alive messages at every ClientAliveInterval interval. When "
"the number of consecutive client alive messages are sent with no "
"response from the client, the ssh session is terminated. For example, "
"if the ClientAliveInterval is set to 15 seconds and the "
"ClientAliveCountMax is set to 3, the client ssh session will be "
"terminated after 45 seconds of idle time."
rationale:
"Having no timeout value associated with a connection could allow an "
"unauthorized user access to another user's ssh session (e.g. user "
"walks away from their computer and doesn't lock the screen). Setting "
"a timeout value at least reduces the risk of this happening.\n"
"While the recommended setting is 300 seconds (5 minutes), set this "
"timeout value based on site policy. The recommended setting for "
"ClientAliveCountMax is 0. In this case, the client session will be "
"terminated after 5 minutes of idle time and no keepalive messages will "
"be sent."
remediation:
"Edit the /etc/ssh/sshd_config file to set the parameters according to "
"site policy:\n"
"```\n"
"ClientAliveInterval 300\n"
"ClientAliveCountMax 0\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/ssh/sshd_config\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"ClientAliveInterval .*\""
" expected_regex: \"ClientAliveInterval (\\\\d+)\""
" group_criteria:{"
" group_index: 1"
" type: LESS_THAN"
" const: 301"
" }"
" }"
" match_criteria: {"
" filter_regex: \"ClientAliveInterval .*\""
" expected_regex: \"ClientAliveInterval (\\\\d+)\""
" group_criteria:{"
" group_index: 1"
" type: GREATER_THAN"
" const: 0"
" }"
" }"
" match_criteria: {"
" filter_regex: \"ClientAliveCountMax .*\""
" expected_regex: \"ClientAliveCountMax (\\\\d+)\""
" group_criteria:{"
" group_index: 1"
" type: LESS_THAN"
" const: 4"
" }"
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*sed .*ClientAliveInterval.* /etc/ssh/sshd_config.*\""
" expected_regex: \".*sed -i 's/\\\\^ClientAliveInterval .*\\\\$/ClientAliveInterval 300/'.*/etc/ssh/sshd_config.*\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*echo.*ClientAliveCountMax.*/etc/ssh/sshd_config.*\""
" expected_regex: \".*echo \\\"ClientAliveCountMax 0\\\" >> /etc/ssh/sshd_config.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "ssh-logingrace-one-minute-or-less-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure SSH LoginGraceTime is set to one minute or less"
description:
"The LoginGraceTime parameter specifies the time allowed for successful "
"authentication to the SSH server. The longer the Grace period is the "
"more open unauthenticated connections can exist. Like other session "
"controls in this session the Grace Period should be limited to "
"appropriate organizational limits to ensure the service is available "
"for needed access."
rationale:
"Setting the LoginGraceTime parameter to a low number will minimize the "
"risk of successful brute force attacks to the SSH server. It will also "
"limit the number of concurrent unauthenticated connections While the "
"recommended setting is 60 seconds (1 Minute), set the number based on "
"site policy."
remediation:
"Edit the /etc/ssh/sshd_config file to set the parameter as follows:\n"
"```\n"
"LoginGraceTime 60\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/ssh/sshd_config\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"LoginGraceTime .*\""
" expected_regex: \"LoginGraceTime (\\\\d+)\""
" group_criteria:{"
" group_index: 1"
" type: LESS_THAN"
" const: 61"
" }"
" }"
" match_criteria: {"
" filter_regex: \"LoginGraceTime .*\""
" expected_regex: \"LoginGraceTime (\\\\d+)\""
" group_criteria:{"
" group_index: 1"
" type: GREATER_THAN"
" const: 0"
" }"
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*echo.*LoginGraceTime.*/etc/ssh/sshd_config.*\""
" expected_regex: \".*echo \\\"LoginGraceTime 60\\\" >> /etc/ssh/sshd_config.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "ssh-warning-banner-configured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure SSH warning banner is configured"
description:
"The Banner parameter specifies a file whose contents must be sent to "
"the remote user before authentication is permitted. By default, no "
"banner is displayed."
rationale:
"Banners are used to warn connecting users of the particular site's "
"policy regarding connection. Presenting a warning message prior to "
"the normal user login may assist the prosecution of trespassers on "
"the computer system."
remediation:
"Edit the /etc/ssh/sshd_config file to set the parameter as follows:\n"
"```\n"
"Banner /etc/issue.net\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/ssh/sshd_config\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"Banner .*\""
" expected_regex: \"Banner /etc/issue.net\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*echo.*Banner.*/etc/ssh/sshd_config.*\""
" expected_regex: \".*echo \\\"Banner /etc/issue.net\\\" >> /etc/ssh/sshd_config.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "ssh-allowtcpforwarding-disabled-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure SSH AllowTcpForwarding is disabled"
description:
"SSH port forwarding is a mechanism in SSH for tunneling application "
"ports from the client to the server, or servers to clients. It can be "
"used for adding encryption to legacy applications, going through "
"firewalls, and some system administrators and IT professionals use it "
"for opening backdoors into the internal network from their home machines"
rationale:
"Leaving port forwarding enabled can expose the organization to "
"security risks and backdoors.\n"
"SSH connections are protected with strong encryption. This makes their "
"contents invisible to most deployed network monitoring and traffic "
"filtering solutions. This invisibility carries considerable risk "
"potential if it is used for malicious purposes such as data "
"exfiltration. Cybercriminals or malware could exploit SSH to hide their "
"unauthorized communications, or to exfiltrate stolen data from the "
"target network"
remediation:
"Edit the /etc/ssh/sshd_config file to set the parameter as follows:\n"
"```\n"
"AllowTcpForwarding no\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/ssh/sshd_config\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"AllowTcpForwarding .*\""
" expected_regex: \"AllowTcpForwarding no\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*sed.*AllowTcpForwarding.*/etc/ssh/sshd_config.*\""
" expected_regex: \".*sed -i 's/\\\\^AllowTcpForwarding \\\\.\\\\*\\\\$/AllowTcpForwarding no/' /etc/ssh/sshd_config.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "ssh-maxstartups-configured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure SSH MaxStartups is configured"
description:
"The MaxStartups parameter specifies the maximum number of concurrent "
"unauthenticated connections to the SSH daemon."
rationale:
"To protect a system from denial of service due to a large number of "
"pending authentication connection attempts, use the rate limiting "
"function of MaxStartups to protect availability of sshd logins and "
"prevent overwhelming the daemon."
remediation:
"Edit the /etc/ssh/sshd_config file to set the parameter as follows:\n"
"```\n"
"maxstartups 10:30:60\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/ssh/sshd_config\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"maxstartups .*\""
" expected_regex: \"maxstartups 10:30:60\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*echo.*maxstartups.*/etc/ssh/sshd_config.*\""
" expected_regex: \".*echo \\\"maxstartups 10:30:60\\\" >> /etc/ssh/sshd_config.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "ssh-maxsessions-4-or-less-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure SSH MaxSessions is set to 4 or less"
description:
"The MaxSessions parameter specifies the maximum number of open "
"sessions permitted from a given connection."
rationale:
"To protect a system from denial of service due to a large number of "
"concurrent sessions, use the rate limiting function of MaxSessions to "
"protect availability of sshd logins and prevent overwhelming the daemon."
remediation:
"Edit the /etc/ssh/sshd_config file to set the parameter as follows:\n"
"```\n"
"MaxSessions 4\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/ssh/sshd_config\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"MaxSessions .*\""
" expected_regex: \"MaxSessions (\\\\d+)\""
" group_criteria:{"
" group_index: 1"
" type: LESS_THAN"
" const: 5"
" }"
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*echo.*MaxSessions.*/etc/ssh/sshd_config.*\""
" expected_regex: \".*echo \\\"MaxSessions 4\\\" >> /etc/ssh/sshd_config.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "password-reuse-limited-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure password reuse is limited"
description:
"The /etc/security/opasswd file stores the users' old passwords and can "
"be checked to ensure that users are not recycling recent passwords."
rationale:
"Forcing users not to reuse their past 5 passwords make it less likely "
"that an attacker will be able to guess the password.\n"
"Note that these change only apply to accounts configured on the local "
"system."
remediation:
"Set remembered password history to conform to site policy. Many "
"distributions provide tools for updating PAM configuration, consult "
"your documentation for details. If no tooling is provided edit the "
"appropriate /etc/pam.d/ configuration file and add or modify the "
"pam_pwhistory.so or pam_unix.so lines to include the remember option:\n"
"```\n"
"password required pam_pwhistory.so remember=5\n"
"password sufficient pam_unix.so remember=5\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/pam.d\""
" filename_regex: \"(system-auth)|(common-password)\""
" recursive: false"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"password.*pam_pwhistory.so.*\""
" expected_regex: \"password\\\\s+.*pam_pwhistory.so\\\\s+remember=5\""
" }"
" match_criteria: {"
" filter_regex: \"password.*pam_unix.so.*\""
" expected_regex: \"password\\\\s+.*pam_unix.so\\\\s+.*remember=5.*\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*sed.*pam_pwhistory.so.*/etc/pam.d/system-auth.*\""
" expected_regex: \".*sed -i '0,/password/s//password\\\\s+required\\\\s+pam_pwhistory.so\\\\s+remember=5\\\\\\\\n&/'.*/etc/pam.d/system-auth.*\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*sed.*pam_unix.so.*/etc/pam.d/system-auth.*\""
" expected_regex: \".*sed -i 's/password\\\\.\\\\*pam_unix.so/& remember=5/' /etc/pam.d/system-auth.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "password-hashing-algorithm-sha-512-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure password hashing algorithm is SHA-512"
description:
"The commands below change password encryption from md5 to sha512 (a "
"much stronger hashing algorithm). All existing accounts will need to "
"perform a password change to upgrade the stored hashes to the new "
"algorithm."
rationale:
"The SHA-512 algorithm provides much stronger hashing than MD5, thus "
"providing additional protection to the system by increasing the level "
"of effort for an attacker to successfully determine passwords.\n"
"Note that these change only apply to accounts configured on the local "
"system."
remediation:
"Set password hashing algorithm to sha512. Many distributions provide "
"tools for updating PAM configuration, consult your documentation for "
"details. If no tooling is provided edit the appropriate /etc/pam.d/ "
"configuration file and add or modify the pam_unix.so lines to include "
"the sha512 option:\n"
"```\n"
"password sufficient pam_unix.so sha512\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/etc/pam.d\""
" filename_regex: \"(system-auth)|(common-password)\""
" recursive: false"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"password.*pam_unix.so.*\""
" expected_regex: \"password\\\\s+.*pam_unix.so\\\\s+.*sha512.*\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*sed.*md5.*/etc/pam.d/system-auth.*\""
" expected_regex: \".*sed -i '/password/s/md5/sha512/' /etc/pam.d/system-auth.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "password-expiration-365-days-or-less-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure password expiration is 365 days or less"
description:
"The PASS_MAX_DAYS parameter in /etc/login.defs allows an administrator "
"to force passwords to expire once they reach a defined age. It is "
"recommended that the PASS_MAX_DAYS parameter be set to less than or "
"equal to 365 days."
rationale:
"The window of opportunity for an attacker to leverage compromised "
"credentials or successfully compromise credentials via an online "
"brute force attack is limited by the age of the password. Therefore, "
"reducing the maximum age of a password also reduces an attacker's "
"window of opportunity."
remediation:
"Set the PASS_MAX_DAYS parameter to conform to site policy in "
"/etc/login.defs:\n"
"```\n"
"PASS_MAX_DAYS 365\n"
"```\n"
"Modify user parameters for all users with a password set to match:\n"
"```\n"
"# chage --maxdays 365 <user>\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/login.defs\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"PASS_MAX_DAYS.*\""
" expected_regex: \"PASS_MAX_DAYS\\\\s+(\\\\d+)\""
" group_criteria: {"
" group_index: 1"
" type: LESS_THAN"
" const: 366"
" }"
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/shadow\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".+:[^!*]+:.*:.*:.*:.*:.*:.*:.*\""
" expected_regex: \".*:.*:.*:.*:.*:(\\\\d+):.*:.*:.*\""
" group_criteria: {"
" group_index: 1"
" type: LESS_THAN"
" const: 366"
" }"
" }"
" }"
" non_compliance_msg: \"there are users whose PASS_MAX_DAYS is more than 365 days\""
" file_display_command: \"grep -E '^[^:]+:[^!*]' /etc/shadow | cut -d: -f1,5\""
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*sed.*PASS_MAX_DAYS.*/etc/login.defs.*\""
" expected_regex: \".*sed -i 's/\\\\^PASS_MAX_DAYS\\\\\\\\t\\\\.\\\\*\\\\$/PASS_MAX_DAYS 365/' /etc/login.defs.*\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/shadow\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".+:[^!*]+:.*:.*:.*:.*:.*:.*:.*\""
" expected_regex: \".*:.*:.*:.*:.*:(\\\\d+):.*:.*:.*\""
" group_criteria: {"
" group_index: 1"
" type: LESS_THAN"
" const: 366"
" }"
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "minimum-days-between-password-changes-7-or-more-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure minimum days between password changes is 7 or more"
description:
"The PASS_MIN_DAYS parameter in /etc/login.defs allows an administrator "
"to prevent users from changing their password until a minimum number of "
"days have passed since the last time the user changed their password. "
"It is recommended that PASS_MIN_DAYS parameter be set to 7 or more days."
rationale:
"By restricting the frequency of password changes, an administrator can "
"prevent users from repeatedly changing their password in an attempt to "
"circumvent password reuse controls."
remediation:
"Set the PASS_MIN_DAYS parameter to 7 in /etc/login.defs:\n"
"```\n"
"PASS_MIN_DAYS 7\n"
"```\n"
"Modify user parameters for all users with a password set to match:\n"
"```\n"
"# chage --mindays 7 <user>\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/login.defs\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"PASS_MIN_DAYS.*\""
" expected_regex: \"PASS_MIN_DAYS\\\\s+(\\\\d+)\""
" group_criteria: {"
" group_index: 1"
" type: GREATER_THAN"
" const: 6"
" }"
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/shadow\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".+:[^!*]+:.*:.*:.*:.*:.*:.*:.*\""
" expected_regex: \".*:.*:.*:.*:(\\\\d+):.*:.*:.*:.*\""
" group_criteria: {"
" group_index: 1"
" type: GREATER_THAN"
" const: 6"
" }"
" }"
" }"
" non_compliance_msg: \"there are users whose PASS_MIN_DAYS is less than 6 days\""
" file_display_command: \"grep -E '^[^:]+:[^!*]' /etc/shadow | cut -d: -f1,4\""
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*sed.*PASS_MIN_DAYS.*/etc/login.defs.*\""
" expected_regex: \".*sed -i 's/\\\\^PASS_MIN_DAYS\\\\\\\\t\\\\.\\\\*\\\\$/PASS_MIN_DAYS 7/' /etc/login.defs.*\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/shadow\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".+:[^!*]+:.*:.*:.*:.*:.*:.*:.*\""
" expected_regex: \".*:.*:.*:.*:(\\\\d+):.*:.*:.*:.*\""
" group_criteria: {"
" group_index: 1"
" type: GREATER_THAN"
" const: 6"
" }"
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "inactive-password-lock-30-days-or-less-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure inactive password lock is 30 days or less"
description:
"User accounts that have been inactive for over a given period of time "
"can be automatically disabled. It is recommended that accounts that are "
"inactive for 30 days after password expiration be disabled."
rationale:
"Inactive accounts pose a threat to system security since the users are "
"not logging in to notice failed login attempts or other anomalies."
remediation:
"Run the following command to set the default password inactivity "
"period to 30 days:\n"
"```\n"
"# useradd -D -f 30\n"
"```\n"
"Modify user parameters for all users with a password set to match:\n"
"```\n"
"# chage --inactive 30 <user>\n"
"```\n"
cis_benchmark: {
profile_level: 1
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/default/useradd\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"INACTIVE.*\""
" expected_regex: \"INACTIVE=(\\\\d+)\""
" group_criteria: {"
" group_index: 1"
" type: LESS_THAN"
" const: 31"
" }"
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/shadow\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".+:[^!*]+:.*:.*:.*:.*:.*:.*:.*\""
" expected_regex: \".*:.*:.*:.*:.*:.*:.*:(\\\\d+):.*\""
" group_criteria: {"
" group_index: 1"
" type: LESS_THAN"
" const: 31"
" }"
" }"
" }"
" non_compliance_msg: \"there are users whose password inactive password lock is more than 30 days\""
" file_display_command: \"grep -E ^[^:]+:[^\\\\!*] /etc/shadow | cut -d: -f1,6\""
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*useradd -D -f .*.*\""
" expected_regex: \".*useradd -D -f 30.*\""
" }"
" }"
" }"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/shadow\"}}"
" content_entry:{"
" match_type: NONE_MATCH"
" match_criteria: {"
" filter_regex: \".+:[^!*]+:.*:.*:.*:.*:.*:.*:.*\""
" expected_regex: \".*:.*:.*:.*:.*:.*:.*:(\\\\d+):.*\""
" group_criteria: {"
" group_index: 1"
" type: LESS_THAN"
" const: 31"
" }"
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "ipv6-default-deny-firewall-policy-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure IPv6 default deny firewall policy"
description:
"A default deny all policy on connections ensures that any "
"unconfigured network usage will be rejected."
rationale:
"With a default accept policy the firewall will accept any "
"packet that is not configured to be denied. "
"It is easier to white list acceptable usage than "
"to black list unacceptable usage."
remediation:
"Run the following commands to implement a default DROP policy: \n"
"```# ip6tables -P INPUT DROP \n"
"# ip6tables -P OUTPUT DROP \n"
"# ip6tables -P FORWARD DROP```"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/share/cloud/ip6tables-setup\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"ip6tables\\\\s+-P\\\\s+INPUT\\\\s+[a-zA-Z]+\\\\s+-w\\\\s*\""
" expected_regex: \"ip6tables\\\\s+-P\\\\s+INPUT\\\\s+(DROP|REJECT)\\\\s+-w\\\\s*\""
" }"
" match_criteria: {"
" filter_regex: \"ip6tables\\\\s+-P\\\\s+OUTPUT\\\\s+[a-zA-Z]+\\\\s+-w\\\\s*\""
" expected_regex: \"ip6tables\\\\s+-P\\\\s+OUTPUT\\\\s+(DROP|REJECT)\\\\s+-w\\\\s*\""
" }"
" match_criteria: {"
" filter_regex: \"ip6tables\\\\s+-P\\\\s+FORWARD\\\\s+[a-zA-Z]+\\\\s+-w\\\\s*\""
" expected_regex: \"ip6tables\\\\s+-P\\\\s+FORWARD\\\\s+(DROP|REJECT)\\\\s+-w\\\\s*\""
" }"
" }"
" }"
" }"
"}"
}
}
benchmark_configs: {
id: "configure-ipv6-loopback-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure IPv6 loopback traffic is configured"
description:
"Configure the loopback interface to accept traffic. "
"Configure all other interfaces to deny traffic to the loopback network (::1)."
rationale:
"Loopback traffic is generated between processes on machine and "
"is typically critical to operation of the system. "
"The loopback interface is the only place that loopback network (::1) "
"traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure."
remediation:
"Run the following commands to implement the loopback rules: \n"
"```# ip6tables -A INPUT -i lo -j ACCEPT \n"
"# ip6tables -A OUTPUT -o lo -j ACCEPT \n"
"# ip6tables -A INPUT -s ::1 -j DROP```"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/var/run/ip6tables-conf-cis-2\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"ip6tables\\\\s+-[A-Z]\\\\s+INPUT\\\\s+-s\\\\s+::1\\\\s+-j\\\\s+[a-zA-Z]+.*\""
" expected_regex: \"ip6tables\\\\s+-(A|I)\\\\s+INPUT\\\\s+-s\\\\s+::1\\\\s+-j\\\\s+DROP.*\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*ip6tables\\\\s+-[A-Z]\\\\s+INPUT\\\\s+-s\\\\s+::1\\\\s+-j\\\\s+[a-zA-Z]+.*\""
" expected_regex: \".*ip6tables\\\\s+-(A|I)\\\\s+INPUT\\\\s+-s\\\\s+::1\\\\s+-j\\\\s+DROP.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "configure-loopback-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure loopback traffic is configured"
description:
"Configure the loopback interface to accept traffic. "
"Configure all other interfaces to deny traffic to the loopback network (127.0.0.0/8)."
rationale:
"Loopback traffic is generated between processes on machine and "
"is typically critical to operation of the system. "
"The loopback interface is the only place that loopback network "
"(127.0.0.0/8) traffic should be seen, all other interfaces should "
"ignore traffic on this network as an anti-spoofing measure."
remediation:
"Run the following commands to implement the loopback rules: \n"
"```# iptables -A INPUT -i lo -j ACCEPT \n"
"# iptables -A OUTPUT -o lo -j ACCEPT \n"
"# iptables -A INPUT -s 127.0.0.0/8 -j DROP```"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"scan_type_specific:{instance_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/var/run/iptables-conf-cis-2\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"iptables\\\\s+-[A-Z]\\\\s+INPUT\\\\s+-s\\\\s+127.0.0.0/8\\\\s+-j\\\\s+[a-zA-Z]+.*\""
" expected_regex: \"iptables\\\\s+-(A|I)\\\\s+INPUT\\\\s+-s\\\\s+127.0.0.0/8\\\\s+-j\\\\s+DROP.*\""
" }"
" }"
" }"
" }"
"}"
"image_scanning:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{files_in_dir:{"
" dir_path:\"/usr/share/google/security\""
" filename_regex: \".*\\\\.sh\""
" recursive: true"
" }}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
# Use a null byte as the delimiter to be able to match multi-line commands.
" delimiter: \"\\0\""
" match_criteria: {"
" filter_regex: \".*iptables\\\\s+-[A-Z]\\\\s+INPUT\\\\s+-s\\\\s+::1\\\\s+-j\\\\s+[a-zA-Z]+.*\""
" expected_regex: \".*iptables\\\\s+-(A|I)\\\\s+INPUT\\\\s+-s\\\\s+::1\\\\s+-j\\\\s+DROP.*\""
" }"
" }"
" }"
" }"
"}}"
}
}
benchmark_configs: {
id: "ipv6-outbound-established-connections-configured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure IPv6 outbound and established connections are configured"
description: "Configure the firewall rules for new outbound, and established IPv6 connections."
rationale:
"If rules are not in place for new outbound, and established connections all "
"packets will be dropped by the default policy preventing network usage."
remediation:
"Configure iptables in accordance with site policy. "
"The following commands will implement a policy to "
"allow all outbound connections and all established connections: \n"
"```# ip6tables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED -j ACCEPT \n"
"# ip6tables -A OUTPUT -p udp -m state --state NEW,ESTABLISHED -j ACCEPT \n"
"# ip6tables -A OUTPUT -p icmp -m state --state NEW,ESTABLISHED -j ACCEPT \n"
"# ip6tables -A INPUT -p tcp -m state --state ESTABLISHED -j ACCEPT \n"
"# ip6tables -A INPUT -p udp -m state --state ESTABLISHED -j ACCEPT \n"
"# ip6tables -A INPUT -p icmp -m state --state ESTABLISHED -j ACCEPT```"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/share/cloud/ip6tables-setup\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"ip6tables\\\\s+-[A-Z]\\\\s+OUTPUT\\\\s+-p\\\\s+tcp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"ip6tables\\\\s+-(A|I)\\\\s+OUTPUT\\\\s+-p\\\\s+tcp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+(NEW|ESTABLISHED|,){1,3}\\\\s+-j\\\\s+ACCEPT\""
" }"
" match_criteria: {"
" filter_regex: \"ip6tables\\\\s+-[A-Z]\\\\s+OUTPUT\\\\s+-p\\\\s+udp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"ip6tables\\\\s+-(A|I)\\\\s+OUTPUT\\\\s+-p\\\\s+udp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+(NEW|ESTABLISHED|,){1,3}\\\\s+-j\\\\s+ACCEPT\""
" }"
" match_criteria: {"
" filter_regex: \"ip6tables\\\\s+-[A-Z]\\\\s+OUTPUT\\\\s+-p\\\\s+icmp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"ip6tables\\\\s+-(A|I)\\\\s+OUTPUT\\\\s+-p\\\\s+icmp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+(NEW|ESTABLISHED|,){1,3}\\\\s+-j\\\\s+ACCEPT\""
" }"
" match_criteria: {"
" filter_regex: \"ip6tables\\\\s+-[A-Z]\\\\s+INPUT\\\\s+-p\\\\s+tcp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"ip6tables\\\\s+-(A|I)\\\\s+INPUT\\\\s+-p\\\\s+tcp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+ESTABLISHED\\\\s+-j\\\\s+ACCEPT\""
" }"
" match_criteria: {"
" filter_regex: \"ip6tables\\\\s+-[A-Z]\\\\s+INPUT\\\\s+-p\\\\s+udp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"ip6tables\\\\s+-(A|I)\\\\s+INPUT\\\\s+-p\\\\s+udp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+ESTABLISHED\\\\s+-j\\\\s+ACCEPT\""
" }"
" match_criteria: {"
" filter_regex: \"ip6tables\\\\s+-[A-Z]\\\\s+INPUT\\\\s+-p\\\\s+icmp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"ip6tables\\\\s+-(A|I)\\\\s+INPUT\\\\s+-p\\\\s+icmp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+ESTABLISHED\\\\s+-j\\\\s+ACCEPT\""
" }"
" }"
" }"
" }"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/share/cloud/ip6tables-setup\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"ip6tables\\\\s+-[A-Z]\\\\s+INPUT\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"ip6tables\\\\s+-(A|I)\\\\s+INPUT\\\\s+-m\\\\s+state\\\\s+--state\\\\s+(NEW|ESTABLISHED|RELATED|,){3,5}\\\\s+-j\\\\s+ACCEPT\\\\s+-w\""
" }"
" match_criteria: {"
" filter_regex: \"ip6tables\\\\s+-[A-Z]\\\\s+OUTPUT\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"ip6tables\\\\s+-(A|I)\\\\s+OUTPUT\\\\s+-m\\\\s+state\\\\s+--state\\\\s+(NEW|ESTABLISHED|RELATED|,){3,5}\\\\s+-j\\\\s+ACCEPT\\\\s+-w\""
" }"
" }"
" }"
" }"
"}"
}
}
benchmark_configs: {
id: "default-deny-firewall-policy-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure default deny firewall policy"
description:
"A default deny all policy on connections ensures that "
"any unconfigured network usage will be rejected."
rationale:
"With a default accept policy the firewall will accept "
"any packet that is not configured to be denied. "
"It is easier to white list acceptable usage than to black list unacceptable usage."
remediation:
"Run the following commands to implement a default DROP policy: \n"
"```# iptables -P INPUT DROP \n"
"# iptables -P OUTPUT DROP \n"
"# iptables -P FORWARD DROP```"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/share/cloud/iptables-setup\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"iptables\\\\s+-P\\\\s+INPUT\\\\s+[a-zA-Z]+\\\\s+-w\\\\s*\""
" expected_regex: \"iptables\\\\s+-P\\\\s+INPUT\\\\s+(DROP|REJECT)\\\\s+-w\\\\s*\""
" }"
" match_criteria: {"
" filter_regex: \"iptables\\\\s+-P\\\\s+OUTPUT\\\\s+[a-zA-Z]+\\\\s+-w\\\\s*\""
" expected_regex: \"iptables\\\\s+-P\\\\s+OUTPUT\\\\s+(DROP|REJECT)\\\\s+-w\\\\s*\""
" }"
" match_criteria: {"
" filter_regex: \"iptables\\\\s+-P\\\\s+FORWARD\\\\s+[a-zA-Z]+\\\\s+-w\\\\s*\""
" expected_regex: \"iptables\\\\s+-P\\\\s+FORWARD\\\\s+(DROP|REJECT)\\\\s+-w\\\\s*\""
" }"
" }"
" }"
" }"
"}"
}
}
benchmark_configs: {
id: "outbound-established-connections-configured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure outbound and established connections are configured"
description: "Configure the firewall rules for new outbound, and established connections."
rationale:
"If rules are not in place for new outbound, and established "
"connections all packets will be dropped by the default policy preventing network usage."
remediation:
"Configure iptables in accordance with site policy. "
"The following commands will implement a policy to "
"allow all outbound connections and all established connections: \n"
"```# iptables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED -j ACCEPT \n"
"# iptables -A OUTPUT -p udp -m state --state NEW,ESTABLISHED -j ACCEPT \n"
"# iptables -A OUTPUT -p icmp -m state --state NEW,ESTABLISHED -j ACCEPT \n"
"# iptables -A INPUT -p tcp -m state --state ESTABLISHED -j ACCEPT \n"
"# iptables -A INPUT -p udp -m state --state ESTABLISHED -j ACCEPT \n"
"# iptables -A INPUT -p icmp -m state --state ESTABLISHED -j ACCEPT```"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/share/cloud/iptables-setup\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"iptables\\\\s+-[A-Z]\\\\s+OUTPUT\\\\s+-p\\\\s+tcp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"iptables\\\\s+-(A|I)\\\\s+OUTPUT\\\\s+-p\\\\s+tcp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+(NEW|ESTABLISHED|,){1,3}\\\\s+-j\\\\s+ACCEPT\""
" }"
" match_criteria: {"
" filter_regex: \"iptables\\\\s+-[A-Z]\\\\s+OUTPUT\\\\s+-p\\\\s+udp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"iptables\\\\s+-(A|I)\\\\s+OUTPUT\\\\s+-p\\\\s+udp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+(NEW|ESTABLISHED|,){1,3}\\\\s+-j\\\\s+ACCEPT\""
" }"
" match_criteria: {"
" filter_regex: \"iptables\\\\s+-[A-Z]\\\\s+OUTPUT\\\\s+-p\\\\s+icmp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"iptables\\\\s+-(A|I)\\\\s+OUTPUT\\\\s+-p\\\\s+icmp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+(NEW|ESTABLISHED|,){1,3}\\\\s+-j\\\\s+ACCEPT\""
" }"
" match_criteria: {"
" filter_regex: \"iptables\\\\s+-[A-Z]\\\\s+INPUT\\\\s+-p\\\\s+tcp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"iptables\\\\s+-(A|I)\\\\s+INPUT\\\\s+-p\\\\s+tcp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+ESTABLISHED\\\\s+-j\\\\s+ACCEPT\""
" }"
" match_criteria: {"
" filter_regex: \"iptables\\\\s+-[A-Z]\\\\s+INPUT\\\\s+-p\\\\s+udp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"ip6tables\\\\s+-(A|I)\\\\s+INPUT\\\\s+-p\\\\s+udp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+ESTABLISHED\\\\s+-j\\\\s+ACCEPT\""
" }"
" match_criteria: {"
" filter_regex: \"iptables\\\\s+-[A-Z]\\\\s+INPUT\\\\s+-p\\\\s+icmp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"ip6tables\\\\s+-(A|I)\\\\s+INPUT\\\\s+-p\\\\s+icmp\\\\s+-m\\\\s+state\\\\s+--state\\\\s+ESTABLISHED\\\\s+-j\\\\s+ACCEPT\""
" }"
" }"
" }"
" }"
" check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/usr/share/cloud/iptables-setup\"}}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"iptables\\\\s+-[A-Z]\\\\s+INPUT\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"iptables\\\\s+-(A|I)\\\\s+INPUT\\\\s+-m\\\\s+state\\\\s+--state\\\\s+(NEW|ESTABLISHED|RELATED|,){3,5}\\\\s+-j\\\\s+ACCEPT\\\\s+-w\""
" }"
" match_criteria: {"
" filter_regex: \"iptables\\\\s+-[A-Z]\\\\s+OUTPUT\\\\s+-m\\\\s+state\\\\s+--state\\\\s+[A-Za-z,]+\\\\s+-j\\\\s+[A-Za-z]+\\\\s+-w\""
" expected_regex: \"iptables\\\\s+-(A|I)\\\\s+OUTPUT\\\\s+-m\\\\s+state\\\\s+--state\\\\s+(NEW|ESTABLISHED|RELATED|,){3,5}\\\\s+-j\\\\s+ACCEPT\\\\s+-w\""
" }"
" }"
" }"
" }"
"}"
}
}
benchmark_configs: {
id: "system-accounts-secured-cos"
compliance_note: {
version: { cpe_uri: "cpe:/o:cos:cos_linux:93" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
version: { cpe_uri: "cpe:/o:cos:cos_linux:97" version: "1.0.0" benchmark_document: "CIS Container-Optimized OS" }
title: "Ensure system accounts are secured"
description:
"There are a number of accounts provided with most distributions that are used to manage "
"applications and are not intended to provide an interactive shell."
rationale:
"It is important to make sure that accounts that are not being used by regular users are "
"prevented from being used to provide an interactive shell. By default, most distributions "
"set the password field for these accounts to an invalid string, but it is also recommended "
"that the shell field in the password file be set to the nologin shell. This prevents the "
"account from potentially being used to run any commands."
remediation:
"Run the commands appropriate for your distribution:\n"
"Set the shell for any accounts returned by the audit to nologin:\n"
"```\n"
"# usermod -s $(which nologin) <user>\n"
"```\n"
"Lock any non root accounts returned by the audit:\n"
"```\n"
"# usermod -L <user>\n"
"```\n"
"The following command will set all system accounts to a non login shell:\n"
"```\n"
"awk -F: '($1!=\"root\" && $1!=\"sync\" && $1!=\"shutdown\" && $1!=\"halt\" && $1!~/^\\+/ && $3<'\"$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\"' && $7!=\"'\"$(which nologin)\"'\" && $7!=\"/bin/false\") {print $1}' /etc/passwd | while read user do usermod -s $(which nologin) $user done\n"
"```\n"
"The following command will automatically lock not root system accounts:\n"
"```\n"
"awk -F: '($1!=\"root\" && $1!~/^\\+/ && $3<'\"$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\"') {print $1}' /etc/passwd | xargs -I '{}' passwd -S '{}' | awk '($2!=\"L\" && $2!=\"LK\") {print $1}' | while read user do usermod -L $user done\n"
"```\n"
cis_benchmark: {
profile_level: 2
severity: LOW
}
scan_instructions:
"generic:{check_alternatives:{"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/passwd\"}}"
" repeat_config:{type: FOR_EACH_SYSTEM_USER_WITH_LOGIN}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"$user:.*:.*:.*:.*:.*:.*\""
# Only the root, sync, shutdown and halt system users are allowed to have a login shell.
" expected_regex: \"(root|sync|shutdown|halt):.*:.*:.*:.*:.*:.*\""
" }"
" }"
" non_compliance_msg: \"there are system users with a login shell\""
" file_display_command: \"awk -F: '($1!=\\\"root\\\" && $1!=\\\"sync\\\" && $1!=\\\"shutdown\\\" && $1!=\\\"halt\\\" && $1!~/^\\\\+/ && $3>='\\\"$(awk '/^\\\\s*SYS_UID_MIN/{print $2}' /etc/login.defs)\\\"' && $3<='\\\"$(awk '/^\\\\s*SYS_UID_MAX/{print $2}' /etc/login.defs)\\\"' && $7!=\\\"'\\\"$(which nologin)\\\"'\\\" && $7!=\\\"/bin/false\\\") {print}' /etc/passwd\""
" }"
" file_checks:{"
" files_to_check:{single_file:{path:\"/etc/shadow\"}}"
" repeat_config:{type: FOR_EACH_SYSTEM_USER_WITH_LOGIN}"
" content_entry:{"
" match_type: ALL_MATCH_ANY_ORDER"
" match_criteria: {"
" filter_regex: \"$user:.*:.*:.*:.*:.*:.*:.*:.*\""
# Only the root system user is allowed to have a non-locked account.
" expected_regex: \"(.*:.*[*!].*:.*:.*:.*:.*:.*:.*:.*)|(root:.*:.*:.*:.*:.*:.*:.*:.*)\""
" }"
" }"
" non_compliance_msg: \"there are non-locked system user accounts\""
" file_display_command: \"awk -F: '($1!=\\\"root\\\" && $1!~/^\\\\+/ && $3>='\\\"$(awk '/^\\\\s*SYS_UID_MIN/{print $2}' /etc/login.defs)\\\"' && $3<='\\\"$(awk '/^\\\\s*SYS_UID_MAX/{print $2}' /etc/login.defs)\\\"' {print $1}' /etc/passwd | xargs -I '{}' passwd -S '{}' | awk '($2!=\\\"L\\\" && $2!=\\\"LK\\\") {print $1}'\""
" }"
"}}"
}
}