1

Initial Setup

1.1

Filesystem Configuration

1.1.1

Disable unused filesystems

1.1.1.1

Ensure mounting of cramfs filesystems is disabled (Automated)

L1

S

—

1.1.1.2

Ensure mounting of vFAT filesystems is limited (Manual)

L2

S

n/a

—

1.1.1.3

Ensure mounting of squashfs filesystems is disabled (Automated)

L1

S

—

1.1.1.4

Ensure mounting of udf filesystems is disabled (Automated)

L1

S

—

1.1.2

Ensure /tmp is configured (Automated)

L1

S

—

1.1.3

Ensure nodev option set on /tmp partition (Automated)

L1

S

—

1.1.4

Ensure nosuid option set on /tmp partition (Automated)

L1

S

—

1.1.5

Ensure noexec option set on /tmp partition (Automated)

L1

S

—

1.1.6

Ensure separate partition exists for /var (Automated)

L2

S

Customer determines appropriate partition size; disk space cannot be taken from partitions defined in NSP deployment documentation

1.1.7

Ensure separate partition exists for /var/tmp (Automated)

L2

S

Customer determines appropriate partition size; disk space cannot be taken from partitions defined in NSP deployment documentation

1.1.8

Ensure nodev option set on /var/tmp partition (Automated)

L1

S

—

1.1.9

Ensure nosuid option set on /var/tmp partition (Automated)

L1

S

—

1.1.10

Ensure noexec option set on /var/tmp partition (Automated)

L1

S

—

1.1.11

Ensure separate partition exists for /var/log (Automated)

L2

S

—

1.1.12

Ensure separate partition exists for /var/log/audit (Automated)

L2

S

—

1.1.13

Ensure separate partition exists for /home (Automated)

L2

S

—

1.1.14

Ensure nodev option set on /home partition (Automated)

L1

S

—

1.1.15

Ensure nodev option set on /dev/shm partition (Automated)

L1

S

—

1.1.16

Ensure nosuid option set on /dev/shm partition (Automated)

L1

P

S

NS

Not supported in NSP RHEL qcow2/OVA or for NFM-P database stations

1.1.17

Ensure noexec option set on /dev/shm partition (Automated)

L1

P

S

NS

Not supported in NSP RHEL qcow2/OVA or for NFM-P database stations

1.1.18

Ensure nodev option set on removable media partitions (Manual)

L1

S

n/a

Not applicable to NSP qcow2/OVA, which lacks removable partitions

1.1.19

Ensure nosuid option set on removable media partitions (Manual)

L1

S

n/a

Not applicable to NSP qcow2/OVA, which lacks removable partitions

1.1.20

Ensure noexec option set on removable media partitions (Manual)

L1

S

n/a

Not applicable to NSP qcow2/OVA, which lacks removable partitions

1.1.21

Ensure sticky bit is set on all world-writable directories (Automated)

L1

P

NS

S

Not supported on NSP Kubernetes deployer, cluster nodes.

1.1.22

Disable Automounting (Automated)

L1

S

—

1.1.23

Disable USB Storage (Automated)

L1

S

—

1.2

Configure Software Updates

1.2.1

Ensure Red Hat Subscription Manager connection is configured (Manual)

L1

S

n/a

Not applicable to NSP qcow2/OVA; patch updates provided only via NSP RHEL update patch bundle

1.2.2

Disable the rhnsd Daemon (Manual)

L1

S

—

1.2.3

Ensure GPG keys are configured (Manual)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA

Nokia digitally signs each NSP software RPM file using GNU Privacy Guard, or GPG, which enables you to ensure the integrity of a file before use. See the NSP Installation and Upgrade Guide for information about importing NSP GPG keys.

1.2.4

Ensure gpgcheck is globally activated (Automated)

L1

S

—

1.2.5

Ensure package manager repositories are configured (Manual)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA; NSP RHEL qcow2/OVA OS updates provided only via NSP RHEL update patch bundle.

1.3

Configure sudo

1.3.1

Ensure sudo is installed (Automated)

L1

S

See RHEL sudoer configuration.

1.3.2

Ensure sudo commands use pty (Automated)

L1

S

—

1.3.3

Ensure sudo log file exists (Automated)

L1

S

—

1.4

Filesystem Integrity Checking

1.4.1

Ensure AIDE is installed (Automated)

L1

S

