| CCE-83067-9 |
Install AIDE [ref] |
The aide package can be installed with the following command: $ sudo zypper install aide |
The AIDE package must be installed if it is to be available for integrity checking. |
medium |
content_rule_package_aide_installed |
SLES-12-010500 |
CM-6(a) |
4.3.4.3.2,4.3.4.3.3,4.3.4.4.4 |
PR.DS-1,PR.DS-6,PR.DS-8,PR.IP-1,PR.IP-3,DE.CM-1,DE.CM-7 |
SRG-OS-000363-GPOS-00150 |
NaN |
SV-217148r603262_rule |
CCI-002699,CCI-001744 |
1,2,3,5,7,8,9,11,12,13,14,15,16 |
NaN |
NaN |
APO01.06,BAI01.06,BAI02.01,BAI03.05,BAI06.01,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.03,DSS03.05,DSS04.07,DSS05.02,DSS05.03,DSS05.05,DSS05.07,DSS06.02,DSS06.06 |
A.8.2.3,A.11.2.4,A.12.1.2,A.12.2.1,A.12.4.1,A.12.5.1,A.12.6.2,A.14.1.2,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4,A.14.2.7,A.15.2.1 |
SR,3.1,SR,3.3,SR,3.4,SR,3.8,SR,4.1,SR,6.2,SR,7.6 |
BP28(R51) |
5.10.1.3,1034,1288,1341,1417,Req-11.5,1.3.1 |
| CCE-83204-8 |
Configure AIDE to Verify the Audit Tools [ref] |
The operating system file integrity tool must be configured to protect the integrity of the audit tools. |
Protecting the integrity of the tools used for auditing purposes is acritical step toward ensuring the integrity of audit information. Auditinformation includes all information (e.g., audit records, audit settings,and audit reports) needed to successfully audit information systemactivity.Audit tools include but are not limited to vendor-provided and open-sourceaudit tools needed to successfully view and manipulate audit informationsystem activity and records. Audit tools include custom queries and reportgenerators.It is not uncommon for attackers to replace the audit tools or inject codeinto the existing tools to provide the capability to hide or erase systemactivity from the audit logs.To address this risk, audit tools must be cryptographically signed toprovide the capability to identify when the audit tools have been modified,manipulated, or replaced. An example is a checksum hash of the file orfiles. |
medium |
content_rule_aide_check_audit_tools |
SLES-12-010540 |
AU-9(3),AU-9(3).1 |
NaN |
NaN |
SRG-OS-000278-GPOS-00108 |
NaN |
SV-217152r603262_rule |
CCI-001496 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83048-9 |
Configure Notification of Post-AIDE Scan Details [ref] |
AIDE should notify appropriate personnel of the details of a scan after the scan has been run. If AIDE has already been configured for periodic execution in /etc/crontab, append the following line to the existing AIDE line: | /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhost Otherwise, add the following line to /etc/crontab: 05 4 * * * root /usr/sbin/aide --check | /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhost AIDE can be executed periodically through other means; this is merely one example. |
Unauthorized changes to the baseline configuration could make the system vulnerableto various attacks or allow unauthorized access to the operating system. Changes tooperating system configurations can have unintended side effects, some of which maybe relevant to security.Detecting such changes and providing an automated response can help avoid unintended,negative consequences that could ultimately affect the security state of the operatingsystem. The operating system's Information Management Officer (IMO)/Information SystemSecurity Officer (ISSO) and System Administrators (SAs) must be notified via email and/ormonitoring system trap when there is an unauthorized modification of a configuration item. |
medium |
content_rule_aide_scan_notification |
SLES-12-010510 |
SI-6d |
4.3.4.3.2,4.3.4.3.3 |
PR.IP-1,PR.IP-3,DE.CM-1,DE.CM-7 |
SRG-OS-000363-GPOS-00150,SRG-OS-000447-GPOS-00201 |
NaN |
SV-217149r603262_rule |
CCI-001744,CCI-002702 |
1,2,3,5,7,8,9,11,12,13,15,16 |
NaN |
NaN |
BAI01.06,BAI06.01,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.03,DSS03.05,DSS05.02,DSS05.05,DSS05.07 |
A.12.1.2,A.12.4.1,A.12.5.1,A.12.6.2,A.14.2.2,A.14.2.3,A.14.2.4,A.14.2.7,A.15.2.1 |
SR,6.2,SR,7.6 |
BP28(R51) |
NaN |
| CCE-83150-3 |
Configure AIDE to Verify Access Control Lists (ACLs) [ref] |
By default, the acl option is added to the FIPSR ruleset in AIDE. If using a custom ruleset or the acl option is missing, add acl to the appropriate ruleset. For example, add acl to the following line in /etc/aide.conf: FIPSR = p+i+n+u+g+s+m+c+acl+selinux+xattrs+sha256 AIDE rules can be configured in multiple ways; this is merely one example that is already configured by default. The remediation provided with this rule adds acl to all rule sets available in /etc/aide.conf |
ACLs can provide permissions beyond those permitted through the file mode and must beverified by the file integrity tools. |
low |
content_rule_aide_verify_acls |
SLES-12-010520 |
CM-6(a),SI-7,SI-7(1) |
4.3.4.4.4 |
PR.DS-6,PR.DS-8 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217150r646711_rule |
CCI-000366 |
2,3 |
NaN |
NaN |
APO01.06,BAI03.05,BAI06.01,DSS06.02 |
A.11.2.4,A.12.2.1,A.12.5.1,A.14.1.2,A.14.1.3,A.14.2.4 |
SR,3.1,SR,3.3,SR,3.4,SR,3.8 |
BP28(R51) |
NaN |
| CCE-83151-1 |
Configure AIDE to Verify Extended Attributes [ref] |
By default, the xattrs option is added to the FIPSR ruleset in AIDE. If using a custom ruleset or the xattrs option is missing, add xattrs to the appropriate ruleset. For example, add xattrs to the following line in /etc/aide.conf: FIPSR = p+i+n+u+g+s+m+c+acl+selinux+xattrs+sha256 AIDE rules can be configured in multiple ways; this is merely one example that is already configured by default. The remediation provided with this rule adds xattrs to all rule sets available in /etc/aide.conf |
Extended attributes in file systems are used to contain arbitrary data and file metadatawith security implications. |
low |
content_rule_aide_verify_ext_attributes |
SLES-12-010530 |
CM-6(a),SI-7,SI-7(1) |
4.3.4.4.4 |
PR.DS-6,PR.DS-8 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217151r646713_rule |
CCI-000366 |
2,3 |
NaN |
NaN |
APO01.06,BAI03.05,BAI06.01,DSS06.02 |
A.11.2.4,A.12.2.1,A.12.5.1,A.14.1.2,A.14.1.3,A.14.2.4 |
SR,3.1,SR,3.3,SR,3.4,SR,3.8 |
BP28(R51) |
NaN |
| CCE-83224-6 |
Verify '/proc/sys/crypto/fips_enabled' exists [ref] |
On a system where FIPS 140-2 mode is enabled, /proc/sys/crypto/fips_enabled must exist. To verify FIPS mode, run the following command: cat /proc/sys/crypto/fips_enabledWarning: To configure the OS to run in FIPS 140-2 mode, the kernel parameter "fips=1" needs to be added during its installation. Enabling FIPS mode on a preexisting system involves a number of modifications to it. Refer to the vendor installation guidances.Warning: System Crypto Modules must be provided by a vendor that undergoes FIPS-140 certifications. FIPS-140 is applicable to all Federal agencies that use cryptographic-based security systems to protect sensitive information in computer and telecommunication systems (including voice systems) as defined in Section 5131 of the Information Technology Management Reform Act of 1996, Public Law 104-106. This standard shall be used in designing and implementing cryptographic modules that Federal departments and agencies operate or are operated for them under contract. See https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf To meet this, the system has to have cryptographic software provided by a vendor that has undergone this certification. This means providing documentation, test results, design information, and independent third party review by an accredited lab. While open source software is capable of meeting this, it does not meet FIPS-140 unless the vendor submits to this process. |
Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption toprotect data. The operating system must implement cryptographic modules adhering to the higherstandards approved by the federal government since this provides assurance they have been testedand validated. |
high |
content_rule_is_fips_mode_enabled |
SLES-12-010420 |
SC-13 |
NaN |
NaN |
SRG-OS-000396-GPOS-00176,SRG-OS-000478-GPOS-00223 |
NaN |
SV-217143r603262_rule |
CCI-002450 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83037-2 |
The Installed Operating System Is FIPS 140-2 Certified [ref] |
To enable processing of sensitive information the operating system must provide certified cryptographic modules compliant with FIPS 140-2 standard. SUSE Enterprise Linux is supported by SUSE Software Solutions Germany GmbH. As the SUSE Enterprise Linux vendor, SUSE Software Solutions Germany GmbH is responsible for maintaining government certifications and standards.Warning: There is no remediation besides switching to a different operating system.Warning: System Crypto Modules must be provided by a vendor that undergoes FIPS-140 certifications. FIPS-140 is applicable to all Federal agencies that use cryptographic-based security systems to protect sensitive information in computer and telecommunication systems (including voice systems) as defined in Section 5131 of the Information Technology Management Reform Act of 1996, Public Law 104-106. This standard shall be used in designing and implementing cryptographic modules that Federal departments and agencies operate or are operated for them under contract. See https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf To meet this, the system has to have cryptographic software provided by a vendor that has undergone this certification. This means providing documentation, test results, design information, and independent third party review by an accredited lab. While open source software is capable of meeting this, it does not meet FIPS-140 unless the vendor submits to this process. |
The Federal Information Processing Standard (FIPS) Publication 140-2, (FIPSPUB 140-2) is a computer security standard. The standard specifies securityrequirements for cryptographic modules used to protect sensitiveunclassified information. Refer to the full FIPS 140-2 standard at http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdffor further details on the requirements.FIPS 140-2 validation is required by U.S. law when information systems usecryptography to protect sensitive government information. In order toachieve FIPS 140-2 certification, cryptographic modules are subject toextensive testing by independent laboratories, accredited by NationalInstitute of Standards and Technology (NIST). |
high |
content_rule_installed_OS_is_FIPS_certified |
NaN |
CM-6(a),IA-7,SC-12(2),SC-12(3),SC-13,SC-12 |
CIP-003-3,R4.2 |
NaN |
SRG-OS-000120-VMM-000600,SRG-OS-000478-VMM-001980,SRG-OS-000396-VMM-001590 |
NaN |
NaN |
CCI-000803,CCI-002450 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
CIP-007-3,R5.1 |
| CCE-83001-8 |
The Installed Operating System Is Vendor Supported [ref] |
The installed operating system must be maintained by a vendor. SUSE Linux Enterprise is supported by SUSE. As the SUSE Linux Enterprise vendor, SUSE is responsible for providing security patches.Warning: There is no remediation besides switching to a different operating system. |
An operating system is considered "supported" if the vendor continues toprovide security patches for the product. With an unsupported release, itwill not be possible to resolve any security issue discovered in the systemsoftware. |
high |
content_rule_installed_OS_is_vendor_supported |
SLES-12-010000 |
CM-6(a),MA-6 |
4.2.3.12 |
ID.RA-1,PR.IP-12 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217101r603262_rule |
CCI-000366 |
4,18,20 |
NaN |
NaN |
APO12.01,APO12.02,APO12.03,APO12.04,BAI03.10,DSS05.01,DSS05.02 |
A.12.6.1,SA-13(a),A.14.2.3,A.16.1.3,A.18.2.2,A.18.2.3 |
NaN |
NaN |
4.2.3,4.2.3.7,4.2.3.9 |
| CCE-83046-3 |
Encrypt Partitions [ref] |
SUSE Linux Enterprise 12 natively supports partition encryption through the Linux Unified Key Setup-on-disk-format (LUKS) technology. The easiest way to encrypt a partition is during installation time. For manual installations, select the Encrypt checkbox during partition creation to encrypt the partition. When this option is selected the system will prompt for a passphrase to use in decrypting the partition. The passphrase will subsequently need to be entered manually every time the system boots. Detailed information on encrypting partitions using LUKS or LUKS ciphers can be found on the SUSE Linux Enterprise 12 Documentation web site:https://www.suse.com/documentation/sled-12/book_security/data/sec_security_cryptofs_y2.html |
The risk of a system's physical compromise, particularly mobile systems such aslaptops, places its data at risk of compromise. Encrypting this data mitigatesthe risk of its loss if the system is lost. |
high |
content_rule_encrypt_partitions |
SLES-12-010450 |
SC-28,SC-28.1 |
3.13.16,CIP-003-3,R4.2 |
PR.DS-1,PR.DS-5 |
SRG-OS-000405-GPOS-00184,SRG-OS-000185-GPOS-00079,SRG-OS-000404-GPOS-00183,SRG-OS-000404-VMM-001650,SRG-OS-000405-VMM-001660 |
NaN |
SV-217146r603262_rule |
CCI-001199,CCI-002475,CCI-002476 |
13,14 |
NaN |
164.308(a)(1)(ii)(D),164.308(b)(1),164.310(d),164.312(a)(1),164.312(a)(2)(iii),164.312(a)(2)(iv),164.312(b),164.312(c),164.314(b)(2)(i),164.312(d) |
APO01.06,BAI02.01,BAI06.01,DSS04.07,DSS05.03,DSS05.04,DSS05.07,DSS06.02,DSS06.06 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,3.4,SR,4.1,SR,5.2 |
NaN |
CIP-007-3,R5.1 |
| CCE-83152-9 |
Ensure /home Located On Separate Partition [ref] |
If user home directories will be stored locally, create a separate partition for /home at installation time (or migrate it later using LVM). If /home will be mounted from another system such as an NFS server, then creating a separate partition is not necessary at installation time, and the mountpoint can instead be configured later. |
Ensuring that /home is mounted on its own partition enables thesetting of more restrictive mount options, and also helps ensure thatusers cannot trivially fill partitions used for log or audit data storage. |
low |
content_rule_partition_for_home |
SLES-12-010850 |
CM-6(a),SC-5(2) |
NaN |
PR.PT-4 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217184r603893_rule |
CCI-000366,CCI-001208 |
8,12,15 |
NaN |
NaN |
APO13.01,DSS05.02 |
A.13.1.1,A.13.2.1,A.14.1.3 |
SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,7.1,SR,7.6 |
BP28(R12) |
1.1.17 |
| CCE-83153-7 |
Ensure /var Located On Separate Partition [ref] |
The /var directory is used by daemons and other system services to store frequently-changing data. Ensure that /var has its own partition or logical volume at installation time, or migrate it using LVM. |
Ensuring that /var is mounted on its own partition enables thesetting of more restrictive mount options. This helps protectsystem services such as daemons or other programs which use it.It is not uncommon for the /var directory to containworld-writable directories installed by other software packages. |
low |
content_rule_partition_for_var |
SLES-12-010860 |
CM-6(a),SC-5(2) |
NaN |
PR.PT-4 |
SRG-OS-000480-GPOS-00227,SRG-OS-000341-VMM-001220 |
NaN |
SV-217185r603262_rule |
CCI-000366 |
8,12,15 |
NaN |
NaN |
APO13.01,DSS05.02 |
A.13.1.1,A.13.2.1,A.14.1.3 |
SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,7.1,SR,7.6 |
BP28(R12) |
1.1.10 |
| CCE-83154-5 |
Ensure /var/log/audit Located On Separate Partition [ref] |
Audit logs are stored in the /var/log/audit directory. Ensure that /var/log/audit has its own partition or logical volume at installation time, or migrate it using LVM. Make absolutely certain that it is large enough to store all audit logs that will be created by the auditing daemon. |
Placing /var/log/audit in its own partitionenables better separation between audit filesand other files, and helps ensure thatauditing cannot be halted due to the partition running outof space. |
low |
content_rule_partition_for_var_log_audit |
SLES-12-010870 |
AU-4,CM-6(a),SC-5(2) |
4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
PR.DS-4,PR.PT-1,PR.PT-4 |
SRG-OS-000341-GPOS-00132,SRG-OS-000480-GPOS-00227,SRG-OS-000341-VMM-001220 |
NaN |
SV-217186r603262_rule |
CCI-000366,CCI-001849 |
1,2,3,5,6,8,12,13,14,15,16 |
NaN |
164.312(a)(2)(ii) |
APO11.04,APO13.01,BAI03.05,BAI04.04,DSS05.02,DSS05.04,DSS05.07,MEA02.01 |
A.12.1.3,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.17.2.1 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,7.1,SR,7.2,SR,7.6 |
BP28(R43) |
4.4.2.1,4.4.2.2,4.4.2.4,CIP-007-3,R6.5,1.1.16 |
| CCE-83245-1 |
Disable GDM Unattended or Automatic Login [ref] |
The GNOME Display Manager (GDM) can allow users to automatically login without user interaction or credentials or unattended login. User should always be required to authenticate themselves to the system that they are authorized to use. To disable user ability to automatically login to the system, set the DISPLAYMANAGER_AUTOLOGIN="" or DISPLAYMANAGER_PASSWORD_LESS_LOGIN="no" in the /etc/sysconfig/displaymanager. For example: DISPLAYMANAGER_AUTOLOGIN="" DISPLAYMANAGER_PASSWORD_LESS_LOGIN="no" |
Failure to restrict system access to authenticated users negatively impacts operatingsystem security. |
high |
content_rule_gnome_gdm_disable_unattended_automatic_login |
SLES-12-010380 |
CM-6(b),CM-6.1(iv) |
NaN |
NaN |
SRG-OS-000480-GPOS-00229 |
NaN |
SV-217139r646707_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83010-9 |
Set GNOME3 Screensaver Inactivity Timeout [ref] |
The idle time-out value for inactivity in the GNOME3 desktop is configured via the idle-delay setting must be set under an appropriate configuration file(s) in the /etc/dconf/db/local.d directory and locked in /etc/dconf/db/local.d/locks directory to prevent user modification. For example, to configure the system for a 15 minute delay, add the following to /etc/dconf/db/local.d/00-security-settings: [org/gnome/desktop/session] idle-delay=uint32 900 Once the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example: /org/gnome/desktop/session/idle-delay After the settings have been set, run dconf update. |
A session time-out lock is a temporary action taken when a user stops work and moves away fromthe immediate physical vicinity of the information system but does not logout because of thetemporary nature of the absence. Rather than relying on the user to manually lock their operatingsystem session prior to vacating the vicinity, GNOME3 can be configured to identify whena user's session has idled and take action to initiate a session lock. |
medium |
content_rule_dconf_gnome_screensaver_idle_delay |
SLES-12-010080 |
AC-11(a),AC-11.1,(ii) |
3.1.10,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9 |
PR.AC-7 |
SRG-OS-000029-GPOS-00010 |
NaN |
SV-217109r646684_rule |
CCI-000057 |
1,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.10,DSS06.10 |
A.9.2.1,A.9.2.4,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.5,SR,1.7,SR,1.8,SR,1.9 |
NaN |
5.5.5,FMT_MOF_EXT.1,Req-8.1.8 |
| CCE-83222-0 |
Enable GNOME3 Screensaver Lock After Idle Period [ref] |
To activate locking of the screensaver in the GNOME3 desktop when it is activated, run the following command to configure the SUSE operating system to allow the user to lock the GUI: gsettings set org.gnome.desktop.lockdown disable-lock-screen false Validate that disable-lock-screen has been set to false with the command: gsettings get org.gnome.desktop.lockdown disable-lock-screen |
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinityof the information system but does not want to logout because of the temporary nature of the absense. |
medium |
content_rule_dconf_gnome_screensaver_lock_enabled |
SLES-12-010060 |
AC-11(b),AC-11(a),AC-11(1),AC-11(1).1,AC-11.1(iii),AC-11 |
3.1.10,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9 |
PR.AC-7 |
SRG-OS-000028-GPOS-00009,SRG-OS-000030-GPOS-00011 |
NaN |
SV-217107r603262_rule |
CCI-000056,CCI-000058,CCI-000060 |
1,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.10,DSS06.10 |
A.9.2.1,A.9.2.4,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.5,SR,1.7,SR,1.8,SR,1.9 |
NaN |
5.5.5,FMT_MOF_EXT.1,Req-8.1.8 |
| CCE-83221-2 |
Implement Blank Screensaver [ref] |
On SUSE users should set the screensaver to use publicly viewable images or blank screen by doing the following: Find the Settings menu and then navigate to the Background selection section - Click "Applications" on the bottom left. - Hover over "System Tools" with the mouse. - Click the "Settings" icon under System Tools. - Click "Background" and then "Lock Screen". - Select image and set the Lock Screen image to the user's choice. - Click "Select". - Exit Settings Dialog. To set the screensaver mode in the GNOME3 desktop to a blank screen, add or set picture-uri to string '' in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/desktop/screensaver] picture-uri='' Once the settings have been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example: /org/gnome/desktop/screensaver/picture-uri After the settings have been set, run dconf update. |
Setting the screensaver mode to blank-only conceals thecontents of the display from passersby. |
medium |
content_rule_dconf_gnome_screensaver_mode_blank |
SLES-12-010100 |
AC-11(1),AC-11(1).1,CM-6(a) |
3.1.10,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9 |
PR.AC-7 |
SRG-OS-000031-GPOS-00012 |
NaN |
SV-217111r603262_rule |
CCI-000060 |
1,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.10,DSS06.10 |
A.9.2.1,A.9.2.4,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.5,SR,1.7,SR,1.8,SR,1.9 |
NaN |
5.5.5,FMT_MOF_EXT.1,Req-8.1.8 |
| CCE-83182-6 |
Make sure that the dconf databases are up-to-date with regards to respective keyfiles [ref] |
By default, DConf uses a binary database as a data backend. The system-level database is compiled from keyfiles in the /etc/dconf/db/ directory by the dconf update command. |
Unlike text-based keyfiles, the binary database is impossible to check by OVAL.Therefore, in order to evaluate dconf configuration, both have to be true at the same time -configuration files have to be compliant, and the database needs to be more recent than those keyfiles,which gives confidence that it reflects them. |
high |
content_rule_dconf_db_up_to_date |
NaN |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
NaN |
NaN |
NaN |
NaN |
164.308(a)(1)(ii)(B),164.308(a)(5)(ii)(A) |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83006-7 |
Configure GNOME3 DConf User Profile [ref] |
By default, DConf provides a standard user profile. This profile contains a list of DConf configuration databases. The user profile and database always take the highest priority. As such the DConf User profile should always exist and be configured correctly. To make sure that the user profile is configured correctly, the /etc/dconf/profile/gdm should be set as follows: user-db:user system-db:gdm |
Failure to have a functional DConf profile prevents GNOME3 configuration settingsfrom being enforced for all users and allows various security risks. |
high |
content_rule_enable_dconf_user_profile |
NaN |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
NaN |
NaN |
NaN |
NaN |
164.308(a)(1)(ii)(B),164.308(a)(5)(ii)(A) |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83013-3 |
Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticate [ref] |
The sudo !authenticate option, when specified, allows a user to execute commands using sudo without having to authenticate. This should be disabled by making sure that the !authenticate option does not exist in /etc/sudoers configuration file or any sudo configuration snippets in /etc/sudoers.d/. |
Without re-authentication, users may access resources or perform tasks for which theydo not have authorization.When operating systems provide the capability to escalate a functional capability, itis critical that the user re-authenticate. |
medium |
content_rule_sudo_remove_no_authenticate |
SLES-12-010110 |
CM-6(a),IA-11 |
4.3.3.5.1,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9 |
PR.AC-1,PR.AC-7 |
SRG-OS-000373-GPOS-00156,SRG-OS-000373-GPOS-00157,SRG-OS-000373-GPOS-00158,SRG-OS-000373-VMM-001470,SRG-OS-000373-VMM-001480,SRG-OS-000373-VMM-001490 |
NaN |
SV-217112r646686_rule |
CCI-002038 |
1,5,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.10,DSS06.03,DSS06.10 |
A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9 |
BP28(R5),BP28(R59) |
NaN |
| CCE-83012-5 |
Ensure Users Re-Authenticate for Privilege Escalation - sudo NOPASSWD [ref] |
The sudo NOPASSWD tag, when specified, allows a user to execute commands using sudo without having to authenticate. This should be disabled by making sure that the NOPASSWD tag does not exist in /etc/sudoers configuration file or any sudo configuration snippets in /etc/sudoers.d/. |
Without re-authentication, users may access resources or perform tasks for which theydo not have authorization.When operating systems provide the capability to escalate a functional capability, itis critical that the user re-authenticate. |
medium |
content_rule_sudo_remove_nopasswd |
SLES-12-010110 |
CM-6(a),IA-11 |
4.3.3.5.1,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9 |
PR.AC-1,PR.AC-7 |
SRG-OS-000373-GPOS-00156,SRG-OS-000373-GPOS-00157,SRG-OS-000373-GPOS-00158,SRG-OS-000373-VMM-001470,SRG-OS-000373-VMM-001480,SRG-OS-000373-VMM-001490 |
NaN |
SV-217112r646686_rule |
CCI-002038 |
1,5,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.10,DSS06.03,DSS06.10 |
A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9 |
BP28(R5),BP28(R59) |
NaN |
| CCE-83231-1 |
The operating system must require Re-Authentication when using the sudo command. Ensure sudo timestamp_timeout is appropriate - sudo timestamp_timeout [ref] |
The sudo timestamp_timeout tag sets the amount of time sudo password prompt waits. The default timestamp_timeout value is 5 minutes. The timestamp_timeout should be configured by making sure that the timestamp_timeout tag exists in /etc/sudoers configuration file or any sudo configuration snippets in /etc/sudoers.d/. If the value is set to an integer less than 0, the user's time stamp will not expire and the user will not have to re-authenticate for privileged actions until the user's session is terminated. |
Without re-authentication, users may access resources or perform tasks for which theydo not have authorization.When operating systems provide the capability to escalate a functional capability, itis critical that the user re-authenticate. |
medium |
content_rule_sudo_require_reauthentication |
SLES-12-010113 |
IA-11 |
NaN |
NaN |
SRG-OS-000373-GPOS-00156 |
NaN |
SV-237605r646778_rule |
CCI-002038 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83229-5 |
The operating system must restrict privilege elevation to authorized personnel [ref] |
The sudo command allows a user to execute programs with elevated (administrator) privileges. It prompts the user for their password and confirms your request to execute a command by checking a file, called sudoers. Restrict privileged actions by removing the following entries from the sudoers file: ALL ALL=(ALL) ALL ALL ALL=(ALL:ALL) ALLWarning: This rule doesn't come with a remediation, as the exact requirement allows exceptions, and removing lines from the sudoers file can make the system non-administrable. |
If the "sudoers" file is not configured correctly, any user definedon the system can initiate privileged actions on the target system. |
medium |
content_rule_sudo_restrict_privilege_elevation_to_authorized |
SLES-12-010111 |
CM-6(b),CM-6(iv) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-237603r646772_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83230-3 |
Ensure invoking users password for privilege escalation when using sudo [ref] |
The sudoers security policy requires that users authenticate themselves before they can use sudo. When sudoers requires authentication, it validates the invoking user's credentials. The expected output for: sudo egrep -i '(!rootpw|!targetpw|!runaspw)' /etc/sudoers /etc/sudoers.d/* | grep -v '#' /etc/sudoers:Defaults !targetpw /etc/sudoers:Defaults !rootpw /etc/sudoers:Defaults !runaspw |
If the rootpw, targetpw, or runaspw flags are defined and not disabled, by default the operating system will promptthe invoking user for the "root" user password. |
medium |
content_rule_sudoers_validate_passwd |
SLES-12-010112 |
CM-6(b),CM-6.1(iv) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-237604r646775_rule |
CCI-000366,CCI-002227 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83186-7 |
Ensure zypper Removes Previous Package Versions [ref] |
zypper should be configured to remove previous software components after new versions have been installed. To configure zypper to remove the previous software components after updating, set the solver.upgradeRemoveDroppedPackages to 1 in /etc/zypp/zypp.conf. |
Previous versions of software components that are not removed from the informationsystem after updates have been installed may be exploited by some adversaries. |
low |
content_rule_clean_components_post_updating |
SLES-12-010570 |
CM-11(a),CM-11(b),CM-6(a),SI-2(6) |
4.2.3.12,3.4.8 |
ID.RA-1,PR.IP-12 |
SRG-OS-000437-GPOS-00194,SRG-OS-000437-VMM-001760 |
NaN |
SV-217154r603262_rule |
CCI-002617 |
4,18,20 |
NaN |
NaN |
APO12.01,APO12.02,APO12.03,APO12.04,BAI03.10,DSS05.01,DSS05.02 |
A.12.6.1,A.14.2.3,A.16.1.3,A.18.2.2,A.18.2.3 |
NaN |
NaN |
4.2.3,4.2.3.7,4.2.3.9 |
| CCE-83068-7 |
Ensure gpgcheck Enabled In Main zypper Configuration [ref] |
The gpgcheck option controls whether RPM packages' signatures are always checked prior to installation. To configure zypper to check package signatures before installing them, ensure the following line appears in /etc/zypp/zypp.conf in the [main] section: gpgcheck=1 |
Changes to any software components can have significant effects on theoverall security of the operating system. This requirement ensures thesoftware has not been tampered with and that it has been provided by atrusted vendor.Accordingly, patches, service packs, device drivers, or operating systemcomponents must be signed with a certificate recognized and approved by theorganization.Verifying the authenticity of the software prior to installationvalidates the integrity of the patch or upgrade received from a vendor.This ensures the software has not been tampered with and that it has beenprovided by a trusted vendor. Self-signed certificates are disallowed bythis requirement. Certificates used to verify the software must be from anapproved Certificate Authority (CA). |
high |
content_rule_ensure_gpgcheck_globally_activated |
SLES-12-010550 |
CM-5(3),CM-6(a),CM-11(a),CM-11(b),SA-12,SC-12,SC-12(3),SI-7 |
3.4.8,4.3.4.3.2,4.3.4.3.3,4.3.4.4.4 |
PR.DS-6,PR.DS-8,PR.IP-1 |
SRG-OS-000366-GPOS-00153,SRG-OS-000366-VMM-001430,SRG-OS-000370-VMM-001460,SRG-OS-000404-VMM-001650 |
NaN |
SV-217153r646716_rule |
CCI-001749 |
2,3,9,11 |
NaN |
164.308(a)(1)(ii)(D),164.312(b),164.312(c)(1),164.312(c)(2),164.312(e)(2)(i) |
APO01.06,BAI03.05,BAI06.01,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS06.02 |
A.11.2.4,A.12.1.2,A.12.2.1,A.12.5.1,A.12.6.2,SA-12(10),A.14.1.2,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,3.1,SR,3.3,SR,3.4,SR,3.8,SR,7.6 |
BP28(R15) |
5.10.4.1,FPT_TUD_EXT.1,FPT_TUD_EXT.2,Req-6.2,1.2.3 |
| CCE-83002-6 |
Ensure Software Patches Installed [ref] |
If the system is configured for online updates, invoking the following command will list available security updates: $ sudo zypper refresh && sudo zypper list-patches -g security NOTE: U.S. Defense systems are required to be patched within 30 days or sooner as local policy dictates. |
Installing software updates is a fundamental mitigation againstthe exploitation of publicly-known vulnerabilities. If the mostrecent security patches and updates are not installed, unauthorizedusers may take advantage of weaknesses in the unpatched software. Thelack of prompt attention to patching could result in a system compromise. |
high |
content_rule_security_patches_up_to_date |
SLES-12-010010 |
CM-6(a),SI-2(5),SI-2(c) |
4.2.3.12 |
ID.RA-1,PR.IP-12 |
SRG-OS-000480-GPOS-00227,SRG-OS-000480-VMM-002000 |
NaN |
SV-217102r603262_rule |
CCI-000366,CCI-001227 |
4,18,20 |
NaN |
NaN |
APO12.01,APO12.02,APO12.03,APO12.04,BAI03.10,DSS05.01,DSS05.02 |
A.12.6.1,A.14.2.3,A.16.1.3,A.18.2.2,A.18.2.3 |
NaN |
BP28(R08) |
5.10.4.1,4.2.3,4.2.3.7,4.2.3.9,FMT_MOF_EXT.1,Req-6.2 |
| CCE-83183-4 |
Modify the System GUI Login Banner [ref] |
To configure the GUI system login banner edit /etc/gdm/banner. Replace the default text with a message compliant with the local site policy or a legal disclaimer. The DoD required text is either: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests -- not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. OR: I've read & consent to terms in IS user agreem't. |
Display of a standardized and approved use notification before grantingaccess to the operating system ensures privacy and security notificationverbiage used is consistent with applicable federal laws, Executive Orders,directives, policies, regulations, standards, and guidance.System use notifications are required only for access via login interfaceswith human users and are not required when such human interfaces do notexist. |
medium |
content_rule_banner_etc_gdm_banner |
SLES-12-030020 |
AC-8(b) |
NaN |
NaN |
NaN |
NaN |
SV-217260r603262_rule |
CCI-000050 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83005-9 |
Enable GNOME3 Login Warning Banner [ref] |
In the default graphical environment, displaying a login warning banner in the GNOME Display Manager's login screen can be enabled on the login screen by setting banner-message-enable to true. To enable, add or edit banner-message-enable to /etc/dconf/db/gdm.d/00-security-settings. For example: [org/gnome/login-screen] banner-message-enable=true Once the setting has been added, add a lock to /etc/dconf/db/gdm.d/locks/00-security-settings-lock to prevent user modification. For example: /org/gnome/login-screen/banner-message-enable After the settings have been set, run dconf update. The banner text must also be set. |
Display of a standardized and approved use notification before granting access to the operating systemensures privacy and security notification verbiage used is consistent with applicable federal laws,Executive Orders, directives, policies, regulations, standards, and guidance.For U.S. Government systems, system use notifications are required only for access via login interfaceswith human users and are not required when such human interfaces do not exist. |
medium |
content_rule_dconf_gnome_banner_enabled |
SLES-12-010040 |
AC-8(a),AC-8(b),AC-8(c) |
3.1.9,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9 |
PR.AC-7 |
SRG-OS-000023-GPOS-00006,SRG-OS-000024-GPOS-00007,SRG-OS-000228-GPOS-00088 |
NaN |
SV-217105r646678_rule |
CCI-000048,CCI-000050,CCI-001384,CCI-001385,CCI-001386,CCI-001387,CCI-001388 |
1,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.10,DSS06.10 |
A.9.2.1,A.9.2.4,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.5,SR,1.7,SR,1.8,SR,1.9 |
NaN |
FMT_MOF_EXT.1,1.9 |
| CCE-83007-5 |
Set the GNOME3 Login Warning Banner Text [ref] |
In the default graphical environment, configuring the login warning banner text in the GNOME Display Manager's login screen can be configured on the login screen by setting banner-message-text to 'APPROVED_BANNER' where APPROVED_BANNER is the approved banner for your environment. To enable, add or edit banner-message-text to /etc/dconf/db/gdm.d/00-security-settings. For example: [org/gnome/login-screen] banner-message-text='APPROVED_BANNER' Once the setting has been added, add a lock to /etc/dconf/db/gdm.d/locks/00-security-settings-lock to prevent user modification. For example: /org/gnome/login-screen/banner-message-text After the settings have been set, run dconf update. When entering a warning banner that spans several lines, remember to begin and end the string with ' and use \n for new lines. |
An appropriate warning message reinforces policy awareness during the logonprocess and facilitates possible legal action against attackers. |
medium |
content_rule_dconf_gnome_login_banner_text |
SLES-12-010050 |
AC-8(a),AC-8(c) |
3.1.9,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9 |
PR.AC-7 |
SRG-OS-000023-GPOS-00006,SRG-OS-000024-GPOS-00007,SRG-OS-000228-GPOS-00088 |
NaN |
SV-217106r646681_rule |
CCI-000048 |
1,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.10,DSS06.10 |
A.9.2.1,A.9.2.4,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.5,SR,1.7,SR,1.8,SR,1.9 |
NaN |
FMT_MOF_EXT.1,1.9 |
| CCE-83003-4 |
Display the Standard Mandatory DoD Notice and Consent Banner until Explicit Acknowledgement [ref] |
Display of a standardized and approved use notification before granting access to the SUSE operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. The banner must be acknowledged by the user prior to allowing the user access to the SUSE operating system. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD will not be in compliance with system use notifications required by law. System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for the SUSE operating system: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. Check the configuration by running the following command: # more /etc/gdm/Xsession The beginning of the file must contain the following text immediately after #!/bin/sh: if ! zenity --text-info \ --title "Consent" \ --filename=/etc/gdm/banner \ --no-markup \ --checkbox="Accept." 10 10; then sleep 1; exit 1; fi |
Display of a standardized and approved use notification before granting access to the operating systemensures privacy and security notification verbiage used is consistent with applicable federal laws,Executive Orders, directives, policies, regulations, standards, and guidance.For U.S. Government systems, system use notifications are required only for access via login interfaceswith human users and are not required when such human interfaces do not exist. |
medium |
content_rule_gui_login_dod_acknowledgement |
SLES-12-010020 |
AC-8,a,AC-8.1,(ii),AC-8,b,AC-8.1,(iii) |
NaN |
NaN |
SRG-OS-000023-GPOS-00006 |
NaN |
SV-217103r603262_rule |
CCI-000048,CCI-000050 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83054-7 |
Modify the System Login Banner [ref] |
To configure the system login banner edit /etc/issue. Replace the default text with a message compliant with the local site policy or a legal disclaimer. The DoD required text is either: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests -- not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. OR: I've read & consent to terms in IS user agreem't. |
Display of a standardized and approved use notification before grantingaccess to the operating system ensures privacy and security notificationverbiage used is consistent with applicable federal laws, Executive Orders,directives, policies, regulations, standards, and guidance.System use notifications are required only for access via login interfaceswith human users and are not required when such human interfaces do notexist. |
medium |
content_rule_banner_etc_issue |
SLES-12-010030 |
AC-8(a),AC-8.1(ii) |
3.1.9,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9 |
PR.AC-7 |
SRG-OS-000023-GPOS-00006,SRG-OS-000024-GPOS-00007,SRG-OS-000023-VMM-000060,SRG-OS-000024-VMM-000070 |
NaN |
SV-217104r603262_rule |
CCI-000048,CCI-000050 |
1,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.10,DSS06.10 |
A.9.2.1,A.9.2.4,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.5,SR,1.7,SR,1.8,SR,1.9 |
NaN |
FMT_MOF_EXT.1,1.7.1.2 |
| CCE-83173-5 |
Limit Password Reuse [ref] |
Do not allow users to reuse recent passwords. This can be accomplished by using the remember option for the pam_pwhistory PAM modules. In the file /etc/pam.d/common-password, make sure the parameters remember and use_authtok are present, and that the value for the remember parameter is 5 or greater. For example: password requisite pam_pwhistory.so ...existing_options... remember=5 use_authtok The DoD STIG requirement is 5 passwords. |
Preventing re-use of previous passwords helps ensure that a compromised password is not re-used by a user. |
medium |
content_rule_accounts_password_pam_pwhistory_remember |
SLES-12-010310 |
NaN |
NaN |
NaN |
SRG-OS-000077-GPOS-00045 |
NaN |
SV-217133r603262_rule |
CCI-000200 |
NaN |
NaN |
NaN |
NaN |
IA-5(1)(e),IA-5,(1).1(v) |
NaN |
NaN |
NaN |
| CCE-83176-8 |
Enforce Delay After Failed Logon Attempts [ref] |
To configure the system to introduce a delay after failed logon attempts, add or correct the pam_faildelay settings in /etc/pam.d/common-auth to make sure its delay parameter is at least 4000000 or greater. For example: auth required pam_faildelay.so delay=4000000 |
Limiting the number of logon attempts over a certain time interval reducesthe chances that an unauthorized user may gain access to an account. |
medium |
content_rule_accounts_passwords_pam_faildelay_delay |
SLES-12-010370 |
CM-6(b),CM-6.1(iv) |
NaN |
NaN |
SRG-OS-000480-GPOS-00226 |
NaN |
SV-217138r603262_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83055-4 |
Set Deny For Failed Password Attempts [ref] |
The SUSE Linux Enterprise 12 operating system must lock an account after - at most - 3 consecutive invalid access attempts. |
By limiting the number of failed logon attempts, the risk of unauthorizedsystem access via user password guessing, otherwise known as brute-forceattacks, is reduced. Limits are imposed by locking the account.To configure the operating system to lock an account after threeunsuccessful consecutive access attempts using pam_tally2.so,modify the content of both /etc/pam.d/common-auth and/etc/pam.d/common-account as follows: add or modify the pam_tally2.so module line in/etc/pam.d/common-auth to ensure both onerr=fail anddeny=3 are present. For example:auth required pam_tally2.so onerr=fail silent audit deny=3 add or modify the following line in /etc/pam.d/common-account:account required pam_tally2.so |
medium |
content_rule_accounts_passwords_pam_tally2 |
SLES-12-010130 |
AC-7(a) |
NaN |
NaN |
SRG-OS-000021-GPOS-00005 |
NaN |
SV-217114r603262_rule |
CCI-000044 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
5.4.2 |
| CCE-83168-5 |
Set Password Strength Minimum Digit Characters [ref] |
The pam_cracklib module's dcredit parameter controls requirements for usage of digits in a password. When set to a negative number, any password will be required to contain that many digits. When set to a positive number, pam_cracklib will grant +1 additional length credit for each digit. Add dcredit=-1 after pam_cracklib.so to require use of a digit in passwords. |
Requiring digits makes password guessing attacks more difficult by ensuringa larger search space. |
medium |
content_rule_cracklib_accounts_password_pam_dcredit |
SLES-12-010170 |
NaN |
NaN |
NaN |
SRG-OS-000071-GPOS-00039 |
NaN |
SV-217119r603262_rule |
CCI-000194 |
NaN |
NaN |
NaN |
NaN |
IA-5(a),IA-5(v) |
NaN |
NaN |
5.4.1 |
| CCE-83170-1 |
Set Password Strength Minimum Different Characters [ref] |
The pam_cracklib module's difok parameter controls requirements for usage of different characters during a password change. The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different. Make sure the difok parameter for the pam_cracklib module is configured to greater than or equal to 8. |
Requiring a minimum number of different characters during password changesensures that newly changed passwords should not resemble previouslycompromised ones. Note that passwords which are changed on compromisedsystems will still be compromised, however. |
medium |
content_rule_cracklib_accounts_password_pam_difok |
SLES-12-010190 |
NaN |
NaN |
NaN |
SRG-OS-000072-GPOS-00040 |
NaN |
SV-217121r603262_rule |
CCI-000195 |
NaN |
NaN |
NaN |
NaN |
IA-5(b),IA-5(v) |
NaN |
NaN |
NaN |
| CCE-83167-7 |
Set Password Strength Minimum Lowercase Characters [ref] |
The pam_cracklib module's lcredit= parameter controls requirements for usage of lowercase letters in a password. When set to a negative number, any password will be required to contain that many lowercase characters. When set to a positive number, pam_cracklib will grant +1 additional length credit for each lowercase character. Add lcredit=-1 after pam_cracklib.so to require use of a lowercase character in passwords. |
Requiring a minimum number of lowercase characters makes password guessingattacks more difficult by ensuring a larger search space. |
medium |
content_rule_cracklib_accounts_password_pam_lcredit |
SLES-12-010160 |
NaN |
NaN |
NaN |
SRG-OS-000070-GPOS-00038 |
NaN |
SV-217118r603262_rule |
CCI-000193 |
NaN |
NaN |
NaN |
NaN |
IA-5(a),IA-5(v) |
NaN |
NaN |
5.4.1 |
| CCE-83188-3 |
Set Password Minimum Length [ref] |
The pam_cracklib module's minlen parameter controls requirements for minimum characters required in a password. Add minlen=15 to set minimum password length requirements. |
Password length is one factor of several that helps to determinestrength and how long it takes to crack a password. Use of more characters ina password helps to exponentially increase the time and/or resourcesrequired to compromise the password. |
medium |
content_rule_cracklib_accounts_password_pam_minlen |
SLES-12-010250 |
NaN |
NaN |
NaN |
SRG-OS-000078-GPOS-00046 |
NaN |
SV-217127r603262_rule |
CCI-000205 |
NaN |
NaN |
NaN |
NaN |
IA-5(1)(a) |
NaN |
NaN |
5.4.1 |
| CCE-83169-3 |
Set Password Strength Minimum Special Characters [ref] |
The pam_cracklib module's ocredit= parameter controls requirements for usage of special (or ``other'') characters in a password. When set to a negative number, any password will be required to contain that many special characters. When set to a positive number, pam_cracklib will grant +1 additional length credit for each special character. Make sure the ocredit parameter for the pam_cracklib module is set to less than or equal to -1. For example, ocredit=-1. |
Requiring a minimum number of special characters makes password guessingattacks more difficult by ensuring a larger search space. |
medium |
content_rule_cracklib_accounts_password_pam_ocredit |
SLES-12-010180 |
NaN |
NaN |
NaN |
SRG-OS-000266-GPOS-00101 |
NaN |
SV-217120r603262_rule |
CCI-001619 |
NaN |
NaN |
NaN |
NaN |
IA-5(a),IA-5(v) |
NaN |
NaN |
5.4.1 |
| CCE-83174-3 |
Set Password Retry Limit [ref] |
The pam_cracklib module's retry parameter controls the maximum number of times to prompt the user for the password before returning with error. Make sure it is configured with a value that is no more than 3. For example, retry=1. |
To reduce opportunities for successful guesses and brute-force attacks. |
medium |
content_rule_cracklib_accounts_password_pam_retry |
SLES-12-010320 |
CM-6(b),CM-6.1 |
NaN |
NaN |
SRG-OS-000480-GPOS-00225 |
NaN |
SV-217134r603262_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
5.4.1 |
| CCE-83166-9 |
Set Password Strength Minimum Uppercase Characters [ref] |
The pam_cracklib module's ucredit= parameter controls requirements for usage of uppercase letters in a password. When set to a negative number, any password will be required to contain that many uppercase characters. When set to a positive number, pam_cracklib will grant +1 additional length credit for each uppercase character. Add ucredit=-1 after pam_cracklib.so to require use of an upper case character in passwords. |
Requiring a minimum number of uppercase characters makes password guessingattacks more difficult by ensuring a larger search space. |
medium |
content_rule_cracklib_accounts_password_pam_ucredit |
SLES-12-010150 |
NaN |
NaN |
NaN |
SRG-OS-000069-GPOS-00037 |
NaN |
SV-217117r603262_rule |
CCI-000192 |
NaN |
NaN |
NaN |
NaN |
IA-5(a),IA-5(v) |
NaN |
NaN |
5.4.1 |
| CCE-83029-9 |
Set Password Hashing Algorithm in /etc/login.defs [ref] |
In /etc/login.defs, add or correct the following line to ensure the system will use SHA-512 as the hashing algorithm: ENCRYPT_METHOD SHA512 |
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords.If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. Passwordsthat are encrypted with a weak algorithm are no more protected than if they are kept in plain text.Using a stronger hashing algorithm makes password cracking attacks more difficult. |
medium |
content_rule_set_password_hashing_algorithm_logindefs |
SLES-12-010210 |
CM-6(a) |
3.13.11,4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.4 |
PR.AC-1,PR.AC-6,PR.AC-7 |
SRG-OS-000073-GPOS-00041 |
NaN |
SV-217122r646689_rule |
CCI-000196 |
1,5,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10 |
IA-5(c),IA-5(1)(c),A.7.1.1,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1 |
BP28(R32) |
5.6.2.2,0418,1055,1402,Req-8.2.1,5.5.1.2 |
| CCE-83184-2 |
Set PAM's Password Hashing Algorithm [ref] |
The PAM system service can be configured to only store encrypted representations of passwords. In /etc/pam.d/common-password, the password section of the file controls which PAM modules execute during a password change. Set the pam_unix.so module in the password section to include the argument sha512, as shown below: password required pam_unix.so sha512 other arguments... This will help ensure when local users change their passwords, hashes for the new passwords will be generated using the SHA-512 algorithm. This is the default. |
Passwords need to be protected at all times, and encryption is the standardmethod for protecting passwords. If passwords are not encrypted, they canbe plainly read (i.e., clear text) and easily compromised. Passwords thatare encrypted with a weak algorithm are no more protected than if they arekepy in plain text.This setting ensures user and group account administration utilities areconfigured to store only encrypted representations of passwords.Additionally, the crypt_style configuration option ensures the useof a strong hashing algorithm that makes password cracking attacks moredifficult. |
medium |
content_rule_set_password_hashing_algorithm_systemauth |
SLES-12-010230 |
CM-6(a) |
3.13.11,4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.4 |
PR.AC-1,PR.AC-6,PR.AC-7 |
SRG-OS-000073-GPOS-00041,SRG-OS-000480-VMM-002000 |
NaN |
SV-217124r603262_rule |
CCI-000196 |
1,5,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10 |
IA-5(c),IA-5(1)(c),A.7.1.1,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1 |
BP28(R32) |
5.6.2.2,0418,1055,1402,Req-8.2.1 |
| CCE-83171-9 |
Set Password Hashing Rounds in /etc/login.defs [ref] |
In /etc/login.defs, ensure SHA_CRYPT_MIN_ROUNDS and SHA_CRYPT_MAX_ROUNDS has the minimum value of 5000. For example: SHA_CRYPT_MIN_ROUNDS 5000 SHA_CRYPT_MAX_ROUNDS 5000 Notice that if neither are set, they already have the default value of 5000. If either is set, they must have the minimum value of 5000. |
Passwords need to be protected at all times, and encryption is the standardmethod for protecting passwords. If passwords are not encrypted, they canbe plainly read (i.e., clear text) and easily compromised. Passwordsthat are encrypted with a weak algorithm are no more protected than ifthey are kept in plain text.Using more hashing rounds makes password cracking attacks more difficult. |
medium |
content_rule_set_password_hashing_min_rounds_logindefs |
SLES-12-010240 |
IA-7 |
NaN |
NaN |
SRG-OS-000073-GPOS-00041,SRG-OS-000120-GPOS-00061 |
NaN |
SV-217126r603262_rule |
CCI-000803 |
NaN |
NaN |
NaN |
NaN |
IA-5(1)(c),IA-5(1).1(v),IA-7.1 |
NaN |
NaN |
NaN |
| CCE-83149-5 |
Ensure PAM Displays Last Logon/Access Notification [ref] |
To configure the system to notify users of last logon/access using pam_lastlog, add or correct the pam_lastlog settings in /etc/pam.d/login to read as follows: session required pam_lastlog.so showfailed And make sure that the silent option is not set. |
Users need to be aware of activity that occurs regardingtheir account. Providing users with information regarding the numberof unsuccessful attempts that were made to login to their accountallows the user to determine if any unauthorized activity has occurredand gives them an opportunity to notify administrators. |
low |
content_rule_display_login_attempts |
SLES-12-010390 |
AC-9(1),CM-6(a) |
4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9 |
PR.AC-7 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217140r646709_rule |
CCI-000366 |
1,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.10,DSS06.10 |
A.9.2.1,A.9.2.4,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.5,SR,1.7,SR,1.8,SR,1.9 |
NaN |
5.5.2,0582,0584,05885,0586,0846,0957,Req-10.2.4 |
| CCE-83113-1 |
The PAM configuration should not be changed automatically [ref] |
Verify the SUSE operating system is configured to not overwrite Pluggable Authentication Modules (PAM) configuration on package changes. |
pam-config is a command line utility that automatically generatesa system PAM configuration as packages are installed, updated or removedfrom the system. pam-config removes configurations for PAM modulesand parameters that it does not know about. It may render ineffective PAMconfiguration by the system administrator and thus impact system security. |
medium |
content_rule_pam_disable_automatic_configuration |
SLES-12-010910 |
CM-6(b),CM-6.1(iv) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217189r646737_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83009-1 |
Check that vlock is installed to allow session locking [ref] |
The SUSE Linux Enterprise 12 operating system must have vlock installed to allow for session locking. The kbd package can be installed with the following command: $ sudo zypper install kbd |
A session lock is a temporary action taken when a user stops work andmoves away from the immediate physical vicinity of the informationsystem but does not want to log out because of the temporary nature ofthe absence.The session lock is implemented at the point where session activity canbe determined.Regardless of where the session lock is determined and implemented,once invoked, the session lock must remain in place until the userreauthenticates. No other activity aside from reauthentication mustunlock the system. |
medium |
content_rule_vlock_installed |
SLES-12-010070 |
AC-11(a),AC-11(b),AC-11(1) |
NaN |
NaN |
SRG-OS-000028-GPOS-00009 |
NaN |
SV-217108r603262_rule |
CCI-000056,CCI-000058,CCI-000060 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83177-6 |
Install Smart Card Packages For Multifactor Authentication [ref] |
Configure the operating system to implement multifactor authentication by installing the required package with the following command: The pam_pkcs11 package can be installed with the following command: $ sudo zypper install pam_pkcs11 The mozilla-nss package can be installed with the following command: $ sudo zypper install mozilla-nss The mozilla-nss-tools package can be installed with the following command: $ sudo zypper install mozilla-nss-tools The pcsc-ccid package can be installed with the following command: $ sudo zypper install pcsc-ccid The pcsc-lite package can be installed with the following command: $ sudo zypper install pcsc-lite The pcsc-tools package can be installed with the following command: $ sudo zypper install pcsc-tools The opensc package can be installed with the following command: $ sudo zypper install opensc The coolkey package can be installed with the following command: $ sudo zypper install coolkey |
Using an authentication device, such as a CAC or token that is separate fromthe information system, ensures that even if the information system iscompromised, that compromise will not affect credentials stored on theauthentication device.Multifactor solutions that require devices separate frominformation systems gaining access include, for example, hardware tokensproviding time-based or challenge-response authenticators and smart cards suchas the U.S. Government Personal Identity Verification card and the DoD CommonAccess Card. |
medium |
content_rule_install_smartcard_packages |
SLES-12-030500 |
CM-6(a) |
NaN |
NaN |
SRG-OS-000105-GPOS-00052,SRG-OS-000375-GPOS-00160,SRG-OS-000375-GPOS-00161,SRG-OS-000377-GPOS-00162 |
NaN |
SV-217299r603262_rule |
CCI-000765,CCI-001948,CCI-001953,CCI-001954 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83198-2 |
Configure Smart Card Certificate Authority Validation [ref] |
Configure the operating system to do certificate status checking for PKI authentication. Modify all of the cert_policy lines in /etc/pam_pkcs11/pam_pkcs11.conf to include ca like so: cert_policy = ca, ocsp_on, signature; |
Using an authentication device, such as a CAC or token that is separate fromthe information system, ensures that even if the information system iscompromised, that compromise will not affect credentials stored on theauthentication device.Multifactor solutions that require devices separate frominformation systems gaining access include, for example, hardware tokensproviding time-based or challenge-response authenticators and smart cards suchas the U.S. Government Personal Identity Verification card and the DoD CommonAccess Card. |
medium |
content_rule_smartcard_configure_ca |
SLES-12-030530 |
NaN |
NaN |
NaN |
SRG-OS-000066-GPOS-00034,SRG-OS-000384-GPOS-00167 |
NaN |
SV-217302r646769_rule |
CCI-000185,CCI-001991 |
NaN |
NaN |
NaN |
NaN |
IA-5,(2),IA-5(2)(a),IA-5,(2).1,IA-5(2)(d) |
NaN |
NaN |
NaN |
| CCE-83178-4 |
Configure Smart Card Certificate Status Checking [ref] |
Configure the operating system to do certificate status checking for PKI authentication. Modify all of the cert_policy lines in /etc/pam_pkcs11/pam_pkcs11.conf to include ocsp_on like so: cert_policy = ca, ocsp_on, signature; |
Using an authentication device, such as a CAC or token that is separate fromthe information system, ensures that even if the information system iscompromised, that compromise will not affect credentials stored on theauthentication device.Multifactor solutions that require devices separate frominformation systems gaining access include, for example, hardware tokensproviding time-based or challenge-response authenticators and smart cards suchas the U.S. Government Personal Identity Verification card and the DoD CommonAccess Card. |
medium |
content_rule_smartcard_configure_cert_checking |
SLES-12-030510 |
NaN |
NaN |
NaN |
SRG-OS-000375-GPOS-00160,SRG-OS-000376-GPOS-00161,SRG-OS-000377-GPOS-00162,SRG-OS-000384-GPOS-00167 |
NaN |
SV-217300r603262_rule |
CCI-001948,CCI-001953,CCI-001954 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83208-9 |
Enable Smart Card Logins in PAM [ref] |
This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management). Check that the pam_pkcs11.so option is configured in the etc/pam.d/common-auth file with the following command: # grep pam_pkcs11.so /etc/pam.d/common-auth auth sufficient pam_pkcs11.so For general information about enabling smart card authentication, consult the documentation at: https://www.suse.com/c/configuring-smart-card-authentication-suse-linux-enterprise/ |
Smart card login provides two-factor authentication stronger thanthat provided by a username and password combination. Smart cards leverage PKI(public key infrastructure) in order to provide and verify credentials.Using an authentication device, such as a CAC or token that is separatefrom the information system, ensures that even if the information system iscompromised, that compromise will not affect credentials stored on theauthentication device.Multifactor solutions that require devices separate from informationsystems gaining access include, for example, hardware tokens providingtime-based or challenge-response authenticators and smart cards such as theU.S. Government Personal Identity Verification card and the DoD CommonAccess Card. |
medium |
content_rule_smartcard_pam_enabled |
SLES-12-030520 |
IA-2(1),IA-2(1).1,IA-2(2),IA-2(2).1,IA-2(3),IA-2(3).1,IA-2(4),IA-2(4).1,IA-2(11),IA-2(12) |
NaN |
NaN |
SRG-OS-000068-GPOS-00036,SRG-OS-000105-GPOS-00052,SRG-OS-000106-GPOS-00053,SRG-OS-000107-GPOS-00054,SRG-OS-000108-GPOS-00055,SRG-OS-000375-GPOS-00160,SRG-OS-000375-GPOS-00161,SRG-OS-000375-GPOS-00162 |
NaN |
SV-217301r603262_rule |
CCI-000765,CCI-000766,CCI-000767,CCI-000768,CCI-000187,CCI-001948,CCI-001953,CCI-001954 |
NaN |
NaN |
NaN |
NaN |
IA-5(2),IA-5(2).1,IA-5(2)(c) |
NaN |
NaN |
NaN |
| CCE-83018-2 |
Disable Ctrl-Alt-Del Reboot Activation [ref] |
By default, SystemD will reboot the system if the Ctrl-Alt-Del key sequence is pressed. To configure the system to ignore the Ctrl-Alt-Del key sequence from the command line instead of rebooting the system, do either of the following: ln -sf /dev/null /etc/systemd/system/ctrl-alt-del.target or systemctl mask ctrl-alt-del.target Do not simply delete the /usr/lib/systemd/system/ctrl-alt-del.service file, as this file may be restored during future system updates. |
A locally logged-in user who presses Ctrl-Alt-Del, when at the console,can reboot the system. If accidentally pressed, as could happen inthe case of mixed OS environment, this can create the risk of short-termloss of availability of systems due to unintentional reboot. |
high |
content_rule_disable_ctrlaltdel_reboot |
SLES-12-010610 |
AC-6(1),CM-6(a) |
4.3.3.7.3,CIP-003-3,R5.1.1,CIP-003-3,R5.3,3.4.5 |
PR.AC-4,PR.DS-5 |
SRG-OS-000324-GPOS-00125,SRG-OS-000480-GPOS-00227 |
NaN |
SV-217159r646722_rule |
CCI-000366 |
3,5,12,13,14,15,16,18 |
NaN |
164.308(a)(1)(ii)(B),164.308(a)(7)(i),164.308(a)(7)(ii)(A),164.310(a)(1),164.310(a)(2)(i),164.310(a)(2)(ii),164.310(a)(2)(iii),164.310(b),164.310(c),164.310(d)(1),164.310(d)(2)(iii) |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
NaN |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2 |
| CCE-83051-3 |
Set Account Expiration Following Inactivity [ref] |
To specify the number of days after a password expires (which signifies inactivity) until an account is permanently disabled, add or correct the following line in /etc/default/useradd: INACTIVE=35 If a password is currently on the verge of expiration, then 35 day(s) remain(s) until the account is automatically disabled. However, if the password will not expire for another 60 days, then 60 days plus 35 day(s) could elapse until the account would be automatically disabled. See the useradd man page for more information. |
Disabling inactive accounts ensures that accounts which may nothave been responsibly removed are not available to attackerswho may have compromised their credentials. |
medium |
content_rule_account_disable_post_pw_expiration |
SLES-12-010340 |
AC-2(3),CM-6(a),IA-4(e) |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,3.5.6 |
PR.AC-1,PR.AC-4,PR.AC-6,PR.AC-7,DE.CM-1,DE.CM-3 |
SRG-OS-000118-GPOS-00060,SRG-OS-000003-VMM-000030,SRG-OS-000118-VMM-000590 |
NaN |
SV-217136r603262_rule |
CCI-000017,CCI-000795 |
1,3,5,7,8,12,13,14,15,16,18 |
NaN |
NaN |
DSS01.03,DSS03.05,DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10 |
A.6.1.2,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.12.4.1,A.12.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,6.2 |
NaN |
5.6.2.1.1,CIP-004-3,R2.2.2,CIP-004-3,R2.2.3,CIP-007-3,R.1.3,CIP-007-3,R5,CIP-007-3,R5.1.1,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3,Req-8.1.4,5.5.1.5 |
| CCE-83175-0 |
Never Automatically Remove or Disable Emergency Administrator Accounts [ref] |
Emergency accounts are privileged accounts that are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. Check to see if an emergency administrator account password or account expires with the following command: # sudo chage -l [Emergency_Administrator] Password expires:never If Password expires or Account expires is set to anything other than never, this is a finding. |
Emergency accounts are different from infrequently used accounts (i.e.,local logon accounts used by the organization's system administrators whennetwork or normal logon/access is not available). Infrequently usedaccounts are not subject to automatic termination dates. Emergency accountsare accounts created in response to crisis situations, usually for use bymaintenance personnel. The automatic expiration or disabling time periodmay be extended as needed until the crisis is resolved; however, it mustnot be extended indefinitely. A permanent account should be established forprivileged users who need long-term maintenance accounts.To address access requirements the SUSE operating system can be integratedwith enterprise-level authentication/access mechanisms that meet or exceedaccess control policy requirements. |
medium |
content_rule_account_emergency_admin |
SLES-12-010330 |
AC-2(2),AC-2(2).1(ii) |
NaN |
NaN |
SRG-OS-000123-GPOS-00064 |
NaN |
SV-217135r603262_rule |
CCI-001682 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83043-0 |
Assign Expiration Date to Temporary Accounts [ref] |
Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts. In the event temporary or emergency accounts are required, configure the system to terminate them after a documented time period. For every temporary and emergency account, run the following command to set an expiration date on it, substituting USER and YYYY-MM-DD appropriately: $ sudo chage -E YYYY-MM-DD USER YYYY-MM-DD indicates the documented expiration date for the account. For U.S. Government systems, the operating system must be configured to automatically terminate these types of accounts after a period of 72 hours. |
If temporary user accounts remain active when no longer needed or foran excessive period, these accounts may be used to gain unauthorized access.To mitigate this risk, automated termination of all temporary accountsmust be set upon account creation. |
medium |
content_rule_account_temp_expire_date |
SLES-12-010360 |
AC-2(2),AC-2(3),CM-6(a) |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4 |
PR.AC-1,PR.AC-4,PR.AC-6,DE.CM-1,DE.CM-3 |
SRG-OS-000123-GPOS-00064,SRG-OS-000002-GPOS-00002,SRG-OS-000002-VMM-000020,SRG-OS-000123-VMM-000620 |
NaN |
SV-217137r603262_rule |
CCI-000016,CCI-001682 |
1,3,5,7,8,12,13,14,15,16,18 |
NaN |
NaN |
DSS01.03,DSS03.05,DSS05.04,DSS05.05,DSS05.07,DSS06.03 |
A.6.1.2,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.12.4.1,A.12.4.3 |
SR,1.1,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,6.2 |
NaN |
NaN |
| CCE-83205-5 |
Policy Requires Immediate Change of Temporary Passwords [ref] |
Temporary passwords for SUSE Linux Enterprise 12 operating system logons must require an immediate change to a permanent password. Verify that a policy exists that ensures when a user is created, it is creating using a method that forces a user to change their password upon their next login. |
Without providing this capability, an account may be created without apassword. Nonrepudiation cannot be guaranteed once an account is created ifa user is not forced to change the temporary password upon initial logon.Temporary passwords are typically used to allow access when new accountsare created or passwords are changed. It is common practice foradministrators to create temporary passwords for user accounts that allowthe users to log on, yet force them to change the password once they havesuccessfully authenticated. |
medium |
content_rule_policy_temp_passwords_immediate_change |
SLES-12-010660 |
NaN |
NaN |
NaN |
SRG-OS-000380-GPOS-00165 |
NaN |
NaN |
CCI-002041 |
NaN |
NaN |
NaN |
NaN |
IA-5(1)(f) |
NaN |
NaN |
NaN |
| CCE-83050-5 |
Set Password Maximum Age [ref] |
To specify password maximum age for new accounts, edit the file /etc/login.defs and add or correct the following line: PASS_MAX_DAYS 60 A value of 180 days is sufficient for many environments. The DoD requirement is 60. The profile requirement is 60. |
Any password, no matter how complex, can eventually be cracked. Therefore, passwordsneed to be changed periodically. If the operating system does not limit the lifetimeof passwords and force users to change their passwords, there is the risk that theoperating system passwords could be compromised.Setting the password maximum age ensures users are required toperiodically change their passwords. Requiring shorter password lifetimesincreases the risk of users writing down the password in a convenientlocation subject to physical compromise. |
medium |
content_rule_accounts_maximum_age_login_defs |
SLES-12-010280 |
CM-6(a) |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.4,3.5.6 |
PR.AC-1,PR.AC-6,PR.AC-7 |
SRG-OS-000076-GPOS-00044 |
NaN |
SV-217130r646701_rule |
CCI-000199 |
1,5,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10 |
IA-5(f),IA-5(1)(d),A.7.1.1,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1 |
BP28(R18) |
5.6.2.1,0418,1055,1402,Req-8.2.4,5.5.1.2 |
| CCE-83049-7 |
Set Password Minimum Age [ref] |
To specify password minimum age for new accounts, edit the file /etc/login.defs and add or correct the following line: PASS_MIN_DAYS 7 A value of 1 day is considered sufficient for many environments. The DoD requirement is 1. The profile requirement is 7. |
Enforcing a minimum password lifetime helps to prevent repeated passwordchanges to defeat the password reuse or history enforcement requirement. Ifusers are allowed to immediately and continually change their password,then the password could be repeatedly changed in a short period of time todefeat the organization's policy regarding password reuse.Setting the minimum password age protects against users cycling back to afavorite password after satisfying the password reuse requirement. |
medium |
content_rule_accounts_minimum_age_login_defs |
SLES-12-010270 |
CM-6(a) |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.4,3.5.8 |
PR.AC-1,PR.AC-6,PR.AC-7 |
SRG-OS-000075-GPOS-00043 |
NaN |
SV-217129r646698_rule |
CCI-000198 |
1,5,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10 |
IA-5(f),IA-5(1)(d),A.7.1.1,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1 |
NaN |
5.6.2.1.1,0418,1055,1402,5.5.1.3 |
| CCE-83041-4 |
Set Existing Passwords Maximum Age [ref] |
Configure non-compliant accounts to enforce a 60-day maximum password lifetime restriction by running the following command: $ sudo chage -M 60 USER |
Any password, no matter how complex, can eventually be cracked. Therefore,passwords need to be changed periodically. If the operating system doesnot limit the lifetime of passwords and force users to change theirpasswords, there is the risk that the operating system passwords could becompromised. |
medium |
content_rule_accounts_password_set_max_life_existing |
SLES-12-010290 |
CM-6(a) |
NaN |
NaN |
SRG-OS-000076-GPOS-00044,SRG-OS-000076-VMM-000430 |
NaN |
SV-217131r646704_rule |
CCI-000199 |
NaN |
NaN |
NaN |
NaN |
IA-5(f),IA-5(1)(d) |
NaN |
NaN |
NaN |
| CCE-83042-2 |
Set Existing Passwords Minimum Age [ref] |
Configure non-compliant accounts to enforce a 24 hours/1 day minimum password lifetime by running the following command: $ sudo chage -m 1 USER |
Enforcing a minimum password lifetime helps to prevent repeated passwordchanges to defeat the password reuse or history enforcement requirement. Ifusers are allowed to immediately and continually change their password, thepassword could be repeatedly changed in a short period of time to defeat theorganization's policy regarding password reuse. |
medium |
content_rule_accounts_password_set_min_life_existing |
SLES-12-010260 |
CM-6(a) |
NaN |
NaN |
SRG-OS-000075-GPOS-00043,SRG-OS-000075-VMM000420 |
NaN |
SV-217128r646695_rule |
CCI-000198 |
NaN |
NaN |
NaN |
NaN |
IA-5(f),IA-5(1)(d) |
NaN |
NaN |
NaN |
| CCE-83038-0 |
Verify All Account Password Hashes are Shadowed with SHA512 [ref] |
Verify the operating system requires the shadow password suite configuration be set to encrypt interactive user passwords using a strong cryptographic hash. Check that the interactive user account passwords are using a strong password hash with the following command: # sudo cut -d: -f2 /etc/shadow $6$kcOnRq/5$NUEYPuyL.wghQwWssXRcLRFiiru7f5JPV6GaJhNC2aK5F3PZpE/BCCtwrxRc/AInKMNX3CdMw11m9STiql12f/ Password hashes ! or * indicate inactive accounts not available for logon and are not evaluated. If any interactive user password hash does not begin with $6, this is a finding. |
The system must use a strong hashing algorithm to store the password. Thesystem must use a sufficient number of hashing rounds to ensure the requiredlevel of entropy. |
medium |
content_rule_accounts_password_all_shadowed_sha512 |
SLES-12-010220 |
IA-7 |
NaN |
NaN |
SRG-OS-000073-GPOS-00041,SRG-OS-000120-GPOS-00061 |
NaN |
SV-217123r646692_rule |
CCI-000196,CCI-000803 |
NaN |
NaN |
NaN |
NaN |
IA-5(1)(c),IA-5(1).1(v),IA-7.1 |
NaN |
NaN |
NaN |
| CCE-83039-8 |
Prevent Login to Accounts With Empty Password [ref] |
If an account is configured for password authentication but does not have an assigned password, it may be possible to log into the account without authentication. Remove any instances of the nullok in password authentication configurations in /etc/pam.d/ to prevent logins with empty passwords. Note that this rule is not applicable for systems running within a container. Having user with empty password within a container is not considered a risk, because it should not be possible to directly login into a container anyway. |
If an account has an empty password, anyone could log in andrun commands with the privileges of that account. Accounts withempty passwords should never be used in operational environments. |
high |
content_rule_no_empty_passwords |
SLES-12-010231 |
CM-6(a) |
3.1.1,3.1.5,4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4 |
PR.AC-1,PR.AC-4,PR.AC-6,PR.AC-7,PR.DS-5 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217125r603262_rule |
CCI-000366 |
1,3,5,12,13,14,15,16,18 |
NaN |
164.308(a)(1)(ii)(B),164.308(a)(7)(i),164.308(a)(7)(ii)(A),164.310(a)(1),164.310(a)(2)(i),164.310(a)(2)(ii),164.310(a)(2)(iii),164.310(b),164.310(c),164.310(d)(1),164.310(d)(2)(iii) |
APO01.06,DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.02,DSS06.03,DSS06.10 |
IA-5(1)(a),IA-5(c),A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,5.2 |
NaN |
5.5.2,FIA_UAU.1,Req-8.2.3 |
| CCE-83020-8 |
Verify Only Root Has UID 0 [ref] |
If any account other than root has a UID of 0, this misconfiguration should be investigated and the accounts other than root should be removed or have their UID changed. If the account is associated with system commands or applications the UID should be changed to one greater than "0" but less than "1000." Otherwise assign a UID greater than "1000" that has not already been assigned. |
An account has root authority if it has a UID of 0. Multiple accountswith a UID of 0 afford more opportunity for potential intruders toguess a password for a privileged account. Proper configuration ofsudo is recommended to afford multiple system administratorsaccess to root privileges in an accountable manner. |
high |
content_rule_accounts_no_uid_except_zero |
SLES-12-010650 |
CM-6(b),CM-6.1(iv) |
3.1.1,3.1.5,4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,CIP-003-3,R5.1.1,CIP-003-3,R5.3 |
PR.AC-1,PR.AC-4,PR.AC-6,PR.AC-7,PR.DS-5 |
SRG-OS-000480-GPOS-00227 |
NaN |
NaN |
CCI-000366 |
1,3,5,12,13,14,15,16,18 |
NaN |
SV-217164r603262_rule |
APO01.06,DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.02,DSS06.03,DSS06.10 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,5.2 |
NaN |
CIP-004-3,R2.2.3,CIP-004-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.2,CIP-007-3,R5.2,CIP-007-3,R5.3.1,CIP-007-3,R5.3.2,CIP-007-3,R5.3.3,6.2.3 |
| CCE-83232-9 |
Ensure that System Accounts Do Not Run a Shell Upon Login [ref] |
Some accounts are not associated with a human user of the system, and exist to perform some administrative function. Should an attacker be able to log into these accounts, they should not be granted access to a shell. The login shell for each local account is stored in the last field of each line in /etc/passwd. System accounts are those user accounts with a user ID less than UID_MIN, where value of UID_MIN directive is set in /etc/login.defs configuration file. In the default configuration UID_MIN is set to 1000, thus system accounts are those user accounts with a user ID less than 1000. The user ID is stored in the third field. If any system account SYSACCT (other than root) has a login shell, disable it with the command: $ sudo usermod -s /sbin/nologin SYSACCTWarning: Do not perform the steps in this section on the root account. Doing so might cause the system to become inaccessible. |
Ensuring shells are not given to system accounts upon login makes it moredifficult for attackers to make use of system accounts. |
medium |
content_rule_no_shelllogin_for_systemaccounts |
SLES-12-010631 |
AC-6,CM-6(a),CM-6(b),CM-6.1(iv) |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4 |
PR.AC-1,PR.AC-4,PR.AC-6,DE.CM-1,DE.CM-3 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-237606r646781_rule |
CCI-000366 |
1,3,5,7,8,12,13,14,15,16,18 |
NaN |
NaN |
DSS01.03,DSS03.05,DSS05.04,DSS05.05,DSS05.07,DSS06.03 |
A.6.1.2,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.12.4.1,A.12.4.3 |
SR,1.1,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,6.2 |
NaN |
1491,5.5.2 |
| CCE-83196-6 |
Ensure All Accounts on the System Have Unique User IDs [ref] |
Change user IDs (UIDs), or delete accounts, so each has a unique name. |
To assure accountability and prevent unauthenticated access, interactive users must be identified and authenticated to prevent potential misuse and compromise of the system. |
medium |
content_rule_account_unique_id |
SLES-12-010640 |
IA-2,IA-2.1,IA-8 |
NaN |
NaN |
SRG-OS-000104-GPOS-00051,SRG-OS-000121-GPOS-00062,SRG-OS-000042-GPOS-00020 |
NaN |
SV-217163r603262_rule |
CCI-000764,CCI-000804 |
NaN |
NaN |
NaN |
NaN |
IA-8.1 |
NaN |
NaN |
6.2.14 |
| CCE-83052-1 |
Ensure the Default Umask is Set Correctly in login.defs [ref] |
To ensure the default umask controlled by /etc/login.defs is set properly, add or correct the UMASK setting in /etc/login.defs to read as follows: UMASK 027 |
The umask value influences the permissions assigned to files when they are created.A misconfigured umask value could result in files with excessive permissions that can be read andwritten to by unauthorized users. |
medium |
content_rule_accounts_umask_etc_login_defs |
SLES-12-010620 |
AC-6(1),CM-6(a) |
CIP-003-3,R5.1.1,CIP-003-3,R5.3,4.3.4.3.2,4.3.4.3.3 |
PR.IP-1,PR.IP-2 |
SRG-OS-000480-GPOS-00228 |
NaN |
SV-217161r603262_rule |
CCI-000366 |
3,9,11,18 |
NaN |
NaN |
APO13.01,BAI03.01,BAI03.02,BAI03.03,BAI10.01,BAI10.02,BAI10.03,BAI10.05 |
A.6.1.5,A.12.1.2,A.12.5.1,A.12.6.2,A.14.1.1,A.14.2.1,A.14.2.2,A.14.2.3,A.14.2.4,A.14.2.5 |
SR,7.6 |
BP28(R35) |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2,5.5.5 |
| CCE-83053-9 |
Ensure Home Directories are Created for New Users [ref] |
All local interactive user accounts, upon creation, should be assigned a home directory. Configure the operating system to assign home directories to all new local interactive users by setting the CREATE_HOME parameter in /etc/login.defs to yes as follows: CREATE_HOME yes |
If local interactive users are not assigned a valid home directory, there is no placefor the storage and control of files they should own. |
medium |
content_rule_accounts_have_homedir_login_defs |
SLES-12-010720 |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217171r603262_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83028-1 |
Ensure the Logon Failure Delay is Set Correctly in login.defs [ref] |
To ensure the logon failure delay controlled by /etc/login.defs is set properly, add or correct the FAIL_DELAY setting in /etc/login.defs to read as follows: FAIL_DELAY 4 |
Increasing the time between a failed authentication attempt and re-prompting toenter credentials helps to slow a single-threaded brute force attack. |
medium |
content_rule_accounts_logon_fail_delay |
SLES-12-010140 |
AC-7(b),CM-6(a) |
4.3.4.3.2,4.3.4.3.3 |
PR.IP-1 |
SRG-OS-000480-GPOS-00226 |
NaN |
SV-217116r603262_rule |
CCI-000366 |
3,9,11 |
NaN |
NaN |
BAI10.01,BAI10.02,BAI10.03,BAI10.05 |
A.12.1.2,A.12.5.1,A.12.6.2,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,7.6 |
NaN |
NaN |
| CCE-83065-3 |
Limit the Number of Concurrent Login Sessions Allowed Per User [ref] |
Limiting the number of allowed users and sessions per user can limit risks related to Denial of Service attacks. This addresses concurrent sessions for a single account and does not address concurrent sessions by a single user via multiple accounts. To set the number of concurrent sessions per user add the following line in /etc/security/limits.conf or a file under /etc/security/limits.d/: * hard maxlogins 1 |
Limiting simultaneous user logins can insulate the system from denial of serviceproblems caused by excessive logins. Automated login processes operating improperly ormaliciously may result in an exceptional number of simultaneous login sessions. |
low |
content_rule_accounts_max_concurrent_login_sessions |
SLES-12-010120 |
AC-10,CM-6(a) |
4.3.3.4 |
PR.AC-5 |
SRG-OS-000027-GPOS-00008,SRG-OS-000027-VMM-000080 |
NaN |
SV-217113r603262_rule |
CCI-000054 |
9,14,15,18 |
NaN |
NaN |
DSS01.05,DSS05.02 |
A.13.1.1,A.13.1.3,A.13.2.1,A.14.1.2,A.14.1.3 |
SR,3.1,SR,3.8 |
NaN |
5.5.2.2,CIP-007-3,R5.1,CIP-007-3,R5.1.2 |
| CCE-83011-7 |
Set Interactive Session Timeout [ref] |
Setting the TMOUT option in /etc/profile ensures that all user sessions will terminate based on inactivity. The TMOUT setting in /etc/profile.d/autologout.sh should read as follows: TMOUT=900 readonly TMOUT export TMOUT |
Terminating an idle session within a short time period reducesthe window of opportunity for unauthorized personnel to take control of amanagement session enabled on the console or console port that has beenleft unattended. |
medium |
content_rule_accounts_tmout |
SLES-12-010090 |
AC-11(a) |
3.1.11,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9 |
PR.AC-7 |
SRG-OS-000163-GPOS-00072,SRG-OS-000029-GPOS-00010,SRG-OS-000163-VMM-000700,SRG-OS-000279-VMM-001010 |
NaN |
SV-217110r603262_rule |
CCI-000057,CCI-001133,CCI-002361 |
1,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.10,DSS06.10 |
A.9.2.1,A.9.2.4,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.5,SR,1.7,SR,1.8,SR,1.9 |
BP28(R29) |
CIP-004-3,R2.2.3,CIP-007-3,R5.1,CIP-007-3,R5.2,CIP-007-3,R5.3.1,CIP-007-3,R5.3.2,CIP-007-3,R5.3.3,FMT_MOF_EXT.1,5.5.4 |
| CCE-83099-2 |
User Initialization Files Must Not Run World-Writable Programs [ref] |
Set the mode on files being executed by the user initialization files with the following command: $ sudo chmod 0755 FILE |
If user start-up files execute world-writable programs, especially inunprotected directories, they could be maliciously modified to destroy userfiles or otherwise compromise the system at the user level. If the system iscompromised at the user level, it is easier to elevate privileges to eventuallycompromise the system at the root and network level. |
medium |
content_rule_accounts_user_dot_no_world_writable_programs |
SLES-12-010780 |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217177r646731_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83098-4 |
Ensure that Users Path Contains Only Local Directories [ref] |
Ensure that all interactive user initialization files executable search path statements do not contain statements that will reference a working directory other than the users home directory. |
The executable search path (typically the PATH environment variable) contains alist of directories for the shell to search to find executables. If this pathincludes the current working directory (other than the users home directory),executables in these directories may be executed instead of system commands.This variable is formatted as a colon-separated list of directories. If there isan empty entry, such as a leading or trailing colon or two consecutive colons,this is interpreted as the current working directory. If deviations from thedefault system search path for the local interactive user are required, theymust be documented with the Information System Security Officer (ISSO). |
medium |
content_rule_accounts_user_home_paths_only |
SLES-12-010770 |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217176r603262_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83075-2 |
All Interactive Users Must Have A Home Directory Defined [ref] |
Assign home directories to all interactive users that currently do not have a home directory assigned. |
If local interactive users are not assigned a valid home directory, there is noplace for the storage and control of files they should own. |
medium |
content_rule_accounts_user_interactive_home_directory_defined |
SLES-12-010710 |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217170r646728_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83074-5 |
All Interactive Users Home Directories Must Exist [ref] |
Create home directories to all interactive users that currently do not have a home directory assigned. Use the following commands to create the user home directory assigned in /etc/passwd: $ sudo mkdir /home/USER |
If a local interactive user has a home directory defined that does not exist,the user may be given access to the / directory as the current working directoryupon logon. This could create a Denial of Service because the user would not beable to access their logon configuration files, and it may give them visibilityto system files they normally would not be able to access. |
medium |
content_rule_accounts_user_interactive_home_directory_exists |
SLES-12-010730 |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217172r603885_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
6.2.5 |
| CCE-83096-8 |
All Interactive User Home Directories Must Be Group-Owned By The Primary User [ref] |
Change the group owner of interactive users home directory to the group found in /etc/passwd. To change the group owner of interactive users home directory, use the following command: $ sudo chgrp USER_GROUP /home/USER |
If the Group Identifier (GID) of a local interactive users home directory isnot the same as the primary GID of the user, this would allow unauthorizedaccess to the users files, and users that share the same group may not beable to access files that they legitimately should. |
medium |
content_rule_file_groupownership_home_directories |
SLES-12-010750 |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217174r603889_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83097-6 |
Ensure All User Initialization Files Have Mode 0740 Or Less Permissive [ref] |
Set the mode of the user initialization files to 0740 with the following command: $ sudo chmod 0740 /home/USER/.INIT_FILE |
Local initialization files are used to configure the user's shell environmentupon logon. Malicious modification of these files could compromise accounts uponlogon. |
medium |
content_rule_file_permission_user_init_files |
SLES-12-010760 |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217175r603262_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83076-0 |
All Interactive User Home Directories Must Have mode 0750 Or Less Permissive [ref] |
Change the mode of interactive users home directories to 0750. To change the mode of interactive users home directory, use the following command: $ sudo chmod 0750 /home/USER |
Excessive permissions on local interactive user home directories may allowunauthorized access to user files by other users. |
medium |
content_rule_file_permissions_home_directories |
SLES-12-010740 |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217173r603887_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
6.2.6 |
| CCE-83106-5 |
Record Events that Modify the System's Discretionary Access Controls - chmod [ref] |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_chmod |
SLES-12-020460 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000466-GPOS-00210,SRG-OS-000458-GPOS-00203,SRG-OS-000458-VMM-001810,SRG-OS-000474-VMM-001940 |
NaN |
SV-217227r603262_rule |
CCI-000126,CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.5.5,4.1.9 |
| CCE-83137-0 |
Record Events that Modify the System's Discretionary Access Controls - chown [ref] |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_chown |
SLES-12-020420 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000466-GPOS-00210,SRG-OS-000458-GPOS-00203,SRG-OS-000474-GPOS-00219,SRG-OS-000458-VMM-001810,SRG-OS-000474-VMM-001940 |
NaN |
SV-217223r603262_rule |
CCI-000126,CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.5.5,4.1.9 |
| CCE-83133-9 |
Record Events that Modify the System's Discretionary Access Controls - fchmod [ref] |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_fchmod |
SLES-12-020470 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000466-GPOS-00210,SRG-OS-000458-GPOS-00203,SRG-OS-000458-VMM-001810,SRG-OS-000474-VMM-001940 |
NaN |
SV-217228r603262_rule |
CCI-000126,CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.5.5,4.1.9 |
| CCE-83132-1 |
Record Events that Modify the System's Discretionary Access Controls - fchmodat [ref] |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_fchmodat |
SLES-12-020480 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000466-GPOS-00210,SRG-OS-000458-GPOS-00203,SRG-OS-000458-VMM-001810,SRG-OS-000474-VMM-001940 |
NaN |
SV-217229r603262_rule |
CCI-000126,CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.5.5,4.1.9 |
| CCE-83136-2 |
Record Events that Modify the System's Discretionary Access Controls - fchown [ref] |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_fchown |
SLES-12-020430 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000466-GPOS-00210,SRG-OS-000458-GPOS-00203,SRG-OS-000474-GPOS-00219,SRG-OS-000458-VMM-001810,SRG-OS-000474-VMM-001940 |
NaN |
SV-217224r603262_rule |
CCI-000126,CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.5.5,4.1.9 |
| CCE-83134-7 |
Record Events that Modify the System's Discretionary Access Controls - fchownat [ref] |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_fchownat |
SLES-12-020450 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000466-GPOS-00210,SRG-OS-000458-GPOS-00203,SRG-OS-000474-GPOS-00219,SRG-OS-000458-VMM-001810,SRG-OS-000474-VMM-001940 |
NaN |
SV-217226r603262_rule |
CCI-000126,CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.5.5,4.1.9 |
| CCE-83138-8 |
Record Events that Modify the System's Discretionary Access Controls - fremovexattr [ref] |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_fremovexattr |
SLES-12-020410 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000462-GPOS-00206,SRG-OS-000463-GPOS-00207,SRG-OS-000471-GPOS-00215,SRG-OS-000474-GPOS-00219,SRG-OS-000466-GPOS-00210,SRG-OS-000064-GPOS-00033,SRG-OS-000458-VMM-001810,SRG-OS-000474-VMM-001940 |
NaN |
SV-217222r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.5.5,4.1.9 |
| CCE-83141-2 |
Record Events that Modify the System's Discretionary Access Controls - fsetxattr [ref] |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_fsetxattr |
SLES-12-020380 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000462-GPOS-00206,SRG-OS-000463-GPOS-00207,SRG-OS-000468-GPOS-00212,SRG-OS-000471-GPOS-00215,SRG-OS-000474-GPOS-00219,SRG-OS-000064-GPOS-00033,SRG-OS-000458-VMM-001810,SRG-OS-000474-VMM-001940 |
NaN |
SV-217219r603262_rule |
CCI-000126,CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.5.5,4.1.9 |
| CCE-83135-4 |
Record Events that Modify the System's Discretionary Access Controls - lchown [ref] |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_lchown |
SLES-12-020440 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000466-GPOS-00210,SRG-OS-000458-GPOS-00203,SRG-OS-000474-GPOS-00219,SRG-OS-000458-VMM-001810,SRG-OS-000474-VMM-001940 |
NaN |
SV-217225r603262_rule |
CCI-000126,CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.5.5,4.1.9 |
| CCE-83139-6 |
Record Events that Modify the System's Discretionary Access Controls - lremovexattr [ref] |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_lremovexattr |
SLES-12-020400 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000462-GPOS-00206,SRG-OS-000463-GPOS-00207,SRG-OS-000468-GPOS-00212,SRG-OS-000471-GPOS-00215,SRG-OS-000474-GPOS-00219,SRG-OS-000466-GPOS-00210,SRG-OS-000064-GPOS-00033,SRG-OS-000458-VMM-001810,SRG-OS-000474-VMM-001940 |
NaN |
SV-217221r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.5.5,4.1.9 |
| CCE-83140-4 |
Record Events that Modify the System's Discretionary Access Controls - removexattr [ref] |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_removexattr |
SLES-12-020390 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000462-GPOS-00206,SRG-OS-000463-GPOS-00207,SRG-OS-000468-GPOS-00212,SRG-OS-000471-GPOS-00215,SRG-OS-000474-GPOS-00219,SRG-OS-000466-GPOS-00210,SRG-OS-000064-GPOS-00033,SRG-OS-000458-VMM-001810,SRG-OS-000474-VMM-001940 |
NaN |
SV-217220r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.5.5,4.1.9 |
| CCE-83142-0 |
Record Events that Modify the System's Discretionary Access Controls - setxattr [ref] |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_setxattr |
SLES-12-020370 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000458-GPOS-00203,SRG-OS-000458-VMM-001810,SRG-OS-000474-VMM-001940 |
NaN |
SV-217218r603262_rule |
CCI-000126,CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.5.5,4.1.9 |
| CCE-83218-8 |
Record Events that Modify the System's Discretionary Access Controls - umount [ref] |
At a minimum, the audit system should collect file system umount changes. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S umount -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S umount -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_umount |
SLES-12-020300 |
AU-3,AU-3.1,AU-12.1(ii),AU-12(a),AU-12.1(iv),AU-12(c),MA-4(1)(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 |
NaN |
SV-217214r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83219-6 |
Record Events that Modify the System's Discretionary Access Controls - umount2 [ref] |
At a minimum, the audit system should collect file system umount2 changes. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S umount2 -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S umount2 -F auid>=1000 -F auid!=unset -F key=perm_mod If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S umount2 -F auid>=1000 -F auid!=unset -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S umount2 -F auid>=1000 -F auid!=unset -F key=perm_modWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
The changing of file permissions could indicate that a user is attempting togain access to information that would otherwise be disallowed. Auditing DAC modificationscan facilitate the identification of patterns of abuse among both authorized andunauthorized users. |
medium |
content_rule_audit_rules_dac_modification_umount2 |
SLES-12-020300 |
AU-3,AU-3.1,AU-12.1(ii),AU-12(a),AU-12.1(iv),AU-12(c),MA-4(1)(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 |
NaN |
SV-217214r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83190-9 |
Record Any Attempts to Run chacl [ref] |
At a minimum, the audit system should collect any execution attempt of the chacl command for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file: -a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Without generating audit records that are specific to the security andmission needs of the organization, it would be difficult to establish,correlate, and investigate the events relating to an incident or identifythose responsible for one.Audit records can be generated from various components within theinformation system (e.g., module or policy filter). |
medium |
content_rule_audit_rules_execution_chacl |
SLES-12-020620 |
AU-3,AU-3.1,AU-12.1(ii),AU-12(a),AU-12.1(iv),AU-12(c),MA-4(1)(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000466-GPOS-00210 |
NaN |
SV-217243r603929_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83214-7 |
Record Any Attempts to Run chmod [ref] |
At a minimum, the audit system should collect any execution attempt of the chmod command for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/chmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file: -a always,exit -F path=/usr/bin/chmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Without generating audit records that are specific to the security andmission needs of the organization, it would be difficult to establish,correlate, and investigate the events relating to an incident or identifythose responsible for one.Audit records can be generated from various components within theinformation system (e.g., module or policy filter). |
medium |
content_rule_audit_rules_execution_chmod |
SLES-12-020600 |
AU-3,AU-3.1,AU-12.1(ii),AU-12(a),AU-12.1(iv),AU-12(c),MA-4(1)(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 |
NaN |
SV-217241r603923_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83189-1 |
Record Any Attempts to Run setfacl [ref] |
At a minimum, the audit system should collect any execution attempt of the setfacl command for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file: -a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Without generating audit records that are specific to the security andmission needs of the organization, it would be difficult to establish,correlate, and investigate the events relating to an incident or identifythose responsible for one.Audit records can be generated from various components within theinformation system (e.g., module or policy filter). |
medium |
content_rule_audit_rules_execution_setfacl |
SLES-12-020610 |
AU-3,AU-3.1,AU-12.1(ii),AU-12(a),AU-12.1(iv),AU-12(c),MA-4(1)(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 |
NaN |
SV-217242r603926_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83215-4 |
Record Any Attempts to Run chcon [ref] |
At a minimum, the audit system should collect any execution attempt of the chcon command for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file: -a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_execution_chcon |
SLES-12-020630 |
AU-3,AU-3.1,AU-12.1(ii),AU-12(a),AU-12.1(iv),AU-12(c),MA-4(1)(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000468-GPOS-00212,SRG-OS-000471-GPOS-00215,SRG-OS-000463-GPOS-00207,SRG-OS-000465-GPOS-00209,SRG-OS-000463-VMM-001850 |
NaN |
SV-217244r603932_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c |
| CCE-83216-2 |
Record Any Attempts to Run rm [ref] |
At a minimum, the audit system should collect any execution attempt of the rm command for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/rm -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file: -a always,exit -F path=/usr/bin/rm -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Without generating audit records that are specific to the security andmission needs of the organization, it would be difficult to establish,correlate, and investigate the events relating to an incident or identifythose responsible for one.Audit records can be generated from various components within theinformation system (e.g., module or policy filter). |
medium |
content_rule_audit_rules_execution_rm |
SLES-12-020640 |
AU-3,AU-3.1,AU-12.1(ii),AU-12(a),AU-12.1(iv),AU-12(c),MA-4(1)(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 |
NaN |
SV-217245r603935_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83092-7 |
Record Unsuccessful Access Attempts to Files - creat [ref] |
At a minimum, the audit system should collect unauthorized file accesses for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditingthese events could serve as evidence of potential system compromise. |
medium |
content_rule_audit_rules_unsuccessful_file_modification_creat |
SLES-12-020520 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205,SRG-OS-000458-VMM-001810,SRG-OS-000461-VMM-001830 |
NaN |
SV-217233r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.2.4,Req-10.2.1,4.1.10 |
| CCE-83091-9 |
Record Unsuccessful Access Attempts to Files - ftruncate [ref] |
At a minimum, the audit system should collect unauthorized file accesses for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S ftruncate -F exiu=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditingthese events could serve as evidence of potential system compromise. |
medium |
content_rule_audit_rules_unsuccessful_file_modification_ftruncate |
SLES-12-020510 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205,SRG-OS-000458-VMM-001810,SRG-OS-000461-VMM-001830 |
NaN |
SV-217232r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.2.4,Req-10.2.1,4.1.10 |
| CCE-83131-3 |
Record Unsuccessful Access Attempts to Files - open [ref] |
At a minimum, the audit system should collect unauthorized file accesses for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditingthese events could serve as evidence of potential system compromise. |
medium |
content_rule_audit_rules_unsuccessful_file_modification_open |
SLES-12-020490 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205,SRG-OS-000458-VMM-001810,SRG-OS-000461-VMM-001830 |
NaN |
SV-217230r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.2.4,Req-10.2.1,4.1.10 |
| CCE-83094-3 |
Record Unsuccessful Access Attempts to Files - open_by_handle_at [ref] |
At a minimum, the audit system should collect unauthorized file accesses for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditingthese events could serve as evidence of potential system compromise. |
medium |
content_rule_audit_rules_unsuccessful_file_modification_open_by_handle_at |
SLES-12-020540 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205,SRG-OS-000458-VMM-001810,SRG-OS-000461-VMM-001830 |
NaN |
SV-217235r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.2.4,Req-10.2.1 |
| CCE-83093-5 |
Record Unsuccessful Access Attempts to Files - openat [ref] |
At a minimum, the audit system should collect unauthorized file accesses for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditingthese events could serve as evidence of potential system compromise. |
medium |
content_rule_audit_rules_unsuccessful_file_modification_openat |
SLES-12-020530 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205,SRG-OS-000458-VMM-001810,SRG-OS-000461-VMM-001830 |
NaN |
SV-217234r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.2.4,Req-10.2.1,4.1.10 |
| CCE-83085-1 |
Record Unsuccessful Access Attempts to Files - truncate [ref] |
At a minimum, the audit system should collect unauthorized file accesses for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file: -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessWarning: Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient. |
Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditingthese events could serve as evidence of potential system compromise. |
medium |
content_rule_audit_rules_unsuccessful_file_modification_truncate |
SLES-12-020500 |
AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000064-GPOS-00033,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205,SRG-OS-000458-VMM-001810,SRG-OS-000461-VMM-001830 |
NaN |
SV-217231r603262_rule |
CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.2.4,Req-10.2.1,4.1.10 |
| CCE-83128-9 |
Ensure auditd Collects Information on Kernel Module Unloading - delete_module [ref] |
To capture kernel module unloading events, use following line, setting ARCH to either b32 for 32-bit system, or having two lines for both b32 and b64 in case your system is 64-bit: -a always,exit -F arch=ARCH -S delete_module -F key=modules Place to add the line depends on a way auditd daemon is configured. If it is configured to use the augenrules program (the default), add the line to a file with suffix .rules in the directory /etc/audit/rules.d. If the auditd daemon is configured to use the auditctl utility, add the line to file /etc/audit/audit.rules. |
The removal of kernel modules can be used to alter the behavior ofthe kernel and potentially introduce malicious code into kernel space. It is importantto have an audit trail of modules that have been introduced into the kernel. |
medium |
content_rule_audit_rules_kernel_module_loading_delete |
SLES-12-020730 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000471-GPOS-00216,SRG-OS-000477-GPOS-00222,SRG-OS-000477-VMM-001970 |
NaN |
SV-217254r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.2.7,4.1.16 |
| CCE-83129-7 |
Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module [ref] |
If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d to capture kernel module loading and unloading events, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S finit_module -F key=modules If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file in order to capture kernel module loading and unloading events, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S finit_module -F key=modules |
The addition/removal of kernel modules can be used to alter the behavior ofthe kernel and potentially introduce malicious code into kernel space. It is importantto have an audit trail of modules that have been introduced into the kernel. |
medium |
content_rule_audit_rules_kernel_module_loading_finit |
SLES-12-020740 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000471-GPOS-00216,SRG-OS-000477-GPOS-00222,SRG-OS-000477-VMM-001970 |
NaN |
SV-217255r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.2.7 |
| CCE-83130-5 |
Ensure auditd Collects Information on Kernel Module Loading - init_module [ref] |
To capture kernel module loading events, use following line, setting ARCH to either b32 for 32-bit system, or having two lines for both b32 and b64 in case your system is 64-bit: -a always,exit -F arch=ARCH -S init_module -F key=modules Place to add the line depends on a way auditd daemon is configured. If it is configured to use the augenrules program (the default), add the line to a file with suffix .rules in the directory /etc/audit/rules.d. If the auditd daemon is configured to use the auditctl utility, add the line to file /etc/audit/audit.rules. |
The addition of kernel modules can be used to alter the behavior ofthe kernel and potentially introduce malicious code into kernel space. It is importantto have an audit trail of modules that have been introduced into the kernel. |
medium |
content_rule_audit_rules_kernel_module_loading_init |
SLES-12-020750 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000471-GPOS-00216,SRG-OS-000477-GPOS-00222,SRG-OS-000477-VMM-001970 |
NaN |
SV-217256r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.2.7,4.1.16 |
| CCE-83192-5 |
Record Attempts to Alter Logon and Logout Events - faillog [ref] |
The audit system already collects login information for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d in order to watch for attempted manual edits of files involved in storing logon events: -w /var/log/faillog -p wa -k logins If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file in order to watch for unattempted manual edits of files involved in storing logon events: -w /var/log/faillog -p wa -k logins |
Manual editing of these files may indicate nefarious activity, suchas an attacker attempting to remove evidence of an intrusion. |
medium |
content_rule_audit_rules_login_events_faillog |
SLES-12-020760 |
AU-3,AU-12(a),AU-12(c),MA-4(1)(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015 |
NaN |
SV-217257r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83108-1 |
Record Attempts to Alter Logon and Logout Events - lastlog [ref] |
The audit system already collects login information for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d in order to watch for attempted manual edits of files involved in storing logon events: -w /var/log/lastlog -p wa -k logins If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file in order to watch for unattempted manual edits of files involved in storing logon events: -w /var/log/lastlog -p wa -k logins |
Manual editing of these files may indicate nefarious activity, suchas an attacker attempting to remove evidence of an intrusion. |
medium |
content_rule_audit_rules_login_events_lastlog |
SLES-12-020660 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000473-GPOS-00218,SRG-OS-000470-GPOS-00214,SRG-OS-000473-VMM-001930,SRG-OS-000470-VMM-001900 |
NaN |
SV-217247r603262_rule |
CCI-000126,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.2.3,4.1.7 |
| CCE-83107-3 |
Record Attempts to Alter Logon and Logout Events - tallylog [ref] |
The audit system already collects login information for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d in order to watch for attempted manual edits of files involved in storing logon events: -w /var/log/tallylog -p wa -k logins If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file in order to watch for unattempted manual edits of files involved in storing logon events: -w /var/log/tallylog -p wa -k logins |
Manual editing of these files may indicate nefarious activity, suchas an attacker attempting to remove evidence of an intrusion. |
medium |
content_rule_audit_rules_login_events_tallylog |
SLES-12-020650 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000392-GPOS-00172,SRG-OS-000470-GPOS-00214,SRG-OS-000473-GPOS-00218,SRG-OS-000473-VMM-001930,SRG-OS-000470-VMM-001900 |
NaN |
SV-217246r603262_rule |
CCI-000172,CCI-002884,CCI-000126 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c,Req-10.2.3 |
| CCE-83110-7 |
Ensure auditd Collects Information on the Use of Privileged Commands - chage [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_chage |
SLES-12-020690 |
AC-2(4),AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000468-GPOS-00212,SRG-OS-000471-GPOS-00215,SRG-OS-000471-VMM-001910 |
NaN |
SV-217250r603944_rule |
CCI-000135,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R2.2.2,CIP-004-3,R2.2.3,CIP-007-3,R.1.3,CIP-007-3,R5,CIP-007-3,R5.1.1,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3 |
| CCE-83187-5 |
Ensure auditd Collects Information on the Use of Privileged Commands - chfn [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/chfn -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/chfn -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Without generating audit records that are specific to the security andmission needs of the organization, it would be difficult to establish,correlate, and investigate the events relating to an incident or identifythose responsible for one.Audit records can be generated from various components within theinformation system (e.g., module or policy filter). |
medium |
content_rule_audit_rules_privileged_commands_chfn |
SLES-12-020280 |
AU-3,AU-12(a),AU-12(c),MA-4(1)(a) |
NaN |
NaN |
NaN |
NaN |
SV-217212r603902_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83163-6 |
Ensure auditd Collects Information on the Use of Privileged Commands - chsh [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_chsh |
SLES-12-020580 |
AC-2(4),AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000471-VMM-001910 |
NaN |
SV-217239r603920_rule |
CCI-000130,CCI-000135,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R2.2.2,CIP-004-3,R2.2.3,CIP-007-3,R.1.3,CIP-007-3,R5,CIP-007-3,R5.1.1,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3 |
| CCE-83126-3 |
Ensure auditd Collects Information on the Use of Privileged Commands - crontab [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_crontab |
SLES-12-020710 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000471-VMM-001910 |
NaN |
SV-217252r603950_rule |
CCI-000135,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4 |
| CCE-83161-0 |
Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_gpasswd |
SLES-12-020560 |
AC-2(4),AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000471-VMM-001910 |
NaN |
SV-217237r603914_rule |
CCI-000135,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R2.2.2,CIP-004-3,R2.2.3,CIP-007-3,R.1.3,CIP-007-3,R5,CIP-007-3,R5.1.1,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3,FAU_GEN.1.1.c |
| CCE-83207-1 |
Ensure auditd Collects Information on the Use of Privileged Commands - kmod [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -w /usr/bin/kmod -p x -k modules If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -w /usr/bin/kmod -p x -k modules |
Without generating audit records that are specific to the security andmission needs of the organization, it would be difficult to establish,correlate, and investigate the events relating to an incident or identifythose responsible for one.Audit records can be generated from various components within theinformation system (e.g., module or policy filter). |
medium |
content_rule_audit_rules_privileged_commands_kmod |
SLES-12-020360 |
AU-3,AU-3.1,AU-12(a),AU-12.1(ii),AU-12.1(iv)AU-12(c),MA-4(1)(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000471-GPOS-00216,SRG-OS-000477-GPOS-00222 |
NaN |
SV-217217r603262_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83145-3 |
Ensure auditd Collects Information on the Use of Privileged Commands - mount [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_mount |
SLES-12-020290 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-VMM-001910 |
NaN |
SV-217213r603262_rule |
CCI-000135,CCI-000172,CCI-002884 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
FAU_GEN.1.1.c |
| CCE-83162-8 |
Ensure auditd Collects Information on the Use of Privileged Commands - newgrp [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_newgrp |
SLES-12-020570 |
AC-2(4),AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000471-VMM-001910 |
NaN |
SV-217238r603917_rule |
CCI-000130,CCI-000169,CCI-000135,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R2.2.2,CIP-004-3,R2.2.3,CIP-007-3,R.1.3,CIP-007-3,R5,CIP-007-3,R5.1.1,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3,FAU_GEN.1.1.c |
| CCE-83127-1 |
Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_pam_timestamp_check |
SLES-12-020720 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000471-VMM-001910 |
NaN |
SV-217253r603953_rule |
CCI-000135,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4 |
| CCE-83193-3 |
Ensure auditd Collects Information on the Use of Privileged Commands - passmass [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/passmass -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/passmass -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_passmass |
SLES-12-020670 |
AU-3,AU-12(a),AU-12(c),MA-4(1)(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015 |
NaN |
SV-217248r603938_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83160-2 |
Ensure auditd Collects Information on the Use of Privileged Commands - passwd [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_passwd |
SLES-12-020550 |
AC-2(4),AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000471-VMM-001910 |
NaN |
SV-217236r603911_rule |
CCI-000135,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R2.2.2,CIP-004-3,R2.2.3,CIP-007-3,R.1.3,CIP-007-3,R5,CIP-007-3,R5.1.1,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3,FAU_GEN.1.1.c |
| CCE-83199-0 |
Record Any Attempts to Run ssh-agent [ref] |
At a minimum, the audit system should collect any execution attempt of the ssh-agent command for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file: -a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
Without generating audit records that are specific to the security andmission needs of the organization, it would be difficult to establish,correlate, and investigate the events relating to an incident or identifythose responsible for one.Audit records can be generated from various components within theinformation system (e.g., module or policy filter). |
medium |
content_rule_audit_rules_privileged_commands_ssh_agent |
SLES-12-020310 |
AU-3,AU-3.1,AU-12(a),AU-12(c),AU-12.1(a),AU-12.1(ii),AU-12.1(iv),MA-4(1)(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 |
NaN |
SV-217215r603905_rule |
CCI-000130,CCI-000169,CCI-000172 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83159-4 |
Ensure auditd Collects Information on the Use of Privileged Commands - ssh-keysign [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/lib/ssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/lib/ssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_ssh_keysign |
SLES-12-020320 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000471-VMM-001910 |
NaN |
SV-217216r603908_rule |
CCI-000135,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c |
| CCE-83143-8 |
Ensure auditd Collects Information on the Use of Privileged Commands - su [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_su |
SLES-12-020250 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000064-GPOS-0003,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000466-GPOS-00210,SRG-OS-000471-VMM-001910 |
NaN |
SV-217210r603896_rule |
CCI-000130,CCI-000135,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c |
| CCE-83144-6 |
Ensure auditd Collects Information on the Use of Privileged Commands - sudo [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_sudo |
SLES-12-020260 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000466-GPOS-00210,SRG-OS-000471-VMM-001910 |
NaN |
SV-217211r603899_rule |
CCI-000130,CCI-000135,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
BP28(R19) |
4.4.2.1,4.4.2.2,4.4.2.4,FAU_GEN.1.1.c |
| CCE-83158-6 |
Ensure auditd Collects Information on the Use of Privileged Commands - umount [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_umount |
SLES-12-020300 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215,SRG-OS-000471-VMM-001910 |
NaN |
SV-217214r603262_rule |
CCI-000135,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4 |
| CCE-83109-9 |
Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_unix_chkpwd |
SLES-12-020680 |
AC-2(4),AC-6(9),AU-2(d),AU-3,AU-3.1,AU-12(a),AU-12(c),AU-12.1(ii),AU-12.1(iv),CM-6(a),MA-4(1)(a) |
3.1.7,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
ID.SC-4,PR.PT-1,DE.CM-1,DE.CM-3,DE.CM-7 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000471-VMM-001910 |
NaN |
SV-217249r603941_rule |
CCI-000130,CCI-000135,CCI-000169,CCI-000172,CCI-002884 |
1,2,3,5,6,7,8,9,12,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,BAI03.05,DSS01.03,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,6.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R2.2.2,CIP-004-3,R2.2.3,CIP-007-3,R.1.3,CIP-007-3,R5,CIP-007-3,R5.1.1,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3,CIP-007-3,R6.5,FAU_GEN.1.1.c |
| CCE-83191-7 |
Ensure auditd Collects Information on the Use of Privileged Commands - usermod [ref] |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that have compromised system accounts,is a serious and ongoing concern and can have significant adverse impacts on organizations.Auditing the use of privileged functions is one way to detect such misuse and identifythe risk from insider and advanced persistent threats.Privileged programs are subject to escalation-of-privilege attacks,which attempt to subvert their normal role of providing some necessary butlimited capability. As such, motivation exists to monitor these programs forunusual activity. |
medium |
content_rule_audit_rules_privileged_commands_usermod |
SLES-12-020700 |
AU-3,AU-12(a),AU-12(c),MA-4(1)(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000466-GPOS-00210 |
NaN |
SV-217251r603947_rule |
CCI-000130,CCI-000169,CCI-000172,CCI-002884 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83119-8 |
Remove Default Configuration to Disable Syscall Auditing [ref] |
By default, SUSE Linux Enterprise 12 ships an audit rule to disable syscall auditing for performance reasons. To make sure that syscall auditing works, this line must be removed from /etc/audit/rules.d/audit.rules and /etc/audit/audit.rules: -a task,never |
Audit rules for syscalls do not take effect unless this line is removed. |
medium |
content_rule_audit_rules_enable_syscall_auditing |
SLES-12-020199 |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217204r646746_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83217-0 |
Ensure auditd Collects Information on Exporting to Media (successful) [ref] |
At a minimum, the audit system should collect media exportation events for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S mount -F auid>=1000 -F auid!=unset -F key=export If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S mount -F auid>=1000 -F auid!=unset -F key=export |
The unauthorized exportation of data to external media could result in an information leakwhere classified information, Privacy Act information, and intellectual property could be lost. An audittrail should be created each time a filesystem is mounted to help identify and guard against informationloss. |
medium |
content_rule_audit_rules_media_export |
SLES-12-020290 |
AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 |
NaN |
SV-217213r603262_rule |
CCI-000135,CCI-000169,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,Req-10.2.7,4.1.12 |
| CCE-83200-6 |
Record Events When Privileged Executables Are Run [ref] |
Verify the system generates an audit record when privileged functions are executed. # grep -iw execve /etc/audit/audit.rules -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid If both the "b32" and "b64" audit rules for "SUID" files are not defined, this is a finding. If both the "b32" and "b64" audit rules for "SGID" files are not defined, this is a finding.Warning: Note that these rules can be configured in a number of ways while still achieving the desired effect. |
Misuse of privileged functions, either intentionally or unintentionally byauthorized users, or by unauthorized external entities that havecompromised information system accounts, is a serious and ongoing concernand can have significant adverse impacts on organizations. Auditing the useof privileged functions is one way to detect such misuse and identify therisk from insider threats and the advanced persistent threat. |
medium |
content_rule_audit_rules_suid_privilege_function |
SLES-12-020240 |
AC-6(9),AU-7(a),AU-7(b),AU-8(b),AU-12(3),CM-5(1) |
NaN |
NaN |
SRG-OS-000326-GPOS-00126,SRG-OS-000327-GPOS-00127,SRG-OS-000337-GPOS-00129,SRG-OS-000348-GPOS-00136,SRG-OS-000349-GPOS-00137,SRG-OS-000350-GPOS-00138,SRG-OS-000351-GPOS-00139,SRG-OS-000352-GPOS-00140,SRG-OS-000353-GPOS-00141,SRG-OS-000354-GPOS-00142,SRG-OS-000358-GPOS-00145,SRG-OS-000359-GPOS-00146,SRG-OS-000365-GPOS-00152 |
NaN |
SV-217209r603262_rule |
CCI-001814,CCI-001882,CCI-001889,CCI-001880,CCI-001881,CCI-001878,CCI-001879,CCI-001875,CCI-001877,CCI-001914,CCI-002234 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83121-4 |
Record Events that Modify User/Group Information - /etc/group [ref] |
If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d, in order to capture events that modify account changes: -w /etc/group -p wa -k audit_rules_usergroup_modification If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file, in order to capture events that modify account changes: -w /etc/group -p wa -k audit_rules_usergroup_modification |
In addition to auditing new user and group accounts, these watcheswill alert the system administrator(s) to any modifications. Any unexpectedusers, groups, or modifications should be investigated for legitimacy. |
medium |
content_rule_audit_rules_usergroup_modification_group |
SLES-12-020210 |
AC-2(4),AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.2.2,4.3.3.3.9,4.3.3.5.1,4.3.3.5.2,4.3.3.5.8,4.3.3.6.6,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-1,PR.AC-3,PR.AC-4,PR.AC-6,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000004-GPOS-00004,SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000304-GPOS-00121,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000470-GPOS-00214,SRG-OS-000471-GPOS-00215,SRG-OS-000239-GPOS-00089,SRG-OS-000240-GPOS-00090,SRG-OS-000241-GPOS-00091,SRG-OS-000303-GPOS-00120,SRG-OS-000304-GPOS-00121,SRG-OS-000466-GPOS-00210,SRG-OS-000476-GPOS-00221,SRG-OS-000004-VMM-000040,SRG-OS-000239-VMM-000810,SRG-OS-000240-VMM-000820,SRG-OS-000241-VMM-000830,SRG-OS-000274-VMM-000960,SRG-OS-000275-VMM-000970,SRG-OS-000276-VMM-000980,SRG-OS-000277-VMM-000990,SRG-OS-000303-VMM-001090,SRG-OS-000304-VMM-001100,SRG-OS-000476-VMM-001960 |
NaN |
SV-217206r603262_rule |
CCI-000018,CCI-000169,CCI-000172,CCI-001403,CCI-001404,CCI-001405,CCI-001683,CCI-001684,CCI-001685,CCI-001686,CCI-002130,CCI-002132,CCI-002884 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,18,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,DSS06.03,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.1.2,A.6.2.1,A.6.2.2,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.1,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R2.2.2,CIP-004-3,R2.2.3,CIP-007-3,R.1.3,CIP-007-3,R5,CIP-007-3,R5.1.1,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3,FAU_GEN.1.1.c,Req-10.2.5,4.1.4 |
| CCE-83095-0 |
Record Events that Modify User/Group Information - /etc/gshadow [ref] |
If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d, in order to capture events that modify account changes: -w /etc/gshadow -p wa -k audit_rules_usergroup_modification If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file, in order to capture events that modify account changes: -w /etc/gshadow -p wa -k audit_rules_usergroup_modification |
In addition to auditing new user and group accounts, these watcheswill alert the system administrator(s) to any modifications. Any unexpectedusers, groups, or modifications should be investigated for legitimacy. |
medium |
content_rule_audit_rules_usergroup_modification_gshadow |
SLES-12-020590 |
AC-2(4),AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.2.2,4.3.3.3.9,4.3.3.5.1,4.3.3.5.2,4.3.3.5.8,4.3.3.6.6,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-1,PR.AC-3,PR.AC-4,PR.AC-6,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000004-GPOS-00004,SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000304-GPOS-00121,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000470-GPOS-00214,SRG-OS-000471-GPOS-00215,SRG-OS-000239-GPOS-00089,SRG-OS-000240-GPOS-00090,SRG-OS-000241-GPOS-00091,SRG-OS-000303-GPOS-00120,SRG-OS-000304-GPOS-00121,SRG-OS-000466-GPOS-00210,SRG-OS-000476-GPOS-00221,SRG-OS-000004-VMM-000040,SRG-OS-000239-VMM-000810,SRG-OS-000240-VMM-000820,SRG-OS-000241-VMM-000830,SRG-OS-000274-VMM-000960,SRG-OS-000275-VMM-000970,SRG-OS-000276-VMM-000980,SRG-OS-000277-VMM-000990,SRG-OS-000303-VMM-001090,SRG-OS-000304-VMM-001100,SRG-OS-000476-VMM-001960 |
NaN |
SV-217240r603262_rule |
CCI-000018,CCI-000169,CCI-000172,CCI-001403,CCI-001404,CCI-001405,CCI-001683,CCI-001684,CCI-001685,CCI-001686,CCI-002130,CCI-002132 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,18,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,DSS06.03,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.1.2,A.6.2.1,A.6.2.2,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.1,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R2.2.2,CIP-004-3,R2.2.3,CIP-007-3,R.1.3,CIP-007-3,R5,CIP-007-3,R5.1.1,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3,FAU_GEN.1.1.c,Req-10.2.5,4.1.4 |
| CCE-83123-0 |
Record Events that Modify User/Group Information - /etc/security/opasswd [ref] |
If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d, in order to capture events that modify account changes: -w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file, in order to capture events that modify account changes: -w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification |
In addition to auditing new user and group accounts, these watcheswill alert the system administrator(s) to any modifications. Any unexpectedusers, groups, or modifications should be investigated for legitimacy. |
medium |
content_rule_audit_rules_usergroup_modification_opasswd |
SLES-12-020230 |
AC-2(4),AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.2.2,4.3.3.3.9,4.3.3.5.1,4.3.3.5.2,4.3.3.5.8,4.3.3.6.6,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-1,PR.AC-3,PR.AC-4,PR.AC-6,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000004-GPOS-00004,SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000304-GPOS-00121,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000470-GPOS-00214,SRG-OS-000471-GPOS-00215,SRG-OS-000239-GPOS-00089,SRG-OS-000240-GPOS-00090,SRG-OS-000241-GPOS-00091,SRG-OS-000303-GPOS-00120,SRG-OS-000304-GPOS-00121,SRG-OS-000476-GPOS-00221,SRG-OS-000463-GPOS-00207,SRG-OS-000004-VMM-000040,SRG-OS-000239-VMM-000810,SRG-OS-000240-VMM-000820,SRG-OS-000241-VMM-000830,SRG-OS-000274-VMM-000960,SRG-OS-000275-VMM-000970,SRG-OS-000276-VMM-000980,SRG-OS-000277-VMM-000990,SRG-OS-000303-VMM-001090,SRG-OS-000304-VMM-001100,SRG-OS-000476-VMM-001960 |
NaN |
SV-217208r603262_rule |
CCI-000018,CCI-000169,CCI-000172,CCI-001403,CCI-001404,CCI-001405,CCI-001683,CCI-001684,CCI-001685,CCI-001686,CCI-002130,CCI-002132 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,18,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,DSS06.03,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.1.2,A.6.2.1,A.6.2.2,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.1,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R2.2.2,CIP-004-3,R2.2.3,CIP-007-3,R.1.3,CIP-007-3,R5,CIP-007-3,R5.1.1,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3,FAU_GEN.1.1.c,Req-10.2.5,4.1.4 |
| CCE-83120-6 |
Record Events that Modify User/Group Information - /etc/passwd [ref] |
If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d, in order to capture events that modify account changes: -w /etc/passwd -p wa -k audit_rules_usergroup_modification If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file, in order to capture events that modify account changes: -w /etc/passwd -p wa -k audit_rules_usergroup_modification |
In addition to auditing new user and group accounts, these watcheswill alert the system administrator(s) to any modifications. Any unexpectedusers, groups, or modifications should be investigated for legitimacy. |
medium |
content_rule_audit_rules_usergroup_modification_passwd |
SLES-12-020200 |
AC-2(4),AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.2.2,4.3.3.3.9,4.3.3.5.1,4.3.3.5.2,4.3.3.5.8,4.3.3.6.6,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-1,PR.AC-3,PR.AC-4,PR.AC-6,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000004-GPOS-00004,SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000304-GPOS-00121,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000470-GPOS-00214,SRG-OS-000471-GPOS-00215,SRG-OS-000239-GPOS-00089,SRG-OS-000240-GPOS-00090,SRG-OS-000241-GPOS-00091,SRG-OS-000303-GPOS-00120,SRG-OS-000304-GPOS-00121,SRG-OS-000466-GPOS-00210,SRG-OS-000476-GPOS-00221,SRG-OS-000274-GPOS-00104,SRG-OS-000275-GPOS-00105,SRG-OS-000276-GPOS-00106,SRG-OS-000277-GPOS-00107,SRG-OS-000004-VMM-000040,SRG-OS-000239-VMM-000810,SRG-OS-000240-VMM-000820,SRG-OS-000241-VMM-000830,SRG-OS-000274-VMM-000960,SRG-OS-000275-VMM-000970,SRG-OS-000276-VMM-000980,SRG-OS-000277-VMM-000990,SRG-OS-000303-VMM-001090,SRG-OS-000304-VMM-001100,SRG-OS-000476-VMM-001960 |
NaN |
SV-217205r603262_rule |
CCI-000018,CCI-000169,CCI-000172,CCI-001403,CCI-001404,CCI-001405,CCI-001683,CCI-001684,CCI-001685,CCI-001686,CCI-002130,CCI-002132 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,18,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,DSS06.03,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.1.2,A.6.2.1,A.6.2.2,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.1,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R2.2.2,CIP-004-3,R2.2.3,CIP-007-3,R.1.3,CIP-007-3,R5,CIP-007-3,R5.1.1,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3,FAU_GEN.1.1.c,Req-10.2.5,4.1.4 |
| CCE-83122-2 |
Record Events that Modify User/Group Information - /etc/shadow [ref] |
If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d, in order to capture events that modify account changes: -w /etc/shadow -p wa -k audit_rules_usergroup_modification If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file, in order to capture events that modify account changes: -w /etc/shadow -p wa -k audit_rules_usergroup_modification |
In addition to auditing new user and group accounts, these watcheswill alert the system administrator(s) to any modifications. Any unexpectedusers, groups, or modifications should be investigated for legitimacy. |
medium |
content_rule_audit_rules_usergroup_modification_shadow |
SLES-12-020220 |
AC-2(4),AC-6(9),AU-2(d),AU-12(c),CM-6(a) |
3.1.7,4.2.3.10,4.3.2.6.7,4.3.3.2.2,4.3.3.3.9,4.3.3.5.1,4.3.3.5.2,4.3.3.5.8,4.3.3.6.6,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-1,PR.AC-3,PR.AC-4,PR.AC-6,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000004-GPOS-00004,SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000304-GPOS-00121,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000470-GPOS-00214,SRG-OS-000471-GPOS-00215,SRG-OS-000239-GPOS-00089,SRG-OS-000240-GPOS-00090,SRG-OS-000241-GPOS-00091,SRG-OS-000303-GPOS-00120,SRG-OS-000304-GPOS-00121,SRG-OS-000466-GPOS-00210,SRG-OS-000476-GPOS-00221,SRG-OS-000004-VMM-000040,SRG-OS-000239-VMM-000810,SRG-OS-000240-VMM-000820,SRG-OS-000241-VMM-000830,SRG-OS-000274-VMM-000960,SRG-OS-000275-VMM-000970,SRG-OS-000276-VMM-000980,SRG-OS-000277-VMM-000990,SRG-OS-000303-VMM-001090,SRG-OS-000304-VMM-001100,SRG-OS-000476-VMM-001960 |
NaN |
SV-217207r603262_rule |
CCI-000018,CCI-000169,CCI-000172,CCI-001403,CCI-001404,CCI-001405,CCI-001683,CCI-001684,CCI-001685,CCI-001686,CCI-002130,CCI-002132 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,18,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3)(ii)(A),164.308(a)(5)(ii)(C),164.312(a)(2)(i),164.312(b),164.312(d),164.312(e) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,DSS06.03,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.1.2,A.6.2.1,A.6.2.2,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.1,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R2.2.2,CIP-004-3,R2.2.3,CIP-007-3,R.1.3,CIP-007-3,R5,CIP-007-3,R5.1.1,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3,FAU_GEN.1.1.c,Req-10.2.5,4.1.4 |
| CCE-83114-9 |
Configure a Sufficiently Large Partition for Audit Logs [ref] |
The SUSE Linux Enterprise 12 operating system must allocate audit record storage capacity to store at least one weeks worth of audit records when audit records are not immediately sent to a central audit record storage facility. The partition size needed to capture a week's worth of audit records is based on the activity level of the system and the total storage capacity available. In normal circumstances, 10.0 GB of storage space for audit records will be sufficient. Determine which partition the audit records are being written to with the following command: # grep log_file /etc/audit/auditd.conf log_file = /var/log/audit/audit.log Check the size of the partition that audit records are written to with the following command: # df -h /var/log/audit/ /dev/sda2 24G 10.4G 13.6G 43% /var/log/audit |
Information stored in one location is vulnerable to accidental or incidentaldeletion or alteration.Off-loading is a common process in informationsystems with limited audit storage capacity. |
medium |
content_rule_auditd_audispd_configure_sufficiently_large_partition |
SLES-12-020020 |
NaN |
NaN |
NaN |
SRG-OS-000341-GPOS-00132,SRG-OS-000342-GPOS-00133 |
NaN |
SV-217192r603262_rule |
CCI-001849 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83116-4 |
Configure audispd's Plugin disk_full_action When Disk Is Full [ref] |
Configure the action the operating system takes if the disk the audit records are written to becomes full. Edit the file /etc/audisp/audisp-remote.conf. Add or modify the following line, substituting ACTION appropriately: disk_full_action = ACTION Set this value to single to cause the system to switch to single user mode for corrective action. Acceptable values also include syslog and halt. For certain systems, the need for availability outweighs the need to log all actions, and a different setting should be determined. |
Taking appropriate action in case of a filled audit storage volume willminimize the possibility of losing audit records. |
medium |
content_rule_auditd_audispd_disk_full_action |
SLES-12-020110 |
AU-5(b),AU-5(2),AU-5(1),AU-5(4),CM-6(a) |
NaN |
NaN |
SRG-OS-000342-GPOS-00133,SRG-OS-000479-GPOS-00224 |
NaN |
SV-217201r603262_rule |
CCI-001851 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83063-8 |
Encrypt Audit Records Sent With audispd Plugin [ref] |
Configure the operating system to encrypt the transfer of off-loaded audit records onto a different system or media from the system being audited. Uncomment the enable_krb5 option in /etc/audisp/audisp-remote.conf, and set it with the following line: enable_krb5 = yes |
Information stored in one location is vulnerable to accidental or incidental deletionor alteration. Off-loading is a common process in information systems with limitedaudit storage capacity. |
medium |
content_rule_auditd_audispd_encrypt_sent_records |
SLES-12-020080 |
AU-9(3),CM-6(a) |
NaN |
NaN |
SRG-OS-000342-GPOS-00133,SRG-OS-000479-GPOS-00224 |
NaN |
SV-217198r603262_rule |
CCI-001851 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
FAU_GEN.1.1.c |
| CCE-83115-6 |
Configure audispd's Plugin network_failure_action On Network Failure [ref] |
Configure the action the operating system takes if there is an error sending audit records to a remote system. Edit the file /etc/audisp/audisp-remote.conf. Add or modify the following line, substituting ACTION appropriately: network_failure_action = ACTION Set this value to single to cause the system to switch to single user mode for corrective action. Acceptable values also include syslog and halt. For certain systems, the need for availability outweighs the need to log all actions, and a different setting should be determined. This profile configures the action to be single. |
Taking appropriate action when there is an error sending audit records to aremote system will minimize the possibility of losing audit records. |
medium |
content_rule_auditd_audispd_network_failure_action |
SLES-12-020100 |
AU-5(b),AU-5(2),AU-5(1),AU-5(4),CM-6(a) |
NaN |
NaN |
SRG-OS-000342-GPOS-00133,SRG-OS-000479-GPOS-00224 |
NaN |
SV-217200r603262_rule |
CCI-001851 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83032-3 |
Configure auditd Disk Full Action when Disk Space Is Full [ref] |
The auditd service can be configured to take an action when disk space is running low but prior to running out of space completely. Edit the file /etc/audit/auditd.conf. Add or modify the following line, substituting ACTION appropriately: disk_full_action = ACTION Set this value to single to cause the system to switch to single-user mode for corrective action. Acceptable values also include syslog, single, and halt. For certain systems, the need for availability outweighs the need to log all actions, and a different setting should be determined. Details regarding all possible values for ACTION are described in the auditd.conf man page. |
Taking appropriate action in case of a filled audit storage volume will minimizethe possibility of losing audit records. |
medium |
content_rule_auditd_data_disk_full_action |
SLES-12-020060 |
AU-5(b),AU-5.1(iv) |
4.2.3.10,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
PR.DS-4,PR.PT-1,DE.AE-3,DE.AE-5,RS.AN-1,RS.AN-4 |
SRG-OS-000047-GPOS-00023 |
NaN |
SV-217196r603262_rule |
CCI-000140 |
1,2,3,4,5,6,7,8,11,12,13,14,15,16,19 |
NaN |
NaN |
APO11.04,APO12.06,APO13.01,BAI03.05,BAI04.04,BAI08.02,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS05.04,DSS05.07,MEA02.01 |
A.12.1.3,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.16.1.4,A.16.1.5,A.16.1.7,A.17.2.1 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,7.1,SR,7.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4 |
| CCE-83030-7 |
Configure auditd mail_acct Action on Low Disk Space [ref] |
The auditd service can be configured to send email to a designated account in certain situations. Add or correct the following line in /etc/audit/auditd.conf to ensure that administrators are notified via email for those situations: action_mail_acct = root |
Email sent to the root account is typically aliased to theadministrators of the system, who can take appropriate action. |
medium |
content_rule_auditd_data_retention_action_mail_acct |
SLES-12-020040 |
AU-5(a),AU-5.1(ii) |
4.2.3.10,3.3.1,4.3.3.3.9,4.3.3.5.8,CIP-003-3,R1.3,CIP-003-3,R3,CIP-003-3,R3.1,CIP-003-3,R3.2,CIP-003-3,R3.3,CIP-003-3,R5.1.1,CIP-003-3,R5.3,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
PR.DS-4,PR.PT-1,DE.AE-3,DE.AE-5,RS.AN-1,RS.AN-4 |
SRG-OS-000046-GPOS-00022,SRG-OS-000343-GPOS-00134,SRG-OS-000046-VMM-000210,SRG-OS-000343-VMM-001240 |
NaN |
SV-217194r603262_rule |
CCI-000139,CCI-001855 |
1,2,3,4,5,6,7,8,11,12,13,14,15,16,19 |
NaN |
164.312(a)(2)(ii) |
APO11.04,APO12.06,APO13.01,BAI03.05,BAI04.04,BAI08.02,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS05.04,DSS05.07,MEA02.01 |
A.12.1.3,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.16.1.4,A.16.1.5,A.16.1.7,A.17.2.1 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,7.1,SR,7.2 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R2.2.3,CIP-004-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.2,CIP-007-3,R5.2,CIP-007-3,R5.3.1,CIP-007-3,R5.3.2,CIP-007-3,R5.3.3,Req-10.7.a,4.1.2.3 |
| CCE-83026-5 |
Configure auditd space_left on Low Disk Space [ref] |
The auditd service can be configured to take an action when disk space is running low but prior to running out of space completely. Edit the file /etc/audit/auditd.conf. Add or modify the following line, substituting SIZE_in_MB appropriately: space_left = SIZE_in_MB Set this value to the appropriate size in Megabytes cause the system to notify the user of an issue. |
Notifying administrators of an impending disk space problem may allow them totake corrective action prior to any disruption. |
medium |
content_rule_auditd_data_retention_space_left |
SLES-12-020030 |
AU-5(1) |
4.2.3.10,4.3.3.3.9,4.3.3.5.8,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
PR.DS-4,PR.PT-1,DE.AE-3,DE.AE-5,RS.AN-1,RS.AN-4 |
SRG-OS-000343-GPOS-00134,SRG-OS-000343-VMM-001240 |
NaN |
SV-217193r603262_rule |
CCI-001855 |
1,2,3,4,5,6,7,8,11,12,13,14,15,16,19 |
NaN |
NaN |
APO11.04,APO12.06,APO13.01,BAI03.05,BAI04.04,BAI08.02,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS05.04,DSS05.07,MEA02.01 |
A.12.1.3,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.16.1.4,A.16.1.5,A.16.1.7,A.17.2.1 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,6.1,SR,7.1,SR,7.2 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4,Req-10.7 |
| CCE-83033-1 |
Ensure the default plugins for the audit dispatcher are Installed [ref] |
The audit-audispd-plugins package should be installed. |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. |
medium |
content_rule_package_audit-audispd-plugins_installed |
SLES-12-020070 |
AU-4(1) |
NaN |
NaN |
SRG-OS-000342-GPOS-00133 |
NaN |
SV-217197r603262_rule |
CCI-001851 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83023-2 |
Ensure the audit Subsystem is Installed [ref] |
The audit package should be installed. |
The auditd service is an access monitoring and accounting daemon, watching system calls to audit any access, in comparison with potential local access control policy such as SELinux policy. |
medium |
content_rule_package_audit_installed |
SLES-12-020000 |
AU-7(a),AU-7(b),AU-8(b),AU-12.1(iv),AU-12(3),AU-12(c),CM-5(1) |
NaN |
NaN |
SRG-OS-000122-GPOS-00063,SRG-OS-000337-GPOS-00129,SRG-OS-000348-GPOS-00136,SRG-OS-000349-GPOS-00137,SRG-OS-000350-GPOS-00138,SRG-OS-000351-GPOS-00139,SRG-OS-000352-GPOS-00140,SRG-OS-000353-GPOS-00141,SRG-OS-000354-GPOS-00142,SRG-OS-000358-GPOS-00145,SRG-OS-000359-GPOS-00146,SRG-OS-000365-GPOS-00152,SRG-OS-000474-GPOS-00219,SRG-OS-000475-GPOS-00220,SRG-OS-000480-GPOS-00227,SRG-OS-000062-GPOS-00031 |
NaN |
SV-217190r603262_rule |
CCI-000172,CCI-001814,CCI-001875,CCI-001877,CCI-001878,CCI-001879,CCI-001880,CCI-001881,CCI-001882,CCI-001889,CCI-001914,CCI-000169 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
BP28(R50) |
CIP-004-3,R3.3,CIP-007-3,R6.5,4.1.1.1 |
| CCE-83024-0 |
Enable auditd Service [ref] |
The auditd service is an essential userspace component of the Linux Auditing System, as it is responsible for writing audit records to disk. The auditd service can be enabled with the following command: $ sudo systemctl enable auditd.service |
Without establishing what type of events occurred, it would be difficultto establish, correlate, and investigate the events leading up to an outage or attack.Ensuring the auditd service is active ensures audit recordsgenerated by the kernel are appropriately recorded.Additionally, a properly configured audit subsystem ensures that actions ofindividual system users can be uniquely traced to those users so theycan be held accountable for their actions. |
medium |
content_rule_service_auditd_enabled |
SLES-12-020010 |
AU-3,AU-3(1),AU-3(1).1(ii),AU-3.1,AU-6(4),AU-6(4).1,AU-7(1),AU-7(1).1,AU-7(a),AU-14(1),AU-14(1).1,CM-6(b),CM-6.1(iv),MA-4(1)(a) |
4.2.3.10,4.3.2.6.7,3.3.1,3.3.2,3.3.6,4.3.3.3.9,4.3.3.5.8,4.3.3.6.6,4.3.4.4.7,4.3.4.5.6,4.3.4.5.7,4.3.4.5.8 |
ID.SC-4,PR.AC-3,PR.PT-1,PR.PT-4,DE.AE-3,DE.AE-5,DE.CM-1,DE.CM-3,DE.CM-7,RS.AN-1,RS.AN-4 |
SRG-OS-000037-GPOS-00015,SRG-OS-000038-GPOS-00016,SRG-OS-000039-GPOS-00017,SRG-OS-000040-GPOS-00018,SRG-OS-000041-GPOS-00019,SRG-OS-000042-GPOS-00021,SRG-OS-000051-GPOS-00024,SRG-OS-000054-GPOS-00025,SRG-OS-000122-GPOS-00063,SRG-OS-000254-GPOS-00095,SRG-OS-000255-GPOS-00096,SRG-OS-000365-GPOS-00152,SRG-OS-000392-GPOS-00172,SRG-OS-000480-GPOS-00227,SRG-OS-000062-GPOS-00031,SRG-OS-000037-VMM-000150,SRG-OS-000063-VMM-000310,SRG-OS-000038-VMM-000160,SRG-OS-000039-VMM-000170,SRG-OS-000040-VMM-000180,SRG-OS-000041-VMM-000190 |
NaN |
SV-217191r603262_rule |
CCI-000126,CCI-000130,CCI-000131,CCI-000132,CCI-000133,CCI-000134,CCI-000135,CCI-000154,CCI-000158,CCI-000366,CCI-001464,CCI-001487,CCI-001814,CCI-001876,CCI-002884,CCI-000169 |
1,2,3,4,5,6,7,8,9,11,12,13,14,15,16,19 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(5)(ii)(C),164.310(a)(2)(iv),164.310(d)(2)(iii),164.312(b) |
APO10.01,APO10.03,APO10.04,APO10.05,APO11.04,APO12.06,APO13.01,BAI03.05,BAI08.02,DSS01.03,DSS01.04,DSS02.02,DSS02.04,DSS02.07,DSS03.01,DSS03.05,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,MEA01.01,MEA01.02,MEA01.03,MEA01.04,MEA01.05,MEA02.01 |
A.6.2.1,A.6.2.2,A.11.2.6,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.7,A.15.2.1,A.15.2.2,A.16.1.4,A.16.1.5,A.16.1.7 |
SR,1.13,SR,2.10,SR,2.11,SR,2.12,SR,2.6,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.1,SR,6.2,SR,7.1,SR,7.6 |
NaN |
5.4.1.1,4.4.2.1,4.4.2.2,4.4.2.4,CIP-004-3,R3.3,CIP-007-3,R6.5,Req-10.1,4.1.1.2 |
| CCE-83225-3 |
Install the pam_apparmor Package [ref] |
The pam_apparmor package can be installed with the following command: $ sudo zypper install pam_apparmor |
Protection of system integrity using AppArmor depends on this package beinginstalled. |
medium |
content_rule_package_pam_apparmor_installed |
SLES-12-010600 |
AC-3(4),AC-6(8),AC-6(10),CM-7(5)(b),CM-7(2),CM-6(a),SC-7(21) |
NaN |
NaN |
SRG-OS-000312-GPOS-00122,SRG-OS-000312-GPOS-00123SRG-OS-000312-GPOS-00124,SRG-OS-000324-GPOS-00125,SRG-OS-000326-GPOS-00126,SRG-OS-000370-GPOS-00155,SRG-OS-000480-GPOS-00230,SRG-OS-000480-GPOS-00227,SRG-OS-000480-GPOS-00231,SRG-OS-000480-GPOS-00232 |
NaN |
SV-217158r646719_rule |
CCI-001764,CCI-001774,CCI-002165,CCI-002233,CCI-002235 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
1.6.1.1 |
| CCE-83194-1 |
Ensure AppArmor is Active and Configured [ref] |
Verify that the Apparmor tool is configured to control whitelisted applications and user home directory access control. The apparmor service can be enabled with the following command: $ sudo systemctl enable apparmor.service |
Using a whitelist provides a configuration management method for allowingthe execution of only authorized software. Using only authorized softwaredecreases risk by limiting the number of potential vulnerabilities.The organization must identify authorized software programs and permitexecution of authorized software by adding each authorized program to the"pam_apparmor" exception policy. The process used to identify softwareprograms that are authorized to execute on organizational informationsystems is commonly referred to as whitelisting.Verification of whitelisted software occurs prior to execution or at systemstartup.Users' home directories/folders may contain information of a sensitivenature. Nonprivileged users should coordinate any sharing of informationwith a System Administrator (SA) through shared resources.Apparmor can confine users to their home directory, not allowing them tomake any changes outside of their own home directories. Confining users totheir home directory will minimize the risk of sharing information. |
medium |
content_rule_apparmor_configured |
SLES-12-010600 |
AC-3(4),AC-6(8),AC-6(10),CM-7(5)(b),CM-7(2),CM-6(a),SC-7(21) |
NaN |
NaN |
SRG-OS-000312-GPOS-00122,SRG-OS-000312-GPOS-00123SRG-OS-000312-GPOS-00124,SRG-OS-000324-GPOS-00125,SRG-OS-000326-GPOS-00126,SRG-OS-000370-GPOS-00155,SRG-OS-000480-GPOS-00230,SRG-OS-000480-GPOS-00227,SRG-OS-000480-GPOS-00231,SRG-OS-000480-GPOS-00232 |
NaN |
SV-217158r646719_rule |
CCI-001764,CCI-001774,CCI-002165,CCI-002233,CCI-002235 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
1.6.1.2 |
| CCE-83044-8 |
Set Boot Loader Password in grub2 [ref] |
The grub2 boot loader should have a superuser account and password protection enabled to protect boot-time settings. Since plaintext passwords are a security risk, generate a hash for the password by running the following command: $ grub2-mkpasswd-pbkdf2 When prompted, enter the password that was selected. Using the hash from the output, modify the /etc/grub.d/40_custom file with the following content: set superusers="boot" password_pbkdf2 boot grub.pbkdf2.sha512.VeryLongString NOTE: the bootloader superuser account and password MUST differ from the root account and password. Once the superuser password has been added, update the grub.cfg file by running: grub2-mkconfig -o /boot/grub2/grub.cfgWarning: To prevent hard-coded passwords, automatic remediation of this control is not available. Remediation must be automated as a component of machine provisioning, or followed manually as outlined above. Also, do NOT manually add the superuser account and password to the grub.cfg file as the grub2-mkconfig command overwrites this file. |
Password protection on the boot loader configuration ensuresusers with physical access cannot trivially alterimportant bootloader settings. These include which kernel to use,and whether to enter single-user mode. |
high |
content_rule_grub2_password |
SLES-12-010430 |
CM-6(a) |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,3.4.5 |
PR.AC-1,PR.AC-4,PR.AC-6,PR.AC-7,PR.PT-3 |
SRG-OS-000080-GPOS-00048 |
NaN |
SV-217144r603262_rule |
CCI-000213 |
1,3,5,11,12,14,15,16,18 |
NaN |
164.308(a)(1)(ii)(B),164.308(a)(7)(i),164.308(a)(7)(ii)(A),164.310(a)(1),164.310(a)(2)(i),164.310(a)(2)(ii),164.310(a)(2)(iii),164.310(b),164.310(c),164.310(d)(1),164.310(d)(2)(iii) |
DSS05.02,DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.06,DSS06.10 |
A.6.1.2,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7 |
BP28(R17) |
FIA_UAU.1,1.4.1 |
| CCE-83045-5 |
Set the UEFI Boot Loader Password [ref] |
The grub2 boot loader should have a superuser account and password protection enabled to protect boot-time settings. Since plaintext passwords are a security risk, generate a hash for the password by running the following command: $ grub2-mkpasswd-pbkdf2 When prompted, enter the password that was selected. Using the hash from the output, modify the /etc/grub.d/40_custom file with the following content: set superusers="boot" password_pbkdf2 boot grub.pbkdf2.sha512.VeryLongString NOTE: the bootloader superuser account and password MUST differ from the root account and password. Once the superuser password has been added, update the grub.cfg file by running: grub2-mkconfig -o /boot/efi/EFI/sles/grub.cfgWarning: To prevent hard-coded passwords, automatic remediation of this control is not available. Remediation must be automated as a component of machine provisioning, or followed manually as outlined above. Also, do NOT manually add the superuser account and password to the grub.cfg file as the grub2-mkconfig command overwrites this file. |
Password protection on the boot loader configuration ensuresusers with physical access cannot trivially alterimportant bootloader settings. These include which kernel to use,and whether to enter single-user mode. |
high |
content_rule_grub2_uefi_password |
SLES-12-010440 |
CM-6(a) |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,3.4.5 |
PR.AC-4,PR.AC-6,PR.PT-3 |
SRG-OS-000080-GPOS-00048 |
NaN |
SV-217145r603262_rule |
CCI-000213 |
3,5,11,12,14,15,16,18 |
NaN |
164.308(a)(1)(ii)(B),164.308(a)(7)(i),164.308(a)(7)(ii)(A),164.310(a)(1),164.310(a)(2)(i),164.310(a)(2)(ii),164.310(a)(2)(iii),164.310(b),164.310(c),164.310(d)(1),164.310(d)(2)(iii) |
DSS05.02,DSS05.04,DSS05.05,DSS05.07,DSS06.03,DSS06.06 |
A.6.1.2,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7 |
BP28(R17) |
FIA_UAU.1,1.4.1 |
| CCE-83180-0 |
Ensure Logs Sent To Remote Host [ref] |
To configure rsyslog to send logs to a remote log server, open /etc/rsyslog.conf and read and understand the last section of the file, which describes the multiple directives necessary to activate remote logging. Along with these other directives, the system can be configured to forward its logs to a particular log server by adding or correcting one of the following lines, substituting logcollector appropriately. The choice of protocol depends on the environment of the system; although TCP and RELP provide more reliable message delivery, they may not be supported in all environments. To use UDP for log message delivery: *.* @logcollector To use TCP for log message delivery: *.* @@logcollector To use RELP for log message delivery: *.* :omrelp:logcollector There must be a resolvable DNS CNAME or Alias record set to "logcollector" for logs to be sent correctly to the centralized logging utility. |
A log server (loghost) receives syslog messages from one or moresystems. This data can be used as an additional log source in the event asystem is compromised and its local logs are suspect. Forwarding log messagesto a remote loghost also provides system administrators with a centralizedplace to view the status of multiple hosts within the enterprise. |
medium |
content_rule_rsyslog_remote_loghost |
SLES-12-030340 |
AU-4(1),AU-9(2),CM-6(a) |
4.3.3.3.9,4.3.3.5.8,CIP-003-3,R5.2,4.3.4.4.7 |
PR.DS-4,PR.PT-1 |
SRG-OS-000479-GPOS-00224,SRG-OS-000480-GPOS-00227,SRG-OS-000342-GPOS-00133,SRG-OS-000032-VMM-000130 |
NaN |
SV-217285r603262_rule |
CCI-000366,CCI-001348,CCI-000136,CCI-001851 |
1,2,3,5,6,13,14,15,16 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(5)(ii)(B),164.308(a)(5)(ii)(C),164.308(a)(6)(ii),164.308(a)(8),164.310(d)(2)(iii),164.312(b),164.314(a)(2)(i)(C),164.314(a)(2)(iii) |
APO11.04,APO13.01,BAI03.05,BAI04.04,DSS05.04,DSS05.07,MEA02.01 |
A.12.1.3,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.17.2.1 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9,SR,7.1,SR,7.2 |
BP28(R7) |
NT28(R43),NT12(R5),4.4.2.1,4.4.2.2,4.4.2.4,0988,1405,CIP-004-3,R3.3,FAU_GEN.1.1.c,4.2.1.5 |
| CCE-83197-4 |
Ensure real-time clock is set to UTC [ref] |
Ensure that the system real-time clock (RTC) is set to Coordinated Universal Time (UTC). |
If time stamps are not consistently applied and there is no commontime reference, it is difficult to perform forensic analysis.Time stamps generated by the operating system include date and time.Time is commonly expressed in UTC, a modern continuation of GMT, orlocal time with an offset from UTC. |
high |
content_rule_ensure_rtc_utc_configuration |
SLES-12-030310 |
AU-8(b) |
NaN |
NaN |
SRG-OS-000359-GPOS-00146 |
NaN |
SV-217282r646758_rule |
CCI-001890 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83246-9 |
Disable Accepting ICMP Redirects for All IPv6 Interfaces [ref] |
To set the runtime status of the net.ipv6.conf.all.accept_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_redirects=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.all.accept_redirects = 0 |
An illicit ICMP redirect message could result in a man-in-the-middle attack. |
medium |
content_rule_sysctl_net_ipv6_conf_all_accept_redirects |
SLES-12-030363 |
CM-7(a),CM-7(b),CM-6(a),CM-6(b),CM-6.1(iv) |
3.1.20,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,3.3.2,4.3.4.3.2,4.3.4.3.3 |
PR.IP-1,PR.PT-3 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-237621r646826_rule |
CCI-000366,CCI-001551 |
3,9,11,14 |
NaN |
NaN |
BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS05.02,DSS05.05,DSS06.06 |
A.9.1.2,A.12.1.2,A.12.5.1,A.12.6.2,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,7.6 |
BP28(R22) |
NaN |
| CCE-83078-6 |
Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv6 Interfaces [ref] |
To set the runtime status of the net.ipv6.conf.all.accept_source_route kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_source_route=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.all.accept_source_route = 0 |
Source-routed packets allow the source of the packet to suggest routersforward the packet along a different path than configured on the router, which canbe used to bypass network security measures. This requirement applies only to theforwarding of source-routerd traffic, such as when IPv6 forwarding is enabled andthe system is functioning as a router.Accepting source-routed packets in the IPv6 protocol has few legitimateuses. It should be disabled unless it is absolutely required. |
medium |
content_rule_sysctl_net_ipv6_conf_all_accept_source_route |
SLES-12-030361 |
CM-7(a),CM-7(b),CM-6(a) |
3.1.20,4.3.3.4,3.3.1 |
ID.AM-3,PR.AC-5,PR.DS-5,PR.PT-4,DE.AE-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217288r603262_rule |
CCI-000366 |
1,4,6,8,9,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,APO13.01,DSS01.05,DSS03.01,DSS05.02,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.12.1.1,A.12.1.2,A.13.1.1,A.13.1.2,A.13.1.3,A.13.2.1,A.13.2.2,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,7.1,SR,7.6 |
BP28(R22) |
4.2.3.4,4.4.3.3 |
| CCE-83247-7 |
Disable Kernel Parameter for IPv6 Forwarding [ref] |
To set the runtime status of the net.ipv6.conf.all.forwarding kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.forwarding=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.all.forwarding = 0 |
IP forwarding permits the kernel to forward packets from one networkinterface to another. The ability to forward packets between two networks isonly appropriate for systems acting as routers. |
medium |
content_rule_sysctl_net_ipv6_conf_all_forwarding |
SLES-12-030364 |
CM-7(a),CM-7(b),CM-6(a),CM-6(b),CM-6.1(iv) |
3.2.1,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.2,4.3.4.3.3 |
PR.DS-4,PR.IP-1,PR.PT-3,DE.CM-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-237622r646829_rule |
CCI-000366 |
1,2,3,7,8,9,11,12,13,14,15,16 |
NaN |
NaN |
APO13.01,BAI04.04,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.03,DSS03.05,DSS05.02,DSS05.05,DSS05.07,DSS06.06 |
A.9.1.2,A.12.1.2,A.12.1.3,A.12.5.1,A.12.6.2,A.14.2.2,A.14.2.3,A.14.2.4,A.17.2.1 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,6.2,SR,7.1,SR,7.2,SR,7.6 |
NaN |
NaN |
| CCE-83223-8 |
Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv6 Interfaces [ref] |
To set the runtime status of the net.ipv6.conf.default.accept_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_redirects=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.default.accept_redirects = 0 |
An illicit ICMP redirect message could result in a man-in-the-middle attack. |
medium |
content_rule_sysctl_net_ipv6_conf_default_accept_redirects |
SLES-12-030401 |
CM-6(b),CM-6.1(iv) |
3.1.20,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,3.3.2,4.3.4.3.2,4.3.4.3.3 |
PR.IP-1,PR.PT-3 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217293r603262_rule |
CCI-000366,CCI-001551 |
3,9,11,14 |
NaN |
NaN |
BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS05.02,DSS05.05,DSS06.06 |
A.9.1.2,A.12.1.2,A.12.5.1,A.12.6.2,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,7.6 |
BP28(R22) |
NaN |
| CCE-83227-9 |
Disable Kernel Parameter for Accepting Source-Routed Packets on IPv6 Interfaces by Default [ref] |
To set the runtime status of the net.ipv6.conf.default.accept_source_route kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_source_route=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.default.accept_source_route = 0 |
Source-routed packets allow the source of the packet to suggest routersforward the packet along a different path than configured on the router, which canbe used to bypass network security measures. This requirement applies only to theforwarding of source-routerd traffic, such as when IPv6 forwarding is enabled andthe system is functioning as a router.Accepting source-routed packets in the IPv6 protocol has few legitimateuses. It should be disabled unless it is absolutely required. |
medium |
content_rule_sysctl_net_ipv6_conf_default_accept_source_route |
SLES-12-030362 |
CM-7(a),CM-7(b),CM-6(a),CM-6(b),CM-6.1(iv) |
3.1.20,4.3.3.4,3.3.1 |
ID.AM-3,PR.AC-5,PR.DS-5,PR.PT-4,DE.AE-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-237620r646823_rule |
CCI-000366 |
1,4,6,8,9,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,APO13.01,DSS01.05,DSS03.01,DSS05.02,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.12.1.1,A.12.1.2,A.13.1.1,A.13.1.2,A.13.1.3,A.13.2.1,A.13.2.2,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,7.1,SR,7.6 |
BP28(R22) |
4.2.3.4,4.4.3.3 |
| CCE-83248-5 |
Disable Kernel Parameter for IPv6 Forwarding by default [ref] |
To set the runtime status of the net.ipv6.conf.default.forwarding kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.forwarding=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.default.forwarding = 0 |
IP forwarding permits the kernel to forward packets from one networkinterface to another. The ability to forward packets between two networks isonly appropriate for systems acting as routers. |
medium |
content_rule_sysctl_net_ipv6_conf_default_forwarding |
SLES-12-030363 |
CM-6(b),CM-6.1(iv) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-237621r646826_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83090-1 |
Disable Accepting ICMP Redirects for All IPv4 Interfaces [ref] |
To set the runtime status of the net.ipv4.conf.all.accept_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.accept_redirects=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.all.accept_redirects = 0 |
ICMP redirect messages are used by routers to inform hosts that a moredirect route exists for a particular destination. These messages modify thehost's route table and are unauthenticated. An illicit ICMP redirectmessage could result in a man-in-the-middle attack.This feature of the IPv4 protocol has few legitimate uses. It should bedisabled unless absolutely required." |
medium |
content_rule_sysctl_net_ipv4_conf_all_accept_redirects |
SLES-12-030390 |
CM-7(a),CM-7(b),CM-6(a),SC-7(a) |
3.1.20,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,3.3.2,4.3.4.3.2,4.3.4.3.3 |
PR.DS-4,PR.IP-1,PR.PT-3,DE.CM-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217291r603262_rule |
CCI-000366,CCI-001503,CCI-001551 |
1,2,3,7,8,9,11,12,13,14,15,16 |
NaN |
NaN |
APO13.01,BAI04.04,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.03,DSS03.05,DSS05.02,DSS05.05,DSS05.07,DSS06.06 |
A.9.1.2,A.12.1.2,A.12.1.3,A.12.5.1,A.12.6.2,A.14.2.2,A.14.2.3,A.14.2.4,A.17.2.1 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,6.2,SR,7.1,SR,7.2,SR,7.6 |
BP28(R22) |
5.10.1.1 |
| CCE-83064-6 |
Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv4 Interfaces [ref] |
To set the runtime status of the net.ipv4.conf.all.accept_source_route kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.accept_source_route=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.all.accept_source_route = 0 |
Source-routed packets allow the source of the packet to suggest routersforward the packet along a different path than configured on the router,which can be used to bypass network security measures. This requirementapplies only to the forwarding of source-routerd traffic, such as when IPv4forwarding is enabled and the system is functioning as a router.Accepting source-routed packets in the IPv4 protocol has few legitimateuses. It should be disabled unless it is absolutely required. |
medium |
content_rule_sysctl_net_ipv4_conf_all_accept_source_route |
SLES-12-030360 |
CM-7(a),CM-7(b),CM-6(a),SC-5,SC-7(a) |
3.1.20,4.3.3.4,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,3.3.1,4.3.4.3.2,4.3.4.3.3 |
ID.AM-3,PR.AC-5,PR.DS-4,PR.DS-5,PR.IP-1,PR.PT-3,PR.PT-4,DE.AE-1,DE.CM-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217287r603262_rule |
CCI-000366 |
1,2,3,4,6,7,8,9,11,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,APO13.01,BAI04.04,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.03,DSS01.05,DSS03.01,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,DSS06.02,DSS06.06 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.12.1.1,A.12.1.2,A.12.1.3,A.12.5.1,A.12.6.2,A.13.1.1,A.13.1.2,A.13.1.3,A.13.2.1,A.13.2.2,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4,A.17.2.1 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.2,SR,7.1,SR,7.2,SR,7.6 |
BP28(R22) |
4.2.3.4,4.4.3.3,CIP-007-3,R4,CIP-007-3,R4.1,CIP-007-3,R4.2,CIP-007-3,R5.1 |
| CCE-83081-0 |
Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv4 Interfaces [ref] |
To set the runtime status of the net.ipv4.conf.default.accept_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.accept_redirects=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.default.accept_redirects = 0 |
ICMP redirect messages are used by routers to inform hosts that a moredirect route exists for a particular destination. These messages modify thehost's route table and are unauthenticated. An illicit ICMP redirectmessage could result in a man-in-the-middle attack.This feature of the IPv4 protocol has few legitimate uses. It shouldbe disabled unless absolutely required. |
medium |
content_rule_sysctl_net_ipv4_conf_default_accept_redirects |
SLES-12-030400 |
CM-7(a),CM-7(b),CM-6(a),SC-7(a) |
3.1.20,4.3.3.4,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,3.3.3,4.3.4.3.2,4.3.4.3.3 |
ID.AM-3,PR.AC-5,PR.DS-4,PR.DS-5,PR.IP-1,PR.PT-3,PR.PT-4,DE.AE-1,DE.CM-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217292r603262_rule |
CCI-000366,CCI-001551 |
1,2,3,4,6,7,8,9,11,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,APO13.01,BAI04.04,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.03,DSS01.05,DSS03.01,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,DSS06.02,DSS06.06 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.12.1.1,A.12.1.2,A.12.1.3,A.12.5.1,A.12.6.2,A.13.1.1,A.13.1.2,A.13.1.3,A.13.2.1,A.13.2.2,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4,A.17.2.1 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.2,SR,7.1,SR,7.2,SR,7.6 |
BP28(R22) |
5.10.1.1,4.2.3.4,4.4.3.3 |
| CCE-83079-4 |
Disable Kernel Parameter for Accepting Source-Routed Packets on IPv4 Interfaces by Default [ref] |
To set the runtime status of the net.ipv4.conf.default.accept_source_route kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.accept_source_route=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.default.accept_source_route = 0 |
Source-routed packets allow the source of the packet to suggest routersforward the packet along a different path than configured on the router,which can be used to bypass network security measures.Accepting source-routed packets in the IPv4 protocol has few legitimateuses. It should be disabled unless it is absolutely required, such as whenIPv4 forwarding is enabled and the system is legitimately functioning as arouter. |
medium |
content_rule_sysctl_net_ipv4_conf_default_accept_source_route |
SLES-12-030370 |
CM-7(a),CM-7(b),SC-5,SC-7(a) |
3.1.20,4.3.3.4,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,3.3.1,4.3.4.3.2,4.3.4.3.3 |
ID.AM-3,PR.AC-5,PR.DS-4,PR.DS-5,PR.IP-1,PR.PT-3,PR.PT-4,DE.AE-1,DE.CM-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217289r603262_rule |
CCI-000366,CCI-001551 |
1,2,3,4,6,7,8,9,11,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,APO13.01,BAI04.04,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.03,DSS01.05,DSS03.01,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,DSS06.02,DSS06.06 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.12.1.1,A.12.1.2,A.12.1.3,A.12.5.1,A.12.6.2,A.13.1.1,A.13.1.2,A.13.1.3,A.13.2.1,A.13.2.2,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4,A.17.2.1 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.2,SR,7.1,SR,7.2,SR,7.6 |
BP28(R22) |
5.10.1.1,4.2.3.4,4.4.3.3,CIP-007-3,R4,CIP-007-3,R4.1,CIP-007-3,R4.2,CIP-007-3,R5.1 |
| CCE-83080-2 |
Enable Kernel Parameter to Ignore ICMP Broadcast Echo Requests on IPv4 Interfaces [ref] |
To set the runtime status of the net.ipv4.icmp_echo_ignore_broadcasts kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.icmp_echo_ignore_broadcasts = 1 |
Responding to broadcast (ICMP) echoes facilitates network mappingand provides a vector for amplification attacks.Ignoring ICMP echo requests (pings) sent to broadcast or multicastaddresses makes the system slightly more difficult to enumerate on the network. |
medium |
content_rule_sysctl_net_ipv4_icmp_echo_ignore_broadcasts |
SLES-12-030380 |
CM-7(a),CM-7(b),SC-5 |
3.1.20,4.3.3.4,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,3.3.5,4.3.4.3.2,4.3.4.3.3 |
ID.AM-3,PR.AC-5,PR.DS-4,PR.DS-5,PR.IP-1,PR.PT-3,PR.PT-4,DE.AE-1,DE.CM-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217290r603262_rule |
CCI-000366 |
1,2,3,4,6,7,8,9,11,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,APO13.01,BAI04.04,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.03,DSS01.05,DSS03.01,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,DSS06.02,DSS06.06 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.12.1.1,A.12.1.2,A.12.1.3,A.12.5.1,A.12.6.2,A.13.1.1,A.13.1.2,A.13.1.3,A.13.2.1,A.13.2.2,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4,A.17.2.1 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.2,SR,7.1,SR,7.2,SR,7.6 |
NaN |
5.10.1.1,4.2.3.4,4.4.3.3,CIP-007-3,R4,CIP-007-3,R4.1,CIP-007-3,R4.2,CIP-007-3,R5.1 |
| CCE-83179-2 |
Enable Kernel Parameter to Use TCP Syncookies on IPv4 Interfaces [ref] |
To set the runtime status of the net.ipv4.tcp_syncookies kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.tcp_syncookies=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.tcp_syncookies = 1 |
A TCP SYN flood attack can cause a denial of service by filling asystem's TCP connection table with connections in the SYN_RCVD state.Syncookies can be used to track a connection when a subsequent ACK is received,verifying the initiator is attempting a valid connection and is not a floodsource. This feature is activated when a flood condition is detected, andenables the system to continue servicing valid connection requests. |
medium |
content_rule_sysctl_net_ipv4_tcp_syncookies |
SLES-12-030350 |
CM-7(a),CM-7(b),CM-6(a),SC-5(1),SC-5(2),SC-5(3)(a) |
3.1.20,4.3.3.4,3.3.8 |
ID.AM-3,PR.AC-5,PR.DS-4,PR.DS-5,PR.PT-4,DE.AE-1,DE.CM-1 |
SRG-OS-000480-GPOS-00227,SRG-OS-000420-GPOS-00186,SRG-OS-000142-GPOS-00071 |
NaN |
SV-217286r603262_rule |
CCI-000366,CCI-001095 |
1,2,4,6,7,8,9,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,APO13.01,BAI04.04,DSS01.03,DSS01.05,DSS03.01,DSS03.05,DSS05.02,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.12.1.1,A.12.1.2,A.12.1.3,A.13.1.1,A.13.1.2,A.13.1.3,A.13.2.1,A.13.2.2,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.17.2.1 |
SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.2,SR,7.1,SR,7.2,SR,7.6 |
BP28(R22) |
5.10.1.1,4.2.3.4,4.4.3.3 |
| CCE-83089-3 |
Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces [ref] |
To set the runtime status of the net.ipv4.conf.all.send_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.send_redirects=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.all.send_redirects = 0 |
ICMP redirect messages are used by routers to inform hosts that a moredirect route exists for a particular destination. These messages contain informationfrom the system's route table possibly revealing portions of the network topology.The ability to send ICMP redirects is only appropriate for systems acting as routers. |
medium |
content_rule_sysctl_net_ipv4_conf_all_send_redirects |
SLES-12-030420 |
CM-7(a),CM-7(b),CM-6(a),SC-5,SC-7(a) |
3.1.20,3.2.2,4.3.3.4,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.2,4.3.4.3.3 |
ID.AM-3,PR.AC-5,PR.DS-4,PR.DS-5,PR.IP-1,PR.PT-3,PR.PT-4,DE.AE-1,DE.CM-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217295r603262_rule |
CCI-000366 |
1,2,3,4,6,7,8,9,11,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,APO13.01,BAI04.04,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.03,DSS01.05,DSS03.01,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,DSS06.02,DSS06.06 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.12.1.1,A.12.1.2,A.12.1.3,A.12.5.1,A.12.6.2,A.13.1.1,A.13.1.2,A.13.1.3,A.13.2.1,A.13.2.2,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4,A.17.2.1 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.2,SR,7.1,SR,7.2,SR,7.6 |
BP28(R22) |
5.10.1.1,4.2.3.4,4.4.3.3,CIP-007-3,R4,CIP-007-3,R4.1,CIP-007-3,R4.2,CIP-007-3,R5.1 |
| CCE-83086-9 |
Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces by Default [ref] |
To set the runtime status of the net.ipv4.conf.default.send_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.send_redirects=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.default.send_redirects = 0 |
ICMP redirect messages are used by routers to inform hosts that a moredirect route exists for a particular destination. These messages contain informationfrom the system's route table possibly revealing portions of the network topology.The ability to send ICMP redirects is only appropriate for systems acting as routers. |
medium |
content_rule_sysctl_net_ipv4_conf_default_send_redirects |
SLES-12-030410 |
CM-7(a),CM-7(b),CM-6(a),SC-5,SC-7(a) |
3.1.20,3.2.2,4.3.3.4,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.2,4.3.4.3.3 |
ID.AM-3,PR.AC-5,PR.DS-4,PR.DS-5,PR.IP-1,PR.PT-3,PR.PT-4,DE.AE-1,DE.CM-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217294r603262_rule |
CCI-000366 |
1,2,3,4,6,7,8,9,11,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,APO13.01,BAI04.04,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.03,DSS01.05,DSS03.01,DSS03.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,DSS06.02,DSS06.06 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.12.1.1,A.12.1.2,A.12.1.3,A.12.5.1,A.12.6.2,A.13.1.1,A.13.1.2,A.13.1.3,A.13.2.1,A.13.2.2,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4,A.17.2.1 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.2,SR,7.1,SR,7.2,SR,7.6 |
BP28(R22) |
5.10.1.1,4.2.3.4,4.4.3.3,CIP-007-3,R4,CIP-007-3,R4.1,CIP-007-3,R4.2,CIP-007-3,R5.1 |
| CCE-83088-5 |
Disable Kernel Parameter for IP Forwarding on IPv4 Interfaces [ref] |
To set the runtime status of the net.ipv4.ip_forward kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.ip_forward=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.ip_forward = 0Warning: Certain technologies such as virtual machines, containers, etc. rely on IPv4 forwarding to enable and use networking. Disabling IPv4 forwarding would cause those technologies to stop working. Therefore, this rule should not be used in profiles or benchmarks that target usage of IPv4 forwarding. |
Routing protocol daemons are typically used on routers to exchangenetwork topology information with other routers. If this capability is used whennot required, system network information may be unnecessarily transmitted acrossthe network. |
medium |
content_rule_sysctl_net_ipv4_ip_forward |
SLES-12-030430 |
CM-7(a),CM-7(b),CM-6(a),SC-5,SC-7(a) |
3.1.20,3.2.1,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.2,4.3.4.3.3 |
PR.DS-4,PR.IP-1,PR.PT-3,PR.PT-4,DE.CM-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217296r646767_rule |
CCI-000366 |
1,2,3,7,8,9,11,12,13,14,15,16 |
NaN |
NaN |
APO13.01,BAI04.04,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.03,DSS03.05,DSS05.02,DSS05.05,DSS05.07,DSS06.06 |
A.9.1.2,A.12.1.2,A.12.1.3,A.12.5.1,A.12.6.2,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4,A.17.2.1 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,6.2,SR,7.1,SR,7.2,SR,7.6 |
BP28(R22) |
CIP-007-3,R4,CIP-007-3,R4.1,CIP-007-3,R4.2,CIP-007-3,R5.1 |
| CCE-83157-8 |
Install SuSEfirewall2 Package [ref] |
The SuSEfirewall2 package can be installed with the following command: $ sudo zypper install SuSEfirewall2 |
The SuSEfirewall2 package should be installed to provide access control methods. |
medium |
content_rule_package_SuSEfirewall2_installed |
SLES-12-030030 |
AC-17(1),CA-3(5),CM-7 |
NaN |
NaN |
SRG-OS-000420-GPOS-00186,SRG-OS-000096-GPOS-00050 |
NaN |
SV-217261r603262_rule |
CCI-000382,CCI-002080,CCI-002314 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83164-4 |
Enable the SuSEfirewall 2 [ref] |
The SuSEfirewall2 service can be enabled with the following command: $ sudo systemctl enable SuSEfirewall2.service |
To prevent unauthorized connection of devices, unauthorized transfer ofinformation, or unauthorized tunneling (i.e., embedding of data typeswithin data types), organizations must disable or restrict unused orunnecessary physical and logical ports/protocols on information systems.SUSE operating systems are capable of providing a wide variety of functionsand services. Some of the functions and services provided by default maynot be necessary to support essential organizational operations.Additionally, it is sometimes convenient to provide multiple services froma single component (e.g., VPN and IPS); however, doing so increases riskover limiting the services provided by any one component. |
medium |
content_rule_service_SuSEfirewall2_enabled |
SLES-12-030030 |
AC-17(1),CA-3(5),CM-7 |
NaN |
NaN |
SRG-OS-000420-GPOS-00186,SRG-OS-000096-GPOS-00050 |
NaN |
SV-217261r603262_rule |
CCI-000382 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83156-0 |
Enable DoS Protections in SuSEfirewall2 [ref] |
The SuSEfirewall2 package can be installed with the following command: $ sudo zypper install SuSEfirewall2 The SuSEfirewall2 service can be enabled with the following command: $ sudo systemctl enable SuSEfirewall2.service Verify "SuSEfirewall2" is configured to protect the SUSE operating system against or limit the effects of DoS attacks. Run the following command: # grep -i fw_services_accept_ext /etc/sysconfig/SuSEfirewall2 FW_SERVICES_ACCEPT_EXT="0/0,tcp,22,,hitcount=3,blockseconds=60,recentname=ssh" If the "FW_SERVICES_ACCEPT_EXT" rule does not contain both the hitcount and blockseconds parameters, this is a finding. |
DoS is a condition when a resource is not available for legitimate users.When this occurs, the organization either cannot accomplish its mission ormust operate at degraded capacity.This requirement addresses the configuration of the SUSE operating system tomitigate the impact on system availability of DoS attacks that have occurredor are ongoing. For each system, known and potential DoS attacks must beidentified and solutions for each type implemented. A variety oftechnologies exist to limit or, in some cases, eliminate the effects ofDoS attacks (e.g., limiting processes or establishing memory partitions).Employing increased capacity and bandwidth, combined with serviceredundancy, may reduce the susceptibility to some DoS attacks. |
medium |
content_rule_susefirewall2_ddos_protection |
SLES-12-030040 |
SC-5 |
NaN |
NaN |
SRG-OS-000420-GPOS-00186 |
NaN |
SV-217262r603262_rule |
CCI-002385 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83165-1 |
Only Allow Authorized Network Services in SuSEfirewall2 [ref] |
The SuSEfirewall2 package can be installed with the following command: $ sudo zypper install SuSEfirewall2 The SuSEfirewall2 service can be enabled with the following command: $ sudo systemctl enable SuSEfirewall2.service Check the firewall configuration for any unnecessary or prohibited functions, ports, protocols, and/or services by running the following command: # grep ^FW_ /etc/sysconfig/SuSEfirewall2 FW_SERVICES_ACCEPT_EXT="0/0,tcp,22,,hitcount=3,blockseconds=60,recentname=ssh" Ask the System Administrator for the site or program PPSM Component Local Services Assessment (Component Local Services Assessment (CLSA). Verify the services allowed by the firewall match the PPSM CLSA. |
To prevent unauthorized connection of devices, unauthorized transfer ofinformation, or unauthorized tunneling (i.e., embedding of data typeswithin data types), organizations must disable or restrict unused orunnecessary physical and logical ports/protocols on information systems.SUSE operating systems are capable of providing a wide variety of functionsand services. Some of the functions and services provided by default may notbe necessary to support essential organizational operations. Additionally,it is sometimes convenient to provide multiple services from a singlecomponent (e.g., VPN and IPS); however, doing so increases risk overlimiting the services provided by any one component.To support the requirements and principles of least functionality, the SUSEoperating system must support the organizational requirements, providingonly essential capabilities and limiting the use of ports, protocols,and/or services to only those required, authorized, and approved to conductofficial business or address authorized quality-of-life issues. |
medium |
content_rule_susefirewall2_only_required_services |
SLES-12-030030 |
AC-17(1),CA-3(5),CM-7 |
NaN |
NaN |
SRG-OS-000096-GPOS-00050,SRG-OS-000297-GPOS-00115,SRG-OS-000480-GPOS-00231,SRG-OS-000480-GPOS-00232 |
NaN |
SV-217261r603262_rule |
CCI-000382 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83148-7 |
Deactivate Wireless Network Interfaces [ref] |
Deactivating wireless network interfaces should prevent normal usage of the wireless capability. Configure the system to disable wireless network interfaces by issuing the following command for every active <WIFI-INTERFACE> in the system: $ sudo wicked ifdown <WIFI-INTERFACE> Also remove the configuration files for every wifi adapter from /etc/wicked/ifconfig/<WIFI-INTERFACE>.xml to prevent future connections. |
The use of wireless networking can introduce many different attack vectors intothe organization's network. Common attack vectors such as malicious associationand ad hoc networks will allow an attacker to spoof a wireless access point(AP), allowing validated systems to connect to the malicious AP and enabling theattacker to monitor and record network traffic. These malicious APs can alsoserve to create a man-in-the-middle attack or be used to create a denial ofservice to valid network resources. |
medium |
content_rule_wireless_disable_interfaces |
SLES-12-030450 |
AC-18(1),SC-8 |
3.1.16,3.1.2,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.2,4.3.4.3.3 |
PR.AC-3,PR.IP-1,PR.PT-3,PR.PT-4 |
SRG-OS-000299-GPOS-00117,SRG-OS-000300-GPOS-00118,SRG-OS-000424-GPOS-00188,SRG-OS-000481-GPOS-000481 |
NaN |
SV-217298r603262_rule |
CCI-000085,CCI-002418,CCI-002421,CCI-001444 |
3,8,9,11,12,14,15 |
NaN |
NaN |
APO13.01,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.04,DSS05.02,DSS05.03,DSS05.05,DSS06.06 |
A.6.2.1,A.6.2.2,A.9.1.2,A.11.2.6,A.12.1.2,A.12.5.1,A.12.6.2,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,7.1,SR,7.6 |
NaN |
1315,1319 |
| CCE-83147-9 |
Ensure System is Not Acting as a Network Sniffer [ref] |
The system should not be acting as a network sniffer, which can capture all traffic on the network to which it is connected. Run the following to determine if any interface is running in promiscuous mode: $ ip link | grep PROMISC Promiscuous mode of an interface can be disabled with the following command: $ sudo ip link set dev device_name multicast off promisc off |
Network interfaces in promiscuous mode allow for the capture of all network trafficvisible to the system. If unauthorized individuals can access these applications, itmay allow them to collect information such as logon IDs, passwords, and key exchangesbetween systems.If the system is being used to perform a network troubleshooting function, the use of thesetools must be documented with the Information Systems Security Manager (ISSM) and restrictedto only authorized personnel. |
medium |
content_rule_network_sniffer_disabled |
SLES-12-030440 |
CM-6(b) |
4.3.3.3.7,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.2,4.3.4.3.3 |
ID.AM-1,PR.IP-1,PR.MA-1,PR.PT-3,DE.DP-5 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217297r603262_rule |
CCI-000366 |
1,3,9,11,14 |
NaN |
NaN |
APO11.06,APO12.06,BAI03.10,BAI09.01,BAI09.02,BAI09.03,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.05,DSS04.05,DSS05.02,DSS05.05,DSS06.06 |
A.8.1.1,A.8.1.2,A.9.1.2,A.11.1.2,A.11.2.4,A.11.2.5,A.11.2.6,A.12.1.2,A.12.5.1,A.12.6.2,A.14.2.2,A.14.2.3,A.14.2.4,A.16.1.6 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,7.6,SR,7.8 |
NaN |
4.2.3.4,4.4.3.4 |
| CCE-83172-7 |
Verify Permissions and Ownership of Old Passwords File [ref] |
To properly set the owner of /etc/security/opasswd, run the command: $ sudo chown root /etc/security/opasswd To properly set the group owner of /etc/security/opasswd, run the command: $ sudo chgrp root /etc/security/opasswd To properly set the permissions of /etc/security/opasswd, run the command: $ sudo chmod 0600 /etc/security/opasswd |
The /etc/security/opasswd file stores old passwords to preventpassword reuse. Protection of this file is critical for system security. |
medium |
content_rule_file_etc_security_opasswd |
SLES-12-010300 |
NaN |
NaN |
NaN |
SRG-OS-000077-GPOS-00045 |
NaN |
SV-217132r603262_rule |
CCI-000200 |
NaN |
NaN |
NaN |
NaN |
IA-5(1)(e),IA-5(1).1(v) |
NaN |
NaN |
NaN |
| CCE-83238-6 |
Verify that Shared Library Directories Have Root Group Ownership [ref] |
System-wide shared library files, which are linked to executables during process load time or run time, are stored in the following directories by default: /lib /lib64 /usr/lib /usr/lib64 Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules. All files in these directories should be group-owned by the root user. If the directories, is found to be owned by a user other than root correct its ownership with the following command: $ sudo chgrp root DIR |
Files from shared library directories are loaded into the addressspace of processes (including privileged ones) or of the kernel itself atruntime. Proper ownership of library directories is necessary to protectthe integrity of the system. |
medium |
content_rule_dir_group_ownership_library_dirs |
SLES-12-010876 |
CM-5(6),CM-5(6).1 |
NaN |
NaN |
SRG-OS-000259-GPOS-00100 |
NaN |
SV-237612r646799_rule |
CCI-001499 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83236-0 |
Verify that Shared Library Directories Have Root Ownership [ref] |
System-wide shared library files, which are linked to executables during process load time or run time, are stored in the following directories by default: /lib /lib64 /usr/lib /usr/lib64 Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules. All files in these directories should be owned by the root user. If the directories, is found to be owned by a user other than root correct its ownership with the following command: $ sudo chown root DIR |
Files from shared library directories are loaded into the addressspace of processes (including privileged ones) or of the kernel itself atruntime. Proper ownership of library directories is necessary to protectthe integrity of the system. |
medium |
content_rule_dir_ownership_library_dirs |
SLES-12-010874 |
CM-5(6),CM-5(6).1 |
NaN |
NaN |
SRG-OS-000259-GPOS-00100 |
NaN |
SV-237610r646793_rule |
CCI-001499 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83234-5 |
Verify that Shared Library Directories Have Restrictive Permissions [ref] |
System-wide shared library directories, which contain are linked to executables during process load time or run time, are stored in the following directories by default: /lib /lib64 /usr/lib /usr/lib64 Kernel modules, which can be added to the kernel during runtime, are stored in /lib/modules. All sub-directories in these directories should not be group-writable or world-writable. If any file in these directories is found to be group-writable or world-writable, correct its permission with the following command: $ sudo chmod go-w DIR |
If the operating system were to allow any user to make changes to software libraries,then those changes might be implemented without undergoing the appropriate testingand approvals that are part of a robust change management process.This requirement applies to operating systems with software libraries that are accessibleand configurable, as in the case of interpreted languages. Software libraries also includeprivileged programs which execute with escalated privileges. Only qualified and authorizedindividuals must be allowed to obtain access to information system components for purposesof initiating changes, including upgrades and modifications. |
medium |
content_rule_dir_permissions_library_dirs |
SLES-12-010872 |
CM-5,CM-5(6),CM-5(6).1 |
CIP-003-3,R6 |
NaN |
NaN |
NaN |
SV-237608r646787_rule |
CCI-001499 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83243-6 |
Verify that system commands files are group owned by root [ref] |
System commands files are stored in the following directories by default: /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin All files in these directories should be owned by the root group. If the directory, or any file in these directories, is found to be owned by a group other than root correct its ownership with the following command: $ sudo chgrp root FILE |
If the operating system allows any user to make changes to softwarelibraries, then those changes might be implemented without undergoing theappropriate testing and approvals that are part of a robust change managementprocess.This requirement applies to operating systems with software librariesthat are accessible and configurable, as in the case of interpreted languages.Software libraries also include privileged programs which execute withescalated privileges. Only qualified and authorized individuals must beallowed to obtain access to information system components for purposesof initiating changes, including upgrades and modifications. |
medium |
content_rule_file_groupownership_system_commands_dirs |
SLES-12-010882 |
CM-5(6),CM-5(6).1 |
NaN |
NaN |
SRG-OS-000259-GPOS-00100 |
NaN |
SV-237617r646814_rule |
CCI-001499 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83241-0 |
Verify that System Executables Have Root Ownership [ref] |
System executables are stored in the following directories by default: /bin /sbin /usr/bin /usr/libexec /usr/local/bin /usr/local/sbin /usr/sbin All files in these directories should be owned by the root user. If any file FILE in these directories is found to be owned by a user other than root, correct its ownership with the following command: $ sudo chown root FILE |
System binaries are executed by privileged users as well as system services,and restrictive permissions are necessary to ensure that theirexecution of these programs cannot be co-opted. |
medium |
content_rule_file_ownership_binary_dirs |
SLES-15-010879 |
AC-6(1),CM-5(6),CM-5(6).1,CM-6(a) |
4.3.3.7.3,CIP-003-3,R5.1.1,CIP-003-3,R5.3 |
PR.AC-4,PR.DS-5 |
SRG-OS-000259-GPOS-00100 |
NaN |
NaN |
CCI-001499 |
3,5,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
NaN |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2 |
| CCE-83235-2 |
Verify that Shared Library Files Have Root Ownership [ref] |
System-wide shared library files, which are linked to executables during process load time or run time, are stored in the following directories by default: /lib /lib64 /usr/lib /usr/lib64 Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules. All files in these directories should be owned by the root user. If the directory, or any file in these directories, is found to be owned by a user other than root correct its ownership with the following command: $ sudo chown root FILE |
Files from shared library directories are loaded into the addressspace of processes (including privileged ones) or of the kernel itself atruntime. Proper ownership is necessary to protect the integrity of the system. |
medium |
content_rule_file_ownership_library_dirs |
SLES-12-010873 |
AC-6(1),CM-5(6),CM-5(6).1,CM-6(a) |
4.3.3.7.3,CIP-003-3,R5.1.1,CIP-003-3,R5.3 |
PR.AC-4,PR.DS-5 |
SRG-OS-000259-GPOS-00100 |
NaN |
SV-237609r646790_rule |
CCI-001499 |
3,5,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
NaN |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2 |
| CCE-83240-2 |
Verify that System Executables Have Restrictive Permissions [ref] |
System executables are stored in the following directories by default: /bin /sbin /usr/bin /usr/libexec /usr/local/bin /usr/local/sbin /usr/sbin All files in these directories should not be group-writable or world-writable. If any file FILE in these directories is found to be group-writable or world-writable, correct its permission with the following command: $ sudo chmod go-w FILE |
System binaries are executed by privileged users, as well as system services,and restrictive permissions are necessary to ensure execution of these programscannot be co-opted. |
medium |
content_rule_file_permissions_binary_dirs |
SLES-12-010878 |
AC-6(1),CM-5(6),CM-5(6).1,CM-6(a) |
4.3.3.7.3,CIP-003-3,R5.1.1,CIP-003-3,R5.3 |
PR.AC-4,PR.DS-5 |
SRG-OS-000259-GPOS-00100 |
NaN |
SV-237614r646805_rule |
CCI-001499 |
3,5,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
NaN |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2 |
| CCE-83233-7 |
Verify that Shared Library Files Have Restrictive Permissions [ref] |
System-wide shared library files, which are linked to executables during process load time or run time, are stored in the following directories by default: /lib /lib64 /usr/lib /usr/lib64 Kernel modules, which can be added to the kernel during runtime, are stored in /lib/modules. All files in these directories should not be group-writable or world-writable. If any file in these directories is found to be group-writable or world-writable, correct its permission with the following command: $ sudo chmod go-w FILE |
Files from shared library directories are loaded into the addressspace of processes (including privileged ones) or of the kernel itself atruntime. Restrictive permissions are necessary to protect the integrity of the system. |
medium |
content_rule_file_permissions_library_dirs |
SLES-12-010871 |
AC-6(1),CM-6(a),CM-5(6),CM-5(6).1 |
4.3.3.7.3,CIP-003-3,R5.1.1,CIP-003-3,R5.3 |
PR.AC-4,PR.DS-5 |
SRG-OS-000259-GPOS-00100 |
NaN |
SV-237607r646784_rule |
CCI-001499 |
3,5,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
NaN |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2 |
| CCE-83239-4 |
Verify that system commands are protected from unauthorized access [ref] |
System commands are stored in the following directories by default: /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin All files in these directories should not be group-writable or world-writable. If any file FILE in these directories is found to be group-writable or world-writable, correct its permission with the following command: $ sudo chmod 755 FILE |
System binaries are executed by privileged users, as well as system services,and restrictive permissions are necessary to ensure execution of these programscannot be co-opted. |
medium |
content_rule_file_permissions_system_commands_dirs |
SLES-12-010877 |
CM-5(6),CM-5(6).1 |
NaN |
NaN |
SRG-OS-000259-GPOS-00100 |
NaN |
SV-237613r646802_rule |
CCI-001499 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83237-8 |
Verify the system-wide library files in directories"/lib", "/lib64", "/usr/lib/" and "/usr/lib64" are owned by root. [ref] |
System-wide library files are stored in the following directories by default: /lib /lib64 /usr/lib /usr/lib64 All system-wide shared library files should be protected from unauthorised access. If any of these files is not owned by root, correct its owner with the following command: $ sudo chgrp root FILE |
If the operating system were to allow any user to make changes to software libraries,then those changes might be implemented without undergoing the appropriate testing andapprovals that are part of a robust change management process.This requirement applies to operating systems with software libraries that areaccessible and configurable, as in the case of interpreted languages. Software librariesalso include privileged programs which execute with escalated privileges. Only qualifiedand authorized individuals must be allowed to obtain access to information system componentsfor purposes of initiating changes, including upgrades and modifications. |
medium |
content_rule_root_permissions_syslibrary_files |
SLES-12-010875 |
CM-5(6),CM-5(6).1 |
NaN |
NaN |
SRG-OS-000259-GPOS-00100 |
NaN |
SV-237611r646796_rule |
CCI-001499 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83047-1 |
Verify that All World-Writable Directories Have Sticky Bits Set [ref] |
When the so-called 'sticky bit' is set on a directory, only the owner of a given file may remove that file from the directory. Without the sticky bit, any user with write access to a directory may remove any file in the directory. Setting the sticky bit prevents users from removing each other's files. In cases where there is no reason for a directory to be world-writable, a better solution is to remove that permission rather than to set the sticky bit. However, if a directory is used by a particular application, consult that application's documentation instead of blindly changing modes. To set the sticky bit on a world-writable directory DIR, run the following command: $ sudo chmod +t DIR |
Failing to set the sticky bit on public directories allows unauthorizedusers to delete files in the directory structure.The only authorized public directories are those temporary directoriessupplied with the system, or those designed to be temporary filerepositories. The setting is normally reserved for directories used by thesystem, by users for temporary file storage (such as /tmp), andfor directories requiring global read/write access. |
medium |
content_rule_dir_perms_world_writable_sticky_bits |
SLES-12-010460 |
AC-6(1),CM-6(a) |
4.3.3.7.3,CIP-003-3,R5.1.1,CIP-003-3,R5.3 |
PR.AC-4,PR.DS-5 |
SRG-OS-000138-GPOS-00069 |
NaN |
SV-217147r603262_rule |
CCI-001090 |
3,5,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
BP28(R40) |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2,1.1.22 |
| CCE-83104-0 |
Ensure All World-Writable Directories Are Group Owned by a System Account [ref] |
All directories in local partitions which are world-writable should be group owned by root or another system account. If any world-writable directories are not group owned by a system account, this should be investigated. Following this, the files should be deleted or assigned to an appropriate group. |
Allowing a user account to group own a world-writable directory isundesirable because it allows the owner of that directory to removeor replace any files that may be placed in the directory by otherusers. |
medium |
content_rule_dir_perms_world_writable_system_owned_group |
SLES-12-010830 |
CM-6(b) |
4.3.3.7.3 |
PR.AC-4,PR.DS-5 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217182r603262_rule |
CCI-000366 |
3,5,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
NaN |
NaN |
| CCE-83244-4 |
Verify that system commands directories have root as a group owner [ref] |
System commands are stored in the following directories: by default: /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin All these directories should have root user as a group owner. If any system command directory is not group owned by a user other than root correct its ownership with the following command: $ sudo chgrp root DIR |
If the operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.This requirement applies to operating systems with software librariesthat are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. |
medium |
content_rule_dir_system_commands_group_root_owned |
SLES-12-010883 |
CM-5(6),CM-5(6).1 |
NaN |
NaN |
SRG-OS-000259-GPOS-00100 |
NaN |
SV-237618r646817_rule |
CCI-001499 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83242-8 |
Verify that system commands directories have root ownership [ref] |
System commands are stored in the following directories by default: /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin All these directories should be owned by the root user. If any system command directory is not owned by a user other than root correct its ownership with the following command: $ sudo chown root DIR |
If the operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.This requirement applies to operating systems with software librariesthat are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. |
medium |
content_rule_dir_system_commands_root_owned |
SLES-15-010881 |
CM-5(6),CM-5(6).1 |
NaN |
NaN |
SRG-OS-000259-GPOS-00100 |
NaN |
NaN |
CCI-001499 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83073-7 |
Ensure All Files Are Owned by a Group [ref] |
If any files are not owned by a group, then the cause of their lack of group-ownership should be investigated. Following this, the files should be deleted or assigned to an appropriate group. The following command will discover and print any files on local partitions which do not belong to a valid group: $ df --local -P | awk '{if (NR!=1) print $6}' | sudo xargs -I '{}' find '{}' -xdev -nogroup To search all filesystems on a system including network mounted filesystems the following command can be run manually for each partition: $ sudo find PARTITION -xdev -nogroupWarning: This rule only considers local groups. If you have your groups defined outside /etc/group, the rule won't consider those. |
Unowned files do not directly imply a security problem, but they are generallya sign that something is amiss. They maybe caused by an intruder, by incorrect software installation ordraft software removal, or by failure to remove all files belongingto a deleted account. The files should be repaired so theywill not cause problems when accounts are created in the future,and the cause should be discovered and addressed. |
medium |
content_rule_file_permissions_ungroupowned |
SLES-12-010700 |
AC-6(1),CM-6(a) |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4 |
PR.AC-1,PR.AC-4,PR.AC-6,PR.AC-7,PR.DS-5,PR.PT-3 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217169r603262_rule |
CCI-000366,CCI-002165 |
1,3,5,11,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,DSS05.02,DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.02,DSS06.03,DSS06.06,DSS06.10 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,5.2 |
NaN |
6.1.10 |
| CCE-83072-9 |
Ensure All Files Are Owned by a User [ref] |
If any files are not owned by a user, then the cause of their lack of ownership should be investigated. Following this, the files should be deleted or assigned to an appropriate user. The following command will discover and print any files on local partitions which do not belong to a valid user: $ df --local -P | awk {'if (NR!=1) print $6'} | sudo xargs -I '{}' find '{}' -xdev -nouser To search all filesystems on a system including network mounted filesystems the following command can be run manually for each partition: $ sudo find PARTITION -xdev -nouserWarning: For this rule to evaluate centralized user accounts, getent must be working properly so that running the command getent passwd returns a list of all users in your organization. If using the System Security Services Daemon (SSSD), enumerate = true must be configured in your organization's domain to return a complete list of usersWarning: Enabling this rule will result in slower scan times depending on the size of your organization and number of centralized users. |
Unowned files do not directly imply a security problem, but they are generallya sign that something is amiss. They maybe caused by an intruder, by incorrect software installation ordraft software removal, or by failure to remove all files belongingto a deleted account. The files should be repaired so theywill not cause problems when accounts are created in the future,and the cause should be discovered and addressed. |
medium |
content_rule_no_files_unowned_by_user |
SLES-12-010690 |
AC-6(1),CM-6(a) |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.2,4.3.4.3.3 |
PR.AC-4,PR.AC-6,PR.DS-5,PR.IP-1,PR.PT-3 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217168r603262_rule |
CCI-000366,CCI-002165 |
3,5,9,11,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,DSS06.02,DSS06.03,DSS06.06 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.1,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.12.1.2,A.12.5.1,A.12.6.2,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,5.2,SR,7.6 |
NaN |
6.1.9 |
| CCE-83070-3 |
Disable the Automounter [ref] |
The autofs daemon mounts and unmounts filesystems, such as user home directories shared via NFS, on demand. In addition, autofs can be used to handle removable media, and the default configuration provides the cdrom device as /misc/cd. However, this method of providing access to removable media is not common, so autofs can almost always be disabled if NFS is not in use. Even if NFS is required, it may be possible to configure filesystem mounts statically by editing /etc/fstab rather than relying on the automounter. The autofs service can be disabled with the following command: $ sudo systemctl mask --now autofs.service |
Disabling the automounter permits the administrator tostatically control filesystem mounting through /etc/fstab.Additionally, automatically mounting filesystems permits easy introduction ofunknown devices, thereby facilitating malicious activity. |
medium |
content_rule_service_autofs_disabled |
SLES-12-010590 |
CM-7(a),CM-7(b),CM-6(a),MP-7 |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.4,3.4.6 |
PR.AC-1,PR.AC-3,PR.AC-6,PR.AC-7 |
SRG-OS-000114-GPOS-00059,SRG-OS-000378-GPOS-00163,SRG-OS-000480-GPOS-00227 |
NaN |
SV-217156r603262_rule |
CCI-000366,CCI-000778,CCI-001958 |
1,5,12,15,16 |
NaN |
164.308(a)(3)(i),164.308(a)(3)(ii)(A),164.310(d)(1),164.310(d)(2),164.312(a)(1),164.312(a)(2)(iv),164.312(b) |
APO13.01,DSS01.04,DSS05.03,DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10 |
A.6.2.1,A.6.2.2,A.7.1.1,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.2,A.9.4.3,A.11.2.6,A.13.1.1,A.13.2.1,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.6 |
NaN |
1.1.23 |
| CCE-83069-5 |
Disable Modprobe Loading of USB Storage Driver [ref] |
To prevent USB storage devices from being used, configure the kernel module loading system to prevent automatic loading of the USB storage driver. To configure the system to prevent the usb-storage kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install usb-storage /bin/true This will prevent the modprobe program from loading the usb-storage module, but will not prevent an administrator (or another program) from using the insmod program to load the module manually. |
USB storage devices such as thumb drives can be used to introducemalicious software. |
medium |
content_rule_kernel_module_usb-storage_disabled |
SLES-12-010580 |
CM-7(a),CM-7(b),CM-6(a),MP-7 |
3.1.21,4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.4 |
PR.AC-1,PR.AC-3,PR.AC-6,PR.AC-7 |
SRG-OS-000114-GPOS-00059,SRG-OS-000378-GPOS-00163,SRG-OS-000480-GPOS-00227 |
NaN |
SV-217155r603262_rule |
CCI-000366,CCI-000778,CCI-001958 |
1,5,12,15,16 |
NaN |
164.308(a)(3)(i),164.308(a)(3)(ii)(A),164.310(d)(1),164.310(d)(2),164.312(a)(1),164.312(a)(2)(iv),164.312(b) |
APO13.01,DSS01.04,DSS05.03,DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10 |
A.6.2.1,A.6.2.2,A.7.1.1,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.2,A.9.4.3,A.11.2.6,A.13.1.1,A.13.2.1,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.6 |
NaN |
NaN |
| CCE-83100-8 |
Add nosuid Option to /home [ref] |
The nosuid mount option can be used to prevent execution of setuid programs in /home. The SUID and SGID permissions should not be required in these user data directories. Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of /home. |
The presence of SUID and SGID executables should be tightly controlled. Usersshould not be able to execute SUID or SGID binaries from user home directory partitions. |
medium |
content_rule_mount_option_home_nosuid |
SLES-12-010790 |
AC-6,AC-6(1),CM-7(a),CM-7(b),CM-6(a),MP-7 |
4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,CIP-003-3,R5.1.1,CIP-003-3,R5.3,4.3.4.3.2,4.3.4.3.3 |
PR.IP-1,PR.PT-2,PR.PT-3 |
SRG-OS-000368-GPOS-00154,SRG-OS-000480-GPOS-00227 |
NaN |
SV-217178r603891_rule |
CCI-000366 |
3,8,9,11,13,14 |
NaN |
NaN |
APO13.01,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS05.02,DSS05.05,DSS05.06,DSS06.06 |
A.8.2.1,A.8.2.2,A.8.2.3,A.8.3.1,A.8.3.3,A.9.1.2,A.11.2.9,A.12.1.2,A.12.5.1,A.12.6.2,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,7.6 |
BP28(R12) |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2 |
| CCE-83101-6 |
Add nosuid Option to Removable Media Partitions [ref] |
The nosuid mount option prevents set-user-identifier (SUID) and set-group-identifier (SGID) permissions from taking effect. These permissions allow users to execute binaries with the same permissions as the owner and group of the file respectively. Users should not be allowed to introduce SUID and SGID files into the system via partitions mounted from removeable media. Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of any removable media partitions. |
The presence of SUID and SGID executables should be tightly controlled. Allowingusers to introduce SUID or SGID binaries from partitions mounted off ofremovable media would allow them to introduce their own highly-privileged programs. |
medium |
content_rule_mount_option_nosuid_removable_partitions |
SLES-12-010800 |
AC-6,AC-6(1),CM-7(a),CM-7(b),CM-6(a),MP-7 |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,CIP-003-3,R5.1.1,CIP-003-3,R5.3,4.3.4.3.2,4.3.4.3.3 |
PR.AC-3,PR.AC-4,PR.AC-6,PR.DS-5,PR.IP-1,PR.PT-2,PR.PT-3 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217179r603262_rule |
CCI-000366 |
3,5,8,9,11,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,APO13.01,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.04,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.06,DSS05.07,DSS06.02,DSS06.03,DSS06.06 |
A.6.1.2,A.6.2.1,A.6.2.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.1,A.8.2.2,A.8.2.3,A.8.3.1,A.8.3.3,A.9.1.1,A.9.1.2,A.9.2.1,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.11.2.6,A.11.2.9,A.12.1.2,A.12.5.1,A.12.6.2,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,5.2,SR,7.6 |
NaN |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2,1.1.21 |
| CCE-83112-3 |
Verify that local /var/log/messages is not world-readable [ref] |
Files containing sensitive informations should be protected by restrictive permissions. Most of the time, there is no need that these files need to be read by any non-root user To properly set the permissions of /var/log/messages, run the command: $ sudo chmod 0640 /var/log/messages Check that "permissions.local" file contains the correct permissions rules with the following command: # grep -i messages /etc/permissions.local /var/log/messages root:root 640 |
The /var/log/messages file contains system error messages. Onlyauthorized personnel should be aware of errors and the details of theerrors. Error messages are an indicator of an organization's operationalstate or can identify the SUSE operating system or platform. Additionally,Personally Identifiable Information (PII) and operational information mustnot be revealed through error messages to unauthorized personnel or theirdesignated representatives. |
medium |
content_rule_file_permissions_local_var_log_messages |
SLES-12-010890 |
SI-11(c) |
NaN |
NaN |
SRG-OS-000206-GPOS-00084 |
NaN |
SV-217188r646734_rule |
CCI-001314 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83118-0 |
Verify Permissions of Local Logs of audit Tools [ref] |
The SUSE operating system audit tools must have the proper permissions configured to protect against unauthorized access. Check that "permissions.local" file contains the correct permissions rules with the following command: grep "^/usr/sbin/au" /etc/permissions.local /usr/sbin/audispd root:root 0750 /usr/sbin/auditctl root:root 0750 /usr/sbin/auditd root:root 0750 /usr/sbin/ausearch root:root 0755 /usr/sbin/aureport root:root 0755 /usr/sbin/autrace root:root 0750 /usr/sbin/augenrules root:root 0750 Audit tools include but are not limited to vendor-provided and open-source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators. |
Protecting audit information also includes identifying and protecting thetools used to view and manipulate log data. Therefore, protecting audittools is necessary to prevent unauthorized operation on audit information.SUSE operating systems providing tools to interface with audit informationwill leverage user permissions and roles identifying the user accessing thetools and the corresponding rights the user enjoys to make access decisionsregarding the access to audit tools. |
medium |
content_rule_permissions_local_audit_binaries |
SLES-12-020130 |
AU-9 |
NaN |
NaN |
SRG-OS-000256-GPOS-00097,SRG-OS-000257-GPOS-00098,SRG-OS-000258-GPOS-00099 |
NaN |
SV-217203r646743_rule |
CCI-001493,CCI-001494,CCI-001495 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83117-2 |
Verify that Local Logs of the audit Daemon are not World-Readable [ref] |
Files containing sensitive informations should be protected by restrictive permissions. Most of the time, there is no need that these files need to bei read by any non-root user. Check that "permissions.local" file contains the correct permissions rules with the following command: # grep -i audit /etc/permissions.local /var/log/audit/ root:root 600 /var/log/audit/audit.log root:root 600 /etc/audit/audit.rules root:root 640 /etc/audit/rules.d/audit.rules root:root 640 |
Without the capability to restrict which roles and individuals can selectwhich events are audited, unauthorized personnel may be able to prevent theauditing of critical events. Misconfigured audits may degrade the system'sperformance by overwhelming the audit log. Misconfigured audits may alsomake it more difficult to establish, correlate, and investigate the eventsrelating to an incident or identify those responsible for one. |
medium |
content_rule_permissions_local_var_log_audit |
SLES-12-020120 |
AU-9 |
NaN |
NaN |
SRG-OS-000057-GPOS-00027,SRG-OS-000058-GPOS-00028,SRG-OS-000059-GPOS-00029 |
NaN |
SV-217202r603262_rule |
CCI-000164 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83111-5 |
OS commands and libraries must have the proper permissions to protect from unauthorized access [ref] |
Verify that the SUSE operating system prevents unauthorized users from accessing system command and library files. Check that all of the audit information files and folders have the correct permissions with the following command: # sudo chkstat --warn --system Set the correct permissions with the following command: # sudo chkstat --set --system |
If the SUSE operating system were to allow any user to make changes tosoftware libraries, those changes might be implemented without undergoingthe appropriate testing and approvals that are part of a robust changemanagement process.This requirement applies to SUSE operating systems with software librariesthat are accessible and configurable, as in the case of interpretedlanguages. Software libraries also include privileged programs that executewith escalated privileges. Only qualified and authorized individuals mustbe allowed to obtain access to information system components to initiatechanges, including upgrades and modifications. |
medium |
content_rule_run_chkstat |
SLES-12-010880 |
CM-5(6) |
NaN |
NaN |
SRG-OS-000259-GPOS-00100 |
NaN |
NaN |
CCI-001499 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83125-5 |
Restrict Exposed Kernel Pointer Addresses Access [ref] |
To set the runtime status of the kernel.kptr_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.kptr_restrict=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kptr_restrict = 1 |
Exposing kernel pointers (through procfs or seq_printf()) exposeskernel writeable structures that can contain functions pointers. If a write vulnereability occursin the kernel allowing a write access to any of this structure, the kernel can be compromise. Thisoption disallow any program withtout the CAP_SYSLOG capability from getting the kernel pointers addresses,replacing them with 0. |
medium |
content_rule_sysctl_kernel_kptr_restrict |
SLES-12-030320 |
CM-6(a),SC-30,SC-30(2),SC-30(5) |
CIP-003-3,R5.1.1,CIP-003-3,R5.3,CIP-004-3,4.1,CIP-004-3,4.2 |
NaN |
SRG-OS-000132-GPOS-00067,SRG-OS-000433-GPOS-00192,SRG-OS-000480-GPOS-00227 |
NaN |
SV-217283r646761_rule |
CCI-002824,CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
BP28(R23) |
CIP-002-3,R1.1,CIP-002-3,R1.2,CIP-004-3,R2.2.3,CIP-004-3,R2.2.4,CIP-004-3,R2.3,CIP-004-3,R4,CIP-005-3a,R1,CIP-005-3a,R1.1,CIP-005-3a,R1.2,CIP-007-3,R3,CIP-007-3,R3.1,CIP-007-3,R5.1,CIP-007-3,R5.1.2,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3,CIP-007-3,R8.4,CIP-009-3,R.1.1,CIP-009-3,R4 |
| CCE-83146-1 |
Enable Randomized Layout of Virtual Address Space [ref] |
To set the runtime status of the kernel.randomize_va_space kernel parameter, run the following command: $ sudo sysctl -w kernel.randomize_va_space=2 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.randomize_va_space = 2 |
Address space layout randomization (ASLR) makes it more difficult for anattacker to predict the location of attack code they have introduced into aprocess's address space during an attempt at exploitation. Additionally,ASLR makes it more difficult for an attacker to know the location ofexisting code in order to re-purpose it using return oriented programming(ROP) techniques. |
medium |
content_rule_sysctl_kernel_randomize_va_space |
SLES-12-030330 |
CM-6(a),SC-30,SC-30(2) |
3.1.7,CIP-003-3,R5.1.1,CIP-003-3,R5.3,CIP-004-3,4.1,CIP-004-3,4.2 |
NaN |
SRG-OS-000433-GPOS-00193,SRG-OS-000480-GPOS-00227 |
NaN |
SV-217284r646764_rule |
CCI-000366,CCI-002824 |
NaN |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3),164.308(a)(4),164.310(b),164.310(c),164.312(a),164.312(e) |
NaN |
NaN |
NaN |
BP28(R23) |
CIP-002-3,R1.1,CIP-002-3,R1.2,CIP-004-3,R2.2.3,CIP-004-3,R2.2.4,CIP-004-3,R2.3,CIP-004-3,R4,CIP-005-3a,R1,CIP-005-3a,R1.1,CIP-005-3a,R1.2,CIP-007-3,R3,CIP-007-3,R3.1,CIP-007-3,R5.1,CIP-007-3,R5.1.2,CIP-007-3,R5.1.3,CIP-007-3,R5.2.1,CIP-007-3,R5.2.3,CIP-007-3,R8.4,CIP-009-3,R.1.1,CIP-009-3,R4,1.5.3 |
| CCE-83105-7 |
Disable KDump Kernel Crash Analyzer (kdump) [ref] |
The kdump service provides a kernel crash dump analyzer. It uses the kexec system call to boot a secondary kernel ("capture" kernel) following a system crash, which can load information from the crashed kernel for analysis. The kdump service can be disabled with the following command: $ sudo systemctl mask --now kdump.service |
Kernel core dumps may contain the full contents of system memory at thetime of the crash. Kernel core dumps consume a considerable amount of diskspace and may result in denial of service by exhausting the available spaceon the target file system partition. Unless the system is used for kerneldevelopment or testing, there is little need to run the kdump service. |
medium |
content_rule_service_kdump_disabled |
SLES-12-010840 |
CM-7(a),CM-7(b),CM-6(a) |
4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.2,4.3.4.3.3 |
PR.AC-3,PR.IP-1,PR.PT-3,PR.PT-4 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217183r603262_rule |
CCI-000366 |
3,8,9,11,12,14,15 |
NaN |
164.308(a)(1)(ii)(D),164.308(a)(3),164.308(a)(4),164.310(b),164.310(c),164.312(a),164.312(e) |
APO13.01,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.04,DSS05.02,DSS05.03,DSS05.05,DSS06.06 |
A.6.2.1,A.6.2.2,A.9.1.2,A.11.2.6,A.12.1.2,A.12.5.1,A.12.6.2,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,7.1,SR,7.6 |
NaN |
FMT_SMF_EXT.1.1 |
| CCE-83226-1 |
Uninstall vsftpd Package [ref] |
The vsftpd package can be removed with the following command: $ sudo zypper remove vsftpd |
Removing the vsftpd package decreases the risk of itsaccidental activation. |
high |
content_rule_package_vsftpd_removed |
SLES-12-030011 |
CM-7(a),CM-7(b),CM-6(a),CM-7,CM-7.1(ii) |
4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.2,4.3.4.3.3 |
PR.IP-1,PR.PT-3 |
SRG-OS-000074-GPOS-00042,SRG-OS-000095-GPOS-00049,SRG-OS-000480-GPOS-00227 |
NaN |
SV-237619r646820_rule |
CCI-000197,CCI-000366,CCI-000381 |
3,9,11,14 |
NaN |
NaN |
BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS05.02,DSS05.05,DSS06.06 |
IA-5(1)(c),IA-5(1).1(v),A.9.1.2,A.12.1.2,A.12.5.1,A.12.6.2,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,7.6 |
NaN |
2.2.8 |
| CCE-83059-6 |
Create Warning Banners for All FTP Users [ref] |
Edit the vsftpd configuration file, which resides at /etc/vsftpd.conf by default. Add or correct the following configuration options: banner_file=/etc/issue |
This setting will cause the system greeting banner to be used for FTP connections as well. |
medium |
content_rule_ftp_present_banner |
SLES-12-030010 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
CCI-000048 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83031-5 |
Configure System to Forward All Mail For The Root Account [ref] |
Make sure that mails delivered to root user are forwarded to a monitored email address. Make sure that the address system.administrator@mail.mil is a valid email address reachable from the system in question. Use the following command to configure the alias: $ sudo echo "root: system.administrator@mail.mil" >> /etc/aliases $ sudo newaliases |
A number of system services utilize email messages sent to the root user tonotify system administrators of active or impending issues. These messages mustbe forwarded to at least one monitored email address. |
low |
content_rule_postfix_client_configure_mail_alias |
SLES-12-020050 |
AU-5(a),AU-5.1(ii) |
NaN |
NaN |
SRG-OS-000046-GPOS-00022 |
NaN |
SV-217195r646740_rule |
CCI-000139,CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
BP28(R49) |
NaN |
| CCE-83103-2 |
Mount Remote Filesystems with noexec [ref] |
Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of any NFS mounts. |
The noexec mount option causes the system not to execute binary files. This option must be usedfor mounting any file system not containing approved binary files as they may be incompatible. Executingfiles from untrusted file systems increases the opportunity for unprivileged users to attain unauthorizedadministrative access. |
medium |
content_rule_mount_option_noexec_remote_filesystems |
SLES-12-010820 |
AC-6,AC-6(8),AC-6(10),CM-6(a) |
4.3.3.7.3 |
PR.AC-4,PR.DS-5 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217181r603262_rule |
CCI-000366 |
3,5,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
NaN |
NaN |
| CCE-83102-4 |
Mount Remote Filesystems with nosuid [ref] |
Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of any NFS mounts. |
NFS mounts should not present suid binaries to users. Only vendor-supplied suid executablesshould be installed to their default location on the local filesystem. |
medium |
content_rule_mount_option_nosuid_remote_filesystems |
SLES-12-010810 |
AC-6,AC-6(1) |
4.3.3.7.3 |
PR.AC-4,PR.DS-5 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217180r603262_rule |
CCI-000366 |
3,5,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
NaN |
CM6(a) |
| CCE-83124-8 |
Configure Time Service Maxpoll Interval [ref] |
The maxpoll should be configured to 10 in /etc/ntp.conf or /etc/chrony.conf to continuously poll time servers. To configure maxpoll in /etc/ntp.conf or /etc/chrony.conf add the following: maxpoll 10 |
Inaccurate time stamps make it more difficult to correlateevents and can lead to an inaccurate analysis. Determining the correcttime a particular event occurred on a system is critical when conductingforensic analysis and investigating system events. Sources outside theconfigured acceptable allowance (drift) may be inaccurate. |
medium |
content_rule_chronyd_or_ntpd_set_maxpoll |
SLES-12-030300 |
AU-8(1)(a),AU-8(1)(b) |
4.3.3.3.9,4.3.3.5.8,4.3.4.4.7 |
PR.PT-1 |
SRG-OS-000355-GPOS-00143,SRG-OS-000356-GPOS-00144,SRG-OS-000359-GPOS-00146 |
NaN |
SV-217281r646755_rule |
CCI-001891,CCI-002046 |
1,3,5,6,14,15,16 |
NaN |
NaN |
APO11.04,BAI03.05,DSS05.04,DSS05.07,MEA02.01 |
A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1 |
SR,2.10,SR,2.11,SR,2.12,SR,2.8,SR,2.9 |
NaN |
4.4.2.1,4.4.2.2,4.4.2.4 |
| CCE-83022-4 |
Remove Host-Based Authentication Files [ref] |
The shosts.equiv file list remote hosts and users that are trusted by the local system. To remove these files, run the following command to delete them from any location: $ sudo rm /[path]/[to]/[file]/shosts.equiv |
The shosts.equiv files are used to configure host-based authentication for thesystem via SSH. Host-based authentication is not sufficient for preventingunauthorized access to the system, as it does not require interactiveidentification and authentication of a connection request, or for the use oftwo-factor authentication. |
high |
content_rule_no_host_based_files |
SLES-12-010410 |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217142r603262_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83021-6 |
Remove User Host-Based Authentication Files [ref] |
The ~/.shosts (in each user's home directory) files list remote hosts and users that are trusted by the local system. To remove these files, run the following command to delete them from any location: $ sudo find / -name '.shosts' -type f -delete |
The .shosts files are used to configure host-based authentication forindividual users or the system via SSH. Host-based authentication is notsufficient for preventing unauthorized access to the system, as it does notrequire interactive identification and authentication of a connection request,or for the use of two-factor authentication. |
high |
content_rule_no_user_host_based_files |
SLES-12-010400 |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217141r603262_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83084-4 |
Uninstall telnet-server Package [ref] |
The telnet-server package can be removed with the following command: $ sudo zypper remove telnet-server |
It is detrimental for operating systems to provide, or install by default,functionality exceeding requirements or mission objectives. Theseunnecessary capabilities are often overlooked and therefore may remainunsecure. They increase the risk to the platform by providing additionalattack vectors.The telnet service provides an unencrypted remote access service which doesnot provide for the confidentiality and integrity of user passwords or theremote session. If a privileged user were to login using this service, theprivileged user password could be compromised.Removing the telnet-server package decreases the risk of thetelnet service's accidental (or intentional) activation. |
high |
content_rule_package_telnet-server_removed |
SLES-12-030000 |
CM-7(a),CM-7(b),CM-6(a) |
4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.2,4.3.4.3.3 |
PR.AC-3,PR.IP-1,PR.PT-3,PR.PT-4 |
SRG-OS-000095-GPOS-00049 |
NaN |
SV-217258r603262_rule |
CCI-000381 |
3,8,9,11,12,14,15 |
NaN |
164.308(a)(4)(i),164.308(b)(1),164.308(b)(3),164.310(b),164.312(e)(1),164.312(e)(2)(ii) |
APO13.01,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.04,DSS05.02,DSS05.03,DSS05.05,DSS06.06 |
A.6.2.1,A.6.2.2,A.9.1.2,A.11.2.6,A.12.1.2,A.12.5.1,A.12.6.2,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,7.1,SR,7.6 |
BP28(R1) |
2.2.15 |
| CCE-83062-0 |
Disable Compression Or Set Compression to delayed [ref] |
Compression is useful for slow network connections over long distances but can cause performance issues on local LANs. If use of compression is required, it should be enabled only after a user has authenticated; otherwise, it should be disabled. To disable compression or delay compression until after a user has successfully authenticated, add or correct the following line in the /etc/ssh/sshd_config file: Compression no |
If compression is allowed in an SSH connection prior to authentication,vulnerabilities in the compression software could result in compromise of thesystem from an unauthenticated connection, potentially with root privileges. |
medium |
content_rule_sshd_disable_compression |
SLES-12-030250 |
AC-17(a),CM-7(a),CM-7(b),CM-6(a) |
3.1.12,4.3.4.3.2,4.3.4.3.3 |
PR.IP-1 |
SRG-OS-000480-GPOS-00227,SRG-OS-000480-VMM-002000 |
NaN |
SV-217279r603262_rule |
CCI-000366 |
3,9,11 |
NaN |
164.308(a)(4)(i),164.308(b)(1),164.308(b)(3),164.310(b),164.312(e)(1),164.312(e)(2)(ii) |
BAI10.01,BAI10.02,BAI10.03,BAI10.05 |
A.12.1.2,A.12.5.1,A.12.6.2,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,7.6 |
NaN |
NaN |
| CCE-83014-1 |
Disable SSH Access via Empty Passwords [ref] |
To explicitly disallow SSH login from accounts with empty passwords, add or correct the following line in /etc/ssh/sshd_config: PermitEmptyPasswords no Any accounts with empty passwords should be disabled immediately, and PAM configuration should prevent users from being able to assign themselves empty passwords. |
Configuring this setting for the SSH daemon provides additional assurancethat remote login via SSH will require a password, even in the event ofmisconfiguration elsewhere. |
high |
content_rule_sshd_disable_empty_passwords |
SLES-12-030150 |
AC-17(a),CM-7(a),CM-7(b),CM-6(a) |
3.1.1,3.1.5,5.3.12,4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.2,4.3.4.3.3 |
PR.AC-4,PR.AC-6,PR.DS-5,PR.IP-1,PR.PT-3 |
SRG-OS-000106-GPOS-00053,SRG-OS-000480-GPOS-00229,SRG-OS-000480-GPOS-00227,SRG-OS-000480-VMM-002000 |
NaN |
SV-217268r603262_rule |
CCI-000366,CCI-000766 |
3,5,9,11,12,13,14,15,16,18 |
NaN |
164.308(a)(4)(i),164.308(b)(1),164.308(b)(3),164.310(b),164.312(e)(1),164.312(e)(2)(ii) |
APO01.06,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS05.02,DSS05.04,DSS05.05,DSS05.07,DSS06.02,DSS06.03,DSS06.06 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.1,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.12.1.2,A.12.5.1,A.12.6.2,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,5.2,SR,7.6 |
NaN |
NT007(R17),5.5.6,FIA_UAU.1 |
| CCE-83035-6 |
Disable SSH Root Login [ref] |
The root user should never be allowed to login to a system directly over a network. To disable root login via SSH, add or correct the following line in /etc/ssh/sshd_config: PermitRootLogin no |
Even though the communications channel may be encrypted, an additional layer ofsecurity is gained by extending the policy of not logging directly on as root.In addition, logging in with a user-specific account provides individualaccountability of actions performed on the system and also helps to minimizedirect attack attempts on root's password. |
medium |
content_rule_sshd_disable_root_login |
SLES-12-030140 |
AC-6(2),AC-17(a),CM-7(a),CM-7(b),CM-6(a),IA-2,IA-2(5) |
3.1.1,3.1.5,5.3.11,4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,CIP-003-3,R5.1.1,CIP-003-3,R5.3 |
PR.AC-1,PR.AC-4,PR.AC-6,PR.AC-7,PR.DS-5,PR.PT-3 |
SRG-OS-000109-GPOS-00056,SRG-OS-000480-GPOS-00227,SRG-OS-000480-VMM-002000 |
NaN |
SV-217267r603262_rule |
CCI-000366,CCI-000770 |
1,3,5,11,12,13,14,15,16,18 |
NaN |
164.308(a)(4)(i),164.308(b)(1),164.308(b)(3),164.310(b),164.312(e)(1),164.312(e)(2)(ii) |
APO01.06,DSS05.02,DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.02,DSS06.03,DSS06.06,DSS06.10 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,5.2 |
BP28(R19) |
NT007(R21),5.5.6,CIP-004-3,R2.2.3,CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2,CIP-007-3,R5.2,CIP-007-3,R5.3.1,CIP-007-3,R5.3.2,CIP-007-3,R5.3.3,FIA_UAU.1 |
| CCE-83056-2 |
Disable SSH Support for User Known Hosts [ref] |
SSH can allow system users to connect to systems if a cache of the remote systems public keys is available. This should be disabled. To ensure this behavior is disabled, add or correct the following line in /etc/ssh/sshd_config: IgnoreUserKnownHosts yes |
Configuring this setting for the SSH daemon provides additionalassurance that remote login via SSH will require a password, evenin the event of misconfiguration elsewhere. |
medium |
content_rule_sshd_disable_user_known_hosts |
SLES-12-030200 |
AC-17(a),CM-7(a),CM-7(b),CM-6(a) |
3.1.12,4.3.4.3.2,4.3.4.3.3 |
PR.IP-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217274r603262_rule |
CCI-000366 |
3,9,11 |
NaN |
164.308(a)(4)(i),164.308(b)(1),164.308(b)(3),164.310(b),164.312(e)(1),164.312(e)(2)(ii) |
BAI10.01,BAI10.02,BAI10.03,BAI10.05 |
A.12.1.2,A.12.5.1,A.12.6.2,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,7.6 |
NaN |
FIA_UAU.1 |
| CCE-83015-8 |
Do Not Allow SSH Environment Options [ref] |
To ensure users are not able to override environment variables of the SSH daemon, add or correct the following line in /etc/ssh/sshd_config: PermitUserEnvironment no |
SSH environment options potentially allow users to bypassaccess restriction in some configurations. |
medium |
content_rule_sshd_do_not_permit_user_env |
SLES-12-030151 |
AC-17(a),CM-7(a),CM-7(b),CM-6(a) |
3.1.12,5.3.13,4.3.4.3.2,4.3.4.3.3 |
PR.IP-1 |
SRG-OS-000480-GPOS-00229,SRG-OS-000480-VMM-002000 |
NaN |
SV-217269r646747_rule |
CCI-000366 |
3,9,11 |
NaN |
164.308(a)(4)(i),164.308(b)(1),164.308(b)(3),164.310(b),164.312(e)(1),164.312(e)(2)(ii) |
BAI10.01,BAI10.02,BAI10.03,BAI10.05 |
A.12.1.2,A.12.5.1,A.12.6.2,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,7.6 |
NaN |
5.5.6 |
| CCE-83060-4 |
Enable Use of Strict Mode Checking [ref] |
SSHs StrictModes option checks file and ownership permissions in the user's home directory .ssh folder before accepting login. If world- writable permissions are found, logon is rejected. To enable StrictModes in SSH, add or correct the following line in the /etc/ssh/sshd_config file: StrictModes yes |
If other users have access to modify user-specific SSH configuration files, theymay be able to log into the system as another user. |
medium |
content_rule_sshd_enable_strictmodes |
SLES-12-030230 |
AC-6,AC-17(a),CM-6(a) |
3.1.12,4.3.3.7.3,CIP-003-3,R5.1.1,CIP-003-3,R5.3 |
PR.AC-4,PR.DS-5 |
SRG-OS-000480-GPOS-00227,SRG-OS-000480-VMM-002000 |
NaN |
SV-217277r603262_rule |
CCI-000366 |
3,5,12,13,14,15,16,18 |
NaN |
164.308(a)(4)(i),164.308(b)(1),164.308(b)(3),164.310(b),164.312(e)(1),164.312(e)(2)(ii) |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
NaN |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2 |
| CCE-83066-1 |
Enable SSH Warning Banner [ref] |
To enable the warning banner and ensure it is consistent across the system, add or correct the following line in /etc/ssh/sshd_config: Banner /etc/issue Another section contains information on how to create an appropriate system-wide warning banner. |
The warning message reinforces policy awareness during the logon process andfacilitates possible legal action against attackers. Alternatively, systemswhose ownership should not be obvious should ensure usage of a banner that doesnot provide easy attribution. |
medium |
content_rule_sshd_enable_warning_banner |
SLES-12-030050 |
AC-8(a),AC-8(c),AC-17(a),CM-6(a) |
3.1.9,5.3.19,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9 |
PR.AC-7 |
SRG-OS-000023-GPOS-00006,SRG-OS-000024-GPOS-00007,SRG-OS-000228-GPOS-00088,SRG-OS-000023-VMM-000060,SRG-OS-000024-VMM-000070 |
NaN |
SV-217263r603262_rule |
CCI-000048,CCI-000050,CCI-001384,CCI-001385,CCI-001386,CCI-001387,CCI-001388 |
1,12,15,16 |
NaN |
164.308(a)(4)(i),164.308(b)(1),164.308(b)(3),164.310(b),164.312(e)(1),164.312(e)(2)(ii) |
DSS05.04,DSS05.10,DSS06.10 |
A.9.2.1,A.9.2.4,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.5,SR,1.7,SR,1.8,SR,1.9 |
NaN |
5.5.6,FTA_TAB.1 |
| CCE-83017-4 |
Enable Encrypted X11 Forwarding [ref] |
By default, remote X11 connections are not encrypted when initiated by users. SSH has the capability to encrypt remote X11 connections when SSH's X11Forwarding option is enabled. To enable X11 Forwarding, add or correct the following line in /etc/ssh/sshd_config: X11Forwarding yes |
Non-encrypted X displays allow an attacker to capture keystrokes and to execute commandsremotely. |
high |
content_rule_sshd_enable_x11_forwarding |
SLES-12-030260 |
AC-17(a),AC-17(2),CM-6(a) |
3.1.13,4.3.4.3.2,4.3.4.3.3 |
PR.DS-7,PR.IP-1,DE.AE-1 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217280r603964_rule |
CCI-000366 |
1,3,4,6,9,11,12,13,15,16,18,20 |
NaN |
NaN |
BAI03.08,BAI07.04,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS03.01 |
A.12.1.1,A.12.1.2,A.12.1.4,A.12.5.1,A.12.6.2,A.13.1.1,A.13.1.2,A.14.2.2,A.14.2.3,A.14.2.4 |
SR,7.6 |
NaN |
4.4.3.3,CIP-007-3,R7.1 |
| CCE-83083-6 |
Enable SSH Print Last Log [ref] |
When enabled, SSH will display the date and time of the last successful account logon. To enable LastLog in SSH, add or correct the following line in the /etc/ssh/sshd_config file: PrintLastLog yes |
Providing users feedback on when account accesses last occurred facilitates userrecognition and reporting of unauthorized account use. |
medium |
content_rule_sshd_print_last_log |
SLES-12-030130 |
AC-9,AC-17(a),CM-6(a) |
4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9 |
PR.AC-7 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217266r603262_rule |
CCI-000366 |
1,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.10,DSS06.10 |
A.9.2.1,A.9.2.4,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.5,SR,1.7,SR,1.8,SR,1.9 |
NaN |
NaN |
| CCE-83027-3 |
Set SSH Idle Timeout Interval [ref] |
SSH allows administrators to set an idle timeout interval. After this interval has passed, the idle user will be automatically logged out. To set an idle timeout interval, edit the following line in /etc/ssh/sshd_config as follows: ClientAliveInterval 300 The timeout interval is given in seconds. For example, have a timeout of 10 minutes, set interval to 600. If a shorter timeout has already been set for the login shell, that value will preempt any SSH setting made in /etc/ssh/sshd_config. Keep in mind that some processes may stop SSH from correctly detecting that the user is idle.Warning: SSH disconnecting idle clients will not have desired effect without also configuring ClientAliveCountMax in the SSH service configuration.Warning: Following conditions may prevent the SSH session to time out: Remote processes on the remote machine generates output. As the output has to be transferred over the network to the client, the timeout is reset every time such transfer happens.Any scp or sftp activity by the same user to the host resets the timeout. |
Terminating an idle ssh session within a short time period reduces the window ofopportunity for unauthorized personnel to take control of a management sessionenabled on the console or console port that has been let unattended. |
medium |
content_rule_sshd_set_idle_timeout |
SLES-12-030190 |
AC-17(a),AC-2(5),AC-12,AC-17(a),CM-6(a),CM-6(a),SC-10 |
3.1.11,5.3.17,4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.3 |
PR.AC-1,PR.AC-4,PR.AC-6,PR.AC-7,PR.IP-2,DE.CM-1,DE.CM-3 |
SRG-OS-000126-GPOS-00066,SRG-OS-000163-GPOS-00072,SRG-OS-000279-GPOS-00109,SRG-OS-000395-GPOS-00175,SRG-OS-000480-VMM-002000 |
NaN |
SV-217272r603262_rule |
CCI-000879,CCI-001133,CCI-002361 |
1,3,5,7,8,12,13,14,15,16,18 |
NaN |
NaN |
APO13.01,BAI03.01,BAI03.02,BAI03.03,DSS01.03,DSS03.05,DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10 |
A.6.1.2,A.6.1.5,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.12.4.1,A.12.4.3,A.14.1.1,A.14.2.1,A.14.2.5,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,6.2 |
BP28(R29) |
5.5.6,CIP-004-3,R2.2.3,CIP-007-3,R5.1,CIP-007-3,R5.2,CIP-007-3,R5.3.1,CIP-007-3,R5.3.2,CIP-007-3,R5.3.3,Req-8.1.8 |
| CCE-83407-7 |
Set SSH Client Alive Count Max to zero [ref] |
The SSH server sends at most ClientAliveCountMax messages during a SSH session and waits for a response from the SSH client. The option ClientAliveInterval configures timeout after each ClientAliveCountMax message. If the SSH server does not receive a response from the client, then the connection is considered idle and terminated. To ensure the SSH idle timeout occurs precisely when the ClientAliveInterval is set, set the ClientAliveCountMax to value of 0. |
This ensures a user login will be terminated as soon as the ClientAliveIntervalis reached. |
medium |
content_rule_sshd_set_keepalive_0 |
SLES-12-030191 |
AC-2(5),AC-12,AC-17(a),CM-6(a),SC-10 |
3.1.11,4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.3 |
PR.AC-1,PR.AC-4,PR.AC-6,PR.AC-7,PR.IP-2,DE.CM-1,DE.CM-3 |
SRG-OS-000163-GPOS-00072,SRG-OS-000279-GPOS-00109,SRG-OS-000480-VMM-002000 |
NaN |
SV-217273r603961_rule |
CCI-000879,CCI-001133,CCI-002361 |
1,3,5,7,8,12,13,14,15,16,18 |
NaN |
164.308(a)(4)(i),164.308(b)(1),164.308(b)(3),164.310(b),164.312(e)(1),164.312(e)(2)(ii) |
APO13.01,BAI03.01,BAI03.02,BAI03.03,DSS01.03,DSS03.05,DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10 |
A.6.1.2,A.6.1.5,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.12.4.1,A.12.4.3,A.14.1.1,A.14.2.1,A.14.2.5,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,6.2 |
NaN |
5.5.6,CIP-004-3,R2.2.3,CIP-007-3,R5.1,CIP-007-3,R5.2,CIP-007-3,R5.3.1,CIP-007-3,R5.3.2,CIP-007-3,R5.3.3,Req-8.1.8 |
| CCE-83077-8 |
Set SSH Daemon LogLevel to VERBOSE [ref] |
The VERBOSE parameter configures the SSH daemon to record login and logout activity. To specify the log level in SSH, add or correct the following line in the /etc/ssh/sshd_config file: LogLevel VERBOSE |
SSH provides several logging levels with varying amounts of verbosity. DEBUG is specificallynot recommended other than strictly for debugging SSH communications since it providesso much data that it is difficult to identify important security information. INFO orVERBOSE level is the basic level that only records login activity of SSH users. In manysituations, such as Incident Response, it is important to determine when a particular user was activeon a system. The logout record can eliminate those users who disconnected, which helps narrow thefield. |
medium |
content_rule_sshd_set_loglevel_verbose |
SLES-12-030110 |
AC-17(a),AC-17(1),CM-6(a) |
NaN |
NaN |
SRG-OS-000032-GPOS-00013 |
NaN |
SV-217265r603262_rule |
CCI-000067 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
CIP-007-3,R7.1,5.3.6 |
| CCE-83181-8 |
Use Only FIPS 140-2 Validated Ciphers [ref] |
Limit the ciphers to those algorithms which are FIPS-approved. Counter (CTR) mode is also preferred over cipher-block chaining (CBC) mode. The following line in /etc/ssh/sshd_config demonstrates use of FIPS-approved ciphers: Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc The man page sshd_config(5) contains a list of supported ciphers. The rule is parametrized to use the following ciphers: aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se.Warning: The system needs to be rebooted for these changes to take effect.Warning: System Crypto Modules must be provided by a vendor that undergoes FIPS-140 certifications. FIPS-140 is applicable to all Federal agencies that use cryptographic-based security systems to protect sensitive information in computer and telecommunication systems (including voice systems) as defined in Section 5131 of the Information Technology Management Reform Act of 1996, Public Law 104-106. This standard shall be used in designing and implementing cryptographic modules that Federal departments and agencies operate or are operated for them under contract. See https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf To meet this, the system has to have cryptographic software provided by a vendor that has undergone this certification. This means providing documentation, test results, design information, and independent third party review by an accredited lab. While open source software is capable of meeting this, it does not meet FIPS-140 unless the vendor submits to this process. |
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and thereforecannot be relied upon to provide confidentiality or integrity, and system data may be compromised.Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating tocryptographic modules.FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modulesutilize authentication that meets industry and government requirements. For government systems, this allowsSecurity Levels 1, 2, 3, or 4 for use on SUSE Linux Enterprise 12. |
medium |
content_rule_sshd_use_approved_ciphers |
SLES-12-030170 |
AC-17(a),AC-17(2),CM-6(a),MA-4(6),SC-13,SC-12(2),SC-12(3) |
3.1.13,3.13.11,3.13.8,5.3.14,4.3.3.2.2,4.3.3.3.9,4.3.3.5.1,4.3.3.5.2,4.3.3.5.3,4.3.3.5.4,4.3.3.5.5,4.3.3.5.6,4.3.3.5.7,4.3.3.5.8,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.1,4.3.3.7.2,4.3.3.7.3,4.3.3.7.4,4.3.4.3.2,4.3.4.3.3,4.3.4.4.7 |
PR.AC-1,PR.AC-3,PR.AC-4,PR.AC-6,PR.AC-7,PR.IP-1,PR.PT-1,PR.PT-3,PR.PT-4 |
SRG-OS-000033-GPOS-00014,SRG-OS-000120-GPOS-00061,SRG-OS-000125-GPOS-00065,SRG-OS-000250-GPOS-00093,SRG-OS-000393-GPOS-00173,SRG-OS-000394-GPOS-00174,SRG-OS-000033-VMM-000140,SRG-OS-000120-VMM-000600,SRG-OS-000478-VMM-001980,SRG-OS-000396-VMM-001590 |
NaN |
SV-217270r603956_rule |
CCI-000068,CCI-000366,CCI-000803,CCI-000877,CCI-002890,CCI-003123 |
1,3,5,6,8,9,11,12,14,15,16,18 |
NaN |
164.308(b)(1),164.308(b)(2),164.312(e)(1),164.312(e)(2)(i),164.312(e)(2)(ii),164.314(b)(2)(i) |
APO11.04,APO13.01,BAI03.05,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS01.04,DSS05.02,DSS05.03,DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.06,DSS06.10,MEA02.01 |
IA-5(1)(c),A.6.1.2,A.6.2.1,A.6.2.2,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.11.2.6,A.12.1.2,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.5.1,A.12.6.2,A.12.7.1,A.13.1.1,A.13.2.1,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.11,SR,1.12,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.6,SR,1.7,SR,1.8,SR,1.9,SR,2.1,SR,2.10,SR,2.11,SR,2.12,SR,2.2,SR,2.3,SR,2.4,SR,2.5,SR,2.6,SR,2.7,SR,2.8,SR,2.9,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,7.1,SR,7.6 |
NaN |
5.5.6,4.4.2.1,4.4.2.2,4.4.2.4 |
| CCE-83036-4 |
Use Only FIPS 140-2 Validated MACs [ref] |
Limit the MACs to those hash algorithms which are FIPS-approved. The following line in /etc/ssh/sshd_config demonstrates use of FIPS-approved MACs: MACs hmac-sha2-512,hmac-sha2-256 The man page sshd_config(5) contains a list of supported MACs. The rule is parametrized to use the following MACs: hmac-sha2-512,hmac-sha2-256.Warning: The system needs to be rebooted for these changes to take effect.Warning: System Crypto Modules must be provided by a vendor that undergoes FIPS-140 certifications. FIPS-140 is applicable to all Federal agencies that use cryptographic-based security systems to protect sensitive information in computer and telecommunication systems (including voice systems) as defined in Section 5131 of the Information Technology Management Reform Act of 1996, Public Law 104-106. This standard shall be used in designing and implementing cryptographic modules that Federal departments and agencies operate or are operated for them under contract. See https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf To meet this, the system has to have cryptographic software provided by a vendor that has undergone this certification. This means providing documentation, test results, design information, and independent third party review by an accredited lab. While open source software is capable of meeting this, it does not meet FIPS-140 unless the vendor submits to this process. |
DoD Information Systems are required to use FIPS-approved cryptographic hashfunctions. The only SSHv2 hash algorithms meeting this requirement is SHA2. |
medium |
content_rule_sshd_use_approved_macs |
SLES-12-030180 |
AC-17(a),AC-17(2),CM-6(a),MA-4(6),SC-13,SC-12(2),SC-12(3) |
3.1.13,3.13.11,3.13.8,5.3.15,4.3.3.5.1,4.3.3.6.6 |
PR.AC-1,PR.AC-3,PR.DS-5,PR.PT-4 |
SRG-OS-000125-GPOS-00065,SRG-OS-000250-GPOS-00093,SRG-OS-000394-GPOS-00174,SRG-OS-000033-VMM-000140,SRG-OS-000120-VMM-000600,SRG-OS-000478-VMM-001980,SRG-OS-000480-VMM-002000,SRG-OS-000396-VMM-001590 |
NaN |
SV-217271r603959_rule |
CCI-000068,CCI-000803,CCI-000877,CCI-001453,CCI-003123 |
1,5,8,12,13,15,16 |
NaN |
164.308(b)(1),164.308(b)(2),164.312(e)(1),164.312(e)(2)(i),164.312(e)(2)(ii),164.314(b)(2)(i) |
APO01.06,APO13.01,DSS01.04,DSS05.02,DSS05.03,DSS05.04,DSS05.07,DSS06.02,DSS06.03 |
A.6.1.2,A.6.2.1,A.6.2.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.11.2.6,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,1.1,SR,1.13,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.6,SR,3.1,SR,3.5,SR,3.8,SR,4.1,SR,4.3,SR,5.1,SR,5.2,SR,5.3,SR,7.1,SR,7.6 |
NaN |
NaN |
| CCE-83061-2 |
Enable Use of Privilege Separation [ref] |
When enabled, SSH will create an unprivileged child process that has the privilege of the authenticated user. To enable privilege separation in SSH, add or correct the following line in the /etc/ssh/sshd_config file: UsePrivilegeSeparation sandbox |
SSH daemon privilege separation causes the SSH process to drop root privilegeswhen not needed which would decrease the impact of software vulnerabilities inthe unprivileged section. |
medium |
content_rule_sshd_use_priv_separation |
SLES-12-030240 |
AC-17(a),AC-6,CM-6(a) |
3.1.12,4.3.3.7.3,CIP-003-3,R5.1.1,CIP-003-3,R5.3 |
PR.AC-4,PR.DS-5 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217278r603262_rule |
CCI-000366 |
3,5,12,13,14,15,16,18 |
NaN |
164.308(a)(4)(i),164.308(b)(1),164.308(b)(3),164.310(b),164.312(e)(1),164.312(e)(2)(ii) |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
NaN |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2 |
| CCE-83228-7 |
Prevent remote hosts from connecting to the proxy display [ref] |
The SSH daemon should prevent remote hosts from connecting to the proxy display. Make sure that the option X11UseLocalhost is set to yes within the SSH server configuration file. |
When X11 forwarding is enabled, there may be additional exposure to theserver and client displays if the sshd proxy display is configured to listenon the wildcard address. By default, sshd binds the forwarding server to theloopback address and sets the hostname part of the DISPLAYenvironment variable to localhost. This prevents remote hosts fromconnecting to the proxy display. |
medium |
content_rule_sshd_x11_use_localhost |
SLES-12-030261 |
CM-6(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-233308r603331_rule |
CCI-000366 |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
NaN |
| CCE-83201-4 |
Enable the OpenSSH Service [ref] |
The SSH server service, sshd, is commonly needed. The sshd service can be enabled with the following command: $ sudo systemctl enable sshd.service |
Without protection of the transmitted information, confidentiality, andintegrity may be compromised because unprotected communications can beintercepted and either read or altered.This checklist item applies to both internal and external networks and all typesof information system components from which information can be transmitted (e.g., servers,mobile devices, notebook computers, printers, copiers, scanners, etc). Communication pathsoutside the physical protection of a controlled boundary are exposed to the possibilityof interception and modification. |
medium |
content_rule_service_sshd_enabled |
SLES-12-030100 |
CM-6(a),SC-8,SC-8(1),SC-8(2),SC-8(3),SC-8(4) |
3.1.13,3.13.8,3.5.4 |
PR.DS-2,PR.DS-5 |
SRG-OS-000423-GPOS-00187,SRG-OS-000423-GPOS-00188,SRG-OS-000423-GPOS-00189,SRG-OS-000423-GPOS-00190 |
NaN |
SV-217264r603262_rule |
CCI-002418,CCI-002420,CCI-002421,CCI-002422 |
13,14 |
NaN |
NaN |
APO01.06,DSS05.02,DSS05.04,DSS05.07,DSS06.02,DSS06.06 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,3.1,SR,3.8,SR,4.1,SR,4.2,SR,5.2 |
NaN |
NaN |
| CCE-83058-8 |
Verify Permissions on SSH Server Private *_key Key Files [ref] |
To properly set the permissions of /etc/ssh/*_key, run the command: $ sudo chmod 0600 /etc/ssh/*_key |
If an unauthorized user obtains the private SSH host key file, the host could beimpersonated. |
medium |
content_rule_file_permissions_sshd_private_key |
SLES-12-030220 |
AC-17(a),AC-6(1),CM-6(a) |
3.1.13,3.13.10,4.3.3.7.3,CIP-003-3,R5.1.1,CIP-003-3,R5.3 |
PR.AC-4,PR.DS-5 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217276r646753_rule |
CCI-000366 |
3,5,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
BP28(R36) |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2,5.3.2 |
| CCE-83057-0 |
Verify Permissions on SSH Server Public *.pub Key Files [ref] |
To properly set the permissions of /etc/ssh/*.pub, run the command: $ sudo chmod 0644 /etc/ssh/*.pub |
If a public host key file is modified by an unauthorized user, the SSH servicemay be compromised. |
medium |
content_rule_file_permissions_sshd_pub_key |
SLES-12-030210 |
AC-17(a),AC-6(1),CM-6(a) |
3.1.13,3.13.10,4.3.3.7.3,CIP-003-3,R5.1.1,CIP-003-3,R5.3 |
PR.AC-4,PR.DS-5 |
SRG-OS-000480-GPOS-00227 |
NaN |
SV-217275r646750_rule |
CCI-000366 |
3,5,12,13,14,15,16,18 |
NaN |
NaN |
APO01.06,DSS05.04,DSS05.07,DSS06.02 |
A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5,A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3 |
SR,2.1,SR,5.2 |
NaN |
CIP-004-3,R2.3,CIP-007-3,R2.1,CIP-007-3,R2.2,CIP-007-3,R2.3,CIP-007-3,R5.1,CIP-007-3,R5.1.1,CIP-007-3,R5.1.2,5.3.3 |
| CCE-83040-6 |
Configure SSSD's Memory Cache to Expire [ref] |
SSSD's memory cache should be configured to set to expire records after 86400 seconds. To configure SSSD to expire memory cache, set memcache_timeout to 86400 under the [nss] section in /etc/sssd/sssd.conf. For example: [nss] memcache_timeout = 86400 |
If cached authentication information is out-of-date, the validity of theauthentication information may be questionable. |
medium |
content_rule_sssd_memcache_timeout |
SLES-12-010670 |
CM-6(a) |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.4 |
PR.AC-1,PR.AC-6,PR.AC-7 |
SRG-OS-000383-GPOS-00166,SRG-OS-000383-VMM-001570 |
NaN |
SV-217166r603262_rule |
CCI-002007 |
1,5,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10 |
IA-5(13),A.7.1.1,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1 |
NaN |
NaN |
| CCE-83206-3 |
Configure SSSD to Expire Offline Credentials [ref] |
SSSD should be configured to expire offline credentials after 1 day. To configure SSSD to expire offline credentials, set offline_credentials_expiration to 1 under the [pam] section in /etc/sssd/sssd.conf. For example: [pam] offline_credentials_expiration = 1 |
If cached authentication information is out-of-date, the validity of theauthentication information may be questionable. |
medium |
content_rule_sssd_offline_cred_expiration |
SLES-12-010680 |
CM-6(a) |
4.3.3.2.2,4.3.3.5.1,4.3.3.5.2,4.3.3.6.1,4.3.3.6.2,4.3.3.6.3,4.3.3.6.4,4.3.3.6.5,4.3.3.6.6,4.3.3.6.7,4.3.3.6.8,4.3.3.6.9,4.3.3.7.2,4.3.3.7.4 |
PR.AC-1,PR.AC-6,PR.AC-7 |
SRG-OS-000383-GPOS-00166,SRG-OS-000383-VMM-001570 |
NaN |
SV-217167r603262_rule |
CCI-002007 |
1,5,12,15,16 |
NaN |
NaN |
DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10 |
IA-5(13),A.7.1.1,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.2,A.9.4.3,A.18.1.4 |
SR,1.1,SR,1.10,SR,1.2,SR,1.3,SR,1.4,SR,1.5,SR,1.7,SR,1.8,SR,1.9,SR,2.1 |
NaN |
NaN |