—

1.4.2

Ensure filesystem integrity is regularly checked (Automated)

L1

NS

AIDE initialization and execution cause increased disk I/O and CPU usage that reduce performance; the risk of causing NSP service disruption prevents NSP support for AIDE.

1.5

Secure Boot Settings

1.5.1

Ensure permissions on bootloader config are configured (Automated)

L1

S

—

1.5.2

Ensure bootloader password is set (Automated)

L1

S

—

1.5.3

Ensure authentication required for single user mode (Automated)

L1

S

—

1.6

Additional Process Hardening

1.6.1

Ensure core dumps are restricted (Automated)

L1

S

S/ND

Disabling core dumps may adversely affect ability to provide NSP customer support

The risk associated with compromising customer support capabilities must be accepted unless core dumps are enabled for the following RHEL users, as recommended by Nokia:

• root

• nsp

• samadmin

• oracle

• td-agent

• samauxdb

• kube

• etcd

1.6.2

Ensure address space layout randomization (ASLR) is enabled (Automated)

L1

S

—

1.7

Mandatory Access Control

1.7.1

Configure SELinux

1.7.1.1

Ensure SELinux is installed (Automated)

L2

S

—

1.7.1.2

Ensure SELinux is not disabled in bootloader configuration (Automated)

L2

S

—

1.7.1.3

Ensure SELinux policy is configured (Automated)

L2

S

—

1.7.1.4

Ensure the SELinux state is enforcing (Automated)

L2

P

P/ND

SELinux is enabled in permissive mode by default on NSP RHEL qcow2/OVA.

SELinux is supported only in permissive mode on auxiliary database cluster stations.

See “SELinux administration” in the NSP System Administrator Guide for configuration information.

1.7.1.5

Ensure no unconfined services exist (Automated)

L2

S

—

1.7.1.6

Ensure SETroubleshoot is not installed (Automated)

L2

S

—

1.7.1.7

Ensure the MCS Translation Service (mcstrans) is not installed (Automated)

L2

S

—

1.8

Warning Banners

1.8.1

Command Line Warning Banners

1.8.1.1

Ensure message of the day is configured properly (Automated)

L1

S

—

1.8.1.2

Ensure local login warning banner is configured properly (Automated)

L1

S

—

1.8.1.3

Ensure remote login warning banner is configured properly (Automated)

L1

S

—

1.8.1.4

Ensure permissions on /etc/motd are configured (Automated)

L1

S

—

1.8.1.5

Ensure permissions on /etc/issue are configured (Automated)

L1

S

—

1.8.1.6

Ensure permissions on /etc/issue.net are configured (Automated)

L1

S

—

1.8.2

Ensure GDM login banner is configured (Automated)

L1

S

—

1.9

Ensure updates, patches, and additional security software are installed (Manual)

L1

P

P/ND

Applying RHEL patches is supported, but compatibility issues require backing out RHEL updates until a fix is available. Nokia does not recommend installing any additional software on the OS that hosts the NSP because it may affect NSP operation. Any non-sanctioned software must be removed if the software is suspected of causing NSP issues.

NSP RHEL qcow2/OVA OS-package updates provided only via NSP RHEL update patch bundle

1.10

Ensure system-wide crypto policy is not legacy (Automated)

L1

S

—

1.11

Ensure system-wide crypto policy is FUTURE or FIPS (Automated)

L2

P

System-wide crypto policy level of FUTURE supported; NSP and NFM-P require custom sub-policy to support 2048-bit RSA length

Note: Wavence UBT-SA devices require a crypto policy setting of DEFAULT.

2

Services

2.1

inetd Services

2.1.1

Ensure xinetd is not installed (Automated)

L1

S

—

2.2

Special Purpose Services

2.2.1

Time Synchronization

2.2.1.1

Ensure time synchronization is in use (Manual)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

2.2.1.2

Ensure chrony is configured (Automated)

L1

S

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

2.2.2

Ensure X Window System is not installed (Automated)

L1

S

—

2.2.3

Ensure rsync service is not enabled (Automated)

L1

S

—

2.2.4

Ensure Avahi Server is not enabled (Automated)

L1

S

—

2.2.5

Ensure SNMP Server is not enabled (Automated)

L1

S

—

2.2.6

Ensure HTTP Proxy Server is not enabled (Automated)

L1

S

—

2.2.7

Ensure Samba is not enabled (Automated)

L1

S

—

2.2.8

Ensure IMAP and POP3 server is not enabled (Automated)

L1

S

—

2.2.9

Ensure HTTP server is not enabled (Automated)

L1

S

—

2.2.10

Ensure FTP Server is not enabled (Automated)

L1

S

—

2.2.11

Ensure DNS Server is not enabled (Automated)

L1

S

—

2.2.12

Ensure NFS is not enabled (Automated)

L1

S

—

2.2.13

Ensure  RPC is not enabled (Automated)

L1

S

—

2.2.14

Ensure LDAP server is not enabled (Automated)

L1

S

—

2.2.15

Ensure DHCP Server is not enabled (Automated)

L1

S

—

2.2.16

Ensure CUPS is not enabled (Automated)

L1

S

—

2.2.17

Ensure NIS Server is not enabled (Automated)

L1

S

—

2.2.18

Ensure mail transfer agent is configured for local-only mode (Automated)

L1

S

—

2.3

Service Clients

2.3.1

Ensure NIS Client is not installed (Automated)

L1

S

—

2.3.2

Ensure telnet client is not installed (Automated)

L1

S

—

2.3.3

Ensure LDAP client is not installed (Automated)

L1

S

—

3

Network Configuration

3.1

Network Parameters (Host Only)

3.1.1

Ensure IP forwarding is disabled (Automated)

L1

P

NS

S

IP forwarding required by NSP Kubernetes deployer, cluster nodes

3.1.2

Ensure packet redirect sending is disabled (Automated)

L1

S

—

3.2

Network Parameters (Host and Router)

3.2.1

Ensure source routed packets are not accepted (Automated)

L1

S

—

3.2.2

Ensure ICMP redirects are not accepted (Automated)

L1

S

—

3.2.3

Ensure secure ICMP redirects are not accepted (Automated)

L1

S

—

3.2.4

Ensure suspicious packets are logged (Automated)

L1

S

—

3.2.5

Ensure broadcast ICMP requests are ignored (Automated)

L1

S

—

3.2.6

Ensure bogus ICMP responses are ignored (Automated)

L1

S

—

3.2.7

Ensure Reverse Path Filtering is enabled (Automated)

L1

S

—

3.2.8

Ensure TCP SYN Cookies is enabled (Automated)

L1

S

—

3.2.9

Ensure IPv6 router advertisements are not accepted (Automated)

L1

S

—

3.3

Uncommon Network Protocols

3.3.1

Ensure DCCP is disabled (Automated)

L2

S

—

3.3.2

Ensure SCTP is disabled (Automated)

L2

S

—

3.3.3

Ensure RDS is disabled (Automated)

L2

S

—

3.3.4

Ensure TIPC is disabled (Automated)

L2

S

—

3.4

Firewall Configuration

3.4.1

Ensure Firewall software is installed

3.4.1.1

Ensure a Firewall package is installed (Automated)

L1

S

—

3.4.2

Configure firewalld

3.4.2.1

Ensure firewalld service is enabled and running (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.2.2

Ensure iptables service is not enabled with firewalld (Automated)

L1

S

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.2.3

Ensure nftables is not enabled with firewalld (Automated)

L1

S

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.2.4

Ensure firewalld default zone is set (Automated)

L1

S

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.2.5

Ensure network interfaces are assigned to appropriate zone (Manual)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.2.6

Ensure firewalld drops unnecessary services and ports (Manual)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.3

Configure nftables

3.4.3.1

Ensure iptables are flushed with nftables (Manual)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.3.2

Ensure an nftables table exists (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

Calico network policies required for NSP deployer / cluster host deployment; nftable rules must not be changed.

3.4.3.3

Ensure nftables base chains exist (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

Calico network policies are required for NSP deployer / cluster host deployment, and nftable rules must not be changed.

3.4.3.4

Ensure nftables loopback traffic is configured (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.3.5

Ensure nftables outbound and established connections are configured (Manual)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.3.6

Ensure nftables default deny firewall policy (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.3.7

Ensure nftables service is enabled (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.3.8

Ensure nftables rules are permanent (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.4

Configure iptables

3.4.4.1

Configure IPv4 iptables

3.4.4.1.1

Ensure iptables default deny firewall policy (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.4.1.2

Ensure iptables loopback traffic is configured (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.4.1.3

Ensure iptables outbound and established connections are configured (Manual)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.4.1.4

Ensure iptables firewall rules exist for all open ports (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.4.1.5

Ensure iptables is enabled and active (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.4.2

Configure IPv6  ip6tables

3.4.4.2.1

Ensure ip6tables default deny firewall policy (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.4.2.2

Ensure ip6tables loopback traffic is configured (Automated)

L1

S

—

3.4.4.2.3

Ensure ip6tables outbound and established connections are configured (Manual)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.4.2.4

Ensure ip6tables firewall rules exist for all open ports (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.4.4.2.5

Ensure ip6tables is enabled and active (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

3.5

Ensure wireless interfaces are disabled (Automated)

L1

S

—

3.6

Disable IPv6 (Manual)

L2

S

S/ND

Supported, but not configured by default in NSP qcow2/OVA

4

Logging and Auditing

4.1

Configure System Accounting (auditd)

4.1.1

Ensure auditing is enabled

4.1.1.1

Ensure auditd is installed (Automated)

L2

S

—

4.1.1.2

Ensure auditd service is enabled (Automated)

L2

S

—

4.1.1.3

Ensure auditing for processes that start prior to auditd is enabled (Automated)

L2

S

—

4.1.1.4

Ensure audit_backlog_limit is sufficient (Automated)

L2

S

—

4.1.2

Configure Data Retention

4.1.2.1

Ensure audit log storage size is configured (Automated)

L2

S

—

4.1.2.2

Ensure audit logs are not automatically deleted (Automated)

L2

S

S/ND

Supported, but not configured by default in NSP qcow2/OVA

4.1.2.3

Ensure system is disabled when audit logs are full (Automated)

L2

S

S/ND

To avoid causing NSP service disruption, disabling system when audit logs full not recommended

4.1.3

Ensure changes to system administration scope (sudoers) is collected (Automated)

L2

S

—

4.1.4

Ensure login and logout events are collected (Automated)

L2

S

—

4.1.5

Ensure session initiation information is collected (Automated)

L2

S

—

4.1.6

Ensure events that modify date and time information are collected (Automated)

L2

S

—

4.1.7

Ensure events that modify the system's Mandatory Access Controls are collected (Automated)

L2

S

—

4.1.8

Ensure events that modify the system's network environment are collected (Automated)

L2

S

—

4.1.9

Ensure discretionary access control permission modification events are collected (Automated)

L2

S

—

4.1.10

Ensure unsuccessful unauthorized file access attempts are collected (Automated)

L2

S

—

4.1.11

Ensure events that modify user/group information are collected (Automated)

L2

S

—

4.1.12

Ensure successful file system mounts are collected (Automated)

L2

S

—

4.1.13

Ensure use of privileged commands is collected (Automated)

L2

S

—

4.1.14

Ensure file deletion events by users are collected (Automated)

L2

S

Supported, but may affect system performance

4.1.15

Ensure kernel module loading and unloading is collected (Automated)

L2

S

—

4.1.16

Ensure system administrator actions (sudolog) are collected (Automated)

L2

S

—

4.1.17

Ensure the audit configuration is immutable (Automated)

L2

S

—

4.2

Configure Logging

4.2.1

Configure rsyslog

4.2.1.1

Ensure rsyslog is installed (Automated)

L1

S

—

4.2.1.2

Ensure rsyslog Service is enabled (Automated)

L1

S

—

4.2.1.3

Ensure rsyslog default file permissions configured (Automated)

L1

S

—

4.2.1.4

Ensure logging is configured (Manual)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

4.2.1.5

Ensure rsyslog is configured to send logs to a remote log host (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

4.2.1.6

Ensure remote rsyslog messages are only accepted on designated log hosts. (Manual)

L1

S

—

4.2.2

Configure journald

4.2.2.1

Ensure journald is configured to send logs to rsyslog (Automated)

L1

S

—

4.2.2.2

Ensure journald is configured to compress large log files (Automated)

L1

S

—

4.2.2.3

Ensure journald is configured to write logfiles to persistent disk (Automated)

L1

S

—

4.2.3

Ensure permissions on all logfiles are configured (Automated)

L1

NI

NS

—

4.3

Ensure logrotate is configured (Manual)

L1

S

S/ND

Supported, but not configured by default in NSP qcow2/OVA

5

Access, Authentication and Authorization

5.1

Configure cron

5.1.1

Ensure cron daemon is enabled (Automated)

L1

S

—

5.1.2

Ensure permissions on /etc/crontab are configured (Automated)

L1

S

—

5.1.3

Ensure permissions on /etc/cron.hourly are configured (Automated)

L1

S

—

5.1.4

Ensure permissions on /etc/cron.daily are configured (Automated)

L1

S

—

5.1.5

Ensure permissions on /etc/cron.weekly are configured (Automated)

L1

S

—

5.1.6

Ensure permissions on /etc/cron.monthly are configured (Automated)

L1

S

—

5.1.7

Ensure permissions on /etc/cron.d are configured (Automated)

L1

S

—

5.1.8

Ensure at/cron is restricted to authorized users (Automated)

L1

S

—

5.2

SSH Server Configuration

5.2.1

Ensure permissions on /etc/ssh/sshd_config are configured (Automated)

L1

S

—

5.2.2

Ensure SSH access is limited (Automated)

L1

S

S/ND

Supported; not configured by default in NSP qcow2/OVA, as configuration requires site-specific information

5.2.3

Ensure permissions on SSH private host key files are configured (Automated)

L1

S

—

5.2.4

Ensure permissions on SSH public host key files are configured (Automated)

L1

S

—

5.2.5

Ensure SSH LogLevel is appropriate (Automated)

L1

S

—

5.2.6

Ensure SSH X11 forwarding is disabled (Automated)

L1

S

—

5.2.7

Ensure SSH MaxAuthTries is set to 4 or less (Automated)

L1

S

—

5.2.8

Ensure SSH IgnoreRhosts is enabled (Automated)

L1

S

—

5.2.9

Ensure SSH HostbasedAuthentication is disabled (Automated)

L1

S

—

5.2.10

Ensure SSH root login is disabled (Automated)

L1

S

—

5.2.11

Ensure SSH PermitEmptyPasswords is disabled (Automated)

L1

S

—

5.2.12

Ensure SSH PermitUserEnvironment is disabled (Automated)

L1

S

—

5.2.13

Ensure SSH Idle Timeout Interval is configured (Automated)

L1

S

—

5.2.14

Ensure SSH LoginGraceTime is set to one minute or less (Automated)

L1

S

—

5.2.15

Ensure SSH warning banner is configured (Automated)

L1

S

—

5.2.16

Ensure SSH PAM is enabled (Automated)

L1

S

—

5.2.17

Ensure SSH AllowTcpForwarding is disabled (Automated)

L2

P

S

P

AllowTcpForwarding is required for auxiliary database stations.

5.2.18

Ensure SSH MaxStartups is configured (Automated)

L1

S

—

5.2.19

Ensure SSH MaxSessions is set to 4 or less (Automated)

L1

S

—

5.2.20

Ensure system-wide crypto policy is not over-ridden (Automated)

L1

S

—

5.3

Configure authselect

5.3.1

Create custom authselect profile (Automated)

L1

NS

Custom authselect profile not supported

5.3.2

Select authselect profile (Automated)

L1

NS

Custom authselect profile not supported

5.3.3

Ensure authselect includes with-faillock (Automated)

L1

NS

Custom authselect profile not supported

5.4

Configure PAM

5.4.1

Ensure password creation requirements are configured (Automated)

L1

S

—

5.4.2

Ensure lockout for failed password attempts is configured (Automated)

L1

S

S/ND

—

5.4.3

Ensure password reuse is limited (Automated)

L1

S

—

5.4.4

Ensure password hashing algorithm is SHA-512 (Automated)

L1

S

—

5.5

User Accounts and Environment

5.5.1

Set Shadow Password Suite Parameters

5.5.1.1

Ensure password expiration is 365 days or less (Automated)

L1

P

P/ND

Note: The password expiration period of the following RHEL users must not be altered:

• root

• nsp

• samadmin

• oracle

• td-agent

• samauxdb

• kube

• etcd

5.5.1.2

Ensure minimum days between password changes is 7 or more (Automated)

L1

S

S/ND

Supported, but not configured by default in NSP qcow2/OVA

5.5.1.3

Ensure password expiration warning days is 7 or more (Automated)

L1

S

—

5.5.1.4

Ensure inactive password lock is 30 days or less (Automated)

L1

S

—

5.5.1.5

Ensure all users last password change date is in the past (Automated)

L1

S

—

5.5.2

Ensure system accounts are secured (Automated)

L1

S

—

5.5.3

Ensure default user shell timeout is 900 seconds or less (Automated)

L1

S

S/ND

Supported, but not configured by default in NSP qcow2/OVA; setting of 1800 seconds (30 minutes) recommended to avoid missing console output of long operations

5.5.4

Ensure default group for the root account is GID 0 (Automated)

L1

S

—

5.5.5

Ensure default user umask is 027 or more restrictive (Automated)

S

Must exclude following RHEL users:

• root

• nsp

• samadmin

• oracle

• td-agent

• samauxdb

• kube

• etcd

5.6

Ensure root login is restricted to system console (Manual)

L1

S

S/ND

Supported, but not configured by default in NSP qcow2/OVA

5.7

Ensure access to the su command is restricted (Automated)

L1

S

—

6

System Maintenance

6.1

System File Permissions

6.1.1

Audit system file permissions (Manual)

L2

n/a

Manual audit recommendation only; transferred to customer for review

6.1.2

Ensure permissions on /etc/passwd are configured (Automated)

L1

S

—

6.1.3

Ensure permissions on /etc/passwd- are configured (Automated)

L1

S

—

6.1.4

Ensure permissions on /etc/shadow are configured (Automated)

L1

S

—

6.1.5

Ensure permissions on /etc/shadow- are configured (Automated)

L1

S

—

6.1.6

Ensure permissions on /etc/gshadow are configured (Automated)

L1

S

—

6.1.7

Ensure permissions on /etc/gshadow- are configured (Automated)

L1

S

—

6.1.8

Ensure permissions on /etc/group are configured (Automated)

L1

S

—

6.1.9

Ensure permissions on /etc/group- are configured (Automated)

L1

S

—

6.1.10

Ensure no world writable files exist (Automated)

L1

P

NS

S

Not supported by NSP Kubernetes deployer, cluster nodes; not fully supported until resolved by Kubernetes

6.1.11

Ensure no unowned files or directories exist (Automated)

L1

P

NS

S

Not supported by NSP Kubernetes deployer, cluster nodes

6.1.12

Ensure no ungrouped files or directories exist (Automated)

L1

P

NS

S

Not supported by NSP Kubernetes deployer, cluster nodes

6.1.13

Audit SUID executables (Manual)

L1

n/a

Manual audit recommendation only; transferred to customer for review

6.1.14

Audit SGID executables (Manual)

L1

n/a

Manual audit recommendation only; transferred to customer for review

6.2

User and Group Settings

6.2.1

Ensure password fields are not empty (Automated)

L1

S

—

6.2.2

Ensure no legacy + entries exist in /etc/passwd (Automated)

L1

S

—

6.2.3

Ensure root PATH Integrity (Automated)

L1

S

—

6.2.4

Ensure no legacy + entries exist in /etc/shadow (Automated)

L1

S

—

6.2.5

Ensure no legacy + entries exist in /etc/group (Automated)

L1

S

—

6.2.6

Ensure root is the only UID 0 account (Automated)

L1

S

—

6.2.7

Ensure users' home directories permissions are 750 or more restrictive (Automated)

L1

S

—

6.2.8

Ensure users own their home directories (Automated)

L1

S

—

6.2.9

Ensure users' dot files are not group or world writable (Automated)

L1

S

—

6.2.10

Ensure no users have .forward files (Automated)

L1

S

—

6.2.11

Ensure no users have .netrc files (Automated)

L1

S

—

6.2.12

Ensure users' .netrc Files are not group or world accessible (Automated)

L1

S

—

6.2.13

Ensure no users have .rhosts files (Automated)

L1

S

—

6.2.14

Ensure all groups in /etc/passwd exist in /etc/group (Automated)

L1

S

—

6.2.15

Ensure no duplicate UIDs exist (Automated)

L1

S

—

6.2.16

Ensure no duplicate GIDs exist (Automated)

L1

S

—

6.2.17

Ensure no duplicate user names exist (Automated)

L1

S

—

6.2.18

Ensure no duplicate group names exist (Automated)

L1

S

—

6.2.19

Ensure shadow group is empty (Automated)

L1

S

—

6.2.20

Ensure all users' home directories exist (Automated)

L1

S

—