Checklist
| Group
Guide to the Secure Configuration of Red Hat Enterprise Linux 8
Group contains 106 groups and 403 rules |
| Group
@@ -1552,7 +1552,7 @@
standards approved by the federal government since this provides assurance they have been tested
and validated. |
| Severity: | high |
| Identifiers and References | Identifiers:
CCE-82155-3 References:
- CCI-000068, CCI-000803, CCI-002450, 1446, CIP-003-8 R4.2, CIP-007-3 R5.1, SC-12(2), SC-12(3), IA-7, SC-13, CM-6(a), SC-12, FCS_RBG_EXT.1, SRG-OS-000478-GPOS-00223, RHEL-08-010020, SV-230223r877398_rule |
|
|
| Severity: | high |
| Identifiers and References | Identifiers:
CCE-80942-6 References:
- CCI-000068, CCI-000803, CCI-002450, 1446, CIP-003-8 R4.2, CIP-007-3 R5.1, CM-3(6), SC-12(2), SC-12(3), IA-7, SC-13, CM-6(a), SC-12, FCS_COP.1(1), FCS_COP.1(2), FCS_COP.1(3), FCS_COP.1(4), FCS_CKM.1, FCS_CKM.2, FCS_TLSC_EXT.1, FCS_RBG_EXT.1, SRG-OS-000478-GPOS-00223, SRG-OS-000396-GPOS-00176, RHEL-08-010020, SV-230223r877398_rule |
|
|
| Severity: | high |
| Identifiers and References | Identifiers:
CCE-84027-2 References:
- CCI-000068, CCI-000803, CCI-000877, CCI-001453, CCI-002418, CCI-002450, CCI-002890, CCI-003123, CIP-003-8 R4.2, CIP-007-3 R5.1, SC-12(2), SC-12(3), IA-7, SC-13, CM-6(a), SC-12, SRG-OS-000033-GPOS-00014, SRG-OS-000125-GPOS-00065, SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174, SRG-OS-000396-GPOS-00176, SRG-OS-000423-GPOS-00187, SRG-OS-000478-GPOS-00223, RHEL-08-010020, SV-230223r877398_rule |
|
| Group
+ CCI-000068, CCI-000803, CCI-000877, CCI-001453, CCI-002418, CCI-002450, CCI-002890, CCI-003123, CIP-003-8 R4.2, CIP-007-3 R5.1, SC-12(2), SC-12(3), IA-7, SC-13, CM-6(a), SC-12, SRG-OS-000033-GPOS-00014, SRG-OS-000125-GPOS-00065, SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174, SRG-OS-000396-GPOS-00176, SRG-OS-000423-GPOS-00187, SRG-OS-000478-GPOS-00223, RHEL-08-010020, SV-230223r928585_rule |
|
| Group
System Cryptographic Policies
Group contains 12 rules |
[ref]
Linux has the capability to centrally configure cryptographic polices. The command
@@ -1836,7 +1836,7 @@
include "/etc/crypto-policies/back-ends/bind.config"; |
| Rationale: | Overriding the system crypto policy makes the behavior of the BIND service violate expectations,
and makes system configuration more fragmented. |
| Severity: | high |
| Identifiers and References | Identifiers:
CCE-80934-3 References:
- CIP-003-8 R4.2, CIP-007-3 R5.1, SC-13, SC-12(2), SC-12(3), SRG-OS-000423-GPOS-00187, SRG-OS-000426-GPOS-00190, RHEL-08-010020, SV-230223r877398_rule |
|
|
| Severity: | high |
| Identifiers and References | Identifiers:
CCE-80935-0 References:
- 164.308(a)(4)(i), 164.308(b)(1), 164.308(b)(3), 164.312(e)(1), 164.312(e)(2)(ii), 1446, CIP-003-8 R4.2, CIP-007-3 R5.1, CIP-007-3 R7.1, AC-17(a), AC-17(2), CM-6(a), MA-4(6), SC-13, SC-12(2), SC-12(3), FCS_COP.1(1), FCS_COP.1(2), FCS_COP.1(3), FCS_COP.1(4), FCS_CKM.1, FCS_CKM.2, FCS_TLSC_EXT.1, SRG-OS-000396-GPOS-00176, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174, RHEL-08-010020, 1.10, 1.11, SV-230223r877398_rule |
|
|
| Rationale: | Overriding the system crypto policy makes the behavior of Kerberos violate expectations,
and makes system configuration more fragmented. |
| Severity: | high |
| Identifiers and References | Identifiers:
CCE-80936-8 References:
- 0418, 1055, 1402, CIP-003-8 R4.2, CIP-007-3 R5.1, SC-13, SC-12(2), SC-12(3), SRG-OS-000120-GPOS-00061, RHEL-08-010020, SV-230223r877398_rule |
|
|
| Severity: | high |
| Identifiers and References | Identifiers:
CCE-80937-6 References:
- CIP-003-8 R4.2, CIP-007-3 R5.1, CM-6(a), MA-4(6), SC-13, SC-12(2), SC-12(3), FCS_IPSEC_EXT.1.4, FCS_IPSEC_EXT.1.6, Req-2.2, 2.2, SRG-OS-000033-GPOS-00014, RHEL-08-010020, SV-230223r877398_rule |
|
|
| Severity: | high |
| Identifiers and References | Identifiers:
CCE-85902-5 References:
- CCI-000068, CCI-000877, CCI-001453, CCI-002418, CCI-002890, CCI-003123, AC-17(2), SRG-OS-000033-GPOS-00014, SRG-OS-000125-GPOS-00065, SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174, SRG-OS-000423-GPOS-00187, RHEL-08-010020, SV-230223r877398_rule |
|
|
| Severity: | medium |
| Identifiers and References | Identifiers:
CCE-85870-4 References:
- CCI-000877, CCI-001453, AC-17(2), SRG-OS-000125-GPOS-00065, SRG-OS-000250-GPOS-00093, RHEL-08-010020, SV-230223r877398_rule |
|
|
| Severity: | medium |
| Identifiers and References | Identifiers:
CCE-86353-0 References:
- CCI-002165, CCI-002235, SRG-OS-000324-GPOS-00125, RHEL-08-040400, SV-254520r877392_rule |
|
| Group
+ CCI-002165, CCI-002235, SRG-OS-000324-GPOS-00125, RHEL-08-040400, SV-254520r928805_rule |
|
| Group
Services
Group contains 26 groups and 59 rules |
[ref]
The best protection against vulnerable software is running less software. This section describes how to review
@@ -81478,7 +81478,7 @@
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.
To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues. |
| Severity: | low |
| Identifiers and References | Identifiers:
CCE-82988-7 References:
- CCI-000381, AU-8(1), AU-12(1), FMT_SMF_EXT.1, SRG-OS-000096-GPOS-00050, SRG-OS-000095-GPOS-00049, RHEL-08-030741, SV-230485r627750_rule |
|
|
| Rationale: | Minimizing the exposure of the server functionality of the chrony
daemon diminishes the attack surface. |
| Severity: | low |
| Identifiers and References | Identifiers:
CCE-82840-0 References:
- CCI-000381, CM-7(1), FMT_SMF_EXT.1, SRG-OS-000096-GPOS-00050, SRG-OS-000095-GPOS-00049, RHEL-08-030742, SV-230486r627750_rule |
|
|
| Rationale: | The rngd service
feeds random data from hardware device to kernel random device. |
| Severity: | low |
| Identifiers and References | Identifiers:
CCE-82831-9 References:
- CCI-000366, FCS_RBG_EXT.1, SRG-OS-000480-GPOS-00227, RHEL-08-010471, SV-230285r917876_rule |
|
|
Applicable - Configurable |
Verify the operating system automatically audits account creation. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+$ sudo auditctl -l | grep /etc/sudoers
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account creation. |
- 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
-
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers -p wa -k actions
medium |
|
|
@@ -254,39 +246,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account creations. |
- CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.
To address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
+ | 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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers.d/ -p wa -k actions |
+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
Applicable - Configurable |
Verify the operating system automatically audits account creation. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-$ sudo auditctl -l | grep/etc/sudoers.d
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
--w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account creation. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
+ | 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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers.d/ -p wa -k actions |
+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
medium |
|
|
@@ -299,7 +299,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account creations. |
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+ CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.
@@ -309,29 +309,29 @@
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:
--w /etc/sudoers -p wa -k actions
+-w /etc/sudoers.d/ -p wa -k actions
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:
--w /etc/sudoers -p wa -k actions |
+-w /etc/sudoers.d/ -p wa -k actions
Applicable - Configurable |
Verify the operating system automatically audits account creation. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-$ sudo auditctl -l | grep /etc/sudoers
+$ sudo auditctl -l | grep/etc/sudoers.d
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account creation. |
At a minimum, the audit system should collect administrator actions
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:
--w /etc/sudoers -p wa -k actions
+-w /etc/sudoers.d/ -p wa -k actions
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:
--w /etc/sudoers -p wa -k actions |
+-w /etc/sudoers.d/ -p wa -k actions
medium |
|
|
@@ -344,7 +344,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account creations. |
- CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+ CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.
@@ -355,21 +355,23 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system automatically audits account creation. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
--w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes?
Configure the operating system to automatically audit account creation. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -377,14 +379,14 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -397,7 +399,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account creations. |
- CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+ CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.
@@ -408,21 +410,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/group -p wa -k audit_rules_usergroup_modification
+-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/group -p wa -k audit_rules_usergroup_modification |
+-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system automatically audits account creation. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/group)'
+$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
--w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account creation. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -430,14 +432,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/group -p wa -k audit_rules_usergroup_modification
+-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/group -p wa -k audit_rules_usergroup_modification |
+-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -450,7 +452,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account creations. |
- CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
+ CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.
@@ -461,23 +463,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification
+-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/gshadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/group -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system automatically audits account creation. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
--w /etc/gshadow -p wa -k identity
+$ sudo auditctl -l | grep -E '(/etc/group)'
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
+-w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account creation. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -485,14 +485,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification
+-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/gshadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/group -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -563,56 +563,32 @@
TBD - Assigned by DISA after STIG release |
The operating system must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
- CCE-86099-9: Account Lockouts Must Be Logged |
+ CCE-87096-4: Do Not Show System Messages When Unsuccessful Logon Attempts Occur |
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account. |
- PAM faillock locks an account due to excessive password failures, this event must be logged. |
- Applicable - Configurable |
- Verify that the operating system enforces the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. If it does not, this is a finding. |
- Verify the "/etc/security/faillock.conf" file is configured to log user name information when unsuccessful logon attempts occur:
-
-$ sudo grep audit /etc/security/faillock.conf
-
-audit Is it the case that the "audit" option is not set, is missing or commented out? |
- Configure the operating system to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
- PAM faillock locks an account due to excessive password failures, this event must be logged. |
- medium |
- |
- |
- |
-
-
-
- | CCI-000044 |
- SRG-OS-000021-GPOS-00005 |
- TBD - Assigned by DISA after STIG release |
- The operating system must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
-
- CCE-86248-2: An SELinux Context must be configured for the pam_faillock.so records directory |
+ This rule ensures the system prevents informative messages from being presented to the user
+pertaining to logon information after a number of incorrect login attempts using
+pam_faillock.so.
- | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account. |
- The dir configuration option in PAM pam_faillock.so module defines where the lockout
-records is stored. The configured directory must have the correct SELinux context. |
+pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
+defined to work as expected. In order to avoid errors when manually editing these files, it is
+recommended to use the appropriate tools, such as authselect or authconfig,
+depending on the OS version.
Applicable - Configurable |
Verify that the operating system enforces the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. If it does not, this is a finding. |
- If the system does not have SELinux enabled and enforcing a targeted policy, or if the
-pam_faillock.so module is not configured for use, this requirement is not applicable.
-
-Verify the location of the non-default tally directory for the pam_faillock.so module with
-the following command:
-
-$ sudo grep -w dir /etc/security/faillock.conf
-
-dir = /var/log/faillock
-
-Check the security context type of the non-default tally directory with the following command:
-
-$ sudo ls -Zd /var/log/faillock
-
-unconfined_u:object_r:faillog_t:s0 /var/log/faillock Is it the case that the security context type of the non-default tally directory is not "faillog_t"? |
+ To ensure that the system prevents messages from being shown when three unsuccessful logon
+attempts occur, run the following command:
+$ grep silent /etc/security/faillock.conf
+The output should show silent. Is it the case that the system shows messages when three unsuccessful logon attempts occur? |
Configure the operating system to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
- The dir configuration option in PAM pam_faillock.so module defines where the lockout
-records is stored. The configured directory must have the correct SELinux context. |
+ This rule ensures the system prevents informative messages from being presented to the user
+pertaining to logon information after a number of incorrect login attempts using
+pam_faillock.so.
+
+pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
+defined to work as expected. In order to avoid errors when manually editing these files, it is
+recommended to use the appropriate tools, such as authselect or authconfig,
+depending on the OS version. |
medium |
|
|
@@ -625,12 +601,11 @@
TBD - Assigned by DISA after STIG release |
The operating system must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
- CCE-87096-4: Do Not Show System Messages When Unsuccessful Logon Attempts Occur |
+ CCE-80668-7: Configure the root Account for Failed Password Attempts |
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account. |
- This rule ensures the system prevents informative messages from being presented to the user
-pertaining to logon information after a number of incorrect login attempts using
-pam_faillock.so.
+ | This rule configures the system to lock out the root account after a number of
+incorrect login attempts using pam_faillock.so.
pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid errors when manually editing these files, it is
@@ -638,14 +613,15 @@
depending on the OS version. |
Applicable - Configurable |
Verify that the operating system enforces the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. If it does not, this is a finding. |
- To ensure that the system prevents messages from being shown when three unsuccessful logon
-attempts occur, run the following command:
-$ grep silent /etc/security/faillock.conf
-The output should show silent. Is it the case that the system shows messages when three unsuccessful logon attempts occur? |
+ Verify Red Hat Enterprise Linux 8 is configured to lock the root account after
+unsuccessful logon attempts with the command:
+
+
+$ grep even_deny_root /etc/security/faillock.conf
+even_deny_root Is it the case that the "even_deny_root" option is not set, is missing or commented out? |
Configure the operating system to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
- This rule ensures the system prevents informative messages from being presented to the user
-pertaining to logon information after a number of incorrect login attempts using
-pam_faillock.so.
+ | This rule configures the system to lock out the root account after a number of
+incorrect login attempts using pam_faillock.so.
pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid errors when manually editing these files, it is
@@ -663,39 +639,31 @@
| TBD - Assigned by DISA after STIG release |
The operating system must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
- CCE-80669-5: Set Interval For Counting Failed Password Attempts |
+ CCE-86248-2: An SELinux Context must be configured for the pam_faillock.so records directory |
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account. |
- Utilizing pam_faillock.so, the fail_interval directive configures the system
-to lock out an account after a number of incorrect login attempts within a specified time
-period.
-
-Ensure that the file /etc/security/faillock.conf contains the following entry:
-fail_interval = <interval-in-seconds> where interval-in-seconds is or greater.
-
-
-In order to avoid errors when manually editing these files, it is
-recommended to use the appropriate tools, such as authselect or authconfig,
-depending on the OS version. |
+ The dir configuration option in PAM pam_faillock.so module defines where the lockout
+records is stored. The configured directory must have the correct SELinux context. |
Applicable - Configurable |
Verify that the operating system enforces the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. If it does not, this is a finding. |
- To ensure the failed password attempt policy is configured correctly, run the following command:
+ | If the system does not have SELinux enabled and enforcing a targeted policy, or if the
+pam_faillock.so module is not configured for use, this requirement is not applicable.
-$ grep fail_interval /etc/security/faillock.conf
-The output should show fail_interval = <interval-in-seconds> where interval-in-seconds is or greater. Is it the case that the "fail_interval" option is not set to ""
-or less (but not "0"), the line is commented out, or the line is missing? |
- Configure the operating system to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
- Utilizing pam_faillock.so, the fail_interval directive configures the system
-to lock out an account after a number of incorrect login attempts within a specified time
-period.
+Verify the location of the non-default tally directory for the pam_faillock.so module with
+the following command:
-Ensure that the file /etc/security/faillock.conf contains the following entry:
-fail_interval = <interval-in-seconds> where interval-in-seconds is or greater.
+$ sudo grep -w dir /etc/security/faillock.conf
+dir = /var/log/faillock
-In order to avoid errors when manually editing these files, it is
-recommended to use the appropriate tools, such as authselect or authconfig,
-depending on the OS version. |
+Check the security context type of the non-default tally directory with the following command:
+
+$ sudo ls -Zd /var/log/faillock
+
+unconfined_u:object_r:faillog_t:s0 /var/log/faillock Is it the case that the security context type of the non-default tally directory is not "faillog_t"?
+ Configure the operating system to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
+ The dir configuration option in PAM pam_faillock.so module defines where the lockout
+records is stored. The configured directory must have the correct SELinux context. |
medium |
|
|
@@ -708,39 +676,19 @@
TBD - Assigned by DISA after STIG release |
The operating system must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
- CCE-86067-6: Lock Accounts Must Persist |
+ CCE-86099-9: Account Lockouts Must Be Logged |
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account. |
- This rule ensures that the system lock out accounts using pam_faillock.so persist
-after system reboot. From "pam_faillock" man pages:
-Note that the default directory that "pam_faillock" uses is usually cleared on system
-boot so the access will be reenabled after system reboot. If that is undesirable, a different
-tally directory must be set with the "dir" option.
-
-pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
-defined to work as expected. In order to avoid errors when manually editing these files, it is
-recommended to use the appropriate tools, such as authselect or authconfig,
-depending on the OS version.
-
-The chosen profile expects the directory to be . |
+ PAM faillock locks an account due to excessive password failures, this event must be logged. |
Applicable - Configurable |
Verify that the operating system enforces the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. If it does not, this is a finding. |
- To ensure the tally directory is configured correctly, run the following command:
-$ sudo grep 'dir =' /etc/security/faillock.conf
-The output should show that dir is set to something other than "/var/run/faillock" Is it the case that the "dir" option is not set to a non-default documented tally log directory, is missing or commented out? |
- Configure the operating system to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
- This rule ensures that the system lock out accounts using pam_faillock.so persist
-after system reboot. From "pam_faillock" man pages:
-Note that the default directory that "pam_faillock" uses is usually cleared on system
-boot so the access will be reenabled after system reboot. If that is undesirable, a different
-tally directory must be set with the "dir" option.
+ | Verify the "/etc/security/faillock.conf" file is configured to log user name information when unsuccessful logon attempts occur:
-pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
-defined to work as expected. In order to avoid errors when manually editing these files, it is
-recommended to use the appropriate tools, such as authselect or authconfig,
-depending on the OS version.
+$ sudo grep audit /etc/security/faillock.conf
-The chosen profile expects the directory to be . |
+audit Is it the case that the "audit" option is not set, is missing or commented out?
+ Configure the operating system to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
+ PAM faillock locks an account due to excessive password failures, this event must be logged. |
medium |
|
|
@@ -811,32 +759,84 @@
TBD - Assigned by DISA after STIG release |
The operating system must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
- CCE-80668-7: Configure the root Account for Failed Password Attempts |
+ CCE-80669-5: Set Interval For Counting Failed Password Attempts |
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account. |
- This rule configures the system to lock out the root account after a number of
-incorrect login attempts using pam_faillock.so.
+ | Utilizing pam_faillock.so, the fail_interval directive configures the system
+to lock out an account after a number of incorrect login attempts within a specified time
+period.
-pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
-defined to work as expected. In order to avoid errors when manually editing these files, it is
+Ensure that the file /etc/security/faillock.conf contains the following entry:
+fail_interval = <interval-in-seconds> where interval-in-seconds is or greater.
+
+
+In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig,
depending on the OS version. |
Applicable - Configurable |
Verify that the operating system enforces the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 is configured to lock the root account after
-unsuccessful logon attempts with the command:
+ | To ensure the failed password attempt policy is configured correctly, run the following command:
+
+$ grep fail_interval /etc/security/faillock.conf
+The output should show fail_interval = <interval-in-seconds> where interval-in-seconds is or greater. Is it the case that the "fail_interval" option is not set to ""
+or less (but not "0"), the line is commented out, or the line is missing? |
+ Configure the operating system to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
+ Utilizing pam_faillock.so, the fail_interval directive configures the system
+to lock out an account after a number of incorrect login attempts within a specified time
+period.
+
+Ensure that the file /etc/security/faillock.conf contains the following entry:
+fail_interval = <interval-in-seconds> where interval-in-seconds is or greater.
-$ grep even_deny_root /etc/security/faillock.conf
-even_deny_root Is it the case that the "even_deny_root" option is not set, is missing or commented out? |
+In order to avoid errors when manually editing these files, it is
+recommended to use the appropriate tools, such as authselect or authconfig,
+depending on the OS version.
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000044 |
+ SRG-OS-000021-GPOS-00005 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
+
+ CCE-86067-6: Lock Accounts Must Persist |
+
+ By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account. |
+ This rule ensures that the system lock out accounts using pam_faillock.so persist
+after system reboot. From "pam_faillock" man pages:
+Note that the default directory that "pam_faillock" uses is usually cleared on system
+boot so the access will be reenabled after system reboot. If that is undesirable, a different
+tally directory must be set with the "dir" option.
+
+pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
+defined to work as expected. In order to avoid errors when manually editing these files, it is
+recommended to use the appropriate tools, such as authselect or authconfig,
+depending on the OS version.
+
+The chosen profile expects the directory to be . |
+ Applicable - Configurable |
+ Verify that the operating system enforces the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. If it does not, this is a finding. |
+ To ensure the tally directory is configured correctly, run the following command:
+$ sudo grep 'dir =' /etc/security/faillock.conf
+The output should show that dir is set to something other than "/var/run/faillock" Is it the case that the "dir" option is not set to a non-default documented tally log directory, is missing or commented out? |
Configure the operating system to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
- This rule configures the system to lock out the root account after a number of
-incorrect login attempts using pam_faillock.so.
+ | This rule ensures that the system lock out accounts using pam_faillock.so persist
+after system reboot. From "pam_faillock" man pages:
+Note that the default directory that "pam_faillock" uses is usually cleared on system
+boot so the access will be reenabled after system reboot. If that is undesirable, a different
+tally directory must be set with the "dir" option.
pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig,
-depending on the OS version. |
+depending on the OS version.
+
+The chosen profile expects the directory to be .
medium |
|
|
@@ -854,7 +854,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system. |
- CCE-80763-6: Modify the System Login Banner |
+ CCE-80768-5: Enable GNOME3 Login Warning Banner |
Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
@@ -879,38 +879,20 @@
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've readconsent to terms in IS user agreem't." |
-
-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:
+ | 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.
-I've read & consent to terms in IS user agreem't. |
+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.
Applicable - Configurable |
Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
@@ -935,9 +917,12 @@
"I've read & consent to terms in IS user agreem't."
If it does not, this is a finding. |
- To check if the system login banner is compliant,
-run the following command:
-$ cat /etc/issue Is it the case that it does not display the required banner? |
+ To ensure a login warning banner is enabled, run the following:
+$ grep banner-message-enable /etc/dconf/db/gdm.d/*
+If properly configured, the output should be true.
+To ensure a login warning banner is locked and cannot be changed by a user, run the following:
+$ grep banner-message-enable /etc/dconf/db/gdm.d/locks/*
+If properly configured, the output should be /org/gnome/login-screen/banner-message-enable. Is it the case that it is not? |
Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:
@@ -961,38 +946,20 @@
"I've read & consent to terms in IS user agreem't."
If it does not, this is a finding. |
-
-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:
+ | 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.
-I've read & consent to terms in IS user agreem't. |
+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.
medium |
|
|
@@ -1005,7 +972,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system. |
- CCE-80905-3: Enable SSH Warning Banner |
+ CCE-80770-1: Set the GNOME3 Login Warning Banner Text |
Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
@@ -1030,15 +997,24 @@
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've readconsent to terms in IS user agreem't." |
- To enable the warning banner and ensure it is consistent
-across the system, add or correct the following line in
-
+ | 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/ssh/sshd_config:
+/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
-Banner /etc/issue
-Another section contains information on how to create an
-appropriate system-wide warning banner. |
+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.
Applicable - Configurable |
Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
@@ -1063,12 +1039,13 @@
"I've read & consent to terms in IS user agreem't."
If it does not, this is a finding. |
- To determine how the SSH daemon's Banner option is set, run the following command:
-
-$ sudo grep -i Banner /etc/ssh/sshd_config
-
-If a line indicating /etc/issue is returned, then the required value is set.
- Is it the case that the required value is not set? |
+
+To ensure the login warning banner text is properly set, run the following:
+$ grep banner-message-text /etc/dconf/db/gdm.d/*
+If properly configured, the proper banner text will appear.
+To ensure the login warning banner text is locked and cannot be changed by a user, run the following:
+$ grep banner-message-text /etc/dconf/db/gdm.d/locks/*
+If properly configured, the output should be /org/gnome/login-screen/banner-message-text. Is it the case that it does not? |
Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:
@@ -1092,15 +1069,24 @@
"I've read & consent to terms in IS user agreem't."
If it does not, this is a finding. |
- To enable the warning banner and ensure it is consistent
-across the system, add or correct the following line in
-
+ | 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/ssh/sshd_config:
+/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
-Banner /etc/issue
-Another section contains information on how to create an
-appropriate system-wide warning banner. |
+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.
medium |
|
|
@@ -1113,7 +1099,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system. |
- CCE-80768-5: Enable GNOME3 Login Warning Banner |
+ CCE-80905-3: Enable SSH Warning Banner |
Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
@@ -1138,20 +1124,15 @@
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've readconsent to terms in IS user agreem't." |
- 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. |
+ 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. |
Applicable - Configurable |
Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
@@ -1176,12 +1157,12 @@
"I've read & consent to terms in IS user agreem't."
If it does not, this is a finding. |
- To ensure a login warning banner is enabled, run the following:
-$ grep banner-message-enable /etc/dconf/db/gdm.d/*
-If properly configured, the output should be true.
-To ensure a login warning banner is locked and cannot be changed by a user, run the following:
-$ grep banner-message-enable /etc/dconf/db/gdm.d/locks/*
-If properly configured, the output should be /org/gnome/login-screen/banner-message-enable. Is it the case that it is not? |
+ To determine how the SSH daemon's Banner option is set, run the following command:
+
+$ sudo grep -i Banner /etc/ssh/sshd_config
+
+If a line indicating /etc/issue is returned, then the required value is set.
+ Is it the case that the required value is not set? |
Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:
@@ -1205,20 +1186,15 @@
"I've read & consent to terms in IS user agreem't."
If it does not, this is a finding. |
- 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. |
+ 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. |
medium |
|
|
@@ -1231,7 +1207,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system. |
- CCE-80770-1: Set the GNOME3 Login Warning Banner Text |
+ CCE-80763-6: Modify the System Login Banner |
Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
@@ -1256,24 +1232,38 @@
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've readconsent to terms in IS user agreem't." |
- 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
+ |
+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.
-/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. |
+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.
Applicable - Configurable |
Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
@@ -1298,13 +1288,9 @@
"I've read & consent to terms in IS user agreem't."
If it does not, this is a finding. |
-
-To ensure the login warning banner text is properly set, run the following:
-$ grep banner-message-text /etc/dconf/db/gdm.d/*
-If properly configured, the proper banner text will appear.
-To ensure the login warning banner text is locked and cannot be changed by a user, run the following:
-$ grep banner-message-text /etc/dconf/db/gdm.d/locks/*
-If properly configured, the output should be /org/gnome/login-screen/banner-message-text. Is it the case that it does not? |
+ To check if the system login banner is compliant,
+run the following command:
+$ cat /etc/issue Is it the case that it does not display the required banner? |
Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:
@@ -1328,24 +1314,38 @@
"I've read & consent to terms in IS user agreem't."
If it does not, this is a finding. |
- 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
+ |
+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.
-/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. |
+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.
medium |
|
|
@@ -1434,40 +1434,91 @@
TBD - Assigned by DISA after STIG release |
The operating system must retain a users session lock until that user reestablishes access using established identification and authentication procedures. |
- CCE-80940-0: Configure the tmux Lock Command |
+ CCE-80777-6: Enable GNOME3 Screensaver Lock After Idle Period |
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.
The session lock is implemented at the point where session activity can be determined.
Regardless of where the session lock is determined and implemented, once invoked, the session lock shall remain in place until the user re-authenticates. No other activity aside from re-authentication shall unlock the system. |
- To enable console screen locking in tmux terminal multiplexer,
-the vlock command must be configured to be used as a locking
-mechanism.
+ |
+To activate locking of the screensaver in the GNOME3 desktop when it is activated,
+add or set lock-enabled to true in
+/etc/dconf/db/local.d/00-security-settings. For example:
+[org/gnome/desktop/screensaver]
+lock-enabled=true
+
+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/lock-enabled
+After the settings have been set, run dconf update. |
+ Applicable - Configurable |
+ Verify the operating system retains a user's session lock until that user reestablishes access using established identification and authentication procedures. If it does not, this is a finding. |
+ To check the status of the idle screen lock activation, run the following command:
+
+$ gsettings get org.gnome.desktop.screensaver lock-enabled
+If properly configured, the output should be true.
+To ensure that users cannot change how long until the screensaver locks, run the following:
+$ grep lock-enabled /etc/dconf/db/local.d/locks/*
+If properly configured, the output for lock-enabled should be /org/gnome/desktop/screensaver/lock-enabled Is it the case that screensaver locking is not enabled and/or has not been set or configured correctly? |
+ Configure the operating system to retain a user's session lock until that user reestablishes access using established identification and authentication procedures. |
+
+To activate locking of the screensaver in the GNOME3 desktop when it is activated,
+add or set lock-enabled to true in
+/etc/dconf/db/local.d/00-security-settings. For example:
+[org/gnome/desktop/screensaver]
+lock-enabled=true
+
+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/lock-enabled
+After the settings have been set, run dconf update. |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000056 |
+ SRG-OS-000028-GPOS-00009 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must retain a users session lock until that user reestablishes access using established identification and authentication procedures. |
+
+ CCE-86135-1: Configure the tmux lock session key binding |
+
+ A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.
+
+The session lock is implemented at the point where session activity can be determined.
+
+Regardless of where the session lock is determined and implemented, once invoked, the session lock shall remain in place until the user re-authenticates. No other activity aside from re-authentication shall unlock the system. |
+ To set a key binding for the screen locking in tmux terminal multiplexer,
+the session-lock command must be bound to a key.
Add the following line to /etc/tmux.conf:
-set -g lock-command vlock .
+bind X lock-session .
The console can now be locked with the following key combination:
-ctrl+b :lock-session |
+Ctrl+b Shift+x
Applicable - Configurable |
Verify the operating system retains a user's session lock until that user reestablishes access using established identification and authentication procedures. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 enables the user to initiate a session lock with the following command:
+ | Verify Red Hat Enterprise Linux 8 enables the user to initiate a session lock trhough key bindings with the following commands:
-$ grep lock-command /etc/tmux.conf
+$ grep "lock-session" /etc/tmux.conf
-set -g lock-command vlock
+bind X lock-session
Then, verify that the /etc/tmux.conf file can be read by other users than root:
-$ sudo ls -al /etc/tmux.conf Is it the case that the "lock-command" is not set in the global settings to call "vlock"? |
+$ sudo ls -al /etc/tmux.conf
Is it the case that the "lock-session" is not bound to a specific key?
Configure the operating system to retain a user's session lock until that user reestablishes access using established identification and authentication procedures. |
- To enable console screen locking in tmux terminal multiplexer,
-the vlock command must be configured to be used as a locking
-mechanism.
+ | To set a key binding for the screen locking in tmux terminal multiplexer,
+the session-lock command must be bound to a key.
Add the following line to /etc/tmux.conf:
-set -g lock-command vlock .
+bind X lock-session .
The console can now be locked with the following key combination:
-ctrl+b :lock-session |
- medium |
+Ctrl+b Shift+x
+ low |
|
|
|
@@ -1572,47 +1623,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must retain a users session lock until that user reestablishes access using established identification and authentication procedures. |
- CCE-80777-6: Enable GNOME3 Screensaver Lock After Idle Period |
+ CCE-80940-0: Configure the tmux Lock Command |
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.
The session lock is implemented at the point where session activity can be determined.
Regardless of where the session lock is determined and implemented, once invoked, the session lock shall remain in place until the user re-authenticates. No other activity aside from re-authentication shall unlock the system. |
-
-To activate locking of the screensaver in the GNOME3 desktop when it is activated,
-add or set lock-enabled to true in
-/etc/dconf/db/local.d/00-security-settings. For example:
-[org/gnome/desktop/screensaver]
-lock-enabled=true
-
-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/lock-enabled
-After the settings have been set, run dconf update. |
+ To enable console screen locking in tmux terminal multiplexer,
+the vlock command must be configured to be used as a locking
+mechanism.
+Add the following line to /etc/tmux.conf:
+set -g lock-command vlock .
+The console can now be locked with the following key combination:
+ctrl+b :lock-session |
Applicable - Configurable |
Verify the operating system retains a user's session lock until that user reestablishes access using established identification and authentication procedures. If it does not, this is a finding. |
- To check the status of the idle screen lock activation, run the following command:
+ | Verify Red Hat Enterprise Linux 8 enables the user to initiate a session lock with the following command:
-$ gsettings get org.gnome.desktop.screensaver lock-enabled
-If properly configured, the output should be true.
-To ensure that users cannot change how long until the screensaver locks, run the following:
-$ grep lock-enabled /etc/dconf/db/local.d/locks/*
-If properly configured, the output for lock-enabled should be /org/gnome/desktop/screensaver/lock-enabled Is it the case that screensaver locking is not enabled and/or has not been set or configured correctly? |
+$ grep lock-command /etc/tmux.conf
+
+set -g lock-command vlock
+
+Then, verify that the /etc/tmux.conf file can be read by other users than root:
+
+$ sudo ls -al /etc/tmux.conf
Is it the case that the "lock-command" is not set in the global settings to call "vlock"?
Configure the operating system to retain a user's session lock until that user reestablishes access using established identification and authentication procedures. |
-
-To activate locking of the screensaver in the GNOME3 desktop when it is activated,
-add or set lock-enabled to true in
-/etc/dconf/db/local.d/00-security-settings. For example:
-[org/gnome/desktop/screensaver]
-lock-enabled=true
-
-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/lock-enabled
-After the settings have been set, run dconf update. |
+ To enable console screen locking in tmux terminal multiplexer,
+the vlock command must be configured to be used as a locking
+mechanism.
+Add the following line to /etc/tmux.conf:
+set -g lock-command vlock .
+The console can now be locked with the following key combination:
+ctrl+b :lock-session |
medium |
|
|
@@ -1670,49 +1713,6 @@
|
-
- | CCI-000056 |
- SRG-OS-000028-GPOS-00009 |
- TBD - Assigned by DISA after STIG release |
- The operating system must retain a users session lock until that user reestablishes access using established identification and authentication procedures. |
-
- CCE-86135-1: Configure the tmux lock session key binding |
-
- A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.
-
-The session lock is implemented at the point where session activity can be determined.
-
-Regardless of where the session lock is determined and implemented, once invoked, the session lock shall remain in place until the user re-authenticates. No other activity aside from re-authentication shall unlock the system. |
- To set a key binding for the screen locking in tmux terminal multiplexer,
-the session-lock command must be bound to a key.
-Add the following line to /etc/tmux.conf:
-bind X lock-session .
-The console can now be locked with the following key combination:
-Ctrl+b Shift+x |
- Applicable - Configurable |
- Verify the operating system retains a user's session lock until that user reestablishes access using established identification and authentication procedures. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 enables the user to initiate a session lock trhough key bindings with the following commands:
-
-$ grep "lock-session" /etc/tmux.conf
-
-bind X lock-session
-
-Then, verify that the /etc/tmux.conf file can be read by other users than root:
-
-$ sudo ls -al /etc/tmux.conf Is it the case that the "lock-session" is not bound to a specific key? |
- Configure the operating system to retain a user's session lock until that user reestablishes access using established identification and authentication procedures. |
- To set a key binding for the screen locking in tmux terminal multiplexer,
-the session-lock command must be bound to a key.
-Add the following line to /etc/tmux.conf:
-bind X lock-session .
-The console can now be locked with the following key combination:
-Ctrl+b Shift+x |
- low |
- |
- |
- |
-
-
| CCI-000056 |
SRG-OS-000028-GPOS-00009 |
@@ -1756,30 +1756,29 @@
TBD - Assigned by DISA after STIG release |
The operating system must initiate a session lock after a 15-minute period of inactivity for all connection types. |
- CCE-80776-8: Set GNOME3 Screensaver Lock Delay After Activation Period |
+ CCE-80781-8: Ensure Users Cannot Change GNOME3 Session Idle Settings |
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
The session lock is implemented at the point where session activity can be determined and/or controlled. |
- To activate the locking delay of the screensaver in the GNOME3 desktop when
-the screensaver is activated, add or set lock-delay to uint32 in
-/etc/dconf/db/local.d/00-security-settings. For example:
-[org/gnome/desktop/screensaver]
-lock-delay=uint32
-
+ | If not already configured, ensure that users cannot change GNOME3 session idle settings
+by adding /org/gnome/desktop/session/idle-delay
+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. |
Applicable - Configurable |
Verify the operating system initiates a session lock after a 15-minute period of inactivity for all connection types. If it does not, this is a finding. |
- To check that the screen locks immediately when activated, run the following command:
-$ gsettings get org.gnome.desktop.screensaver lock-delay
-If properly configured, the output should be 'uint32 '. Is it the case that the screensaver lock delay is missing, or is set to a value greater than ? |
+ To ensure that users cannot change session idle and lock settings, run the following:
+$ grep 'idle-delay' /etc/dconf/db/local.d/locks/*
+If properly configured, the output should return:
+/org/gnome/desktop/session/idle-delay Is it the case that idle-delay is not locked? |
Configure the operating system to initiate a session lock after a 15-minute period of inactivity for all connection types. |
- To activate the locking delay of the screensaver in the GNOME3 desktop when
-the screensaver is activated, add or set lock-delay to uint32 in
-/etc/dconf/db/local.d/00-security-settings. For example:
-[org/gnome/desktop/screensaver]
-lock-delay=uint32
-
+ | If not already configured, ensure that users cannot change GNOME3 session idle settings
+by adding /org/gnome/desktop/session/idle-delay
+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. |
medium |
|
@@ -1871,29 +1870,30 @@
TBD - Assigned by DISA after STIG release |
The operating system must initiate a session lock after a 15-minute period of inactivity for all connection types. |
- CCE-80781-8: Ensure Users Cannot Change GNOME3 Session Idle Settings |
+ CCE-80776-8: Set GNOME3 Screensaver Lock Delay After Activation Period |
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
The session lock is implemented at the point where session activity can be determined and/or controlled. |
- If not already configured, ensure that users cannot change GNOME3 session idle settings
-by adding /org/gnome/desktop/session/idle-delay
-to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
-For example:
-/org/gnome/desktop/session/idle-delay
+ | To activate the locking delay of the screensaver in the GNOME3 desktop when
+the screensaver is activated, add or set lock-delay to uint32 in
+/etc/dconf/db/local.d/00-security-settings. For example:
+[org/gnome/desktop/screensaver]
+lock-delay=uint32
+
After the settings have been set, run dconf update. |
Applicable - Configurable |
Verify the operating system initiates a session lock after a 15-minute period of inactivity for all connection types. If it does not, this is a finding. |
- To ensure that users cannot change session idle and lock settings, run the following:
-$ grep 'idle-delay' /etc/dconf/db/local.d/locks/*
-If properly configured, the output should return:
-/org/gnome/desktop/session/idle-delay Is it the case that idle-delay is not locked? |
+ To check that the screen locks immediately when activated, run the following command:
+$ gsettings get org.gnome.desktop.screensaver lock-delay
+If properly configured, the output should be 'uint32 '. Is it the case that the screensaver lock delay is missing, or is set to a value greater than ? |
Configure the operating system to initiate a session lock after a 15-minute period of inactivity for all connection types. |
- If not already configured, ensure that users cannot change GNOME3 session idle settings
-by adding /org/gnome/desktop/session/idle-delay
-to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
-For example:
-/org/gnome/desktop/session/idle-delay
+ | To activate the locking delay of the screensaver in the GNOME3 desktop when
+the screensaver is activated, add or set lock-delay to uint32 in
+/etc/dconf/db/local.d/00-security-settings. For example:
+[org/gnome/desktop/screensaver]
+lock-delay=uint32
+
After the settings have been set, run dconf update. |
medium |
|
@@ -1951,43 +1951,92 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide the capability for users to directly initiate a session lock for all connection types. |
- CCE-80940-0: Configure the tmux Lock Command |
+ CCE-80777-6: Enable GNOME3 Screensaver Lock After Idle Period |
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.
The session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, operating systems need to provide users with the ability to manually invoke a session lock so users may secure their session should the need arise for them to temporarily vacate the immediate physical vicinity. |
- To enable console screen locking in tmux terminal multiplexer,
-the vlock command must be configured to be used as a locking
-mechanism.
-Add the following line to /etc/tmux.conf:
-set -g lock-command vlock .
-The console can now be locked with the following key combination:
-ctrl+b :lock-session |
+
+To activate locking of the screensaver in the GNOME3 desktop when it is activated,
+add or set lock-enabled to true in
+/etc/dconf/db/local.d/00-security-settings. For example:
+[org/gnome/desktop/screensaver]
+lock-enabled=true
+
+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/lock-enabled
+After the settings have been set, run dconf update. |
Applicable - Configurable |
Verify the operating system provides the capability for users to directly initiate a session lock for all connection types. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 enables the user to initiate a session lock with the following command:
-
-$ grep lock-command /etc/tmux.conf
-
-set -g lock-command vlock
-
-Then, verify that the /etc/tmux.conf file can be read by other users than root:
+ | To check the status of the idle screen lock activation, run the following command:
-$ sudo ls -al /etc/tmux.conf Is it the case that the "lock-command" is not set in the global settings to call "vlock"? |
+$ gsettings get org.gnome.desktop.screensaver lock-enabled
+If properly configured, the output should be true.
+To ensure that users cannot change how long until the screensaver locks, run the following:
+$ grep lock-enabled /etc/dconf/db/local.d/locks/*
+If properly configured, the output for lock-enabled should be /org/gnome/desktop/screensaver/lock-enabled Is it the case that screensaver locking is not enabled and/or has not been set or configured correctly?
Configure the operating system to provide the capability for users to directly initiate a session lock for all connection types. |
- To enable console screen locking in tmux terminal multiplexer,
-the vlock command must be configured to be used as a locking
-mechanism.
-Add the following line to /etc/tmux.conf:
-set -g lock-command vlock .
-The console can now be locked with the following key combination:
-ctrl+b :lock-session |
- medium |
- |
- |
- |
-
-
+
+To activate locking of the screensaver in the GNOME3 desktop when it is activated,
+add or set lock-enabled to true in
+/etc/dconf/db/local.d/00-security-settings. For example:
+[org/gnome/desktop/screensaver]
+lock-enabled=true
+
+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/lock-enabled
+After the settings have been set, run dconf update. |
+
medium |
+
|
+
|
+
|
+
+
+
+ | CCI-000058 |
+ SRG-OS-000030-GPOS-00011 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must provide the capability for users to directly initiate a session lock for all connection types. |
+
+ CCE-86135-1: Configure the tmux lock session key binding |
+
+ A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.
+
+The session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, operating systems need to provide users with the ability to manually invoke a session lock so users may secure their session should the need arise for them to temporarily vacate the immediate physical vicinity. |
+ To set a key binding for the screen locking in tmux terminal multiplexer,
+the session-lock command must be bound to a key.
+Add the following line to /etc/tmux.conf:
+bind X lock-session .
+The console can now be locked with the following key combination:
+Ctrl+b Shift+x |
+ Applicable - Configurable |
+ Verify the operating system provides the capability for users to directly initiate a session lock for all connection types. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 enables the user to initiate a session lock trhough key bindings with the following commands:
+
+$ grep "lock-session" /etc/tmux.conf
+
+bind X lock-session
+
+Then, verify that the /etc/tmux.conf file can be read by other users than root:
+
+$ sudo ls -al /etc/tmux.conf Is it the case that the "lock-session" is not bound to a specific key? |
+ Configure the operating system to provide the capability for users to directly initiate a session lock for all connection types. |
+ To set a key binding for the screen locking in tmux terminal multiplexer,
+the session-lock command must be bound to a key.
+Add the following line to /etc/tmux.conf:
+bind X lock-session .
+The console can now be locked with the following key combination:
+Ctrl+b Shift+x |
+ low |
+ |
+ |
+ |
+
+
| CCI-000058 |
SRG-OS-000030-GPOS-00011 |
@@ -2083,45 +2132,37 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide the capability for users to directly initiate a session lock for all connection types. |
- CCE-80777-6: Enable GNOME3 Screensaver Lock After Idle Period |
+ CCE-80940-0: Configure the tmux Lock Command |
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.
The session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, operating systems need to provide users with the ability to manually invoke a session lock so users may secure their session should the need arise for them to temporarily vacate the immediate physical vicinity. |
-
-To activate locking of the screensaver in the GNOME3 desktop when it is activated,
-add or set lock-enabled to true in
-/etc/dconf/db/local.d/00-security-settings. For example:
-[org/gnome/desktop/screensaver]
-lock-enabled=true
-
-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/lock-enabled
-After the settings have been set, run dconf update. |
+ To enable console screen locking in tmux terminal multiplexer,
+the vlock command must be configured to be used as a locking
+mechanism.
+Add the following line to /etc/tmux.conf:
+set -g lock-command vlock .
+The console can now be locked with the following key combination:
+ctrl+b :lock-session |
Applicable - Configurable |
Verify the operating system provides the capability for users to directly initiate a session lock for all connection types. If it does not, this is a finding. |
- To check the status of the idle screen lock activation, run the following command:
+ | Verify Red Hat Enterprise Linux 8 enables the user to initiate a session lock with the following command:
-$ gsettings get org.gnome.desktop.screensaver lock-enabled
-If properly configured, the output should be true.
-To ensure that users cannot change how long until the screensaver locks, run the following:
-$ grep lock-enabled /etc/dconf/db/local.d/locks/*
-If properly configured, the output for lock-enabled should be /org/gnome/desktop/screensaver/lock-enabled Is it the case that screensaver locking is not enabled and/or has not been set or configured correctly? |
+$ grep lock-command /etc/tmux.conf
+
+set -g lock-command vlock
+
+Then, verify that the /etc/tmux.conf file can be read by other users than root:
+
+$ sudo ls -al /etc/tmux.conf
Is it the case that the "lock-command" is not set in the global settings to call "vlock"?
Configure the operating system to provide the capability for users to directly initiate a session lock for all connection types. |
-
-To activate locking of the screensaver in the GNOME3 desktop when it is activated,
-add or set lock-enabled to true in
-/etc/dconf/db/local.d/00-security-settings. For example:
-[org/gnome/desktop/screensaver]
-lock-enabled=true
-
-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/lock-enabled
-After the settings have been set, run dconf update. |
+ To enable console screen locking in tmux terminal multiplexer,
+the vlock command must be configured to be used as a locking
+mechanism.
+Add the following line to /etc/tmux.conf:
+set -g lock-command vlock .
+The console can now be locked with the following key combination:
+ctrl+b :lock-session |
medium |
|
|
@@ -2177,47 +2218,6 @@
|
-
- | CCI-000058 |
- SRG-OS-000030-GPOS-00011 |
- TBD - Assigned by DISA after STIG release |
- The operating system must provide the capability for users to directly initiate a session lock for all connection types. |
-
- CCE-86135-1: Configure the tmux lock session key binding |
-
- A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.
-
-The session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, operating systems need to provide users with the ability to manually invoke a session lock so users may secure their session should the need arise for them to temporarily vacate the immediate physical vicinity. |
- To set a key binding for the screen locking in tmux terminal multiplexer,
-the session-lock command must be bound to a key.
-Add the following line to /etc/tmux.conf:
-bind X lock-session .
-The console can now be locked with the following key combination:
-Ctrl+b Shift+x |
- Applicable - Configurable |
- Verify the operating system provides the capability for users to directly initiate a session lock for all connection types. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 enables the user to initiate a session lock trhough key bindings with the following commands:
-
-$ grep "lock-session" /etc/tmux.conf
-
-bind X lock-session
-
-Then, verify that the /etc/tmux.conf file can be read by other users than root:
-
-$ sudo ls -al /etc/tmux.conf Is it the case that the "lock-session" is not bound to a specific key? |
- Configure the operating system to provide the capability for users to directly initiate a session lock for all connection types. |
- To set a key binding for the screen locking in tmux terminal multiplexer,
-the session-lock command must be bound to a key.
-Add the following line to /etc/tmux.conf:
-bind X lock-session .
-The console can now be locked with the following key combination:
-Ctrl+b Shift+x |
- low |
- |
- |
- |
-
-
| CCI-000058 |
SRG-OS-000030-GPOS-00011 |
@@ -2259,32 +2259,31 @@
TBD - Assigned by DISA after STIG release |
The operating system must conceal, via the session lock, information previously visible on the display with a publicly viewable image. |
- CCE-80776-8: Set GNOME3 Screensaver Lock Delay After Activation Period |
+ CCE-80781-8: Ensure Users Cannot Change GNOME3 Session Idle Settings |
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence.
The session lock is implemented at the point where session activity can be determined. The operating system session lock event must include an obfuscation of the display screen so as to prevent other users from reading what was previously displayed.
Publicly viewable images can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, a clock, a battery life indicator, or a blank screen, with the additional caveat that none of the images convey sensitive information. |
- To activate the locking delay of the screensaver in the GNOME3 desktop when
-the screensaver is activated, add or set lock-delay to uint32 in
-/etc/dconf/db/local.d/00-security-settings. For example:
-[org/gnome/desktop/screensaver]
-lock-delay=uint32
-
+ | If not already configured, ensure that users cannot change GNOME3 session idle settings
+by adding /org/gnome/desktop/session/idle-delay
+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. |
Applicable - Configurable |
Verify the operating system conceals, via the session lock, information previously visible on the display with a publicly viewable image. If it does not, this is a finding. |
- To check that the screen locks immediately when activated, run the following command:
-$ gsettings get org.gnome.desktop.screensaver lock-delay
-If properly configured, the output should be 'uint32 '. Is it the case that the screensaver lock delay is missing, or is set to a value greater than ? |
+ To ensure that users cannot change session idle and lock settings, run the following:
+$ grep 'idle-delay' /etc/dconf/db/local.d/locks/*
+If properly configured, the output should return:
+/org/gnome/desktop/session/idle-delay Is it the case that idle-delay is not locked? |
Configure the operating system to conceal, via the session lock, information previously visible on the display with a publicly viewable image. |
- To activate the locking delay of the screensaver in the GNOME3 desktop when
-the screensaver is activated, add or set lock-delay to uint32 in
-/etc/dconf/db/local.d/00-security-settings. For example:
-[org/gnome/desktop/screensaver]
-lock-delay=uint32
-
+ | If not already configured, ensure that users cannot change GNOME3 session idle settings
+by adding /org/gnome/desktop/session/idle-delay
+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. |
medium |
|
@@ -2380,31 +2379,32 @@
TBD - Assigned by DISA after STIG release |
The operating system must conceal, via the session lock, information previously visible on the display with a publicly viewable image. |
- CCE-80781-8: Ensure Users Cannot Change GNOME3 Session Idle Settings |
+ CCE-80776-8: Set GNOME3 Screensaver Lock Delay After Activation Period |
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence.
The session lock is implemented at the point where session activity can be determined. The operating system session lock event must include an obfuscation of the display screen so as to prevent other users from reading what was previously displayed.
Publicly viewable images can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, a clock, a battery life indicator, or a blank screen, with the additional caveat that none of the images convey sensitive information. |
- If not already configured, ensure that users cannot change GNOME3 session idle settings
-by adding /org/gnome/desktop/session/idle-delay
-to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
-For example:
-/org/gnome/desktop/session/idle-delay
+ | To activate the locking delay of the screensaver in the GNOME3 desktop when
+the screensaver is activated, add or set lock-delay to uint32 in
+/etc/dconf/db/local.d/00-security-settings. For example:
+[org/gnome/desktop/screensaver]
+lock-delay=uint32
+
After the settings have been set, run dconf update. |
Applicable - Configurable |
Verify the operating system conceals, via the session lock, information previously visible on the display with a publicly viewable image. If it does not, this is a finding. |
- To ensure that users cannot change session idle and lock settings, run the following:
-$ grep 'idle-delay' /etc/dconf/db/local.d/locks/*
-If properly configured, the output should return:
-/org/gnome/desktop/session/idle-delay Is it the case that idle-delay is not locked? |
+ To check that the screen locks immediately when activated, run the following command:
+$ gsettings get org.gnome.desktop.screensaver lock-delay
+If properly configured, the output should be 'uint32 '. Is it the case that the screensaver lock delay is missing, or is set to a value greater than ? |
Configure the operating system to conceal, via the session lock, information previously visible on the display with a publicly viewable image. |
- If not already configured, ensure that users cannot change GNOME3 session idle settings
-by adding /org/gnome/desktop/session/idle-delay
-to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
-For example:
-/org/gnome/desktop/session/idle-delay
+ | To activate the locking delay of the screensaver in the GNOME3 desktop when
+the screensaver is activated, add or set lock-delay to uint32 in
+/etc/dconf/db/local.d/00-security-settings. For example:
+[org/gnome/desktop/screensaver]
+lock-delay=uint32
+
After the settings have been set, run dconf update. |
medium |
|
@@ -2418,45 +2418,35 @@
TBD - Assigned by DISA after STIG release |
The operating system must conceal, via the session lock, information previously visible on the display with a publicly viewable image. |
- CCE-90782-4: Support session locking with tmux (not enforcing) |
+ CCE-82199-1: Configure tmux to lock session after inactivity |
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence.
The session lock is implemented at the point where session activity can be determined. The operating system session lock event must include an obfuscation of the display screen so as to prevent other users from reading what was previously displayed.
Publicly viewable images can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, a clock, a battery life indicator, or a blank screen, with the additional caveat that none of the images convey sensitive information. |
- The tmux terminal multiplexer is used to implement
-automatic session locking. It should be started from
-/etc/bashrc or drop-in files within /etc/profile.d/. |
+ To enable console screen locking in tmux terminal multiplexer
+after a period of inactivity,
+the lock-after-time option has to be set to a value greater than 0 and less than
+or equal to 900 in /etc/tmux.conf. |
Applicable - Configurable |
Verify the operating system conceals, via the session lock, information previously visible on the display with a publicly viewable image. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 shell initialization file is configured to start each shell with the tmux terminal multiplexer.
-
-Determine the location of the tmux script with the following command:
-
-$ sudo grep tmux /etc/bashrc /etc/profile.d/*
-
-/etc/profile.d/tmux.sh: case "$name" in (sshd|login) tmux ;; esac
-
-Review the tmux script by using the following example:
+ | Verify Red Hat Enterprise Linux 8 initiates a session lock after 15 minutes of inactivity.
-$ cat /etc/profile.d/tmux.sh
+Check the value of the system inactivity timeout with the following command:
-if [ "$PS1" ]; then
-parent=$(ps -o ppid= -p $$)
-name=$(ps -o comm= -p $parent)
-case "$name" in (sshd|login) tmux ;; esac
-fi
+$ grep -i lock-after-time /etc/tmux.conf
-If the shell file is not configured as the example above, is commented out, or is missing, this is a finding.
+set -g lock-after-time 900
-Determine if tmux is currently running with the following command:
+Then, verify that the /etc/tmux.conf file can be read by other users than root:
-$ sudo ps all | grep tmux | grep -v grep Is it the case that the command does not produce output? |
+$ sudo ls -al /etc/tmux.conf
Is it the case that "lock-after-time" is not set to "900" or less in the global tmux configuration file to enforce session lock after inactivity?
Configure the operating system to conceal, via the session lock, information previously visible on the display with a publicly viewable image. |
- The tmux terminal multiplexer is used to implement
-automatic session locking. It should be started from
-/etc/bashrc or drop-in files within /etc/profile.d/. |
+ To enable console screen locking in tmux terminal multiplexer
+after a period of inactivity,
+the lock-after-time option has to be set to a value greater than 0 and less than
+or equal to 900 in /etc/tmux.conf. |
medium |
|
|
@@ -2469,35 +2459,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must conceal, via the session lock, information previously visible on the display with a publicly viewable image. |
- CCE-82199-1: Configure tmux to lock session after inactivity |
+ CCE-90782-4: Support session locking with tmux (not enforcing) |
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence.
The session lock is implemented at the point where session activity can be determined. The operating system session lock event must include an obfuscation of the display screen so as to prevent other users from reading what was previously displayed.
Publicly viewable images can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, a clock, a battery life indicator, or a blank screen, with the additional caveat that none of the images convey sensitive information. |
- To enable console screen locking in tmux terminal multiplexer
-after a period of inactivity,
-the lock-after-time option has to be set to a value greater than 0 and less than
-or equal to 900 in /etc/tmux.conf. |
+ The tmux terminal multiplexer is used to implement
+automatic session locking. It should be started from
+/etc/bashrc or drop-in files within /etc/profile.d/. |
Applicable - Configurable |
Verify the operating system conceals, via the session lock, information previously visible on the display with a publicly viewable image. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 initiates a session lock after 15 minutes of inactivity.
+ | Verify Red Hat Enterprise Linux 8 shell initialization file is configured to start each shell with the tmux terminal multiplexer.
-Check the value of the system inactivity timeout with the following command:
+Determine the location of the tmux script with the following command:
-$ grep -i lock-after-time /etc/tmux.conf
+$ sudo grep tmux /etc/bashrc /etc/profile.d/*
-set -g lock-after-time 900
+/etc/profile.d/tmux.sh: case "$name" in (sshd|login) tmux ;; esac
-Then, verify that the /etc/tmux.conf file can be read by other users than root:
+Review the tmux script by using the following example:
-$ sudo ls -al /etc/tmux.conf Is it the case that "lock-after-time" is not set to "900" or less in the global tmux configuration file to enforce session lock after inactivity? |
+$ cat /etc/profile.d/tmux.sh
+
+if [ "$PS1" ]; then
+parent=$(ps -o ppid= -p $$)
+name=$(ps -o comm= -p $parent)
+case "$name" in (sshd|login) tmux ;; esac
+fi
+
+If the shell file is not configured as the example above, is commented out, or is missing, this is a finding.
+
+Determine if tmux is currently running with the following command:
+
+$ sudo ps all | grep tmux | grep -v grep
Is it the case that the command does not produce output?
Configure the operating system to conceal, via the session lock, information previously visible on the display with a publicly viewable image. |
- To enable console screen locking in tmux terminal multiplexer
-after a period of inactivity,
-the lock-after-time option has to be set to a value greater than 0 and less than
-or equal to 900 in /etc/tmux.conf. |
+ The tmux terminal multiplexer is used to implement
+automatic session locking. It should be started from
+/etc/bashrc or drop-in files within /etc/profile.d/. |
medium |
|
|
@@ -2601,48 +2601,6 @@
|
-
- | CCI-000068 |
- SRG-OS-000033-GPOS-00014 |
- TBD - Assigned by DISA after STIG release |
- The operating system must implement DoD-approved encryption to protect the confidentiality of remote access sessions. |
-
- CCE-84027-2: Set kernel parameter 'crypto.fips_enabled' to 1 |
-
- Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.
-
-Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
-
-Encryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP), thereby providing a degree of confidentiality. The encryption strength of a mechanism is selected based on the security categorization of the information. |
- System running in FIPS mode is indicated by kernel parameter
-'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
-To enable FIPS mode, run the following command:
-fips-mode-setup --enable
-
-To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
-parameters during system installation so key generation is done with FIPS-approved algorithms
-and continuous monitoring tests in place. |
- Applicable - Configurable |
- Verify the operating system implements DoD-approved encryption to protect the confidentiality of remote access sessions. If it does not, this is a finding. |
- To verify that kernel parameter 'crypto.fips_enabled' is set properly, run the following command:
-sysctl crypto.fips_enabled
-The output should contain the following:
-crypto.fips_enabled = 1 Is it the case that crypto.fips_enabled is not 1? |
- Configure the operating system to implement DoD-approved encryption to protect the confidentiality of remote access sessions. |
- System running in FIPS mode is indicated by kernel parameter
-'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
-To enable FIPS mode, run the following command:
-fips-mode-setup --enable
-
-To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
-parameters during system installation so key generation is done with FIPS-approved algorithms
-and continuous monitoring tests in place. |
- high |
- |
- |
- |
-
-
| CCI-000068 |
SRG-OS-000033-GPOS-00014 |
@@ -2700,6 +2658,48 @@
|
+
+ | CCI-000068 |
+ SRG-OS-000033-GPOS-00014 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must implement DoD-approved encryption to protect the confidentiality of remote access sessions. |
+
+ CCE-84027-2: Set kernel parameter 'crypto.fips_enabled' to 1 |
+
+ Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+
+Encryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP), thereby providing a degree of confidentiality. The encryption strength of a mechanism is selected based on the security categorization of the information. |
+ System running in FIPS mode is indicated by kernel parameter
+'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
+To enable FIPS mode, run the following command:
+fips-mode-setup --enable
+
+To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
+parameters during system installation so key generation is done with FIPS-approved algorithms
+and continuous monitoring tests in place. |
+ Applicable - Configurable |
+ Verify the operating system implements DoD-approved encryption to protect the confidentiality of remote access sessions. If it does not, this is a finding. |
+ To verify that kernel parameter 'crypto.fips_enabled' is set properly, run the following command:
+sysctl crypto.fips_enabled
+The output should contain the following:
+crypto.fips_enabled = 1 Is it the case that crypto.fips_enabled is not 1? |
+ Configure the operating system to implement DoD-approved encryption to protect the confidentiality of remote access sessions. |
+ System running in FIPS mode is indicated by kernel parameter
+'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
+To enable FIPS mode, run the following command:
+fips-mode-setup --enable
+
+To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
+parameters during system installation so key generation is done with FIPS-approved algorithms
+and continuous monitoring tests in place. |
+ high |
+ |
+ |
+ |
+
+
| CCI-000068 |
SRG-OS-000033-GPOS-00014 |
@@ -2760,7 +2760,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-85944-7: Record Any Attempts to Run ssh-agent |
+ CCE-80700-8: Record Any Attempts to Run semanage |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -2768,33 +2768,33 @@
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
At a minimum, the audit system should collect any execution attempt
-of the ssh-agent command for all users and root. If the auditd
+of the semanage 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
+-a always,exit -F path=/usr/sbin/semanage -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/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
-$ sudo auditctl -l | grep ssh-agent
+$ sudo auditctl -l | grep semanage
--a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
At a minimum, the audit system should collect any execution attempt
-of the ssh-agent command for all users and root. If the auditd
+of the semanage 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
+-a always,exit -F path=/usr/sbin/semanage -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/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -2807,7 +2807,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80730-5: Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
+ CCE-80989-7: Ensure auditd Collects Information on the Use of Privileged Commands - mount |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -2819,33 +2819,29 @@
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/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "mount" command with the following command:
-$ sudo auditctl -l | grep pam_timestamp_check
+$ sudo auditctl -l | grep mount
--a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -2905,54 +2901,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80728-9: Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
-
- Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-
-Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
-
-Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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 |
- Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "gpasswd" command with the following command:
-
-$ sudo auditctl -l | grep gpasswd
-
--a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-000130 |
- SRG-OS-000037-GPOS-00015 |
- TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish what type of events occurred. |
-
- CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
+ CCE-80731-3: Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -2964,29 +2913,29 @@
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
+-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/su -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "passwd" command with the following command:
-$ sudo auditctl -l | grep su
+$ sudo auditctl -l | grep passwd
--a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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
+-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/su -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -2999,78 +2948,34 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
+ CCE-80872-5: Enable auditd Service |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | The auditd service is an essential userspace component of
+the Linux Auditing System, as it is responsible for writing audit records to
+disk.
-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 |
+The auditd service can be enabled with the following command:
+$ sudo systemctl enable auditd.service
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r truncate /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep truncate /etc/audit/audit.rules
-
-The output should be the following:
+ |
--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+Run the following command to determine the current status of the
+auditd service:
+$ sudo systemctl is-active auditd
+If the service is running, it should return the following: active
Is it the case that the auditd service is not running?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | The auditd service is an essential userspace component of
+the Linux Auditing System, as it is responsible for writing audit records to
+disk.
-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 |
+The auditd service can be enabled with the following command:
+$ sudo systemctl enable auditd.service
medium |
|
|
@@ -3083,41 +2988,49 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80729-7: Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
+ CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | 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 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 |
+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_mod
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "newgrp" command with the following command:
-
-$ sudo auditctl -l | grep newgrp
-
--a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+chown system call, run the following command:
+$ sudo grep "chown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | 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 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 |
+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_mod
medium |
|
|
@@ -3130,72 +3043,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
+ CCE-80701-6: Record Any Attempts to Run setsebool |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 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
+-a always,exit -F path=/usr/sbin/setsebool -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 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=access |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r open_by_handle_at /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep open_by_handle_at /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep setsebool
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 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
+-a always,exit -F path=/usr/sbin/setsebool -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 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=access |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -3208,96 +3090,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
+ CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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_mod |
- Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-lchown system call, run the following command:
-$ sudo grep "lchown" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-000130 |
- SRG-OS-000037-GPOS-00015 |
- TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish what type of events occurred. |
-
- CCE-89455-0: Ensure auditd Collects Information on the Use of Privileged Commands - kmod |
-
- Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-
-Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
-
-Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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/kmod -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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-w /etc/sudoers -p wa -k actions
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "kmod" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-$ sudo auditctl -l | grep kmod
+$ sudo auditctl -l | grep /etc/sudoers
--a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-kmod Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers -p wa -k actions
medium |
|
|
@@ -3310,7 +3137,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -3323,21 +3150,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+$ sudo auditctl -l | grep -E '(/etc/shadow)'
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -3345,14 +3172,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -3365,7 +3192,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80733-9: Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
+ CCE-89455-0: Ensure auditd Collects Information on the Use of Privileged Commands - kmod |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -3377,29 +3204,29 @@
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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/bin/kmod -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postqueue" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "kmod" command with the following command:
-$ sudo auditctl -l | grep postqueue
+$ sudo auditctl -l | grep kmod
--a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-kmod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/bin/kmod -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -3412,41 +3239,120 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-89446-9: Record Any Attempts to Run chacl |
+ CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | 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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 lines to
+utility to read audit rules during daemon startup, add the following line 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 |
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
+ | To determine if the system is configured to audit calls to the
+fsetxattr system call, run the following command:
+$ sudo grep "fsetxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+ medium |
+ |
+ |
+ |
+
-$ sudo auditctl -l | grep chacl
+
+ | CCI-000130 |
+ SRG-OS-000037-GPOS-00015 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must produce audit records containing information to establish what type of events occurred. |
--a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out?
+ CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
+
+ Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+
+Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+
+Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
+ 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+setxattr system call, run the following command:
+$ sudo grep "setxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | 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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -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 lines to
+utility to read audit rules during daemon startup, add the following line 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 |
+-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -3459,41 +3365,78 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80740-4: Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
+ CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | 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 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 |
+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=access
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-$ sudo auditctl -l | grep unix_chkpwd
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r truncate /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep truncate /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | 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 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 |
+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=access
medium |
|
|
@@ -3506,41 +3449,65 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
+ CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+
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 |
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
-
-$ sudo auditctl -l | grep usermod
-
--a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+removexattr system call, run the following command:
+$ sudo grep "removexattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+
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 |
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -3553,41 +3520,78 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
+ CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | 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 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=access
+
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 |
+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=access
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
-$ sudo auditctl -l | grep sudo
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r ftruncate /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep ftruncate /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | 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 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=access
+
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 |
+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=access
medium |
|
|
@@ -3600,7 +3604,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80726-3: Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
+ CCE-80732-1: Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -3612,29 +3616,29 @@
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
+-a always,exit -F path=/usr/sbin/postdrop -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 |
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chsh" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postdrop" command with the following command:
-$ sudo auditctl -l | grep chsh
+$ sudo auditctl -l | grep postdrop
--a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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
+-a always,exit -F path=/usr/sbin/postdrop -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 |
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -3647,7 +3651,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
+ CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -3660,17 +3664,17 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-unlink system call, run the following command:
-$ sudo grep "unlink" /etc/audit/audit.*
+unlinkat system call, run the following command:
+$ sudo grep "unlinkat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
@@ -3680,12 +3684,12 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -3698,7 +3702,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80741-2: Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
+ CCE-80728-9: Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -3710,29 +3714,29 @@
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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "userhelper" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "gpasswd" command with the following command:
-$ sudo auditctl -l | grep userhelper
+$ sudo auditctl -l | grep gpasswd
--a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -3745,45 +3749,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
+ CCE-80725-5: Ensure auditd Collects Information on the Use of Privileged Commands - chage |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
+ 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 |
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-finit_module system call, run the following command:
-$ sudo grep "finit_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chage" command with the following command:
--a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -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:
+$ sudo auditctl -l | grep chage
--a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -F key=modules |
+-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out?
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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 |
medium |
|
|
@@ -3796,49 +3796,19 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
+ CCE-81043-2: Ensure the audit Subsystem is Installed |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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 |
+ The audit package should be installed. |
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/shadow)'
-
--w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
+ Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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 |
+ The audit package should be installed. |
medium |
|
|
@@ -3851,88 +3821,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80727-1: Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
+ CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | 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 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 |
+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_mod
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "crontab" command with the following command:
-
-$ sudo auditctl -l | grep crontab
-
--a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fchown system call, run the following command:
+$ sudo grep "fchown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-000130 |
- SRG-OS-000037-GPOS-00015 |
- TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish what type of events occurred. |
-
- CCE-80701-6: Record Any Attempts to Run setsebool |
-
- Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-
-Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
-
-Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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
+ | 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 path=/usr/sbin/setsebool -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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
- Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
+-a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-$ sudo auditctl -l | grep setsebool
+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
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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/sbin/setsebool -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
+utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
medium |
|
|
@@ -3945,7 +3882,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
+ CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -3957,60 +3894,60 @@
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
+-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 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
+-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 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
+-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 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 |
+-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=access
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r creat /etc/audit/rules.d
+$ sudo grep -r open_by_handle_at /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep creat /etc/audit/audit.rules
+$ sudo grep open_by_handle_at /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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
+-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 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
+-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 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
+-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 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 |
+-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=access
medium |
|
|
@@ -4023,100 +3960,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80722-2: Ensure auditd Collects Information on Exporting to Media (successful) |
+ CCE-80729-7: Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | 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 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 |
+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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-mount system call, run the following command:
-$ sudo grep "mount" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-000130 |
- SRG-OS-000037-GPOS-00015 |
- TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish what type of events occurred. |
-
- CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
-
- Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "newgrp" command with the following command:
-Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+$ sudo auditctl -l | grep newgrp
-Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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_mod |
- Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchmod system call, run the following command:
-$ sudo grep "fchmod" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | 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 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_mod |
+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
medium |
|
|
@@ -4129,93 +4007,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
-
- Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-
-Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
-
-Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
- Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes audit_backlog_limit=8192,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
-The command should not return any output. Is it the case that audit backlog limit is not configured? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
- low |
- |
- |
- |
-
-
-
- | CCI-000130 |
- SRG-OS-000037-GPOS-00015 |
- TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish what type of events occurred. |
-
- CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
+ CCE-80741-2: Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
+ | 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/userhelper -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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers.d/ -p wa -k actions |
+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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "userhelper" command with the following command:
-$ sudo auditctl -l | grep/etc/sudoers.d
+$ sudo auditctl -l | grep userhelper
--w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
+ | 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/userhelper -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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers.d/ -p wa -k actions |
+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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -4228,78 +4054,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
+ CCE-80740-4: Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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 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=access
-
+ | 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 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=access |
+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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r ftruncate /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep ftruncate /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep unix_chkpwd
--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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 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=access
-
+ | 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 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=access |
+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
medium |
|
|
@@ -4312,7 +4101,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
+ CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -4320,41 +4109,59 @@
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
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
+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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchmodat system call, run the following command:
-$ sudo grep "fchmodat" /etc/audit/audit.*
+lremovexattr system call, run the following command:
+$ sudo grep "lremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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
+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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -4422,57 +4229,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
+ CCE-89446-9: Record Any Attempts to Run chacl |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | 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 arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+-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 line to
+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 setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-setxattr system call, run the following command:
-$ sudo grep "setxattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
+
+$ sudo auditctl -l | grep chacl
+
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | 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 arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+-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 line to
+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 setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -4485,41 +4276,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+ CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- At a minimum, the audit system should collect administrator actions
+ | At a minimum, the audit system should collect file deletion 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:
--w /etc/sudoers -p wa -k actions
+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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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:
--w /etc/sudoers -p wa -k actions |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-
-$ sudo auditctl -l | grep /etc/sudoers
-
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+unlink system call, run the following command:
+$ sudo grep "unlink" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- At a minimum, the audit system should collect administrator actions
+ | At a minimum, the audit system should collect file deletion 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:
--w /etc/sudoers -p wa -k actions
+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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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:
--w /etc/sudoers -p wa -k actions |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -4532,45 +4327,78 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80713-1: Ensure auditd Collects Information on Kernel Module Loading - init_module |
+ CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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 auid>=1000 -F auid!=unset -F key=modules
+ | 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
-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 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 auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules. |
+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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-init_module system call, run the following command:
-$ sudo grep "init_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
--a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modules
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
+
+$ sudo grep -r open /etc/audit/rules.d
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-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.
+$ sudo grep open /etc/audit/audit.rules
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules. |
+The output should be the following:
+
+-a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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=access |
medium |
|
|
@@ -4583,49 +4411,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
+ CCE-80726-3: Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | 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 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_mod |
+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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-chmod system call, run the following command:
-$ sudo grep "chmod" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chsh" command with the following command:
+
+$ sudo auditctl -l | grep chsh
+
+-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | 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 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_mod |
+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
medium |
|
|
@@ -4638,45 +4458,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
+ CCE-80739-6: Ensure auditd Collects Information on the Use of Privileged Commands - umount |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- At a minimum, the audit system should collect file deletion 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-unlinkat system call, run the following command:
-$ sudo grep "unlinkat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "umount" command with the following command:
+
+$ sudo auditctl -l | grep umount
+
+-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- At a minimum, the audit system should collect file deletion 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
@@ -4689,49 +4505,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+ CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- If the auditd daemon is configured to use the
+ | 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 capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
-
+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 capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification |
+/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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+$ sudo auditctl -l | grep /var/log/lastlog
--w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- If the auditd daemon is configured to use the
+ | 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 capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
-
+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 capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification |
+/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
medium |
|
|
@@ -4744,41 +4556,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-88437-9: Record Any Attempts to Run setfacl |
+ CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | 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 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 |
+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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfacl" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
-$ sudo auditctl -l | grep setfacl
+$ sudo auditctl -l | grep su
--a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | 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 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 |
+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
medium |
|
|
@@ -4791,55 +4603,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
+ CCE-80727-1: Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
-
+ | 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 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_mod |
+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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchown system call, run the following command:
-$ sudo grep "fchown" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "crontab" command with the following command:
-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
+$ sudo auditctl -l | grep crontab
+-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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 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_mod |
+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
medium |
|
|
@@ -4852,78 +4650,49 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+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:
--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 |
+/etc/audit/audit.rules file, in order to capture events that modify
+account changes:
+
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r openat /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep openat /etc/audit/audit.rules
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+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:
--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 |
+/etc/audit/audit.rules file, in order to capture events that modify
+account changes:
+
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -4936,19 +4705,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-81043-2: Ensure the audit Subsystem is Installed |
+ CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- The audit package should be installed. |
+ At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
+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 rename -F auid>=1000 -F auid!=unset -F key=delete |
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+ To determine if the system is configured to audit calls to the
+rename system call, run the following command:
+$ sudo grep "rename" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- The audit package should be installed. |
+ At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
+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 rename -F auid>=1000 -F auid!=unset -F key=delete |
medium |
|
|
@@ -4961,41 +4756,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80725-5: Ensure auditd Collects Information on the Use of Privileged Commands - chage |
+ CCE-85944-7: Record Any Attempts to Run ssh-agent |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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 |
+ 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 |
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chage" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command:
-$ sudo auditctl -l | grep chage
+$ sudo auditctl -l | grep ssh-agent
--a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | 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 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 |
+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
medium |
|
|
@@ -5008,7 +4803,58 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+ CCE-80713-1: Ensure auditd Collects Information on Kernel Module Loading - init_module |
+
+ Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+
+Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+
+Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
+ 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 auid>=1000 -F auid!=unset -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. |
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+init_module system call, run the following command:
+$ sudo grep "init_module" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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 auid>=1000 -F auid!=unset -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. |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000130 |
+ SRG-OS-000037-GPOS-00015 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must produce audit records containing information to establish what type of events occurred. |
+
+ CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -5016,49 +4862,41 @@
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lsetxattr system call, run the following command:
-$ sudo grep "lsetxattr" /etc/audit/audit.*
+fchmod system call, run the following command:
+$ sudo grep "fchmod" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -5071,7 +4909,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
+ CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -5083,24 +4921,20 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fsetxattr system call, run the following command:
-$ sudo grep "fsetxattr" /etc/audit/audit.*
+lchown system call, run the following command:
+$ sudo grep "lchown" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
@@ -5109,19 +4943,15 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -5134,41 +4964,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80989-7: Ensure auditd Collects Information on the Use of Privileged Commands - mount |
+ CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
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 |
+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 renameat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "mount" command with the following command:
-
-$ sudo auditctl -l | grep mount
-
--a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+renameat system call, run the following command:
+$ sudo grep "renameat" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
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 |
+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 renameat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -5181,7 +5015,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
+ CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -5193,66 +5027,60 @@
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r open /etc/audit/rules.d
+$ sudo grep -r creat /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep open /etc/audit/audit.rules
+$ sudo grep creat /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
medium |
|
|
@@ -5265,45 +5093,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
+ CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- At a minimum, the audit system should collect file deletion events
+ | At a minimum, the audit system should collect administrator actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-w /etc/sudoers.d/ -p wa -k actions
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-rename system call, run the following command:
-$ sudo grep "rename" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
+
+$ sudo auditctl -l | grep/etc/sudoers.d
+
+-w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- At a minimum, the audit system should collect file deletion events
+ | At a minimum, the audit system should collect administrator actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-w /etc/sudoers.d/ -p wa -k actions
medium |
|
|
@@ -5316,96 +5140,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80739-6: Ensure auditd Collects Information on the Use of Privileged Commands - umount |
+ CCE-80711-5: Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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 |
- Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "umount" command with the following command:
-
-$ sudo auditctl -l | grep umount
-
--a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-000130 |
- SRG-OS-000037-GPOS-00015 |
- TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish what type of events occurred. |
+ 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:
- | CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+-a always,exit -F arch=ARCH -S delete_module -F auid>=1000 -F auid!=unset -F key=modules
- Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+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.
-Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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 |
+If the auditd daemon is configured to use the auditctl utility,
+add the line to file /etc/audit/audit.rules.
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+ | To determine if the system is configured to audit calls to the
+delete_module system call, run the following command:
+$ sudo grep "delete_module" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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:
-$ sudo auditctl -l | grep -E '(/etc/group)'
+-a always,exit -F arch=ARCH -S delete_module -F auid>=1000 -F auid!=unset -F key=modules
--w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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 |
+
+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.
medium |
|
|
@@ -5418,45 +5191,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
+ CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-rmdir system call, run the following command:
-$ sudo grep "rmdir" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
+
+$ sudo auditctl -l | grep usermod
+
+-a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
@@ -5469,7 +5238,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80731-3: Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
+ CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -5481,29 +5250,29 @@
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
+-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/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "passwd" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
-$ sudo auditctl -l | grep passwd
+$ sudo auditctl -l | grep sudo
--a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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
+-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/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -5516,112 +5285,57 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80700-8: Record Any Attempts to Run semanage |
+ CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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
+ | 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 path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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 lines to
+utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
- Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
-
-$ sudo auditctl -l | grep semanage
-
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
- medium |
- |
- |
- |
-
-
-
- | CCI-000130 |
- SRG-OS-000037-GPOS-00015 |
- TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish what type of events occurred. |
-
- CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
-
- Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-
-Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
-
-Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-removexattr system call, run the following command:
-$ sudo grep "removexattr" /etc/audit/audit.*
+lsetxattr system call, run the following command:
+$ sudo grep "lsetxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -5634,100 +5348,78 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
+ CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | 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 line to
+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 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 |
+-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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-chown system call, run the following command:
-$ sudo grep "chown" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-000130 |
- SRG-OS-000037-GPOS-00015 |
- TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish what type of events occurred. |
-
- CCE-80711-5: Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
-
- Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
-Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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:
+$ sudo grep -r openat /etc/audit/rules.d
--a always,exit -F arch=ARCH -S delete_module -F auid>=1000 -F auid!=unset -F key=modules
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+$ sudo grep openat /etc/audit/audit.rules
-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.
+The output should be the following:
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules. |
- Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-delete_module system call, run the following command:
-$ sudo grep "delete_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+-a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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 auid>=1000 -F auid!=unset -F key=modules
+ | 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
-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 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 auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules. |
+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
medium |
|
|
@@ -5740,41 +5432,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-82280-9: Record Any Attempts to Run setfiles |
+ CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- At a minimum, the audit system should collect any execution attempt
-of the setfiles 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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
-
-$ sudo auditctl -l | grep setfiles
-
--a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+rmdir system call, run the following command:
+$ sudo grep "rmdir" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- At a minimum, the audit system should collect any execution attempt
-of the setfiles 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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -5787,7 +5483,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
+ CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -5795,116 +5491,41 @@
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lremovexattr system call, run the following command:
-$ sudo grep "lremovexattr" /etc/audit/audit.*
+fchmodat system call, run the following command:
+$ sudo grep "fchmodat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-000130 |
- SRG-OS-000037-GPOS-00015 |
- TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish what type of events occurred. |
-
- CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
-
- Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-
-Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
-
-Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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 |
- Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
-
--w /etc/gshadow -p wa -k identity
-
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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 |
+-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -5990,45 +5611,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
+ CCE-80722-2: Ensure auditd Collects Information on Exporting to Media (successful) |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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
+ | 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 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 |
+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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
-
-$ sudo auditctl -l | grep /var/log/lastlog
-
--w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+mount system call, run the following command:
+$ sudo grep "mount" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | 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 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 |
+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
medium |
|
|
@@ -6041,34 +5662,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80872-5: Enable auditd Service |
+ CCE-80733-9: Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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 |
+ 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/postqueue -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
-
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postqueue" command with the following command:
-Run the following command to determine the current status of the
-auditd service:
-$ sudo systemctl is-active auditd
-If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
- Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- The auditd service is an essential userspace component of
-the Linux Auditing System, as it is responsible for writing audit records to
-disk.
+$ sudo auditctl -l | grep postqueue
-The auditd service can be enabled with the following command:
-$ sudo systemctl enable auditd.service |
+-a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out?
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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/postqueue -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
medium |
|
|
@@ -6081,41 +5709,92 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80698-4: Record Any Attempts to Run chcon |
+ CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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 |
- Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
+ | 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:
-$ sudo auditctl -l | grep chcon
+-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -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 path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -F key=modules
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+finit_module system call, run the following command:
+$ sudo grep "finit_module" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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
+ | 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000130 |
+ SRG-OS-000037-GPOS-00015 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must produce audit records containing information to establish what type of events occurred. |
+
+ CCE-88437-9: Record Any Attempts to Run setfacl |
+
+ Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+
+Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+
+Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
+ 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/chcon -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/chcon -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfacl" command with the following command:
+
+$ sudo auditctl -l | grep setfacl
+
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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 |
medium |
|
|
@@ -6128,41 +5807,93 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-89480-8: Ensure auditd Collects Information on the Use of Privileged Commands - unix_update |
+ CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- 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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes audit_backlog_limit=8192,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
+The command should not return any output. Is it the case that audit backlog limit is not configured? |
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ low |
+ |
+ |
+ |
+
+
+
+ | CCI-000130 |
+ SRG-OS-000037-GPOS-00015 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must produce audit records containing information to establish what type of events occurred. |
+
+ CCE-82280-9: Record Any Attempts to Run setfiles |
+
+ Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+
+Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+
+Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
+ At a minimum, the audit system should collect any execution attempt
+of the setfiles 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/sbin/setfiles -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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+utility to read audit rules during daemon startup, add the following lines to
+/etc/audit/audit.rules file:
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_update" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
-$ sudo auditctl -l | grep unix_update
+$ sudo auditctl -l | grep setfiles
--a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- 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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | At a minimum, the audit system should collect any execution attempt
+of the setfiles 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/sbin/setfiles -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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+utility to read audit rules during daemon startup, add the following lines to
+/etc/audit/audit.rules file:
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -6227,7 +5958,62 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80732-1: Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
+ CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
+
+ Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+
+Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+
+Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
+ 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_mod |
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+chmod system call, run the following command:
+$ sudo grep "chmod" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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_mod |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000130 |
+ SRG-OS-000037-GPOS-00015 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must produce audit records containing information to establish what type of events occurred. |
+
+ CCE-89480-8: Ensure auditd Collects Information on the Use of Privileged Commands - unix_update |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
@@ -6239,29 +6025,29 @@
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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/sbin/unix_update -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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postdrop" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_update" command with the following command:
-$ sudo auditctl -l | grep postdrop
+$ sudo auditctl -l | grep unix_update
--a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/sbin/unix_update -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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -6274,81 +6060,270 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
+ CCE-80730-5: Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- At a minimum, the audit system should collect file deletion events
-for all users and root. If the auditd daemon is configured to use the
+ | 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/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=/usr/sbin/pam_timestamp_check
+-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command:
+
+$ sudo auditctl -l | grep pam_timestamp_check
+
+-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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/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=/usr/sbin/pam_timestamp_check
+-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000130 |
+ SRG-OS-000037-GPOS-00015 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must produce audit records containing information to establish what type of events occurred. |
+
+ CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
+
+ Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+
+Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+
+Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
+ 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-renameat system call, run the following command:
-$ sudo grep "renameat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
Configure the operating system to produce audit records containing information to establish what type of events occurred. |
- At a minimum, the audit system should collect file deletion events
-for all users and root. If the auditd daemon is configured to use the
+ | 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
|
+
+ | CCI-000130 |
+ SRG-OS-000037-GPOS-00015 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must produce audit records containing information to establish what type of events occurred. |
+
+ CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+
+ Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+-w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
- | CCI-000131 |
- SRG-OS-000038-GPOS-00016 |
+ CCI-000130 |
+ SRG-OS-000037-GPOS-00015 |
TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish when (date and time) the events occurred. |
+ The operating system must produce audit records containing information to establish what type of events occurred. |
- CCE-81043-2: Ensure the audit Subsystem is Installed |
+ CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
- Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.
+ | Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know when events occurred (date and time).
+Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
- The audit package should be installed. |
+ 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 |
Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish when (date and time) the events occurred. If it does not, this is a finding. |
- Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Configure the operating system to produce audit records containing information to establish when (date and time) the events occurred. |
- The audit package should be installed. |
+ Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/group)'
+
+-w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000130 |
+ SRG-OS-000037-GPOS-00015 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must produce audit records containing information to establish what type of events occurred. |
+
+ CCE-80698-4: Record Any Attempts to Run chcon |
+
+ Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+
+Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+
+Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
+
+$ sudo auditctl -l | grep chcon
+
+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to produce audit records containing information to establish what type of events occurred. |
+ 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 |
medium |
|
|
|
+
+
+
+
+
| CCI-000131 |
SRG-OS-000038-GPOS-00016 |
@@ -6389,6 +6364,31 @@
|
+
+ | CCI-000131 |
+ SRG-OS-000038-GPOS-00016 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must produce audit records containing information to establish when (date and time) the events occurred. |
+
+ CCE-81043-2: Ensure the audit Subsystem is Installed |
+
+ Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.
+
+In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know when events occurred (date and time).
+
+Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
+ The audit package should be installed. |
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing information to establish when (date and time) the events occurred. If it does not, this is a finding. |
+ Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+ Configure the operating system to produce audit records containing information to establish when (date and time) the events occurred. |
+ The audit package should be installed. |
+ medium |
+ |
+ |
+ |
+
+
@@ -6400,29 +6400,34 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish where the events occurred. |
-
CCE-82897-0: Set type of computer node name logging in audit logs |
+
CCE-80872-5: Enable auditd Service |
Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.
In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as operating system components, modules, device identifiers, node names, file names, and functionality.
Associating information about where the event occurred within the operating system provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
-
To configure Audit daemon to use a unique identifier
-as computer node name in the audit events,
-set name_format to
-in /etc/audit/auditd.conf. |
+
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 |
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish where the events occurred. If it does not, this is a finding. |
-
To verify that Audit Daemon is configured to record the computer node
-name in the audit events, run the following command:
-$ sudo grep name_format /etc/audit/auditd.conf
-The output should return the following:
-name_format = Is it the case that name_format isn't set to ? |
+
+
+Run the following command to determine the current status of the
+auditd service:
+$ sudo systemctl is-active auditd
+If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
Configure the operating system to produce audit records containing information to establish where the events occurred. |
-
To configure Audit daemon to use a unique identifier
-as computer node name in the audit events,
-set name_format to
-in /etc/audit/auditd.conf. |
+
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 |
medium |
|
|
@@ -6460,34 +6465,29 @@
TBD - Assigned by DISA after STIG release |
The operating system must produce audit records containing information to establish where the events occurred. |
-
CCE-80872-5: Enable auditd Service |
+
CCE-82897-0: Set type of computer node name logging in audit logs |
Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.
In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as operating system components, modules, device identifiers, node names, file names, and functionality.
Associating information about where the event occurred within the operating system provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
-
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 |
+
To configure Audit daemon to use a unique identifier
+as computer node name in the audit events,
+set name_format to
+in /etc/audit/auditd.conf. |
Applicable - Configurable |
Verify the operating system produces audit records containing information to establish where the events occurred. If it does not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-auditd service:
-$ sudo systemctl is-active auditd
-If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
+
To verify that Audit Daemon is configured to record the computer node
+name in the audit events, run the following command:
+$ sudo grep name_format /etc/audit/auditd.conf
+The output should return the following:
+name_format = Is it the case that name_format isn't set to ? |
Configure the operating system to produce audit records containing information to establish where the events occurred. |
-
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 |
+
To configure Audit daemon to use a unique identifier
+as computer node name in the audit events,
+set name_format to
+in /etc/audit/auditd.conf. |
medium |
|
|
@@ -6499,31 +6499,6 @@
-
- | CCI-000133 |
- SRG-OS-000040-GPOS-00018 |
- TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish the source of the events. |
-
- CCE-81043-2: Ensure the audit Subsystem is Installed |
-
- Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.
-
-In addition to logging where events occur within the operating system, the operating system must also generate audit records that identify sources of events. Sources of operating system events include, but are not limited to, processes and services.
-
-In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know the source of the event. |
- The audit package should be installed. |
- Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish the source of the events. If it does not, this is a finding. |
- Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Configure the operating system to produce audit records containing information to establish the source of the events. |
- The audit package should be installed. |
- medium |
- |
- |
- |
-
-
| CCI-000133 |
SRG-OS-000040-GPOS-00018 |
@@ -6564,27 +6539,24 @@
|
-
-
-
-
-
- | CCI-000134 |
- SRG-OS-000041-GPOS-00019 |
+ CCI-000133 |
+ SRG-OS-000040-GPOS-00018 |
TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish the outcome of the events. |
+ The operating system must produce audit records containing information to establish the source of the events. |
CCE-81043-2: Ensure the audit Subsystem is Installed |
- Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system.
+ | Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.
-Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the information system after the event occurred). As such, they also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response. |
+In addition to logging where events occur within the operating system, the operating system must also generate audit records that identify sources of events. Sources of operating system events include, but are not limited to, processes and services.
+
+In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know the source of the event.
The audit package should be installed. |
Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish the outcome of the events. If it does not, this is a finding. |
+ Verify the operating system produces audit records containing information to establish the source of the events. If it does not, this is a finding. |
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Configure the operating system to produce audit records containing information to establish the outcome of the events. |
+ Configure the operating system to produce audit records containing information to establish the source of the events. |
The audit package should be installed. |
medium |
|
@@ -6592,6 +6564,11 @@
|
+
+
+
+
+
| CCI-000134 |
SRG-OS-000041-GPOS-00019 |
@@ -6630,6 +6607,29 @@
|
+
+ | CCI-000134 |
+ SRG-OS-000041-GPOS-00019 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must produce audit records containing information to establish the outcome of the events. |
+
+ CCE-81043-2: Ensure the audit Subsystem is Installed |
+
+ Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system.
+
+Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the information system after the event occurred). As such, they also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response. |
+ The audit package should be installed. |
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing information to establish the outcome of the events. If it does not, this is a finding. |
+ Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+ Configure the operating system to produce audit records containing information to establish the outcome of the events. |
+ The audit package should be installed. |
+ medium |
+ |
+ |
+ |
+
+
@@ -6641,39 +6641,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
-
CCE-85944-7: Record Any Attempts to Run ssh-agent |
+
CCE-80700-8: Record Any Attempts to Run semanage |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
At a minimum, the audit system should collect any execution attempt
-of the ssh-agent command for all users and root. If the auditd
+of the semanage 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
+-a always,exit -F path=/usr/sbin/semanage -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/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
+
-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
-
Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
-$ sudo auditctl -l | grep ssh-agent
+$ sudo auditctl -l | grep semanage
--a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
At a minimum, the audit system should collect any execution attempt
-of the ssh-agent command for all users and root. If the auditd
+of the semanage 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
+-a always,exit -F path=/usr/sbin/semanage -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/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
+
-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -6686,7 +6686,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
-
CCE-80730-5: Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
+
CCE-80989-7: Ensure auditd Collects Information on the Use of Privileged Commands - mount |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -6696,33 +6696,29 @@
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/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+
-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
-
Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "mount" command with the following command:
-$ sudo auditctl -l | grep pam_timestamp_check
+$ sudo auditctl -l | grep mount
--a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
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/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+
-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -6780,7 +6776,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
-
CCE-80728-9: Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
+
CCE-80731-3: Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -6790,29 +6786,29 @@
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
+-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/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+
-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
-
Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "gpasswd" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "passwd" command with the following command:
-$ sudo auditctl -l | grep gpasswd
+$ sudo auditctl -l | grep passwd
--a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
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
+-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/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+
-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -6825,39 +6821,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
-
CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
+
CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
-
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
+ | 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 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 |
+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_mod
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
-
Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
-
-$ sudo auditctl -l | grep su
-
--a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out? |
+
To determine if the system is configured to audit calls to the
+chown system call, run the following command:
+$ sudo grep "chown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
-
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
+ | 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 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 |
+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_mod
medium |
|
|
@@ -6870,76 +6874,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
-
CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
+
CCE-80701-6: Record Any Attempts to Run setsebool |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
-
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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 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
-
+-a always,exit -F path=/usr/sbin/setsebool -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 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 |
+
-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
-
Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r truncate /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep truncate /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep setsebool
--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
-
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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 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
-
+-a always,exit -F path=/usr/sbin/setsebool -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 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 |
+
-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -6952,39 +6919,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
-
CCE-80729-7: Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
+
CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
-
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
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+
/etc/audit/audit.rules file:
+
-w /etc/sudoers -p wa -k actions
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
-
Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "newgrp" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-$ sudo auditctl -l | grep newgrp
+$ sudo auditctl -l | grep /etc/sudoers
--a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
-
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
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+
/etc/audit/audit.rules file:
+
-w /etc/sudoers -p wa -k actions
medium |
|
|
@@ -6997,123 +6964,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
-
CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
+
CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
-
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
+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:
--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=access |
+
/etc/audit/audit.rules file, in order to capture events that modify
+account changes:
+
+
-w /etc/shadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
-
Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r open_by_handle_at /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep open_by_handle_at /etc/audit/audit.rules
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep -E '(/etc/shadow)'
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
-
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
+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:
--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=access |
-
medium |
-
|
-
|
-
|
-
-
-
- | CCI-000135 |
- SRG-OS-000042-GPOS-00020 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records containing the full-text recording of privileged commands. |
-
- CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
-
- Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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_mod |
- Applicable - Configurable |
- Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-lchown system call, run the following command:
-$ sudo grep "lchown" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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_mod |
+/etc/audit/audit.rules file, in order to capture events that modify
+account changes:
+
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -7171,47 +7062,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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 |
+ 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
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
-
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fsetxattr system call, run the following command:
+$ sudo grep "fsetxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
-
+ | 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
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 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 |
+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
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -7224,39 +7123,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80733-9: Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
+ CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postqueue" command with the following command:
-
-$ sudo auditctl -l | grep postqueue
-
--a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+setxattr system call, run the following command:
+$ sudo grep "setxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -7269,39 +7184,76 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-89446-9: Record Any Attempts to Run chacl |
+ CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
+ | 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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-$ sudo auditctl -l | grep chacl
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r truncate /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep truncate /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
+ | 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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
medium |
|
|
@@ -7314,39 +7266,63 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80740-4: Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
+ CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+
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 |
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command:
-
-$ sudo auditctl -l | grep unix_chkpwd
-
--a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+removexattr system call, run the following command:
+$ sudo grep "removexattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+
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 |
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -7359,111 +7335,76 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
+ CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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 |
- Applicable - Configurable |
- Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
+ | 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
-$ sudo auditctl -l | grep usermod
+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=access
--a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-000135 |
- SRG-OS-000042-GPOS-00020 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records containing the full-text recording of privileged commands. |
-
- CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
-
- Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+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
-At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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 |
+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=access
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
-$ sudo auditctl -l | grep sudo
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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 |
- medium |
- |
- |
- |
-
+$ sudo grep -r ftruncate /etc/audit/rules.d
-
- | CCI-000135 |
- SRG-OS-000042-GPOS-00020 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records containing the full-text recording of privileged commands. |
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
- CCE-89903-9: Ensure All Accounts on the System Have Unique User IDs |
+$ sudo grep ftruncate /etc/audit/audit.rules
- Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+The output should be the following:
-At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- Change user IDs (UIDs), or delete accounts, so each has a unique name. |
- Applicable - Configurable |
- Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 contains no duplicate User IDs (UIDs) for interactive users.
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
+ 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
-Check that the operating system contains no duplicate UIDs for interactive users with the following command:
+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=access
-$ sudo awk -F ":" 'list[$3]++{print $1, $3}' /etc/passwd Is it the case that output is produced and the accounts listed are interactive user accounts? |
- Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- Change user IDs (UIDs), or delete accounts, so each has a unique name. |
+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=access
medium |
|
|
@@ -7476,7 +7417,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80726-3: Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
+ CCE-80732-1: Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -7486,29 +7427,29 @@
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
+-a always,exit -F path=/usr/sbin/postdrop -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 |
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chsh" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postdrop" command with the following command:
-$ sudo auditctl -l | grep chsh
+$ sudo auditctl -l | grep postdrop
--a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
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
+-a always,exit -F path=/usr/sbin/postdrop -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 |
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -7521,7 +7462,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
+ CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -7532,17 +7473,17 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-unlink system call, run the following command:
-$ sudo grep "unlink" /etc/audit/audit.*
+unlinkat system call, run the following command:
+$ sudo grep "unlinkat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
@@ -7552,12 +7493,12 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -7570,7 +7511,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80741-2: Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
+ CCE-80728-9: Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -7580,29 +7521,29 @@
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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "userhelper" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "gpasswd" command with the following command:
-$ sudo auditctl -l | grep userhelper
+$ sudo auditctl -l | grep gpasswd
--a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -7615,43 +7556,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
+ CCE-80725-5: Ensure auditd Collects Information on the Use of Privileged Commands - chage |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
+ 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 |
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-finit_module system call, run the following command:
-$ sudo grep "finit_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chage" command with the following command:
--a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -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:
+$ sudo auditctl -l | grep chage
--a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -F key=modules |
+-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out?
+ Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
+ 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 |
medium |
|
|
@@ -7664,47 +7601,129 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
+ CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
-
+ | 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_mod |
+ Applicable - Configurable |
+ Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+fchown system call, run the following command:
+$ sudo grep "fchown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
+ 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_mod |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000135 |
+ SRG-OS-000042-GPOS-00020 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records containing the full-text recording of privileged commands. |
+
+ CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
+
+ Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
+ 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, in order to capture events that modify
-account changes:
-
--w /etc/shadow -p wa -k audit_rules_usergroup_modification |
+/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=access
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
-$ sudo auditctl -l | grep -E '(/etc/shadow)'
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
+$ sudo grep -r open_by_handle_at /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep open_by_handle_at /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
-
+ | 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, in order to capture events that modify
-account changes:
-
--w /etc/shadow -p wa -k audit_rules_usergroup_modification |
+/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=access
medium |
|
|
@@ -7717,7 +7736,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80727-1: Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
+ CCE-80729-7: Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -7727,29 +7746,29 @@
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
+-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/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "crontab" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "newgrp" command with the following command:
-$ sudo auditctl -l | grep crontab
+$ sudo auditctl -l | grep newgrp
--a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
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
+-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/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -7762,39 +7781,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80701-6: Record Any Attempts to Run setsebool |
+ CCE-80741-2: Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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/userhelper -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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "userhelper" command with the following command:
-$ sudo auditctl -l | grep setsebool
+$ sudo auditctl -l | grep userhelper
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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/userhelper -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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -7807,70 +7826,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
+ CCE-80740-4: Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
+ | 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 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=access |
+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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r creat /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep creat /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep unix_chkpwd
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
+ | 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 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=access |
+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
medium |
|
|
@@ -7883,43 +7871,65 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80722-2: Ensure auditd Collects Information on Exporting to Media (successful) |
+ CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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, 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 |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-mount system call, run the following command:
-$ sudo grep "mount" /etc/audit/audit.*
+lremovexattr system call, run the following command:
+$ sudo grep "lremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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, 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 |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -7932,47 +7942,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
+ CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
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
+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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchmod system call, run the following command:
-$ sudo grep "fchmod" /etc/audit/audit.*
+fchownat system call, run the following command:
+$ sudo grep "fchownat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
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
+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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -7985,45 +7995,40 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
+ CCE-89446-9: Record Any Attempts to Run chacl |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ 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 |
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes audit_backlog_limit=8192,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
-The command should not return any output. Is it the case that audit backlog limit is not configured? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
+
+$ sudo auditctl -l | grep chacl
+
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
- low |
+ 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 |
+ medium |
|
|
|
@@ -8035,39 +8040,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
+ CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- At a minimum, the audit system should collect administrator actions
+ | At a minimum, the audit system should collect file deletion 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:
--w /etc/sudoers.d/ -p wa -k actions
+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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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:
--w /etc/sudoers.d/ -p wa -k actions |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-
-$ sudo auditctl -l | grep/etc/sudoers.d
-
--w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+unlink system call, run the following command:
+$ sudo grep "unlink" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- At a minimum, the audit system should collect administrator actions
+ | At a minimum, the audit system should collect file deletion 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:
--w /etc/sudoers.d/ -p wa -k actions
+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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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:
--w /etc/sudoers.d/ -p wa -k actions |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -8080,7 +8089,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
+ CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -8090,66 +8099,66 @@
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
+-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 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=access
+-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 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
+-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 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=access |
+-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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r ftruncate /etc/audit/rules.d
+$ sudo grep -r open /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep ftruncate /etc/audit/audit.rules
+$ sudo grep open /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
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
+-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 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=access
-
+-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 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
+-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 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=access |
+-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
medium |
|
|
@@ -8162,47 +8171,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
+ CCE-80726-3: Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
+ | 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 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_mod |
+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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchmodat system call, run the following command:
-$ sudo grep "fchmodat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chsh" command with the following command:
+
+$ sudo auditctl -l | grep chsh
+
+-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
+ | 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 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_mod |
+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
medium |
|
|
@@ -8215,47 +8216,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
+ CCE-80739-6: Ensure auditd Collects Information on the Use of Privileged Commands - umount |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
+ | 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 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_mod |
+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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchownat system call, run the following command:
-$ sudo grep "fchownat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "umount" command with the following command:
+
+$ sudo auditctl -l | grep umount
+
+-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
+ | 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 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_mod |
+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
medium |
|
|
@@ -8268,55 +8261,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
+ CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+ | 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 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-setxattr system call, run the following command:
-$ sudo grep "setxattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
+
+$ sudo auditctl -l | grep /var/log/lastlog
+
+-w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+ | 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 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+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
medium |
|
|
@@ -8329,39 +8310,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+ CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 the following line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
-$ sudo auditctl -l | grep /etc/sudoers
+$ sudo auditctl -l | grep su
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 the following line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
medium |
|
|
@@ -8374,43 +8355,66 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80713-1: Ensure auditd Collects Information on Kernel Module Loading - init_module |
+ CCE-80727-1: Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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:
+ | 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 |
+ Applicable - Configurable |
+ Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "crontab" command with the following command:
--a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modules
+$ sudo auditctl -l | grep crontab
+
+-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
+ | CCI-000135 |
+ SRG-OS-000042-GPOS-00020 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records containing the full-text recording of privileged commands. |
-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.
+ CCE-89903-9: Ensure All Accounts on the System Have Unique User IDs |
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules.
+ Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
+ Change user IDs (UIDs), or delete accounts, so each has a unique name. |
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-init_module system call, run the following command:
-$ sudo grep "init_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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 auid>=1000 -F auid!=unset -F key=modules
-
+ | Verify that Red Hat Enterprise Linux 8 contains no duplicate User IDs (UIDs) for interactive users.
-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.
+Check that the operating system contains no duplicate UIDs for interactive users with the following command:
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules. |
+$ sudo awk -F ":" 'list[$3]++{print $1, $3}' /etc/passwd Is it the case that output is produced and the accounts listed are interactive user accounts?
+ Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
+ Change user IDs (UIDs), or delete accounts, so each has a unique name. |
medium |
|
|
@@ -8423,47 +8427,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
+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 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_mod |
+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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-chmod system call, run the following command:
-$ sudo grep "chmod" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
+
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
+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 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_mod |
+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
medium |
|
|
@@ -8476,7 +8480,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
+ CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -8487,17 +8491,17 @@
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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-unlinkat system call, run the following command:
-$ sudo grep "unlinkat" /etc/audit/audit.*
+rename system call, run the following command:
+$ sudo grep "rename" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
@@ -8507,65 +8511,12 @@
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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
- medium |
- |
- |
- |
-
-
-
- | CCI-000135 |
- SRG-OS-000042-GPOS-00020 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records containing the full-text recording of privileged commands. |
-
- CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
-
- Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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 |
- Applicable - Configurable |
- Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
-
--w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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 |
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -8578,39 +8529,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-88437-9: Record Any Attempts to Run setfacl |
+ CCE-85944-7: Record Any Attempts to Run ssh-agent |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
At a minimum, the audit system should collect any execution attempt
-of the setfacl command for all users and root. If the auditd
+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/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfacl" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command:
-$ sudo auditctl -l | grep setfacl
+$ sudo auditctl -l | grep ssh-agent
--a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
At a minimum, the audit system should collect any execution attempt
-of the setfacl command for all users and root. If the auditd
+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/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent
medium |
|
|
@@ -8623,53 +8574,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
+ CCE-80713-1: Ensure auditd Collects Information on Kernel Module Loading - init_module |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
+ | 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:
-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
+-a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modules
-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_mod |
+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.
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchown system call, run the following command:
-$ sudo grep "fchown" /etc/audit/audit.*
+init_module system call, run the following command:
+$ sudo grep "init_module" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
+ | 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:
-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
+-a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modules
-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_mod |
+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.
medium |
|
|
@@ -8682,182 +8623,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
-
- Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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=access |
- Applicable - Configurable |
- Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r openat /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep openat /etc/audit/audit.rules
-
-The output should be the following:
-
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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=access |
- medium |
- |
- |
- |
-
-
-
- | CCI-000135 |
- SRG-OS-000042-GPOS-00020 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records containing the full-text recording of privileged commands. |
-
- CCE-80725-5: Ensure auditd Collects Information on the Use of Privileged Commands - chage |
-
- Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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 |
- Applicable - Configurable |
- Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chage" command with the following command:
-
-$ sudo auditctl -l | grep chage
-
--a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-000135 |
- SRG-OS-000042-GPOS-00020 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records containing the full-text recording of privileged commands. |
-
- CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+ CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lsetxattr system call, run the following command:
-$ sudo grep "lsetxattr" /etc/audit/audit.*
+fchmod system call, run the following command:
+$ sudo grep "fchmod" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -8870,7 +8676,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
+ CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -8880,24 +8686,20 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fsetxattr system call, run the following command:
-$ sudo grep "fsetxattr" /etc/audit/audit.*
+lchown system call, run the following command:
+$ sudo grep "lchown" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
@@ -8906,19 +8708,15 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -8931,39 +8729,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80989-7: Ensure auditd Collects Information on the Use of Privileged Commands - mount |
+ CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
+ | At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
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 |
+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 renameat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "mount" command with the following command:
-
-$ sudo auditctl -l | grep mount
-
--a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+renameat system call, run the following command:
+$ sudo grep "renameat" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
+ | At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
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 |
+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 renameat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -8976,7 +8778,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
+ CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -8986,66 +8788,60 @@
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r open /etc/audit/rules.d
+$ sudo grep -r creat /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep open /etc/audit/audit.rules
+$ sudo grep creat /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
medium |
|
|
@@ -9058,43 +8854,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
+ CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- At a minimum, the audit system should collect file deletion events
+ | At a minimum, the audit system should collect administrator actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-w /etc/sudoers.d/ -p wa -k actions
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-rename system call, run the following command:
-$ sudo grep "rename" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
+
+$ sudo auditctl -l | grep/etc/sudoers.d
+
+-w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- At a minimum, the audit system should collect file deletion events
+ | At a minimum, the audit system should collect administrator actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-w /etc/sudoers.d/ -p wa -k actions
medium |
|
|
@@ -9107,7 +8899,56 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80739-6: Ensure auditd Collects Information on the Use of Privileged Commands - umount |
+ CCE-80711-5: Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
+
+ Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
+ 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 auid>=1000 -F auid!=unset -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. |
+ Applicable - Configurable |
+ Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+delete_module system call, run the following command:
+$ sudo grep "delete_module" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
+ 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 auid>=1000 -F auid!=unset -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. |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000135 |
+ SRG-OS-000042-GPOS-00020 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records containing the full-text recording of privileged commands. |
+
+ CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -9117,29 +8958,29 @@
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
+-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/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "umount" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
-$ sudo auditctl -l | grep umount
+$ sudo auditctl -l | grep usermod
--a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
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
+-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/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -9152,47 +8993,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+ CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
-
+ | 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 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 |
+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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
-$ sudo auditctl -l | grep -E '(/etc/group)'
+$ sudo auditctl -l | grep sudo
--w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
-
+ | 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 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 |
+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
medium |
|
|
@@ -9205,43 +9038,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
+ CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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, setting ARCH to either b32 or b64 as
-appropriate for your system:
--a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-rmdir system call, run the following command:
-$ sudo grep "rmdir" /etc/audit/audit.*
+lsetxattr system call, run the following command:
+$ sudo grep "lsetxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
-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 rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+ 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
medium |
|
|
@@ -9254,39 +9099,76 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80731-3: Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
+ CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
+ | 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 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 |
+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=access
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "passwd" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
-$ sudo auditctl -l | grep passwd
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r openat /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep openat /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
+ | 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 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 |
+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=access
medium |
|
|
@@ -9299,39 +9181,96 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80700-8: Record Any Attempts to Run semanage |
+ CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
+ | To determine if the system is configured to audit calls to the
+rmdir system call, run the following command:
+$ sudo grep "rmdir" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
+ At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+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 rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+ medium |
+ |
+ |
+ |
+
-$ sudo auditctl -l | grep semanage
+
+ | CCI-000135 |
+ SRG-OS-000042-GPOS-00020 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records containing the full-text recording of privileged commands. |
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
+ CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
+
+ Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
+ 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_mod |
+ Applicable - Configurable |
+ Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+fchmodat system call, run the following command:
+$ sudo grep "fchmodat" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 lines to
+utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
medium |
|
|
@@ -9344,7 +9283,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
+ CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -9352,55 +9291,57 @@
| 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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
+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
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-removexattr system call, run the following command:
-$ sudo grep "removexattr" /etc/audit/audit.*
+fremovexattr system call, run the following command:
+$ sudo grep "fremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
+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
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -9413,47 +9354,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
+ CCE-80722-2: Ensure auditd Collects Information on Exporting to Media (successful) |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured to
+ | 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:
--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
+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:
--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 |
+/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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-chown system call, run the following command:
-$ sudo grep "chown" /etc/audit/audit.*
+mount system call, run the following command:
+$ sudo grep "mount" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured to
+ | 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:
--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
+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:
--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 |
+/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
medium |
|
|
@@ -9466,43 +9403,88 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80711-5: Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
+ CCE-80733-9: Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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:
+ | 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/postqueue -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ Applicable - Configurable |
+ Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postqueue" command with the following command:
--a always,exit -F arch=ARCH -S delete_module -F auid>=1000 -F auid!=unset -F key=modules
+$ sudo auditctl -l | grep postqueue
+
+-a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
+ 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/postqueue -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ medium |
+ |
+ |
+ |
+
+
+ | CCI-000135 |
+ SRG-OS-000042-GPOS-00020 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records containing the full-text recording of privileged commands. |
-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.
+ CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules.
+ Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
+ 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-delete_module system call, run the following command:
-$ sudo grep "delete_module" /etc/audit/audit.*
+finit_module system call, run the following command:
+$ sudo grep "finit_module" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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 auid>=1000 -F auid!=unset -F key=modules
-
+ | 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:
-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.
+-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -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:
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules. |
+-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -F key=modules
medium |
|
|
@@ -9515,39 +9497,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-82280-9: Record Any Attempts to Run setfiles |
+ CCE-88437-9: Record Any Attempts to Run setfacl |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
At a minimum, the audit system should collect any execution attempt
-of the setfiles command for all users and root. If the auditd
+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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfacl" command with the following command:
-$ sudo auditctl -l | grep setfiles
+$ sudo auditctl -l | grep setfacl
--a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
At a minimum, the audit system should collect any execution attempt
-of the setfiles command for all users and root. If the auditd
+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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -9560,66 +9542,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
+ CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-lremovexattr system call, run the following command:
-$ sudo grep "lremovexattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes audit_backlog_limit=8192,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
+The command should not return any output. Is it the case that audit backlog limit is not configured? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
- medium |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ low |
|
|
|
@@ -9631,49 +9592,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
+ CCE-82280-9: Record Any Attempts to Run setfiles |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
-
+ | At a minimum, the audit system should collect any execution attempt
+of the setfiles 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/sbin/setfiles -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, in order to capture events that modify
-account changes:
-
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification |
+/etc/audit/audit.rules file:
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+$ sudo auditctl -l | grep setfiles
--w /etc/gshadow -p wa -k identity
-
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
-
+ | At a minimum, the audit system should collect any execution attempt
+of the setfiles 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/sbin/setfiles -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, in order to capture events that modify
-account changes:
-
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification |
+/etc/audit/audit.rules file:
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -9686,66 +9637,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
+ CCE-80825-3: Enable Auditing for Processes Which Start Prior to the Audit Daemon |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
+ To ensure all processes can be audited, even those which start
+prior to the audit daemon, add the argument audit=1 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit=1 is added as a kernel command line
+argument to newly installed kernels, add audit=1 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit=1 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fremovexattr system call, run the following command:
-$ sudo grep "fremovexattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes audit=1,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit=1.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*audit=1.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'audit=1'
+The command should not return any output. Is it the case that auditing is not enabled at boot time? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
- medium |
+ To ensure all processes can be audited, even those which start
+prior to the audit daemon, add the argument audit=1 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit=1 is added as a kernel command line
+argument to newly installed kernels, add audit=1 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit=1 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
+ low |
|
|
|
@@ -9757,43 +9687,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
+ CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
+ | 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 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 |
+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_mod
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
-
-$ sudo auditctl -l | grep /var/log/lastlog
-
--w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+chmod system call, run the following command:
+$ sudo grep "chmod" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
+ | 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 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 |
+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_mod
medium |
|
|
@@ -9806,39 +9740,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80698-4: Record Any Attempts to Run chcon |
+ CCE-89480-8: Ensure auditd Collects Information on the Use of Privileged Commands - unix_update |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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
+ | 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_update -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 |
+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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_update" command with the following command:
-$ sudo auditctl -l | grep chcon
+$ sudo auditctl -l | grep unix_update
--a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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
+ | 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_update -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 |
+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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -9851,7 +9785,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-89480-8: Ensure auditd Collects Information on the Use of Privileged Commands - unix_update |
+ CCE-80730-5: Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
@@ -9861,29 +9795,33 @@
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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/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=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/pam_timestamp_check
+-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_update" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command:
-$ sudo auditctl -l | grep unix_update
+$ sudo auditctl -l | grep pam_timestamp_check
--a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/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=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/pam_timestamp_check
+-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -9896,45 +9834,50 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80825-3: Enable Auditing for Processes Which Start Prior to the Audit Daemon |
+ CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- To ensure all processes can be audited, even those which start
-prior to the audit daemon, add the argument audit=1 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit=1 is added as a kernel command line
-argument to newly installed kernels, add audit=1 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit=1 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
+ 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 |
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes audit=1,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit=1.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*audit=1.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'audit=1'
-The command should not return any output. Is it the case that auditing is not enabled at boot time? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- To ensure all processes can be audited, even those which start
-prior to the audit daemon, add the argument audit=1 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit=1 is added as a kernel command line
-argument to newly installed kernels, add audit=1 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit=1 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
- low |
+ 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 |
+ medium |
|
|
|
@@ -9946,39 +9889,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80732-1: Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
+ CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- 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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 a line of the following
-form to /etc/audit/audit.rules:
--a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postdrop" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
-$ sudo auditctl -l | grep postdrop
+$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
--a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- 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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 a line of the following
-form to /etc/audit/audit.rules:
--a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
medium |
|
|
@@ -9991,77 +9942,103 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
+ CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. |
- At a minimum, the audit system should collect file deletion events
-for all users and root. If the auditd daemon is configured to use the
+ | 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-renameat system call, run the following command:
-$ sudo grep "renameat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/group)'
+
+-w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
- At a minimum, the audit system should collect file deletion events
-for all users and root. If the auditd daemon is configured to use the
+ | 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
|
-
-
-
-
-
| CCI-000135 |
- SRG-OS-000042-GPOS-00021 |
+ SRG-OS-000042-GPOS-00020 |
TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing the individual identities of group account users. |
+ The operating system must generate audit records containing the full-text recording of privileged commands. |
- CCE-81043-2: Ensure the audit Subsystem is Installed |
+ CCE-80698-4: Record Any Attempts to Run chcon |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-At a minimum, the organization must audit the individual identities of group users. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the actual account involved in the activity. |
- The audit package should be installed. |
+At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+ 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 |
Applicable - Configurable |
- Verify the operating system produces audit records containing the individual identities of group account users. If it does not, this is a finding. |
- Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Configure the operating system to produce audit records containing the individual identities of group account users. |
- The audit package should be installed. |
+ Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
+
+$ sudo auditctl -l | grep chcon
+
+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records containing the full-text recording of privileged commands. |
+ 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 |
medium |
|
|
|
+
+
+
+
+
| CCI-000135 |
SRG-OS-000042-GPOS-00021 |
@@ -10100,6 +10077,29 @@
|
+
+ | CCI-000135 |
+ SRG-OS-000042-GPOS-00021 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must produce audit records containing the individual identities of group account users. |
+
+ CCE-81043-2: Ensure the audit Subsystem is Installed |
+
+ Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the individual identities of group users. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the actual account involved in the activity. |
+ The audit package should be installed. |
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing the individual identities of group account users. If it does not, this is a finding. |
+ Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+ Configure the operating system to produce audit records containing the individual identities of group account users. |
+ The audit package should be installed. |
+ medium |
+ |
+ |
+ |
+
+
@@ -10111,31 +10111,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must alert the ISSO and SA (at a minimum) in the event of an audit processing failure. |
-
CCE-89063-2: Configure System to Forward All Mail From Postmaster to The Root Account |
+
CCE-85983-5: The Postfix package is installed |
It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected.
Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded.
This requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both. |
-
Verify the administrators are notified in the event of an audit processing failure.
-Check that the "/etc/aliases" file has a defined value for "root".
-$ sudo grep "postmaster:\s*root$" /etc/aliases
-
-postmaster: root |
+
A mail server is required for sending emails.
+The postfix package can be installed with the following command:
+
+$ sudo yum install postfix |
Applicable - Configurable |
Verify the operating system alerts the ISSO and SA (at a minimum) in the event of an audit processing failure. If it does not, this is a finding. |
-
Find the list of alias maps used by the Postfix mail server:
-$ sudo postconf alias_maps
-Query the Postfix alias maps for an alias for the postmaster user:
-$ sudo postmap -q postmaster hash:/etc/aliases
-The output should return root. Is it the case that the alias is not set or is not root? |
+
Run the following command to determine if the postfix package is installed: $ rpm -q postfix Is it the case that the package is not installed? |
Configure the operating system to alert the ISSO and SA (at a minimum) in the event of an audit processing failure. |
-
Verify the administrators are notified in the event of an audit processing failure.
-Check that the "/etc/aliases" file has a defined value for "root".
-$ sudo grep "postmaster:\s*root$" /etc/aliases
-
-postmaster: root |
+
A mail server is required for sending emails.
+The postfix package can be installed with the following command:
+
+$ sudo yum install postfix |
medium |
|
|
@@ -10185,25 +10179,31 @@
TBD - Assigned by DISA after STIG release |
The operating system must alert the ISSO and SA (at a minimum) in the event of an audit processing failure. |
-
CCE-85983-5: The Postfix package is installed |
+
CCE-89063-2: Configure System to Forward All Mail From Postmaster to The Root Account |
It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected.
Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded.
This requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both. |
-
A mail server is required for sending emails.
-The postfix package can be installed with the following command:
-
-$ sudo yum install postfix |
+
Verify the administrators are notified in the event of an audit processing failure.
+Check that the "/etc/aliases" file has a defined value for "root".
+$ sudo grep "postmaster:\s*root$" /etc/aliases
+
+postmaster: root |
Applicable - Configurable |
Verify the operating system alerts the ISSO and SA (at a minimum) in the event of an audit processing failure. If it does not, this is a finding. |
-
Run the following command to determine if the postfix package is installed: $ rpm -q postfix Is it the case that the package is not installed? |
+
Find the list of alias maps used by the Postfix mail server:
+$ sudo postconf alias_maps
+Query the Postfix alias maps for an alias for the postmaster user:
+$ sudo postmap -q postmaster hash:/etc/aliases
+The output should return root. Is it the case that the alias is not set or is not root? |
Configure the operating system to alert the ISSO and SA (at a minimum) in the event of an audit processing failure. |
-
A mail server is required for sending emails.
-The postfix package can be installed with the following command:
-
-$ sudo yum install postfix |
+
Verify the administrators are notified in the event of an audit processing failure.
+Check that the "/etc/aliases" file has a defined value for "root".
+$ sudo grep "postmaster:\s*root$" /etc/aliases
+
+postmaster: root |
medium |
|
|
@@ -10342,19 +10342,34 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide the capability to centrally review and analyze audit records from multiple components within the system. |
-
CCE-81043-2: Ensure the audit Subsystem is Installed |
+
CCE-80872-5: Enable auditd Service |
Successful incident response and auditing relies on timely, accurate system information and analysis in order to allow the organization to identify and respond to potential incidents in a proficient manner. If the operating system does not provide the ability to centrally review the operating system logs, forensic analysis is negatively impacted.
Segregation of logging data to multiple disparate computer systems is counterproductive and makes log analysis and log event alarming difficult to implement and manage, particularly when the system has multiple logging components writing to different locations or systems.
To support the centralized capability, the operating system must be able to provide the information in a format that can be extracted and used, allowing the application performing the centralization of the log records to meet this requirement. |
-
The audit package should be installed. |
+
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 |
Applicable - Configurable |
Verify the operating system provides the capability to centrally review and analyze audit records from multiple components within the system. If it does not, this is a finding. |
-
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+
+
+Run the following command to determine the current status of the
+auditd service:
+$ sudo systemctl is-active auditd
+If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
Configure the operating system to provide the capability to centrally review and analyze audit records from multiple components within the system. |
-
The audit package should be installed. |
+
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 |
medium |
|
|
@@ -10367,19 +10382,19 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide the capability to centrally review and analyze audit records from multiple components within the system. |
-
CCE-80847-7: Ensure rsyslog is Installed |
+
CCE-81043-2: Ensure the audit Subsystem is Installed |
Successful incident response and auditing relies on timely, accurate system information and analysis in order to allow the organization to identify and respond to potential incidents in a proficient manner. If the operating system does not provide the ability to centrally review the operating system logs, forensic analysis is negatively impacted.
Segregation of logging data to multiple disparate computer systems is counterproductive and makes log analysis and log event alarming difficult to implement and manage, particularly when the system has multiple logging components writing to different locations or systems.
To support the centralized capability, the operating system must be able to provide the information in a format that can be extracted and used, allowing the application performing the centralization of the log records to meet this requirement. |
-
Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
+
The audit package should be installed. |
Applicable - Configurable |
Verify the operating system provides the capability to centrally review and analyze audit records from multiple components within the system. If it does not, this is a finding. |
-
Run the following command to determine if the rsyslog package is installed: $ rpm -q rsyslog Is it the case that the package is not installed? |
+
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
Configure the operating system to provide the capability to centrally review and analyze audit records from multiple components within the system. |
-
Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
+
The audit package should be installed. |
medium |
|
|
@@ -10392,34 +10407,19 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide the capability to centrally review and analyze audit records from multiple components within the system. |
-
CCE-80872-5: Enable auditd Service |
+
CCE-80847-7: Ensure rsyslog is Installed |
Successful incident response and auditing relies on timely, accurate system information and analysis in order to allow the organization to identify and respond to potential incidents in a proficient manner. If the operating system does not provide the ability to centrally review the operating system logs, forensic analysis is negatively impacted.
Segregation of logging data to multiple disparate computer systems is counterproductive and makes log analysis and log event alarming difficult to implement and manage, particularly when the system has multiple logging components writing to different locations or systems.
To support the centralized capability, the operating system must be able to provide the information in a format that can be extracted and used, allowing the application performing the centralization of the log records to meet this requirement. |
-
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 |
+
Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
Applicable - Configurable |
Verify the operating system provides the capability to centrally review and analyze audit records from multiple components within the system. If it does not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-auditd service:
-$ sudo systemctl is-active auditd
-If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
+
Run the following command to determine if the rsyslog package is installed: $ rpm -q rsyslog Is it the case that the package is not installed? |
Configure the operating system to provide the capability to centrally review and analyze audit records from multiple components within the system. |
-
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 |
+
Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
medium |
|
|
@@ -10437,19 +10437,34 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide the capability to filter audit records for events of interest based upon all audit fields within audit records. |
-
CCE-81043-2: Ensure the audit Subsystem is Installed |
+
CCE-80872-5: Enable auditd Service |
The ability to specify the event criteria that are of interest provides the individuals reviewing the logs with the ability to quickly isolate and identify these events without having to review entries that are of little or no consequence to the investigation. Without this capability, forensic investigations are impeded.
Events of interest can be identified by the content of specific audit record fields, including, for example, identities of individuals, event types, event locations, event times, event dates, system resources involved, IP addresses involved, or information objects accessed. Organizations may define audit event criteria to any degree of granularity required, for example, locations selectable by general networking location (e.g., by network or subnetwork) or selectable by specific information system component.
This requires operating systems to provide the capability to customize audit record reports based on all available criteria. |
-
The audit package should be installed. |
+
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 |
Applicable - Configurable |
Verify the operating system provides the capability to filter audit records for events of interest based upon all audit fields within audit records. If it does not, this is a finding. |
-
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+
+
+Run the following command to determine the current status of the
+auditd service:
+$ sudo systemctl is-active auditd
+If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
Configure the operating system to provide the capability to filter audit records for events of interest based upon all audit fields within audit records. |
-
The audit package should be installed. |
+
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 |
medium |
|
|
@@ -10462,34 +10477,19 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide the capability to filter audit records for events of interest based upon all audit fields within audit records. |
-
CCE-80872-5: Enable auditd Service |
+
CCE-81043-2: Ensure the audit Subsystem is Installed |
The ability to specify the event criteria that are of interest provides the individuals reviewing the logs with the ability to quickly isolate and identify these events without having to review entries that are of little or no consequence to the investigation. Without this capability, forensic investigations are impeded.
Events of interest can be identified by the content of specific audit record fields, including, for example, identities of individuals, event types, event locations, event times, event dates, system resources involved, IP addresses involved, or information objects accessed. Organizations may define audit event criteria to any degree of granularity required, for example, locations selectable by general networking location (e.g., by network or subnetwork) or selectable by specific information system component.
This requires operating systems to provide the capability to customize audit record reports based on all available criteria. |
-
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 |
+
The audit package should be installed. |
Applicable - Configurable |
Verify the operating system provides the capability to filter audit records for events of interest based upon all audit fields within audit records. If it does not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-auditd service:
-$ sudo systemctl is-active auditd
-If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
+
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
Configure the operating system to provide the capability to filter audit records for events of interest based upon all audit fields within audit records. |
-
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 |
+
The audit package should be installed. |
medium |
|
|
@@ -10531,50 +10531,37 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized read access. |
-
CCE-84048-8: System Audit Logs Must Have Mode 0750 or Less Permissive |
+
CCE-88226-6: System Audit Directories Must Be Owned By Root |
Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity. |
-
-Verify the audit log directories have a mode of "0700" or less permissive by first determining
-where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
+ All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-log_file = /var/log/audit/audit.log
-Configure the audit log directory to be protected from unauthorized read access by setting the
-correct permissive mode with the following command:
-$ sudo chmod 0700 audit_log_directory
-By default, audit_log_directory is "/var/log/audit". |
+To properly set the owner of /var/log/audit, run the command:
+$ sudo chown root /var/log/audit |
Applicable - Configurable |
Verify the operating system protects audit information from unauthorized read access. If it does not, this is a finding. |
-
Verify the audit log directories have a correct mode or less permissive mode.
-
-Find the location of the audit logs:
-
-$ sudo grep "^log_file" /etc/audit/auditd.conf
-
+ | Determine where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
-Run the following command to check the mode of the system audit logs:
+log_file = /var/log/audit/audit.log
-$ sudo stat -c "%a %n" [audit_log_directory]
+Determine the owner of the audit log directory by using the output of the above command
+(default: "/var/log/audit/"). Run the following command with the correct audit log directory
+path:
-Replace "[audit_log_directory]" to the correct audit log directory path, by default this location is "/var/log/audit".
+$ sudo ls -ld /var/log/audit
+drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit
-The correct permissions are 0700 Is it the case that audit logs have a more permissive mode? |
+The audit log directory must be owned by "root" Is it the case that the directory is not owned by root?
Configure the operating system to protect audit information from unauthorized read access. |
-
-Verify the audit log directories have a mode of "0700" or less permissive by first determining
-where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
+ All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-log_file = /var/log/audit/audit.log
-Configure the audit log directory to be protected from unauthorized read access by setting the
-correct permissive mode with the following command:
-$ sudo chmod 0700 audit_log_directory
-By default, audit_log_directory is "/var/log/audit". |
+To properly set the owner of /var/log/audit, run the command:
+$ sudo chown root /var/log/audit |
medium |
|
|
@@ -10646,81 +10633,56 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized read access. |
-
CCE-88225-8: System Audit Directories Must Be Group Owned By Root |
+
CCE-88227-4: System Audit Logs Must Be Group Owned By Root |
Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity. |
-
All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/ .
+ | All audit logs must be group owned by root user. The path for audit log can
+be configured via log_file parameter in /etc/audit/auditd.conf
+or, by default, the path for audit log is /var/log/audit/ .
-To properly set the group owner of /var/log/audit, run the command:
-$ sudo chgrp root /var/log/audit
+To properly set the group owner of /var/log/audit/*, run the command:
+$ sudo chgrp root /var/log/audit/*
-If log_group in /etc/audit/auditd.conf is set to a group other than the root
-group account, change the group ownership of the audit directories to this specific group. |
+If
log_group in
/etc/audit/auditd.conf is set to a group other
+than the
root group account, change the group ownership of the audit logs
+to this specific group.
Applicable - Configurable |
Verify the operating system protects audit information from unauthorized read access. If it does not, this is a finding. |
-
-Determine the audit log group by running the following command:
+ | Check group owners of the system audit logs.
-$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
+First, determine where the audit log file is located.
-Then, check that all directories within the /var/log/audit directory are owned by the group specified as log_group or by root if the log_group is not specified.
-Run the following command:
+$ sudo grep -iw ^log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
-$ sudo find /var/log/audit -type d -printf "%p %g\n"
+The log_file option specifies the audit log file path.
+If the log_file option isn't defined, check all files within /var/log/audit directory.
-All listed directories must be owned by the log_group or by root if the log_group is not specified. Is it the case that there is a directory owned by different group? |
-
Configure the operating system to protect audit information from unauthorized read access. |
-
All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/ .
-To properly set the group owner of /var/log/audit, run the command:
-$ sudo chgrp root /var/log/audit
+Then, determine the audit log group by running the following command:
+$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
-If log_group in /etc/audit/auditd.conf is set to a group other than the root
-group account, change the group ownership of the audit directories to this specific group. |
-
medium |
-
|
-
|
-
|
-
-
- | CCI-000162 |
- SRG-OS-000057-GPOS-00027 |
- TBD - Assigned by DISA after STIG release |
- The operating system must protect audit information from unauthorized read access. |
+Then, check that the audit log file is owned by the correct group.
+Run the following command to display the owner of the audit log file:
- CCE-80819-6: System Audit Logs Must Have Mode 0640 or Less Permissive |
+$ sudo stat -c "%n %G" log_file
- Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
-Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity. |
-
-Determine where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
-Configure the audit log to be protected from unauthorized read access by setting the correct
-permissive mode with the following command:
-$ sudo chmod 0600 audit_log_file
-By default, audit_log_file is "/var/log/audit/audit.log". |
- Applicable - Configurable |
- Verify the operating system protects audit information from unauthorized read access. If it does not, this is a finding. |
- Run the following command to check the mode of the system audit logs:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file=/var/log/audit/audit.log
-$ sudo stat -c "%n %a" /var/log/audit/*
-$ sudo ls -l /var/log/audit
-Audit logs must be mode 0640 or less permissive. Is it the case that any permissions are more permissive? |
+The audit log file must be owned by the log_group or by root if the log_group is not specified. Is it the case that audit log files are owned by incorrect group?
Configure the operating system to protect audit information from unauthorized read access. |
-
-Determine where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
-Configure the audit log to be protected from unauthorized read access by setting the correct
-permissive mode with the following command:
-$ sudo chmod 0600 audit_log_file
-By default, audit_log_file is "/var/log/audit/audit.log". |
+ All audit logs must be group owned by root user. The path for audit log can
+be configured via log_file parameter in /etc/audit/auditd.conf
+or, by default, the path for audit log is /var/log/audit/ .
+
+To properly set the group owner of /var/log/audit/*, run the command:
+$ sudo chgrp root /var/log/audit/*
+
+If log_group in /etc/audit/auditd.conf is set to a group other
+than the root group account, change the group ownership of the audit logs
+to this specific group. |
medium |
|
|
@@ -10772,56 +10734,95 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized read access. |
- CCE-88227-4: System Audit Logs Must Be Group Owned By Root |
+ CCE-88225-8: System Audit Directories Must Be Group Owned By Root |
Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity. |
- All audit logs must be group owned by root user. The path for audit log can
-be configured via log_file parameter in /etc/audit/auditd.conf
-or, by default, the path for audit log is /var/log/audit/ .
+ | All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/ .
-To properly set the group owner of /var/log/audit/*, run the command:
-$ sudo chgrp root /var/log/audit/*
+To properly set the group owner of /var/log/audit, run the command:
+$ sudo chgrp root /var/log/audit
-If log_group in /etc/audit/auditd.conf is set to a group other
-than the root group account, change the group ownership of the audit logs
-to this specific group. |
+If log_group in /etc/audit/auditd.conf is set to a group other than the root
+group account, change the group ownership of the audit directories to this specific group.
Applicable - Configurable |
Verify the operating system protects audit information from unauthorized read access. If it does not, this is a finding. |
- Check group owners of the system audit logs.
+ |
+Determine the audit log group by running the following command:
-First, determine where the audit log file is located.
+$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
-$ sudo grep -iw ^log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
+Then, check that all directories within the /var/log/audit directory are owned by the group specified as log_group or by root if the log_group is not specified.
+Run the following command:
-The log_file option specifies the audit log file path.
-If the log_file option isn't defined, check all files within /var/log/audit directory.
+$ sudo find /var/log/audit -type d -printf "%p %g\n"
+All listed directories must be owned by the log_group or by root if the log_group is not specified. Is it the case that there is a directory owned by different group? |
+ Configure the operating system to protect audit information from unauthorized read access. |
+ All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/ .
-Then, determine the audit log group by running the following command:
-$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
+To properly set the group owner of /var/log/audit, run the command:
+$ sudo chgrp root /var/log/audit
+If log_group in /etc/audit/auditd.conf is set to a group other than the root
+group account, change the group ownership of the audit directories to this specific group. |
+ medium |
+ |
+ |
+ |
+
-Then, check that the audit log file is owned by the correct group.
-Run the following command to display the owner of the audit log file:
+
+ | CCI-000162 |
+ SRG-OS-000057-GPOS-00027 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must protect audit information from unauthorized read access. |
-$ sudo stat -c "%n %G" log_file
+ CCE-84048-8: System Audit Logs Must Have Mode 0750 or Less Permissive |
+ Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
-The audit log file must be owned by the log_group or by root if the log_group is not specified. Is it the case that audit log files are owned by incorrect group? |
- Configure the operating system to protect audit information from unauthorized read access. |
- All audit logs must be group owned by root user. The path for audit log can
-be configured via log_file parameter in /etc/audit/auditd.conf
-or, by default, the path for audit log is /var/log/audit/ .
+Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity. |
+
+Verify the audit log directories have a mode of "0700" or less permissive by first determining
+where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
-To properly set the group owner of /var/log/audit/*, run the command:
-$ sudo chgrp root /var/log/audit/*
+log_file = /var/log/audit/audit.log
+Configure the audit log directory to be protected from unauthorized read access by setting the
+correct permissive mode with the following command:
+$ sudo chmod 0700 audit_log_directory
+By default, audit_log_directory is "/var/log/audit". |
+ Applicable - Configurable |
+ Verify the operating system protects audit information from unauthorized read access. If it does not, this is a finding. |
+ Verify the audit log directories have a correct mode or less permissive mode.
-If log_group in /etc/audit/auditd.conf is set to a group other
-than the root group account, change the group ownership of the audit logs
-to this specific group. |
+Find the location of the audit logs:
+
+$ sudo grep "^log_file" /etc/audit/auditd.conf
+
+
+
+Run the following command to check the mode of the system audit logs:
+
+$ sudo stat -c "%a %n" [audit_log_directory]
+
+Replace "[audit_log_directory]" to the correct audit log directory path, by default this location is "/var/log/audit".
+
+
+The correct permissions are 0700 Is it the case that audit logs have a more permissive mode?
+ Configure the operating system to protect audit information from unauthorized read access. |
+
+Verify the audit log directories have a mode of "0700" or less permissive by first determining
+where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+
+log_file = /var/log/audit/audit.log
+Configure the audit log directory to be protected from unauthorized read access by setting the
+correct permissive mode with the following command:
+$ sudo chmod 0700 audit_log_directory
+By default, audit_log_directory is "/var/log/audit". |
medium |
|
|
@@ -10883,37 +10884,36 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized read access. |
- CCE-88226-6: System Audit Directories Must Be Owned By Root |
+ CCE-80819-6: System Audit Logs Must Have Mode 0640 or Less Permissive |
Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity. |
- All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-
-To properly set the owner of /var/log/audit, run the command:
-$ sudo chown root /var/log/audit |
+
+Determine where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
+Configure the audit log to be protected from unauthorized read access by setting the correct
+permissive mode with the following command:
+$ sudo chmod 0600 audit_log_file
+By default, audit_log_file is "/var/log/audit/audit.log". |
Applicable - Configurable |
Verify the operating system protects audit information from unauthorized read access. If it does not, this is a finding. |
- Determine where the audit logs are stored with the following command:
-
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-
-log_file = /var/log/audit/audit.log
-
-Determine the owner of the audit log directory by using the output of the above command
-(default: "/var/log/audit/"). Run the following command with the correct audit log directory
-path:
-
-$ sudo ls -ld /var/log/audit
-
-drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit
-
-The audit log directory must be owned by "root" Is it the case that the directory is not owned by root? |
+ Run the following command to check the mode of the system audit logs:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file=/var/log/audit/audit.log
+$ sudo stat -c "%n %a" /var/log/audit/*
+$ sudo ls -l /var/log/audit
+Audit logs must be mode 0640 or less permissive. Is it the case that any permissions are more permissive? |
Configure the operating system to protect audit information from unauthorized read access. |
- All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-
-To properly set the owner of /var/log/audit, run the command:
-$ sudo chown root /var/log/audit |
+
+Determine where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
+Configure the audit log to be protected from unauthorized read access by setting the correct
+permissive mode with the following command:
+$ sudo chmod 0600 audit_log_file
+By default, audit_log_file is "/var/log/audit/audit.log". |
medium |
|
|
@@ -10931,52 +10931,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized modification. |
- CCE-84048-8: System Audit Logs Must Have Mode 0750 or Less Permissive |
+ CCE-88226-6: System Audit Directories Must Be Owned By Root |
If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the veracity of audit information, the operating system must protect audit information from unauthorized modification.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. |
-
-Verify the audit log directories have a mode of "0700" or less permissive by first determining
-where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
+ All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-log_file = /var/log/audit/audit.log
-Configure the audit log directory to be protected from unauthorized read access by setting the
-correct permissive mode with the following command:
-$ sudo chmod 0700 audit_log_directory
-By default, audit_log_directory is "/var/log/audit". |
+To properly set the owner of /var/log/audit, run the command:
+$ sudo chown root /var/log/audit |
Applicable - Configurable |
Verify the operating system protects audit information from unauthorized modification. If it does not, this is a finding. |
- Verify the audit log directories have a correct mode or less permissive mode.
-
-Find the location of the audit logs:
-
-$ sudo grep "^log_file" /etc/audit/auditd.conf
-
+ | Determine where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
-Run the following command to check the mode of the system audit logs:
+log_file = /var/log/audit/audit.log
-$ sudo stat -c "%a %n" [audit_log_directory]
+Determine the owner of the audit log directory by using the output of the above command
+(default: "/var/log/audit/"). Run the following command with the correct audit log directory
+path:
-Replace "[audit_log_directory]" to the correct audit log directory path, by default this location is "/var/log/audit".
+$ sudo ls -ld /var/log/audit
+drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit
-The correct permissions are 0700 Is it the case that audit logs have a more permissive mode? |
+The audit log directory must be owned by "root" Is it the case that the directory is not owned by root?
Configure the operating system to protect audit information from unauthorized modification. |
-
-Verify the audit log directories have a mode of "0700" or less permissive by first determining
-where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
+ All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-log_file = /var/log/audit/audit.log
-Configure the audit log directory to be protected from unauthorized read access by setting the
-correct permissive mode with the following command:
-$ sudo chmod 0700 audit_log_directory
-By default, audit_log_directory is "/var/log/audit". |
+To properly set the owner of /var/log/audit, run the command:
+$ sudo chown root /var/log/audit |
medium |
|
|
@@ -11050,41 +11037,58 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized modification. |
- CCE-88225-8: System Audit Directories Must Be Group Owned By Root |
+ CCE-88227-4: System Audit Logs Must Be Group Owned By Root |
If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the veracity of audit information, the operating system must protect audit information from unauthorized modification.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. |
- All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/ .
+ | All audit logs must be group owned by root user. The path for audit log can
+be configured via log_file parameter in /etc/audit/auditd.conf
+or, by default, the path for audit log is /var/log/audit/ .
-To properly set the group owner of /var/log/audit, run the command:
-$ sudo chgrp root /var/log/audit
+To properly set the group owner of /var/log/audit/*, run the command:
+$ sudo chgrp root /var/log/audit/*
-If log_group in /etc/audit/auditd.conf is set to a group other than the root
-group account, change the group ownership of the audit directories to this specific group. |
+If log_group in /etc/audit/auditd.conf is set to a group other
+than the root group account, change the group ownership of the audit logs
+to this specific group.
Applicable - Configurable |
Verify the operating system protects audit information from unauthorized modification. If it does not, this is a finding. |
-
-Determine the audit log group by running the following command:
+ | Check group owners of the system audit logs.
-$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
+First, determine where the audit log file is located.
-Then, check that all directories within the /var/log/audit directory are owned by the group specified as log_group or by root if the log_group is not specified.
-Run the following command:
+$ sudo grep -iw ^log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
-$ sudo find /var/log/audit -type d -printf "%p %g\n"
+The log_file option specifies the audit log file path.
+If the log_file option isn't defined, check all files within /var/log/audit directory.
-All listed directories must be owned by the log_group or by root if the log_group is not specified. Is it the case that there is a directory owned by different group? |
+
+Then, determine the audit log group by running the following command:
+$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
+
+
+Then, check that the audit log file is owned by the correct group.
+Run the following command to display the owner of the audit log file:
+
+$ sudo stat -c "%n %G" log_file
+
+
+The audit log file must be owned by the log_group or by root if the log_group is not specified. Is it the case that audit log files are owned by incorrect group?
Configure the operating system to protect audit information from unauthorized modification. |
- All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/ .
+ | All audit logs must be group owned by root user. The path for audit log can
+be configured via log_file parameter in /etc/audit/auditd.conf
+or, by default, the path for audit log is /var/log/audit/ .
-To properly set the group owner of /var/log/audit, run the command:
-$ sudo chgrp root /var/log/audit
+To properly set the group owner of /var/log/audit/*, run the command:
+$ sudo chgrp root /var/log/audit/*
-If log_group in /etc/audit/auditd.conf is set to a group other than the root
-group account, change the group ownership of the audit directories to this specific group. |
+If log_group in /etc/audit/auditd.conf is set to a group other
+than the root group account, change the group ownership of the audit logs
+to this specific group.
medium |
|
|
@@ -11097,51 +11101,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized modification. |
- CCE-80819-6: System Audit Logs Must Have Mode 0640 or Less Permissive |
-
- If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
-
-To ensure the veracity of audit information, the operating system must protect audit information from unauthorized modification.
-
-Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. |
-
-Determine where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
-Configure the audit log to be protected from unauthorized read access by setting the correct
-permissive mode with the following command:
-$ sudo chmod 0600 audit_log_file
-By default, audit_log_file is "/var/log/audit/audit.log". |
- Applicable - Configurable |
- Verify the operating system protects audit information from unauthorized modification. If it does not, this is a finding. |
- Run the following command to check the mode of the system audit logs:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file=/var/log/audit/audit.log
-$ sudo stat -c "%n %a" /var/log/audit/*
-$ sudo ls -l /var/log/audit
-Audit logs must be mode 0640 or less permissive. Is it the case that any permissions are more permissive? |
- Configure the operating system to protect audit information from unauthorized modification. |
-
-Determine where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
-Configure the audit log to be protected from unauthorized read access by setting the correct
-permissive mode with the following command:
-$ sudo chmod 0600 audit_log_file
-By default, audit_log_file is "/var/log/audit/audit.log". |
- medium |
- |
- |
- |
-
-
-
- | CCI-000163 |
- SRG-OS-000058-GPOS-00028 |
- TBD - Assigned by DISA after STIG release |
- The operating system must protect audit information from unauthorized modification. |
-
- CCE-88228-2: System Audit Logs Must Be Owned By Root |
+ CCE-88228-2: System Audit Logs Must Be Owned By Root |
If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
@@ -11182,58 +11142,99 @@
| TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized modification. |
- CCE-88227-4: System Audit Logs Must Be Group Owned By Root |
+ CCE-88225-8: System Audit Directories Must Be Group Owned By Root |
If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the veracity of audit information, the operating system must protect audit information from unauthorized modification.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. |
- All audit logs must be group owned by root user. The path for audit log can
-be configured via log_file parameter in /etc/audit/auditd.conf
-or, by default, the path for audit log is /var/log/audit/ .
+ | All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/ .
-To properly set the group owner of /var/log/audit/*, run the command:
-$ sudo chgrp root /var/log/audit/*
+To properly set the group owner of /var/log/audit, run the command:
+$ sudo chgrp root /var/log/audit
-If log_group in /etc/audit/auditd.conf is set to a group other
-than the root group account, change the group ownership of the audit logs
-to this specific group. |
+If log_group in /etc/audit/auditd.conf is set to a group other than the root
+group account, change the group ownership of the audit directories to this specific group.
Applicable - Configurable |
Verify the operating system protects audit information from unauthorized modification. If it does not, this is a finding. |
- Check group owners of the system audit logs.
+ |
+Determine the audit log group by running the following command:
-First, determine where the audit log file is located.
+$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
-$ sudo grep -iw ^log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
+Then, check that all directories within the /var/log/audit directory are owned by the group specified as log_group or by root if the log_group is not specified.
+Run the following command:
-The log_file option specifies the audit log file path.
-If the log_file option isn't defined, check all files within /var/log/audit directory.
+$ sudo find /var/log/audit -type d -printf "%p %g\n"
+All listed directories must be owned by the log_group or by root if the log_group is not specified. Is it the case that there is a directory owned by different group? |
+ Configure the operating system to protect audit information from unauthorized modification. |
+ All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/ .
-Then, determine the audit log group by running the following command:
-$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
+To properly set the group owner of /var/log/audit, run the command:
+$ sudo chgrp root /var/log/audit
+If log_group in /etc/audit/auditd.conf is set to a group other than the root
+group account, change the group ownership of the audit directories to this specific group. |
+ medium |
+ |
+ |
+ |
+
-Then, check that the audit log file is owned by the correct group.
-Run the following command to display the owner of the audit log file:
+
+ | CCI-000163 |
+ SRG-OS-000058-GPOS-00028 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must protect audit information from unauthorized modification. |
-$ sudo stat -c "%n %G" log_file
+ CCE-84048-8: System Audit Logs Must Have Mode 0750 or Less Permissive |
+ If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
-The audit log file must be owned by the log_group or by root if the log_group is not specified. Is it the case that audit log files are owned by incorrect group? |
- Configure the operating system to protect audit information from unauthorized modification. |
- All audit logs must be group owned by root user. The path for audit log can
-be configured via log_file parameter in /etc/audit/auditd.conf
-or, by default, the path for audit log is /var/log/audit/ .
+To ensure the veracity of audit information, the operating system must protect audit information from unauthorized modification.
-To properly set the group owner of /var/log/audit/*, run the command:
-$ sudo chgrp root /var/log/audit/*
+Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. |
+
+Verify the audit log directories have a mode of "0700" or less permissive by first determining
+where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
-If log_group in /etc/audit/auditd.conf is set to a group other
-than the root group account, change the group ownership of the audit logs
-to this specific group. |
+log_file = /var/log/audit/audit.log
+Configure the audit log directory to be protected from unauthorized read access by setting the
+correct permissive mode with the following command:
+$ sudo chmod 0700 audit_log_directory
+By default, audit_log_directory is "/var/log/audit".
+ Applicable - Configurable |
+ Verify the operating system protects audit information from unauthorized modification. If it does not, this is a finding. |
+ Verify the audit log directories have a correct mode or less permissive mode.
+
+Find the location of the audit logs:
+
+$ sudo grep "^log_file" /etc/audit/auditd.conf
+
+
+
+Run the following command to check the mode of the system audit logs:
+
+$ sudo stat -c "%a %n" [audit_log_directory]
+
+Replace "[audit_log_directory]" to the correct audit log directory path, by default this location is "/var/log/audit".
+
+
+The correct permissions are 0700 Is it the case that audit logs have a more permissive mode? |
+ Configure the operating system to protect audit information from unauthorized modification. |
+
+Verify the audit log directories have a mode of "0700" or less permissive by first determining
+where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+
+log_file = /var/log/audit/audit.log
+Configure the audit log directory to be protected from unauthorized read access by setting the
+correct permissive mode with the following command:
+$ sudo chmod 0700 audit_log_directory
+By default, audit_log_directory is "/var/log/audit". |
medium |
|
|
@@ -11297,39 +11298,38 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized modification. |
- CCE-88226-6: System Audit Directories Must Be Owned By Root |
+ CCE-80819-6: System Audit Logs Must Have Mode 0640 or Less Permissive |
If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the veracity of audit information, the operating system must protect audit information from unauthorized modification.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. |
- All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-
-To properly set the owner of /var/log/audit, run the command:
-$ sudo chown root /var/log/audit |
+
+Determine where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
+Configure the audit log to be protected from unauthorized read access by setting the correct
+permissive mode with the following command:
+$ sudo chmod 0600 audit_log_file
+By default, audit_log_file is "/var/log/audit/audit.log". |
Applicable - Configurable |
Verify the operating system protects audit information from unauthorized modification. If it does not, this is a finding. |
- Determine where the audit logs are stored with the following command:
-
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-
-log_file = /var/log/audit/audit.log
-
-Determine the owner of the audit log directory by using the output of the above command
-(default: "/var/log/audit/"). Run the following command with the correct audit log directory
-path:
-
-$ sudo ls -ld /var/log/audit
-
-drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit
-
-The audit log directory must be owned by "root" Is it the case that the directory is not owned by root? |
+ Run the following command to check the mode of the system audit logs:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file=/var/log/audit/audit.log
+$ sudo stat -c "%n %a" /var/log/audit/*
+$ sudo ls -l /var/log/audit
+Audit logs must be mode 0640 or less permissive. Is it the case that any permissions are more permissive? |
Configure the operating system to protect audit information from unauthorized modification. |
- All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-
-To properly set the owner of /var/log/audit, run the command:
-$ sudo chown root /var/log/audit |
+
+Determine where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
+Configure the audit log to be protected from unauthorized read access by setting the correct
+permissive mode with the following command:
+$ sudo chmod 0600 audit_log_file
+By default, audit_log_file is "/var/log/audit/audit.log". |
medium |
|
|
@@ -11347,52 +11347,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized deletion. |
- CCE-84048-8: System Audit Logs Must Have Mode 0750 or Less Permissive |
+ CCE-88226-6: System Audit Directories Must Be Owned By Root |
If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the veracity of audit information, the operating system must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. |
-
-Verify the audit log directories have a mode of "0700" or less permissive by first determining
-where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
+ All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-log_file = /var/log/audit/audit.log
-Configure the audit log directory to be protected from unauthorized read access by setting the
-correct permissive mode with the following command:
-$ sudo chmod 0700 audit_log_directory
-By default, audit_log_directory is "/var/log/audit". |
+To properly set the owner of /var/log/audit, run the command:
+$ sudo chown root /var/log/audit |
Applicable - Configurable |
Verify the operating system protects audit information from unauthorized deletion. If it does not, this is a finding. |
- Verify the audit log directories have a correct mode or less permissive mode.
-
-Find the location of the audit logs:
-
-$ sudo grep "^log_file" /etc/audit/auditd.conf
-
+ | Determine where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
-Run the following command to check the mode of the system audit logs:
+log_file = /var/log/audit/audit.log
-$ sudo stat -c "%a %n" [audit_log_directory]
+Determine the owner of the audit log directory by using the output of the above command
+(default: "/var/log/audit/"). Run the following command with the correct audit log directory
+path:
-Replace "[audit_log_directory]" to the correct audit log directory path, by default this location is "/var/log/audit".
+$ sudo ls -ld /var/log/audit
+drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit
-The correct permissions are 0700 Is it the case that audit logs have a more permissive mode? |
+The audit log directory must be owned by "root" Is it the case that the directory is not owned by root?
Configure the operating system to protect audit information from unauthorized deletion. |
-
-Verify the audit log directories have a mode of "0700" or less permissive by first determining
-where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
+ All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-log_file = /var/log/audit/audit.log
-Configure the audit log directory to be protected from unauthorized read access by setting the
-correct permissive mode with the following command:
-$ sudo chmod 0700 audit_log_directory
-By default, audit_log_directory is "/var/log/audit". |
+To properly set the owner of /var/log/audit, run the command:
+$ sudo chown root /var/log/audit |
medium |
|
|
@@ -11466,85 +11453,58 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized deletion. |
- CCE-88225-8: System Audit Directories Must Be Group Owned By Root |
+ CCE-88227-4: System Audit Logs Must Be Group Owned By Root |
If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the veracity of audit information, the operating system must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. |
- All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/ .
+ | All audit logs must be group owned by root user. The path for audit log can
+be configured via log_file parameter in /etc/audit/auditd.conf
+or, by default, the path for audit log is /var/log/audit/ .
-To properly set the group owner of /var/log/audit, run the command:
-$ sudo chgrp root /var/log/audit
+To properly set the group owner of /var/log/audit/*, run the command:
+$ sudo chgrp root /var/log/audit/*
-If log_group in /etc/audit/auditd.conf is set to a group other than the root
-group account, change the group ownership of the audit directories to this specific group. |
+If log_group in /etc/audit/auditd.conf is set to a group other
+than the root group account, change the group ownership of the audit logs
+to this specific group.
Applicable - Configurable |
Verify the operating system protects audit information from unauthorized deletion. If it does not, this is a finding. |
-
-Determine the audit log group by running the following command:
-
-$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
+ | Check group owners of the system audit logs.
-Then, check that all directories within the /var/log/audit directory are owned by the group specified as log_group or by root if the log_group is not specified.
-Run the following command:
+First, determine where the audit log file is located.
-$ sudo find /var/log/audit -type d -printf "%p %g\n"
+$ sudo grep -iw ^log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
-All listed directories must be owned by the log_group or by root if the log_group is not specified. Is it the case that there is a directory owned by different group? |
- Configure the operating system to protect audit information from unauthorized deletion. |
- All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/ .
+The log_file option specifies the audit log file path.
+If the log_file option isn't defined, check all files within /var/log/audit directory.
-To properly set the group owner of /var/log/audit, run the command:
-$ sudo chgrp root /var/log/audit
-If log_group in /etc/audit/auditd.conf is set to a group other than the root
-group account, change the group ownership of the audit directories to this specific group. |
- medium |
- |
- |
- |
-
+Then, determine the audit log group by running the following command:
+
$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
-
- | CCI-000164 |
- SRG-OS-000059-GPOS-00029 |
- TBD - Assigned by DISA after STIG release |
- The operating system must protect audit information from unauthorized deletion. |
- CCE-80819-6: System Audit Logs Must Have Mode 0640 or Less Permissive |
+Then, check that the audit log file is owned by the correct group.
+Run the following command to display the owner of the audit log file:
- If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
+$ sudo stat -c "%n %G" log_file
-To ensure the veracity of audit information, the operating system must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design.
-Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. |
-
-Determine where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
-Configure the audit log to be protected from unauthorized read access by setting the correct
-permissive mode with the following command:
-$ sudo chmod 0600 audit_log_file
-By default, audit_log_file is "/var/log/audit/audit.log". |
- Applicable - Configurable |
- Verify the operating system protects audit information from unauthorized deletion. If it does not, this is a finding. |
- Run the following command to check the mode of the system audit logs:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file=/var/log/audit/audit.log
-$ sudo stat -c "%n %a" /var/log/audit/*
-$ sudo ls -l /var/log/audit
-Audit logs must be mode 0640 or less permissive. Is it the case that any permissions are more permissive? |
+The audit log file must be owned by the log_group or by root if the log_group is not specified. Is it the case that audit log files are owned by incorrect group?
Configure the operating system to protect audit information from unauthorized deletion. |
-
-Determine where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
-Configure the audit log to be protected from unauthorized read access by setting the correct
-permissive mode with the following command:
-$ sudo chmod 0600 audit_log_file
-By default, audit_log_file is "/var/log/audit/audit.log". |
+ All audit logs must be group owned by root user. The path for audit log can
+be configured via log_file parameter in /etc/audit/auditd.conf
+or, by default, the path for audit log is /var/log/audit/ .
+
+To properly set the group owner of /var/log/audit/*, run the command:
+$ sudo chgrp root /var/log/audit/*
+
+If log_group in /etc/audit/auditd.conf is set to a group other
+than the root group account, change the group ownership of the audit logs
+to this specific group. |
medium |
|
|
@@ -11598,58 +11558,99 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized deletion. |
- CCE-88227-4: System Audit Logs Must Be Group Owned By Root |
+ CCE-88225-8: System Audit Directories Must Be Group Owned By Root |
If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the veracity of audit information, the operating system must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. |
- All audit logs must be group owned by root user. The path for audit log can
-be configured via log_file parameter in /etc/audit/auditd.conf
-or, by default, the path for audit log is /var/log/audit/ .
+ | All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/ .
-To properly set the group owner of /var/log/audit/*, run the command:
-$ sudo chgrp root /var/log/audit/*
+To properly set the group owner of /var/log/audit, run the command:
+$ sudo chgrp root /var/log/audit
-If log_group in /etc/audit/auditd.conf is set to a group other
-than the root group account, change the group ownership of the audit logs
-to this specific group. |
+If log_group in /etc/audit/auditd.conf is set to a group other than the root
+group account, change the group ownership of the audit directories to this specific group.
Applicable - Configurable |
Verify the operating system protects audit information from unauthorized deletion. If it does not, this is a finding. |
- Check group owners of the system audit logs.
+ |
+Determine the audit log group by running the following command:
-First, determine where the audit log file is located.
+$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
-$ sudo grep -iw ^log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
+Then, check that all directories within the /var/log/audit directory are owned by the group specified as log_group or by root if the log_group is not specified.
+Run the following command:
-The log_file option specifies the audit log file path.
-If the log_file option isn't defined, check all files within /var/log/audit directory.
+$ sudo find /var/log/audit -type d -printf "%p %g\n"
+All listed directories must be owned by the log_group or by root if the log_group is not specified. Is it the case that there is a directory owned by different group? |
+ Configure the operating system to protect audit information from unauthorized deletion. |
+ All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/ .
-Then, determine the audit log group by running the following command:
-$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
+To properly set the group owner of /var/log/audit, run the command:
+$ sudo chgrp root /var/log/audit
+If log_group in /etc/audit/auditd.conf is set to a group other than the root
+group account, change the group ownership of the audit directories to this specific group. |
+ medium |
+ |
+ |
+ |
+
-Then, check that the audit log file is owned by the correct group.
-Run the following command to display the owner of the audit log file:
+
+ | CCI-000164 |
+ SRG-OS-000059-GPOS-00029 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must protect audit information from unauthorized deletion. |
-$ sudo stat -c "%n %G" log_file
+ CCE-84048-8: System Audit Logs Must Have Mode 0750 or Less Permissive |
+ If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
-The audit log file must be owned by the log_group or by root if the log_group is not specified. Is it the case that audit log files are owned by incorrect group? |
- Configure the operating system to protect audit information from unauthorized deletion. |
- All audit logs must be group owned by root user. The path for audit log can
-be configured via log_file parameter in /etc/audit/auditd.conf
-or, by default, the path for audit log is /var/log/audit/ .
+To ensure the veracity of audit information, the operating system must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design.
-To properly set the group owner of /var/log/audit/*, run the command:
-$ sudo chgrp root /var/log/audit/*
+Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. |
+
+Verify the audit log directories have a mode of "0700" or less permissive by first determining
+where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
-If log_group in /etc/audit/auditd.conf is set to a group other
-than the root group account, change the group ownership of the audit logs
-to this specific group. |
+log_file = /var/log/audit/audit.log
+Configure the audit log directory to be protected from unauthorized read access by setting the
+correct permissive mode with the following command:
+$ sudo chmod 0700 audit_log_directory
+By default, audit_log_directory is "/var/log/audit".
+ Applicable - Configurable |
+ Verify the operating system protects audit information from unauthorized deletion. If it does not, this is a finding. |
+ Verify the audit log directories have a correct mode or less permissive mode.
+
+Find the location of the audit logs:
+
+$ sudo grep "^log_file" /etc/audit/auditd.conf
+
+
+
+Run the following command to check the mode of the system audit logs:
+
+$ sudo stat -c "%a %n" [audit_log_directory]
+
+Replace "[audit_log_directory]" to the correct audit log directory path, by default this location is "/var/log/audit".
+
+
+The correct permissions are 0700 Is it the case that audit logs have a more permissive mode? |
+ Configure the operating system to protect audit information from unauthorized deletion. |
+
+Verify the audit log directories have a mode of "0700" or less permissive by first determining
+where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+
+log_file = /var/log/audit/audit.log
+Configure the audit log directory to be protected from unauthorized read access by setting the
+correct permissive mode with the following command:
+$ sudo chmod 0700 audit_log_directory
+By default, audit_log_directory is "/var/log/audit". |
medium |
|
|
@@ -11713,39 +11714,38 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit information from unauthorized deletion. |
- CCE-88226-6: System Audit Directories Must Be Owned By Root |
+ CCE-80819-6: System Audit Logs Must Have Mode 0640 or Less Permissive |
If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the veracity of audit information, the operating system must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity. |
- All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-
-To properly set the owner of /var/log/audit, run the command:
-$ sudo chown root /var/log/audit |
+
+Determine where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
+Configure the audit log to be protected from unauthorized read access by setting the correct
+permissive mode with the following command:
+$ sudo chmod 0600 audit_log_file
+By default, audit_log_file is "/var/log/audit/audit.log". |
Applicable - Configurable |
Verify the operating system protects audit information from unauthorized deletion. If it does not, this is a finding. |
- Determine where the audit logs are stored with the following command:
-
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-
-log_file = /var/log/audit/audit.log
-
-Determine the owner of the audit log directory by using the output of the above command
-(default: "/var/log/audit/"). Run the following command with the correct audit log directory
-path:
-
-$ sudo ls -ld /var/log/audit
-
-drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit
-
-The audit log directory must be owned by "root" Is it the case that the directory is not owned by root? |
+ Run the following command to check the mode of the system audit logs:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file=/var/log/audit/audit.log
+$ sudo stat -c "%n %a" /var/log/audit/*
+$ sudo ls -l /var/log/audit
+Audit logs must be mode 0640 or less permissive. Is it the case that any permissions are more permissive? |
Configure the operating system to protect audit information from unauthorized deletion. |
- All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-
-To properly set the owner of /var/log/audit, run the command:
-$ sudo chown root /var/log/audit |
+
+Determine where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
+Configure the audit log to be protected from unauthorized read access by setting the correct
+permissive mode with the following command:
+$ sudo chmod 0600 audit_log_file
+By default, audit_log_file is "/var/log/audit/audit.log". |
medium |
|
|
@@ -11763,7 +11763,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-85944-7: Record Any Attempts to Run ssh-agent |
+ CCE-80700-8: Record Any Attempts to Run semanage |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -11781,15 +11781,15 @@
4) All kernel module load, unload, and restart actions. |
At a minimum, the audit system should collect any execution attempt
-of the ssh-agent command for all users and root. If the auditd
+of the semanage 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
+-a always,exit -F path=/usr/sbin/semanage -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/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -11804,11 +11804,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
-$ sudo auditctl -l | grep ssh-agent
+$ sudo auditctl -l | grep semanage
--a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -11821,15 +11821,15 @@
4) All kernel module load, unload, and restart actions. |
At a minimum, the audit system should collect any execution attempt
-of the ssh-agent command for all users and root. If the auditd
+of the semanage 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
+-a always,exit -F path=/usr/sbin/semanage -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/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -11842,7 +11842,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80730-5: Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
+ CCE-80989-7: Ensure auditd Collects Information on the Use of Privileged Commands - mount |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -11864,13 +11864,11 @@
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/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -11885,11 +11883,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "mount" command with the following command:
-$ sudo auditctl -l | grep pam_timestamp_check
+$ sudo auditctl -l | grep mount
--a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -11906,13 +11904,11 @@
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/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -12004,7 +12000,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80728-9: Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
+ CCE-80731-3: Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -12026,11 +12022,11 @@
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
+-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/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -12045,11 +12041,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "gpasswd" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "passwd" command with the following command:
-$ sudo auditctl -l | grep gpasswd
+$ sudo auditctl -l | grep passwd
--a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -12066,11 +12062,11 @@
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
+-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/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -12083,7 +12079,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
+ CCE-80872-5: Enable auditd Service |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -12100,16 +12096,12 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 |
+ 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 |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -12124,11 +12116,12 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
-
-$ sudo auditctl -l | grep su
+ |
--a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out? |
+Run the following command to determine the current status of the
+auditd service:
+$ sudo systemctl is-active auditd
+If the service is running, it should return the following: active
Is it the case that the auditd service is not running?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -12140,16 +12133,12 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 |
+ 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 |
medium |
|
|
@@ -12162,7 +12151,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
+ CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -12179,29 +12168,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
-
+ | 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 lines to
+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 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 |
+-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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -12216,22 +12196,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r truncate /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep truncate /etc/audit/audit.rules
-
-The output should be the following:
-
--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+chown system call, run the following command:
+$ sudo grep "chown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -12243,29 +12212,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
-
+ | 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 lines to
+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 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 |
+-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
medium |
|
|
@@ -12278,7 +12238,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80729-7: Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
+ CCE-82168-6: Log USBGuard daemon audit events using Linux Audit |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -12295,16 +12255,10 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 |
+ To configure USBGuard daemon to log via Linux Audit
+(as opposed directly to a file),
+AuditBackend option in /etc/usbguard/usbguard-daemon.conf
+needs to be set to LinuxAudit. |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -12319,11 +12273,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "newgrp" command with the following command:
-
-$ sudo auditctl -l | grep newgrp
-
--a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out? |
+ To verify that Linux Audit logging is enabled for the USBGuard daemon,
+run the following command:
+$ sudo grep AuditBackend /etc/usbguard/usbguard-daemon.conf
+The output should be
+AuditBackend=LinuxAudit Is it the case that AuditBackend is not set to LinuxAudit? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -12335,17 +12289,11 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 |
- medium |
+ To configure USBGuard daemon to log via Linux Audit
+(as opposed directly to a file),
+AuditBackend option in /etc/usbguard/usbguard-daemon.conf
+needs to be set to LinuxAudit. |
+ low |
|
|
|
@@ -12357,7 +12305,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
+ CCE-80701-6: Record Any Attempts to Run setsebool |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -12374,26 +12322,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 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
+-a always,exit -F path=/usr/sbin/setsebool -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 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=access |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -12408,22 +12346,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r open_by_handle_at /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep open_by_handle_at /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep setsebool
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -12435,26 +12362,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 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
+-a always,exit -F path=/usr/sbin/setsebool -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 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=access |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -12467,7 +12384,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
+ CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -12484,103 +12401,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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_mod |
- Applicable - Configurable |
- Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
-
-DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
-
-1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);
-
-2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;
-
-3) All account creations, modifications, disabling, and terminations; and
-
-4) All kernel module load, unload, and restart actions.
-
-If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-lchown system call, run the following command:
-$ sudo grep "lchown" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
-
-DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
-
-1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);
-
-2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;
-
-3) All account creations, modifications, disabling, and terminations; and
-
-4) All kernel module load, unload, and restart actions. |
- 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
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-000169 |
- SRG-OS-000062-GPOS-00031 |
- TBD - Assigned by DISA after STIG release |
- The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
-
- CCE-89455-0: Ensure auditd Collects Information on the Use of Privileged Commands - kmod |
-
- Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter).
-
-The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records.
-
-DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
-
-1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);
-
-2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;
-
-3) All account creations, modifications, disabling, and terminations; and
-
-4) All kernel module load, unload, and restart actions. |
- 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/kmod -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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-w /etc/sudoers -p wa -k actions
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -12595,11 +12425,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "kmod" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-$ sudo auditctl -l | grep kmod
+$ sudo auditctl -l | grep /etc/sudoers
--a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-kmod Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -12611,16 +12441,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers -p wa -k actions
medium |
|
|
@@ -12633,7 +12463,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -12656,14 +12486,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -12678,11 +12508,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+$ sudo auditctl -l | grep -E '(/etc/shadow)'
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -12700,14 +12530,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -12720,7 +12550,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80733-9: Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
+ CCE-89455-0: Ensure auditd Collects Information on the Use of Privileged Commands - kmod |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -12742,11 +12572,11 @@
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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/bin/kmod -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -12761,11 +12591,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postqueue" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "kmod" command with the following command:
-$ sudo auditctl -l | grep postqueue
+$ sudo auditctl -l | grep kmod
--a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-kmod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -12782,11 +12612,11 @@
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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/bin/kmod -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -12799,7 +12629,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-89446-9: Record Any Attempts to Run chacl |
+ CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -12816,16 +12646,24 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 lines to
+utility to read audit rules during daemon startup, add the following line 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 |
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -12840,11 +12678,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
-
-$ sudo auditctl -l | grep chacl
-
--a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fsetxattr system call, run the following command:
+$ sudo grep "fsetxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -12856,16 +12694,24 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 lines to
+utility to read audit rules during daemon startup, add the following line 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 |
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -12878,7 +12724,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80740-4: Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
+ CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -12895,16 +12741,24 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
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 |
+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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -12919,11 +12773,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command:
-
-$ sudo auditctl -l | grep unix_chkpwd
-
--a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+setxattr system call, run the following command:
+$ sudo grep "setxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -12935,16 +12789,24 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
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 |
+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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -12957,7 +12819,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
+ CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -12974,16 +12836,29 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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 |
+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=access
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -12998,11 +12873,22 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-$ sudo auditctl -l | grep usermod
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r truncate /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep truncate /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -13014,16 +12900,29 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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 |
+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=access
medium |
|
|
@@ -13036,7 +12935,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
+ CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -13053,16 +12952,28 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+
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 |
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -13077,11 +12988,126 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
+ | To determine if the system is configured to audit calls to the
+removexattr system call, run the following command:
+$ sudo grep "removexattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
-$ sudo auditctl -l | grep sudo
+DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
--a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out? |
+1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);
+
+2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;
+
+3) All account creations, modifications, disabling, and terminations; and
+
+4) All kernel module load, unload, and restart actions.
+ 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000169 |
+ SRG-OS-000062-GPOS-00031 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
+
+ CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
+
+ Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter).
+
+The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records.
+
+DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
+
+1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);
+
+2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;
+
+3) All account creations, modifications, disabling, and terminations; and
+
+4) All kernel module load, unload, and restart actions. |
+ 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 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=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=access |
+ Applicable - Configurable |
+ Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
+
+DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
+
+1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);
+
+2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;
+
+3) All account creations, modifications, disabling, and terminations; and
+
+4) All kernel module load, unload, and restart actions.
+
+If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
+
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
+
+$ sudo grep -r ftruncate /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep ftruncate /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -13093,16 +13119,29 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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=access
+
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 |
+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=access
medium |
|
|
@@ -13115,7 +13154,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80726-3: Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
+ CCE-80732-1: Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -13137,11 +13176,11 @@
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
+-a always,exit -F path=/usr/sbin/postdrop -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 |
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -13156,11 +13195,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chsh" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postdrop" command with the following command:
-$ sudo auditctl -l | grep chsh
+$ sudo auditctl -l | grep postdrop
--a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -13177,11 +13216,11 @@
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
+-a always,exit -F path=/usr/sbin/postdrop -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 |
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -13194,7 +13233,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
+ CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -13217,12 +13256,12 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -13238,8 +13277,8 @@
If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-unlink system call, run the following command:
-$ sudo grep "unlink" /etc/audit/audit.*
+unlinkat system call, run the following command:
+$ sudo grep "unlinkat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -13259,12 +13298,12 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -13277,7 +13316,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80741-2: Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
+ CCE-80728-9: Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -13299,11 +13338,11 @@
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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -13318,11 +13357,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "userhelper" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "gpasswd" command with the following command:
-$ sudo auditctl -l | grep userhelper
+$ sudo auditctl -l | grep gpasswd
--a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -13339,11 +13378,11 @@
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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -13356,7 +13395,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
+ CCE-80725-5: Ensure auditd Collects Information on the Use of Privileged Commands - chage |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -13373,18 +13412,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
+ 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 |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -13399,11 +13436,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-finit_module system call, run the following command:
-$ sudo grep "finit_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chage" command with the following command:
+
+$ sudo auditctl -l | grep chage
+
+-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -13415,18 +13452,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
+ 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 |
medium |
|
|
@@ -13439,7 +13474,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
+ CCE-81043-2: Ensure the audit Subsystem is Installed |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -13456,20 +13491,7 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 |
+ The audit package should be installed. |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -13484,11 +13506,7 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/shadow)'
-
--w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
+ Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -13500,20 +13518,7 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 |
+ The audit package should be installed. |
medium |
|
|
@@ -13526,7 +13531,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80727-1: Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
+ CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -13543,16 +13548,23 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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 |
+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_mod
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -13567,11 +13579,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "crontab" command with the following command:
-
-$ sudo auditctl -l | grep crontab
-
--a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fchown system call, run the following command:
+$ sudo grep "fchown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -13583,16 +13595,23 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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 |
+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_mod
medium |
|
|
@@ -13605,7 +13624,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80701-6: Record Any Attempts to Run setsebool |
+ CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -13622,16 +13641,26 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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
+ | 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 path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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 path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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=access
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -13646,32 +13675,53 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
-$ sudo auditctl -l | grep setsebool
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
+$ sudo grep -r open_by_handle_at /etc/audit/rules.d
-DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);
+$ sudo grep open_by_handle_at /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
+
+DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
+
+1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);
2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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
+ | 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 path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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 path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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=access
medium |
|
|
@@ -13684,7 +13734,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
+ CCE-80729-7: Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -13701,26 +13751,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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=access |
+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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -13735,22 +13775,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r creat /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep creat /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "newgrp" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep newgrp
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -13762,26 +13791,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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=access |
+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
medium |
|
|
@@ -13794,7 +13813,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80722-2: Ensure auditd Collects Information on Exporting to Media (successful) |
+ CCE-80741-2: Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -13811,18 +13830,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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/userhelper -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 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 |
+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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -13837,11 +13854,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-mount system call, run the following command:
-$ sudo grep "mount" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "userhelper" command with the following command:
+
+$ sudo auditctl -l | grep userhelper
+
+-a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -13853,18 +13870,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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/userhelper -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 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 |
+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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -13877,7 +13892,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
+ CCE-80740-4: Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -13894,20 +13909,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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_mod |
+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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -13922,11 +13933,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchmod system call, run the following command:
-$ sudo grep "fchmod" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command:
+
+$ sudo auditctl -l | grep unix_chkpwd
+
+-a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -13938,20 +13949,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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_mod |
+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
medium |
|
|
@@ -13964,7 +13971,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
+ CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -13981,15 +13988,29 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ 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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14004,18 +14025,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes audit_backlog_limit=8192,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
-The command should not return any output. Is it the case that audit backlog limit is not configured? |
+ To determine if the system is configured to audit calls to the
+lremovexattr system call, run the following command:
+$ sudo grep "lremovexattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -14027,16 +14041,30 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
- low |
+ 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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+ medium |
|
|
|
@@ -14048,7 +14076,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
+ CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -14065,16 +14093,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
+ | 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:
--w /etc/sudoers.d/ -p wa -k actions |
+-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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14089,11 +14121,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-
-$ sudo auditctl -l | grep/etc/sudoers.d
-
--w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fchownat system call, run the following command:
+$ sudo grep "fchownat" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -14105,16 +14137,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
+ | 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:
--w /etc/sudoers.d/ -p wa -k actions |
+-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
medium |
|
|
@@ -14127,7 +14163,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
+ CCE-89446-9: Record Any Attempts to Run chacl |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -14144,29 +14180,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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=access
-
+-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 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=access |
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14181,22 +14204,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r ftruncate /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep ftruncate /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep chacl
--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -14208,29 +14220,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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=access
-
+-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 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=access |
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -14243,7 +14242,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
+ CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -14260,20 +14259,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | At a minimum, the audit system should collect file deletion 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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14289,8 +14286,8 @@
If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchmodat system call, run the following command:
-$ sudo grep "fchmodat" /etc/audit/audit.*
+unlink system call, run the following command:
+$ sudo grep "unlink" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14304,20 +14301,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | At a minimum, the audit system should collect file deletion 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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -14330,7 +14325,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
+ CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -14347,20 +14342,29 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured
+ | 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 line to a file with suffix
+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 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
+-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 line to
+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 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 |
+-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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14375,36 +14379,56 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchownat system call, run the following command:
-$ sudo grep "fchownat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
-DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);
+$ sudo grep -r open /etc/audit/rules.d
-2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep open /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
+
+DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
+
+1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);
+
+2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured
+ | 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 line to a file with suffix
+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 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
+-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 line to
+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 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 |
+-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
medium |
|
|
@@ -14417,7 +14441,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
+ CCE-80726-3: Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -14434,24 +14458,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+ | 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 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14466,11 +14482,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-setxattr system call, run the following command:
-$ sudo grep "setxattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chsh" command with the following command:
+
+$ sudo auditctl -l | grep chsh
+
+-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -14482,24 +14498,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+ | 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 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+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
medium |
|
|
@@ -14512,7 +14520,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+ CCE-80739-6: Ensure auditd Collects Information on the Use of Privileged Commands - umount |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -14529,16 +14537,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 the following line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14553,11 +14561,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "umount" command with the following command:
-$ sudo auditctl -l | grep /etc/sudoers
+$ sudo auditctl -l | grep umount
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -14569,16 +14577,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 the following line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
medium |
|
|
@@ -14591,7 +14599,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80713-1: Ensure auditd Collects Information on Kernel Module Loading - init_module |
+ CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -14608,18 +14616,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 auid>=1000 -F auid!=unset -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 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 |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14634,11 +14642,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-init_module system call, run the following command:
-$ sudo grep "init_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
+
+$ sudo auditctl -l | grep /var/log/lastlog
+
+-w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -14650,18 +14658,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 auid>=1000 -F auid!=unset -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 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 |
medium |
|
|
@@ -14674,7 +14682,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
+ CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -14691,20 +14699,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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_mod |
+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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14719,11 +14723,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-chmod system call, run the following command:
-$ sudo grep "chmod" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
+
+$ sudo auditctl -l | grep su
+
+-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -14735,20 +14739,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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_mod |
+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
medium |
|
|
@@ -14761,7 +14761,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
+ CCE-80727-1: Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -14778,18 +14778,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect file deletion 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14804,11 +14802,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-unlinkat system call, run the following command:
-$ sudo grep "unlinkat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "crontab" command with the following command:
+
+$ sudo auditctl -l | grep crontab
+
+-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -14820,18 +14818,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect file deletion 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
@@ -14844,7 +14840,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -14867,14 +14863,14 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14889,11 +14885,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
--w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -14911,14 +14907,14 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -14931,7 +14927,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-88437-9: Record Any Attempts to Run setfacl |
+ CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -14948,16 +14944,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
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 |
+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 rename -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -14972,11 +14970,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfacl" command with the following command:
-
-$ sudo auditctl -l | grep setfacl
-
--a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+rename system call, run the following command:
+$ sudo grep "rename" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -14988,16 +14986,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
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 |
+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 rename -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -15010,7 +15010,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
+ CCE-85944-7: Record Any Attempts to Run ssh-agent |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -15027,23 +15027,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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
-
+-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 line to
+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 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 |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15058,11 +15051,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchown system call, run the following command:
-$ sudo grep "fchown" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command:
+
+$ sudo auditctl -l | grep ssh-agent
+
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -15074,23 +15067,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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
-
+-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 line to
+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 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 |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent
medium |
|
|
@@ -15103,7 +15089,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
+ CCE-80713-1: Ensure auditd Collects Information on Kernel Module Loading - init_module |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -15120,29 +15106,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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:
-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
+-a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -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:
--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 |
+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.
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15157,22 +15132,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r openat /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep openat /etc/audit/audit.rules
-
-The output should be the following:
-
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+init_module system call, run the following command:
+$ sudo grep "init_module" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -15184,29 +15148,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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:
-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
+-a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -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:
--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 |
+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.
medium |
|
|
@@ -15219,7 +15172,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-81043-2: Ensure the audit Subsystem is Installed |
+ CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -15236,7 +15189,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- The audit package should be installed. |
+ 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_mod |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15251,7 +15217,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+ To determine if the system is configured to audit calls to the
+fchmod system call, run the following command:
+$ sudo grep "fchmod" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -15263,7 +15233,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- The audit package should be installed. |
+ 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_mod |
medium |
|
|
@@ -15276,7 +15259,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80725-5: Ensure auditd Collects Information on the Use of Privileged Commands - chage |
+ CCE-82233-8: Include Local Events in Audit Logs |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -15293,16 +15276,9 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 |
+ To configure Audit daemon to include local events in Audit logs, set
+local_events to yes in /etc/audit/auditd.conf.
+This is the default setting. |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15317,11 +15293,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chage" command with the following command:
-
-$ sudo auditctl -l | grep chage
-
--a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out? |
+ To verify that Audit Daemon is configured to include local events, run the
+following command:
+$ sudo grep local_events /etc/audit/auditd.conf
+The output should return the following:
+local_events = yes Is it the case that local_events isn't set to yes? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -15333,16 +15309,9 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 |
+ To configure Audit daemon to include local events in Audit logs, set
+local_events to yes in /etc/audit/auditd.conf.
+This is the default setting. |
medium |
|
|
@@ -15355,7 +15324,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+ CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -15377,19 +15346,15 @@
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15405,8 +15370,8 @@
If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lsetxattr system call, run the following command:
-$ sudo grep "lsetxattr" /etc/audit/audit.*
+lchown system call, run the following command:
+$ sudo grep "lchown" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15425,19 +15390,15 @@
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -15450,7 +15411,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
+ CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -15467,24 +15428,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+ | At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15500,8 +15455,8 @@
If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fsetxattr system call, run the following command:
-$ sudo grep "fsetxattr" /etc/audit/audit.*
+renameat system call, run the following command:
+$ sudo grep "renameat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15515,24 +15470,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+ | At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -15545,7 +15494,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80989-7: Ensure auditd Collects Information on the Use of Privileged Commands - mount |
+ CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -15562,16 +15511,26 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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 |
+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=access
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15586,11 +15545,22 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "mount" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
-$ sudo auditctl -l | grep mount
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r creat /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep creat /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -15602,16 +15572,26 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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 |
+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=access
medium |
|
|
@@ -15624,7 +15604,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
+ CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -15641,29 +15621,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
-
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers.d/ -p wa -k actions
If the auditd daemon is configured to use the auditctl
-utility to read audit rules during daemon startup, add the following lines to
+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 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 |
+-w /etc/sudoers.d/ -p wa -k actions
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15678,22 +15645,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r open /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep open /etc/audit/audit.rules
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep/etc/sudoers.d
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -15705,29 +15661,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
-
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers.d/ -p wa -k actions
If the auditd daemon is configured to use the auditctl
-utility to read audit rules during daemon startup, add the following lines to
+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 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 |
+-w /etc/sudoers.d/ -p wa -k actions
medium |
|
|
@@ -15740,7 +15683,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
+ CCE-80711-5: Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -15757,18 +15700,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
-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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+ 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 auid>=1000 -F auid!=unset -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. |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15784,8 +15727,8 @@
If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-rename system call, run the following command:
-$ sudo grep "rename" /etc/audit/audit.*
+delete_module system call, run the following command:
+$ sudo grep "delete_module" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15799,18 +15742,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
-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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+ 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 auid>=1000 -F auid!=unset -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. |
medium |
|
|
@@ -15823,7 +15766,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80739-6: Ensure auditd Collects Information on the Use of Privileged Commands - umount |
+ CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -15845,11 +15788,11 @@
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
+-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/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15864,11 +15807,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "umount" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
-$ sudo auditctl -l | grep umount
+$ sudo auditctl -l | grep usermod
--a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -15885,11 +15828,11 @@
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
+-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/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -15902,7 +15845,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+ CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -15919,20 +15862,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
-
+ | 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 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 |
+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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -15947,11 +15886,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
-$ sudo auditctl -l | grep -E '(/etc/group)'
+$ sudo auditctl -l | grep sudo
--w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -15963,20 +15902,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
-
+ | 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 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 |
+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
medium |
|
|
@@ -15989,7 +15924,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
+ CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -16006,18 +15941,24 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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, setting ARCH to either b32 or b64 as
-appropriate for your system:
--a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16033,8 +15974,8 @@
If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-rmdir system call, run the following command:
-$ sudo grep "rmdir" /etc/audit/audit.*
+lsetxattr system call, run the following command:
+$ sudo grep "lsetxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16048,18 +15989,24 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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, setting ARCH to either b32 or b64 as
-appropriate for your system:
--a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -16072,7 +16019,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80731-3: Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
+ CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -16089,16 +16036,29 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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 |
+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=access
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16113,11 +16073,22 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "passwd" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
-$ sudo auditctl -l | grep passwd
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r openat /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep openat /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -16129,16 +16100,29 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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 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 |
+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=access
medium |
|
|
@@ -16151,7 +16135,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80700-8: Record Any Attempts to Run semanage |
+ CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -16168,16 +16152,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16192,11 +16178,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
-
-$ sudo auditctl -l | grep semanage
-
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+rmdir system call, run the following command:
+$ sudo grep "rmdir" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -16208,16 +16194,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -16230,7 +16218,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
+ CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -16248,27 +16236,19 @@
4) All kernel module load, unload, and restart actions. |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16284,8 +16264,8 @@
If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-removexattr system call, run the following command:
-$ sudo grep "removexattr" /etc/audit/audit.*
+fchmodat system call, run the following command:
+$ sudo grep "fchmodat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16300,27 +16280,19 @@
4) All kernel module load, unload, and restart actions. |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -16333,7 +16305,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
+ CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -16351,19 +16323,28 @@
4) All kernel module load, unload, and restart actions. |
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
+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
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16379,8 +16360,8 @@
If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-chown system call, run the following command:
-$ sudo grep "chown" /etc/audit/audit.*
+fremovexattr system call, run the following command:
+$ sudo grep "fremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16395,19 +16376,28 @@
4) All kernel module load, unload, and restart actions. |
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
+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
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -16420,7 +16410,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80711-5: Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
+ CCE-80722-2: Ensure auditd Collects Information on Exporting to Media (successful) |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -16437,18 +16427,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 auid>=1000 -F auid!=unset -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. |
+ 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 |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16464,8 +16454,8 @@
If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-delete_module system call, run the following command:
-$ sudo grep "delete_module" /etc/audit/audit.*
+mount system call, run the following command:
+$ sudo grep "mount" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16479,18 +16469,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 auid>=1000 -F auid!=unset -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. |
+ 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 |
medium |
|
|
@@ -16503,7 +16493,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-82280-9: Record Any Attempts to Run setfiles |
+ CCE-80733-9: Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -16520,16 +16510,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect any execution attempt
-of the setfiles 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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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/postqueue -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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16544,11 +16534,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postqueue" command with the following command:
-$ sudo auditctl -l | grep setfiles
+$ sudo auditctl -l | grep postqueue
--a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -16560,16 +16550,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect any execution attempt
-of the setfiles 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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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/postqueue -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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -16582,7 +16572,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
+ CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -16599,29 +16589,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+ 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16637,8 +16616,8 @@
If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lremovexattr system call, run the following command:
-$ sudo grep "lremovexattr" /etc/audit/audit.*
+finit_module system call, run the following command:
+$ sudo grep "finit_module" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16652,29 +16631,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+ 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
medium |
|
|
@@ -16687,7 +16655,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
+ CCE-88437-9: Record Any Attempts to Run setfacl |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -16704,20 +16672,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
-
+ | 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, in order to capture events that modify
-account changes:
-
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification |
+/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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16732,13 +16696,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfacl" command with the following command:
--w /etc/gshadow -p wa -k identity
+$ sudo auditctl -l | grep setfacl
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -16750,20 +16712,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
-
+ | 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, in order to capture events that modify
-account changes:
-
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification |
+/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
medium |
|
|
@@ -16776,7 +16734,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
+ CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -16793,29 +16751,15 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16830,46 +16774,39 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fremovexattr system call, run the following command:
-$ sudo grep "fremovexattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
-
-DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
-
-1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);
-
-2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;
-
-3) All account creations, modifications, disabling, and terminations; and
+ | Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes audit_backlog_limit=8192,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
+The command should not return any output. Is it the case that audit backlog limit is not configured? |
+ Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
+
+DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
+
+1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);
+
+2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;
+
+3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
- medium |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ low |
|
|
|
@@ -16881,7 +16818,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
+ CCE-82280-9: Record Any Attempts to Run setfiles |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -16898,18 +16835,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setfiles 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/sbin/setfiles -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 in order to watch for unattempted manual
-edits of files involved in storing logon events:
--w /var/log/lastlog -p wa -k logins |
+/etc/audit/audit.rules file:
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16924,11 +16859,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
-$ sudo auditctl -l | grep /var/log/lastlog
+$ sudo auditctl -l | grep setfiles
--w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -16940,18 +16875,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setfiles 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/sbin/setfiles -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 in order to watch for unattempted manual
-edits of files involved in storing logon events:
--w /var/log/lastlog -p wa -k logins |
+/etc/audit/audit.rules file:
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -16964,7 +16897,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-82233-8: Include Local Events in Audit Logs |
+ CCE-80825-3: Enable Auditing for Processes Which Start Prior to the Audit Daemon |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -16981,9 +16914,15 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- To configure Audit daemon to include local events in Audit logs, set
-local_events to yes in /etc/audit/auditd.conf.
-This is the default setting. |
+ To ensure all processes can be audited, even those which start
+prior to the audit daemon, add the argument audit=1 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit=1 is added as a kernel command line
+argument to newly installed kernels, add audit=1 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit=1 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -16998,11 +16937,18 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To verify that Audit Daemon is configured to include local events, run the
-following command:
-$ sudo grep local_events /etc/audit/auditd.conf
-The output should return the following:
-local_events = yes Is it the case that local_events isn't set to yes? |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes audit=1,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit=1.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*audit=1.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'audit=1'
+The command should not return any output. Is it the case that auditing is not enabled at boot time? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -17014,10 +16960,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- To configure Audit daemon to include local events in Audit logs, set
-local_events to yes in /etc/audit/auditd.conf.
-This is the default setting. |
- medium |
+ To ensure all processes can be audited, even those which start
+prior to the audit daemon, add the argument audit=1 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit=1 is added as a kernel command line
+argument to newly installed kernels, add audit=1 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit=1 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
+ low |
|
|
|
@@ -17029,7 +16981,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80872-5: Enable auditd Service |
+ CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -17046,12 +16998,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 |
+ 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_mod |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -17066,12 +17026,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-auditd service:
-$ sudo systemctl is-active auditd
-If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
+ To determine if the system is configured to audit calls to the
+chmod system call, run the following command:
+$ sudo grep "chmod" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -17083,12 +17042,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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 |
+ 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_mod |
medium |
|
|
@@ -17101,7 +17068,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80698-4: Record Any Attempts to Run chcon |
+ CCE-89480-8: Ensure auditd Collects Information on the Use of Privileged Commands - unix_update |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -17118,16 +17085,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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_update -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 |
+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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -17142,11 +17109,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_update" command with the following command:
-$ sudo auditctl -l | grep chcon
+$ sudo auditctl -l | grep unix_update
--a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -17158,16 +17125,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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
+ | 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_update -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 |
+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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -17180,7 +17147,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-82168-6: Log USBGuard daemon audit events using Linux Audit |
+ CCE-80730-5: Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -17197,10 +17164,18 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- To configure USBGuard daemon to log via Linux Audit
-(as opposed directly to a file),
-AuditBackend option in /etc/usbguard/usbguard-daemon.conf
-needs to be set to LinuxAudit. |
+ 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/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=/usr/sbin/pam_timestamp_check
+-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -17215,11 +17190,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To verify that Linux Audit logging is enabled for the USBGuard daemon,
-run the following command:
-$ sudo grep AuditBackend /etc/usbguard/usbguard-daemon.conf
-The output should be
-AuditBackend=LinuxAudit Is it the case that AuditBackend is not set to LinuxAudit? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command:
+
+$ sudo auditctl -l | grep pam_timestamp_check
+
+-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -17231,11 +17206,19 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- To configure USBGuard daemon to log via Linux Audit
-(as opposed directly to a file),
-AuditBackend option in /etc/usbguard/usbguard-daemon.conf
-needs to be set to LinuxAudit. |
- low |
+ 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/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=/usr/sbin/pam_timestamp_check
+-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ medium |
|
|
|
@@ -17247,7 +17230,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-89480-8: Ensure auditd Collects Information on the Use of Privileged Commands - unix_update |
+ CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -17264,16 +17247,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 a line of the following
-form to /etc/audit/audit.rules:
--a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -17288,11 +17275,13 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_update" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-$ sudo auditctl -l | grep unix_update
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
--a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -17304,16 +17293,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 a line of the following
-form to /etc/audit/audit.rules:
--a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
medium |
|
|
@@ -17326,7 +17319,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80825-3: Enable Auditing for Processes Which Start Prior to the Audit Daemon |
+ CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -17343,15 +17336,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- To ensure all processes can be audited, even those which start
-prior to the audit daemon, add the argument audit=1 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit=1 is added as a kernel command line
-argument to newly installed kernels, add audit=1 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit=1 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
+ 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 |
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -17366,18 +17364,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes audit=1,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit=1.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*audit=1.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'audit=1'
-The command should not return any output. Is it the case that auditing is not enabled at boot time? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+
+-w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -17389,16 +17380,21 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- To ensure all processes can be audited, even those which start
-prior to the audit daemon, add the argument audit=1 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit=1 is added as a kernel command line
-argument to newly installed kernels, add audit=1 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit=1 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
- low |
+ 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 |
+ medium |
|
|
|
@@ -17410,7 +17406,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80732-1: Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
+ CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -17427,16 +17423,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 a line of the following
-form to /etc/audit/audit.rules:
--a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -17451,11 +17451,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postdrop" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
-$ sudo auditctl -l | grep postdrop
+$ sudo auditctl -l | grep -E '(/etc/group)'
--a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -17467,16 +17467,20 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- 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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 a line of the following
-form to /etc/audit/audit.rules:
--a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
medium |
|
|
@@ -17489,7 +17493,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components. |
- CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
+ CCE-80698-4: Record Any Attempts to Run chcon |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -17506,18 +17510,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components.
@@ -17532,11 +17534,11 @@
4) All kernel module load, unload, and restart actions.
If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-renameat system call, run the following command:
-$ sudo grep "renameat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
+
+$ sudo auditctl -l | grep chcon
+
+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components.
DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following:
@@ -17548,18 +17550,16 @@
3) All account creations, modifications, disabling, and terminations; and
4) All kernel module load, unload, and restart actions. |
- At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
@@ -17640,76 +17640,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
+ CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | 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 lines to
+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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r truncate /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep truncate /etc/audit/audit.rules
-
-The output should be the following:
-
--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+chown system call, run the following command:
+$ sudo grep "chown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
- 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
-
+ | 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 lines to
+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 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 |
+-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
medium |
|
|
@@ -17722,70 +17693,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
+ CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect unauthorized file
-accesses for all users and root. If the auditd daemon is configured
+ | 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 lines to a file with suffix
+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 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
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 lines to
+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 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=access |
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r open_by_handle_at /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep open_by_handle_at /etc/audit/audit.rules
-
-The output should be the following:
-
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fsetxattr system call, run the following command:
+$ sudo grep "fsetxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
- At a minimum, the audit system should collect unauthorized file
-accesses for all users and root. If the auditd daemon is configured
+ | 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 lines to a file with suffix
+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 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
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 lines to
+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 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=access |
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -17798,7 +17754,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
+ CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -17808,20 +17764,24 @@
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
+-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lchown system call, run the following command:
-$ sudo grep "lchown" /etc/audit/audit.*
+setxattr system call, run the following command:
+$ sudo grep "setxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
@@ -17830,15 +17790,19 @@
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
+-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -17851,7 +17815,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
+ CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -17861,60 +17825,66 @@
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
+-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 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
+-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 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
+-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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r creat /etc/audit/rules.d
+$ sudo grep -r truncate /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep creat /etc/audit/audit.rules
+$ sudo grep truncate /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
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
+-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 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
+-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 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
+-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 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 |
+-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
medium |
|
|
@@ -17927,47 +17897,63 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
+ CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchmod system call, run the following command:
-$ sudo grep "fchmod" /etc/audit/audit.*
+removexattr system call, run the following command:
+$ sudo grep "removexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
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
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -18062,47 +18048,53 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
+ CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
+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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchmodat system call, run the following command:
-$ sudo grep "fchmodat" /etc/audit/audit.*
+fchown system call, run the following command:
+$ sudo grep "fchown" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
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
+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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -18115,47 +18107,141 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
+ CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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=access |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
+
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
+
+$ sudo grep -r open_by_handle_at /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep open_by_handle_at /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
+ 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=access |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000064-GPOS-00033 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
+
+ CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured
+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
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchownat system call, run the following command:
-$ sudo grep "fchownat" /etc/audit/audit.*
+lremovexattr system call, run the following command:
+$ sudo grep "lremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured
+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
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -18168,7 +18254,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
+ CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -18178,24 +18264,20 @@
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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_mod
+-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 setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+-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 setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_mod
+-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 setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-setxattr system call, run the following command:
-$ sudo grep "setxattr" /etc/audit/audit.*
+fchownat system call, run the following command:
+$ sudo grep "fchownat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
@@ -18204,19 +18286,15 @@
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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_mod
+-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 setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+-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 setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_mod
+-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 setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -18229,30 +18307,112 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
+ CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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=access |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
+
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
+
+$ sudo grep -r open /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep open /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
+ 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=access |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000064-GPOS-00033 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
+
+ CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 chmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 chmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 chmod -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-chmod system call, run the following command:
-$ sudo grep "chmod" /etc/audit/audit.*
+fchmod system call, run the following command:
+$ sudo grep "fchmod" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
@@ -18261,15 +18421,15 @@
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
+-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 chmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 chmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 chmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -18282,7 +18442,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
+ CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -18292,23 +18452,20 @@
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
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchown system call, run the following command:
-$ sudo grep "fchown" /etc/audit/audit.*
+lchown system call, run the following command:
+$ sudo grep "lchown" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
@@ -18317,18 +18474,15 @@
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
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -18341,7 +18495,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
+ CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -18351,66 +18505,60 @@
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r openat /etc/audit/rules.d
+$ sudo grep -r creat /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep openat /etc/audit/audit.rules
+$ sudo grep creat /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
medium |
|
|
@@ -18484,68 +18632,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fsetxattr system call, run the following command:
-$ sudo grep "fsetxattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
- 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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000064-GPOS-00033 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
-
- CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
+ CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -18555,135 +18642,66 @@
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
+-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 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
+-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 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
+-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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r open /etc/audit/rules.d
+$ sudo grep -r openat /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep open /etc/audit/audit.rules
+$ sudo grep openat /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
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
+-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 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
+-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 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
+-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 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000064-GPOS-00033 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
-
- CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-removexattr system call, run the following command:
-$ sudo grep "removexattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
- 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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-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
medium |
|
|
@@ -18696,7 +18714,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
+ CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -18706,20 +18724,20 @@
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
+-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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-chown system call, run the following command:
-$ sudo grep "chown" /etc/audit/audit.*
+fchmodat system call, run the following command:
+$ sudo grep "fchmodat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
@@ -18728,15 +18746,15 @@
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
+-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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -18749,7 +18767,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
+ CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -18761,27 +18779,27 @@
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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lremovexattr system call, run the following command:
-$ sudo grep "lremovexattr" /etc/audit/audit.*
+fremovexattr system call, run the following command:
+$ sudo grep "fremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
@@ -18792,22 +18810,22 @@
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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -18820,65 +18838,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. |
- CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
+ CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -F key=perm_mod
-
+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 fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
-
+-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 fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -F key=perm_mod
-
+-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 fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fremovexattr system call, run the following command:
-$ sudo grep "fremovexattr" /etc/audit/audit.*
+chmod system call, run the following command:
+$ sudo grep "chmod" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur. |
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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -F key=perm_mod
-
+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 fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
-
+-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 fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -F key=perm_mod
-
+-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 fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -19083,34 +19083,73 @@
TBD - Assigned by DISA after STIG release |
The operating system must enforce password complexity by requiring that at least one upper-case character be used. |
- CCE-85877-9: Ensure PAM password complexity module is enabled in password-auth |
+ CCE-80664-6: Ensure PAM Enforces Password Requirements - Authentication Retry Prompts Permitted Per-Session |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. |
- To enable PAM password complexity in password-auth file:
-Edit the password section in
-/etc/pam.d/password-auth to show
-password requisite pam_pwquality.so. |
+ To configure the number of retry prompts that are permitted per-session:
+
+Edit the /etc/security/pwquality.conf to include
+
+retry=, or a lower value if site
+policy is more restrictive. The DoD requirement is a maximum of 3 prompts
+per session. |
Applicable - Configurable |
Verify the operating system enforces password complexity by requiring that at least one upper-case character be used. If it does not, this is a finding. |
- To check if pam_pwquality.so is enabled in password-auth, run the following command:
-$ grep pam_pwquality /etc/pam.d/password-auth
-The output should be similar to the following:
-password requisite pam_pwquality.so Is it the case that pam_pwquality.so is not enabled in password-auth? |
- Configure the operating system to enforce password complexity by requiring that at least one upper-case character be used. |
- To enable PAM password complexity in password-auth file:
-Edit the password section in
-/etc/pam.d/password-auth to show
-password requisite pam_pwquality.so. |
- medium |
- |
- |
- |
-
+
Verify Red Hat Enterprise Linux 8 is configured to limit the "pwquality" retry option to .
- |
- | CCI-000192 |
+
+Check for the use of the "pwquality" retry option in the pwquality.conf file with the following command:
+$ grep retry /etc/security/pwquality.conf
Is it the case that the value of "retry" is set to "0" or greater than "", or is missing?
+ Configure the operating system to enforce password complexity by requiring that at least one upper-case character be used. |
+ To configure the number of retry prompts that are permitted per-session:
+
+Edit the /etc/security/pwquality.conf to include
+
+retry=, or a lower value if site
+policy is more restrictive. The DoD requirement is a maximum of 3 prompts
+per session. |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000192 |
+ SRG-OS-000069-GPOS-00037 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must enforce password complexity by requiring that at least one upper-case character be used. |
+
+ CCE-85877-9: Ensure PAM password complexity module is enabled in password-auth |
+
+ Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+
+Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. |
+ To enable PAM password complexity in password-auth file:
+Edit the password section in
+/etc/pam.d/password-auth to show
+password requisite pam_pwquality.so. |
+ Applicable - Configurable |
+ Verify the operating system enforces password complexity by requiring that at least one upper-case character be used. If it does not, this is a finding. |
+ To check if pam_pwquality.so is enabled in password-auth, run the following command:
+$ grep pam_pwquality /etc/pam.d/password-auth
+The output should be similar to the following:
+password requisite pam_pwquality.so Is it the case that pam_pwquality.so is not enabled in password-auth? |
+ Configure the operating system to enforce password complexity by requiring that at least one upper-case character be used. |
+ To enable PAM password complexity in password-auth file:
+Edit the password section in
+/etc/pam.d/password-auth to show
+password requisite pam_pwquality.so. |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000192 |
SRG-OS-000069-GPOS-00037 |
TBD - Assigned by DISA after STIG release |
The operating system must enforce password complexity by requiring that at least one upper-case character be used. |
@@ -19146,50 +19185,48 @@
|
+
+
+
+
+
- | CCI-000192 |
- SRG-OS-000069-GPOS-00037 |
+ CCI-000193 |
+ SRG-OS-000070-GPOS-00038 |
TBD - Assigned by DISA after STIG release |
- The operating system must enforce password complexity by requiring that at least one upper-case character be used. |
+ The operating system must enforce password complexity by requiring that at least one lower-case character be used. |
- CCE-80664-6: Ensure PAM Enforces Password Requirements - Authentication Retry Prompts Permitted Per-Session |
+ CCE-80655-4: Ensure PAM Enforces Password Requirements - Minimum Lowercase Characters |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. |
- To configure the number of retry prompts that are permitted per-session:
-
-Edit the /etc/security/pwquality.conf to include
-
-retry=, or a lower value if site
-policy is more restrictive. The DoD requirement is a maximum of 3 prompts
-per session. |
+ The pam_pwquality 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_pwquality will grant +1 additional
+length credit for each lowercase character. Modify the lcredit setting in
+/etc/security/pwquality.conf to require the use of a lowercase character in passwords. |
Applicable - Configurable |
- Verify the operating system enforces password complexity by requiring that at least one upper-case character be used. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 is configured to limit the "pwquality" retry option to .
-
+ | Verify the operating system enforces password complexity by requiring that at least one lower-case character be used. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 enforces password complexity by requiring that at least one lower-case character.
-Check for the use of the "pwquality" retry option in the pwquality.conf file with the following command:
-$ grep retry /etc/security/pwquality.conf Is it the case that the value of "retry" is set to "0" or greater than "", or is missing? |
- Configure the operating system to enforce password complexity by requiring that at least one upper-case character be used. |
- To configure the number of retry prompts that are permitted per-session:
+Check the value for "lcredit" with the following command:
-Edit the /etc/security/pwquality.conf to include
+$ sudo grep lcredit /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf
-retry=, or a lower value if site
-policy is more restrictive. The DoD requirement is a maximum of 3 prompts
-per session. |
+/etc/security/pwquality.conf:lcredit = -1 Is it the case that the value of "lcredit" is a positive number or is commented out?
+ Configure the operating system to enforce password complexity by requiring that at least one lower-case character be used. |
+ The pam_pwquality 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_pwquality will grant +1 additional
+length credit for each lowercase character. Modify the lcredit setting in
+/etc/security/pwquality.conf to require the use of a lowercase character in passwords. |
medium |
|
|
|
-
-
-
-
-
| CCI-000193 |
SRG-OS-000070-GPOS-00038 |
@@ -19222,43 +19259,6 @@
|
-
- | CCI-000193 |
- SRG-OS-000070-GPOS-00038 |
- TBD - Assigned by DISA after STIG release |
- The operating system must enforce password complexity by requiring that at least one lower-case character be used. |
-
- CCE-80655-4: Ensure PAM Enforces Password Requirements - Minimum Lowercase Characters |
-
- Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
-
-Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. |
- The pam_pwquality 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_pwquality will grant +1 additional
-length credit for each lowercase character. Modify the lcredit setting in
-/etc/security/pwquality.conf to require the use of a lowercase character in passwords. |
- Applicable - Configurable |
- Verify the operating system enforces password complexity by requiring that at least one lower-case character be used. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 enforces password complexity by requiring that at least one lower-case character.
-
-Check the value for "lcredit" with the following command:
-
-$ sudo grep lcredit /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf
-
-/etc/security/pwquality.conf:lcredit = -1 Is it the case that the value of "lcredit" is a positive number or is commented out? |
- Configure the operating system to enforce password complexity by requiring that at least one lower-case character be used. |
- The pam_pwquality 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_pwquality will grant +1 additional
-length credit for each lowercase character. Modify the lcredit setting in
-/etc/security/pwquality.conf to require the use of a lowercase character in passwords. |
- medium |
- |
- |
- |
-
-
| CCI-000193 |
SRG-OS-000070-GPOS-00038 |
@@ -19343,43 +19343,6 @@
-
- | CCI-000195 |
- SRG-OS-000072-GPOS-00040 |
- TBD - Assigned by DISA after STIG release |
- The operating system must require the change of at least 50% of the total number of characters when passwords are changed. |
-
- CCE-81034-1: Ensure PAM Enforces Password Requirements - Maximum Consecutive Repeating Characters from Same Character Class |
-
- If the operating system allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks.
-
-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.
-
-If the password length is an odd number then number of changed characters must be rounded up. For example, a password length of 15 characters must require the change of at least 8 characters. |
- The pam_pwquality module's maxclassrepeat parameter controls requirements for
-consecutive repeating characters from the same character class. When set to a positive number, it will reject passwords
-which contain more than that number of consecutive characters from the same character class. Modify the
-maxclassrepeat setting in /etc/security/pwquality.conf to equal
-to prevent a run of ( + 1) or more identical characters. |
- Applicable - Configurable |
- Verify the operating system requires the change of at least eight of the total number of characters when passwords are changed. If it does not, this is a finding. |
- Verify the value of the "maxclassrepeat" option in "/etc/security/pwquality.conf" with the following command:
-
-$ grep maxclassrepeat /etc/security/pwquality.conf
-
-maxclassrepeat = Is it the case that the value of "maxclassrepeat" is set to "0", more than "" or is commented out? |
- Configure the operating system to require the change of at least eight of the total number of characters when passwords are changed. |
- The pam_pwquality module's maxclassrepeat parameter controls requirements for
-consecutive repeating characters from the same character class. When set to a positive number, it will reject passwords
-which contain more than that number of consecutive characters from the same character class. Modify the
-maxclassrepeat setting in /etc/security/pwquality.conf to equal
-to prevent a run of ( + 1) or more identical characters. |
- medium |
- |
- |
- |
-
-
| CCI-000195 |
SRG-OS-000072-GPOS-00040 |
@@ -19515,60 +19478,48 @@
|
-
-
-
-
-
- | CCI-000196 |
- SRG-OS-000073-GPOS-00041 |
+ CCI-000195 |
+ SRG-OS-000072-GPOS-00040 |
TBD - Assigned by DISA after STIG release |
- The operating system must store only encrypted representations of passwords. |
+ The operating system must require the change of at least 50% of the total number of characters when passwords are changed. |
- CCE-83484-6: Verify All Account Password Hashes are Shadowed with SHA512 |
+ CCE-81034-1: Ensure PAM Enforces Password Requirements - Maximum Consecutive Repeating Characters from Same Character Class |
- 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. |
- 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. |
- Applicable - Configurable |
- Verify the operating system stores only encrypted representations of passwords. If it does not, this is a finding. |
- Verify that the interactive user account passwords are using a strong
-password hash with the following command:
+ | If the operating system allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks.
-$ sudo cut -d: -f2 /etc/shadow
+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.
-$6$kcOnRq/5$NUEYPuyL.wghQwWssXRcLRFiiru7f5JPV6GaJhNC2aK5F3PZpE/BCCtwrxRc/AInKMNX3CdMw11m9STiql12f/
+If the password length is an odd number then number of changed characters must be rounded up. For example, a password length of 15 characters must require the change of at least 8 characters. |
+ The pam_pwquality module's maxclassrepeat parameter controls requirements for
+consecutive repeating characters from the same character class. When set to a positive number, it will reject passwords
+which contain more than that number of consecutive characters from the same character class. Modify the
+maxclassrepeat setting in /etc/security/pwquality.conf to equal
+to prevent a run of ( + 1) or more identical characters. |
+ Applicable - Configurable |
+ Verify the operating system requires the change of at least eight of the total number of characters when passwords are changed. If it does not, this is a finding. |
+ Verify the value of the "maxclassrepeat" option in "/etc/security/pwquality.conf" with the following command:
-Password hashes ! or * indicate inactive accounts not
-available for logon and are not evaluated. Is it the case that any interactive user password hash does not begin with "$6"? |
- Configure the operating system to store only encrypted representations of passwords. |
- 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. |
+$ grep maxclassrepeat /etc/security/pwquality.conf
+
+maxclassrepeat =
Is it the case that the value of "maxclassrepeat" is set to "0", more than "" or is commented out?
+ Configure the operating system to require the change of at least eight of the total number of characters when passwords are changed. |
+ The pam_pwquality module's maxclassrepeat parameter controls requirements for
+consecutive repeating characters from the same character class. When set to a positive number, it will reject passwords
+which contain more than that number of consecutive characters from the same character class. Modify the
+maxclassrepeat setting in /etc/security/pwquality.conf to equal
+to prevent a run of ( + 1) or more identical characters. |
medium |
|
|
|
+
+
+
+
+
| CCI-000196 |
SRG-OS-000073-GPOS-00041 |
@@ -19625,29 +19576,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must store only encrypted representations of passwords. |
- CCE-89707-4: Set Password Hashing Rounds in /etc/login.defs |
+ CCE-80893-1: Set PAM''s Password Hashing Algorithm |
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. |
- 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. |
+ The PAM system service can be configured to only store encrypted
+representations of passwords. In "/etc/pam.d/system-auth", 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 sufficient 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. |
Applicable - Configurable |
Verify the operating system stores only encrypted representations of passwords. If it does not, this is a finding. |
- Inspect /etc/login.defs and ensure that if eihter
-SHA_CRYPT_MIN_ROUNDS or SHA_CRYPT_MAX_ROUNDS
-are set, they must have the minimum value of 5000. Is it the case that it does not? |
+ Inspect the password section of /etc/pam.d/system-auth
+and ensure that the pam_unix.so module is configured to use the argument
+sha512:
+
+$ sudo grep "^password.*pam_unix\.so.*sha512" /etc/pam.d/system-auth
+
+password sufficient pam_unix.so sha512 Is it the case that "sha512" is missing, or is commented out? |
Configure the operating system to store only encrypted representations of passwords. |
- 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. |
+ The PAM system service can be configured to only store encrypted
+representations of passwords. In "/etc/pam.d/system-auth", 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 sufficient 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. |
medium |
|
|
@@ -19692,47 +19661,78 @@
TBD - Assigned by DISA after STIG release |
The operating system must store only encrypted representations of passwords. |
- CCE-80893-1: Set PAM''s Password Hashing Algorithm |
+ CCE-89707-4: Set Password Hashing Rounds in /etc/login.defs |
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. |
- The PAM system service can be configured to only store encrypted
-representations of passwords. In "/etc/pam.d/system-auth", 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:
-
+ | 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. |
+ Applicable - Configurable |
+ Verify the operating system stores only encrypted representations of passwords. If it does not, this is a finding. |
+ Inspect /etc/login.defs and ensure that if eihter
+SHA_CRYPT_MIN_ROUNDS or SHA_CRYPT_MAX_ROUNDS
+are set, they must have the minimum value of 5000. Is it the case that it does not? |
+ Configure the operating system to store only encrypted representations of passwords. |
+ 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. |
+ medium |
+ |
+ |
+ |
+
-
password sufficient pam_unix.so sha512 other arguments...
+
+ | CCI-000196 |
+ SRG-OS-000073-GPOS-00041 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must store only encrypted representations of passwords. |
-
-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.
+ CCE-83484-6: Verify All Account Password Hashes are Shadowed with 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. |
+ 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. |
Applicable - Configurable |
Verify the operating system stores only encrypted representations of passwords. If it does not, this is a finding. |
- Inspect the password section of /etc/pam.d/system-auth
-and ensure that the pam_unix.so module is configured to use the argument
-sha512:
-
-$ sudo grep "^password.*pam_unix\.so.*sha512" /etc/pam.d/system-auth
+ | Verify that the interactive user account passwords are using a strong
+password hash with the following command:
-password sufficient pam_unix.so sha512 Is it the case that "sha512" is missing, or is commented out? |
- Configure the operating system to store only encrypted representations of passwords. |
- The PAM system service can be configured to only store encrypted
-representations of passwords. In "/etc/pam.d/system-auth", 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:
-
+$ sudo cut -d: -f2 /etc/shadow
-password sufficient pam_unix.so sha512 other arguments...
+$6$kcOnRq/5$NUEYPuyL.wghQwWssXRcLRFiiru7f5JPV6GaJhNC2aK5F3PZpE/BCCtwrxRc/AInKMNX3CdMw11m9STiql12f/
-
-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. |
+Password hashes ! or * indicate inactive accounts not
+available for logon and are not evaluated. Is it the case that any interactive user password hash does not begin with "$6"? |
+ Configure the operating system to store only encrypted representations of passwords. |
+ 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. |
medium |
|
|
@@ -19919,7 +19919,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must prohibit password reuse for a minimum of five generations. |
- CCE-83480-4: Limit Password Reuse: system-auth |
+ CCE-83478-8: Limit Password Reuse: password-auth |
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements. |
Do not allow users to reuse recent passwords. This can be accomplished by using the
@@ -19940,13 +19940,13 @@
|
Applicable - Configurable |
Verify the operating system prohibits password reuse for a minimum of five generations. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 use the "pam_pwhistory.so" module in the /etc/pam.d/system-auth file
+ | Verify Red Hat Enterprise Linux 8 use the "pam_pwhistory.so" module in the /etc/pam.d/password-auth file
and is configured to prohibit password reuse for a minimum of
generations.
-Verify the "/etc/pam.d/system-auth" file with the following command:
+Verify the "/etc/pam.d/password-auth" file with the following command:
-$ grep pam_pwhistory.so /etc/pam.d/system-auth
+$ grep pam_pwhistory.so /etc/pam.d/password-auth
password pam_pwhistory.so use_authtok remember=
@@ -19956,7 +19956,7 @@
remember =
The pam_pwhistory.so "remember" option must be configured only in one file. Is it the case that the pam_pwhistory.so module is not used, the "remember" module option is not set in
-/etc/pam.d/system-auth or in /etc/security/pwhistory.conf, or is set in both files, or is set
+/etc/pam.d/password-auth or in /etc/security/pwhistory.conf, or is set in both files, or is set
with a value less than ""? |
Configure the operating system to prohibit password reuse for a minimum of five generations. |
Do not allow users to reuse recent passwords. This can be accomplished by using the
@@ -19987,7 +19987,7 @@
| TBD - Assigned by DISA after STIG release |
The operating system must prohibit password reuse for a minimum of five generations. |
- CCE-83478-8: Limit Password Reuse: password-auth |
+ CCE-83480-4: Limit Password Reuse: system-auth |
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements. |
Do not allow users to reuse recent passwords. This can be accomplished by using the
@@ -20008,13 +20008,13 @@
|
Applicable - Configurable |
Verify the operating system prohibits password reuse for a minimum of five generations. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 use the "pam_pwhistory.so" module in the /etc/pam.d/password-auth file
+ | Verify Red Hat Enterprise Linux 8 use the "pam_pwhistory.so" module in the /etc/pam.d/system-auth file
and is configured to prohibit password reuse for a minimum of
generations.
-Verify the "/etc/pam.d/password-auth" file with the following command:
+Verify the "/etc/pam.d/system-auth" file with the following command:
-$ grep pam_pwhistory.so /etc/pam.d/password-auth
+$ grep pam_pwhistory.so /etc/pam.d/system-auth
password pam_pwhistory.so use_authtok remember=
@@ -20024,7 +20024,7 @@
remember =
The pam_pwhistory.so "remember" option must be configured only in one file. Is it the case that the pam_pwhistory.so module is not used, the "remember" module option is not set in
-/etc/pam.d/password-auth or in /etc/security/pwhistory.conf, or is set in both files, or is set
+/etc/pam.d/system-auth or in /etc/security/pwhistory.conf, or is set in both files, or is set
with a value less than ""? |
Configure the operating system to prohibit password reuse for a minimum of five generations. |
Do not allow users to reuse recent passwords. This can be accomplished by using the
@@ -20054,37 +20054,6 @@
- |
- | CCI-000205 |
- SRG-OS-000078-GPOS-00046 |
- TBD - Assigned by DISA after STIG release |
- The operating system must enforce a minimum 15-character password length. |
-
- CCE-80656-2: Ensure PAM Enforces Password Requirements - Minimum Length |
-
- The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
-
-Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password. |
- The pam_pwquality module's minlen parameter controls requirements for
-minimum characters required in a password. Add minlen=
-after pam_pwquality to set minimum password length requirements. |
- Applicable - Configurable |
- Verify the operating system enforces a minimum 15-character password length. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 enforces a minimum -character password length with the following command:
-
-$ grep minlen /etc/security/pwquality.conf
-
-minlen = Is it the case that the command does not return a "minlen" value of "" or greater, does not return a line, or the line is commented out? |
- Configure the operating system to enforce a minimum 15-character password length. |
- The pam_pwquality module's minlen parameter controls requirements for
-minimum characters required in a password. Add minlen=
-after pam_pwquality to set minimum password length requirements. |
- medium |
- |
- |
- |
-
-
| CCI-000205 |
SRG-OS-000078-GPOS-00046 |
@@ -20132,6 +20101,37 @@
|
+
+ | CCI-000205 |
+ SRG-OS-000078-GPOS-00046 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must enforce a minimum 15-character password length. |
+
+ CCE-80656-2: Ensure PAM Enforces Password Requirements - Minimum Length |
+
+ The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
+
+Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password. |
+ The pam_pwquality module's minlen parameter controls requirements for
+minimum characters required in a password. Add minlen=
+after pam_pwquality to set minimum password length requirements. |
+ Applicable - Configurable |
+ Verify the operating system enforces a minimum 15-character password length. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 enforces a minimum -character password length with the following command:
+
+$ grep minlen /etc/security/pwquality.conf
+
+minlen = Is it the case that the command does not return a "minlen" value of "" or greater, does not return a line, or the line is commented out? |
+ Configure the operating system to enforce a minimum 15-character password length. |
+ The pam_pwquality module's minlen parameter controls requirements for
+minimum characters required in a password. Add minlen=
+after pam_pwquality to set minimum password length requirements. |
+ medium |
+ |
+ |
+ |
+
+
@@ -20169,7 +20169,127 @@
TBD - Assigned by DISA after STIG release |
The operating system must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
-
CCE-80829-5: Set the UEFI Boot Loader Password |
+
CCE-83561-1: Set the Boot Loader Admin Username to a Non-Default Value |
+
+
To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.
+
+Access control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system. |
+
The grub2 boot loader should have a superuser account and password
+protection enabled to protect boot-time settings.
+
+To maximize the protection, select a password-protected superuser account with unique name, and modify the
+/etc/grub.d/01_users configuration file to reflect the account name change.
+
+Do not to use common administrator account names like root,
+admin, or administrator for the grub2 superuser account.
+
+Change the superuser to a different username (The default is 'root').
+$ sed -i 's/\(set superusers=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users
+
+Once the superuser account has been added,
+update the
+grub.cfg file by running:
+grubby --update-kernel=ALL --env=/boot/grub2/grubenv |
+
Applicable - Configurable |
+
Verify the operating system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. If it does not, this is a finding. |
+
To verify the boot loader superuser account has been set, run the following
+command:
+sudo grep -A1 "superusers" /boot/grub2/grub.cfg
+The output should show the following:
+set superusers="superusers-account"
+export superusers
+where superusers-account is the actual account name different from common names like root,
+admin, or administrator and different from any other existing user name. Is it the case that superuser account is not set or is set to root, admin, administrator or any other existing user name? |
+
Configure the operating system to enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
+
The grub2 boot loader should have a superuser account and password
+protection enabled to protect boot-time settings.
+
+To maximize the protection, select a password-protected superuser account with unique name, and modify the
+/etc/grub.d/01_users configuration file to reflect the account name change.
+
+Do not to use common administrator account names like root,
+admin, or administrator for the grub2 superuser account.
+
+Change the superuser to a different username (The default is 'root').
+$ sed -i 's/\(set superusers=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users
+
+Once the superuser account has been added,
+update the
+grub.cfg file by running:
+grubby --update-kernel=ALL --env=/boot/grub2/grubenv |
+
high |
+
|
+
|
+
|
+
+
+
+ | CCI-000213 |
+ SRG-OS-000080-GPOS-00048 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
+
+ CCE-83542-1: Set the UEFI Boot Loader Admin Username to a Non-Default Value |
+
+ To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.
+
+Access control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system. |
+ The grub2 boot loader should have a superuser account and password
+protection enabled to protect boot-time settings.
+
+To maximize the protection, select a password-protected superuser account with unique name, and modify the
+/etc/grub.d/01_users configuration file to reflect the account name change.
+
+It is highly suggested not to use common administrator account names like root,
+admin, or administrator for the grub2 superuser account.
+
+Change the superuser to a different username (The default is 'root').
+$ sed -i 's/\(set superusers=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users
+
+Once the superuser account has been added,
+update the
+grub.cfg file by running:
+grubby --update-kernel=ALL --env=/boot/grub2/grubenv |
+ Applicable - Configurable |
+ Verify the operating system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. If it does not, this is a finding. |
+ To verify the boot loader superuser account has been set, run the following
+command:
+sudo grep -A1 "superusers" /boot/efi/EFI/redhat/grub.cfg
+The output should show the following:
+set superusers="superusers-account"
+export superusers
+where superusers-account is the actual account name different from common names like root,
+admin, or administrator and different from any other existing user name. Is it the case that superuser account is not set or is set to an existing name or to a common name? |
+ Configure the operating system to enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
+ The grub2 boot loader should have a superuser account and password
+protection enabled to protect boot-time settings.
+
+To maximize the protection, select a password-protected superuser account with unique name, and modify the
+/etc/grub.d/01_users configuration file to reflect the account name change.
+
+It is highly suggested not to use common administrator account names like root,
+admin, or administrator for the grub2 superuser account.
+
+Change the superuser to a different username (The default is 'root').
+$ sed -i 's/\(set superusers=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users
+
+Once the superuser account has been added,
+update the
+grub.cfg file by running:
+grubby --update-kernel=ALL --env=/boot/grub2/grubenv |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000213 |
+ SRG-OS-000080-GPOS-00048 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
+
+ CCE-80828-7: Set Boot Loader Password in grub2 |
To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.
@@ -20186,13 +20306,15 @@
|
Applicable - Configurable |
Verify the operating system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. If it does not, this is a finding. |
- To verify the boot loader superuser password has been set, run the following command:
-$ sudo grep "^[\s]*GRUB2_PASSWORD=grub\.pbkdf2\.sha512.*$" /boot/efi/EFI/redhat/user.cfg
-The output should be similar to:
-GRUB2_PASSWORD=grub.pbkdf2.sha512.10000.C4E08AC72FBFF7E837FD267BFAD7AEB3D42DDC
-2C99F2A94DD5E2E75C2DC331B719FE55D9411745F82D1B6CFD9E927D61925F9BBDD1CFAA0080E0
-916F7AB46E0D.1302284FCCC52CD73BA3671C6C12C26FF50BA873293B24EE2A96EE3B57963E6D7
-0C83964B473EC8F93B07FE749AA6710269E904A9B08A6BBACB00A2D242AD828 Is it the case that no password is set? |
+ First, check whether the password is defined in either /boot/grub2/user.cfg or
+/boot/grub2/grub.cfg.
+Run the following commands:
+$ sudo grep '^[\s]*GRUB2_PASSWORD=grub\.pbkdf2\.sha512.*$' /boot/grub2/user.cfg
+$ sudo grep '^[\s]*password_pbkdf2[\s]+.*[\s]+grub\.pbkdf2\.sha512.*$' /boot/grub2/grub.cfg
+
+
+Second, check that a superuser is defined in /boot/grub2/grub.cfg.
+$ sudo grep '^[\s]*set[\s]+superusers=("?)[a-zA-Z_]+\1$' /boot/grub2/grub.cfg Is it the case that it does not produce any output? |
Configure the operating system to enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.
@@ -20306,7 +20428,7 @@
| TBD - Assigned by DISA after STIG release |
The operating system must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
- CCE-80828-7: Set Boot Loader Password in grub2 |
+ CCE-80829-5: Set the UEFI Boot Loader Password |
To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.
@@ -20323,15 +20445,13 @@
|
Applicable - Configurable |
Verify the operating system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. If it does not, this is a finding. |
- First, check whether the password is defined in either /boot/grub2/user.cfg or
-/boot/grub2/grub.cfg.
-Run the following commands:
-$ sudo grep '^[\s]*GRUB2_PASSWORD=grub\.pbkdf2\.sha512.*$' /boot/grub2/user.cfg
-$ sudo grep '^[\s]*password_pbkdf2[\s]+.*[\s]+grub\.pbkdf2\.sha512.*$' /boot/grub2/grub.cfg
-
-
-Second, check that a superuser is defined in /boot/grub2/grub.cfg.
-$ sudo grep '^[\s]*set[\s]+superusers=("?)[a-zA-Z_]+\1$' /boot/grub2/grub.cfg Is it the case that it does not produce any output? |
+ To verify the boot loader superuser password has been set, run the following command:
+$ sudo grep "^[\s]*GRUB2_PASSWORD=grub\.pbkdf2\.sha512.*$" /boot/efi/EFI/redhat/user.cfg
+The output should be similar to:
+GRUB2_PASSWORD=grub.pbkdf2.sha512.10000.C4E08AC72FBFF7E837FD267BFAD7AEB3D42DDC
+2C99F2A94DD5E2E75C2DC331B719FE55D9411745F82D1B6CFD9E927D61925F9BBDD1CFAA0080E0
+916F7AB46E0D.1302284FCCC52CD73BA3671C6C12C26FF50BA873293B24EE2A96EE3B57963E6D7
+0C83964B473EC8F93B07FE749AA6710269E904A9B08A6BBACB00A2D242AD828 Is it the case that no password is set? |
Configure the operating system to enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.
@@ -20349,126 +20469,6 @@
| |
-
- | CCI-000213 |
- SRG-OS-000080-GPOS-00048 |
- TBD - Assigned by DISA after STIG release |
- The operating system must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
-
- CCE-83561-1: Set the Boot Loader Admin Username to a Non-Default Value |
-
- To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.
-
-Access control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system. |
- The grub2 boot loader should have a superuser account and password
-protection enabled to protect boot-time settings.
-
-To maximize the protection, select a password-protected superuser account with unique name, and modify the
-/etc/grub.d/01_users configuration file to reflect the account name change.
-
-Do not to use common administrator account names like root,
-admin, or administrator for the grub2 superuser account.
-
-Change the superuser to a different username (The default is 'root').
-$ sed -i 's/\(set superusers=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users
-
-Once the superuser account has been added,
-update the
-grub.cfg file by running:
-grubby --update-kernel=ALL --env=/boot/grub2/grubenv |
- Applicable - Configurable |
- Verify the operating system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. If it does not, this is a finding. |
- To verify the boot loader superuser account has been set, run the following
-command:
-sudo grep -A1 "superusers" /boot/grub2/grub.cfg
-The output should show the following:
-set superusers="superusers-account"
-export superusers
-where superusers-account is the actual account name different from common names like root,
-admin, or administrator and different from any other existing user name. Is it the case that superuser account is not set or is set to root, admin, administrator or any other existing user name? |
- Configure the operating system to enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
- The grub2 boot loader should have a superuser account and password
-protection enabled to protect boot-time settings.
-
-To maximize the protection, select a password-protected superuser account with unique name, and modify the
-/etc/grub.d/01_users configuration file to reflect the account name change.
-
-Do not to use common administrator account names like root,
-admin, or administrator for the grub2 superuser account.
-
-Change the superuser to a different username (The default is 'root').
-$ sed -i 's/\(set superusers=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users
-
-Once the superuser account has been added,
-update the
-grub.cfg file by running:
-grubby --update-kernel=ALL --env=/boot/grub2/grubenv |
- high |
- |
- |
- |
-
-
-
- | CCI-000213 |
- SRG-OS-000080-GPOS-00048 |
- TBD - Assigned by DISA after STIG release |
- The operating system must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
-
- CCE-83542-1: Set the UEFI Boot Loader Admin Username to a Non-Default Value |
-
- To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.
-
-Access control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system. |
- The grub2 boot loader should have a superuser account and password
-protection enabled to protect boot-time settings.
-
-To maximize the protection, select a password-protected superuser account with unique name, and modify the
-/etc/grub.d/01_users configuration file to reflect the account name change.
-
-It is highly suggested not to use common administrator account names like root,
-admin, or administrator for the grub2 superuser account.
-
-Change the superuser to a different username (The default is 'root').
-$ sed -i 's/\(set superusers=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users
-
-Once the superuser account has been added,
-update the
-grub.cfg file by running:
-grubby --update-kernel=ALL --env=/boot/grub2/grubenv |
- Applicable - Configurable |
- Verify the operating system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. If it does not, this is a finding. |
- To verify the boot loader superuser account has been set, run the following
-command:
-sudo grep -A1 "superusers" /boot/efi/EFI/redhat/grub.cfg
-The output should show the following:
-set superusers="superusers-account"
-export superusers
-where superusers-account is the actual account name different from common names like root,
-admin, or administrator and different from any other existing user name. Is it the case that superuser account is not set or is set to an existing name or to a common name? |
- Configure the operating system to enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
- The grub2 boot loader should have a superuser account and password
-protection enabled to protect boot-time settings.
-
-To maximize the protection, select a password-protected superuser account with unique name, and modify the
-/etc/grub.d/01_users configuration file to reflect the account name change.
-
-It is highly suggested not to use common administrator account names like root,
-admin, or administrator for the grub2 superuser account.
-
-Change the superuser to a different username (The default is 'root').
-$ sed -i 's/\(set superusers=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users
-
-Once the superuser account has been added,
-update the
-grub.cfg file by running:
-grubby --update-kernel=ALL --env=/boot/grub2/grubenv |
- medium |
- |
- |
- |
-
-
@@ -20480,25 +20480,29 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
-
CCE-88955-0: Uninstall libreport-plugin-rhtsupport Package |
+
CCE-81039-0: Uninstall Sendmail Package |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
-
The libreport-plugin-rhtsupport package can be removed with the following command:
+ | Sendmail is not the default mail transfer agent and is
+not installed by default.
+The sendmail package can be removed with the following command:
-$ sudo yum erase libreport-plugin-rhtsupport |
+$ sudo yum erase sendmail
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
-
Run the following command to determine if the libreport-plugin-rhtsupport package is installed:
-$ rpm -q libreport-plugin-rhtsupport Is it the case that the package is installed? |
+
Run the following command to determine if the sendmail package is installed:
+$ rpm -q sendmail Is it the case that the package is installed? |
Configure the operating system to disable non-essential capabilities. |
-
The libreport-plugin-rhtsupport package can be removed with the following command:
+ | Sendmail is not the default mail transfer agent and is
+not installed by default.
+The sendmail package can be removed with the following command:
-$ sudo yum erase libreport-plugin-rhtsupport |
-
low |
+$ sudo yum erase sendmail
+
medium |
|
|
|
@@ -20510,25 +20514,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
-
CCE-82904-4: Uninstall tuned Package |
+
CCE-88955-0: Uninstall libreport-plugin-rhtsupport Package |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
-
The tuned package can be removed with the following command:
+ | The libreport-plugin-rhtsupport package can be removed with the following command:
-$ sudo yum erase tuned |
+$ sudo yum erase libreport-plugin-rhtsupport
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
-
Run the following command to determine if the tuned package is installed:
-$ rpm -q tuned Is it the case that the package is installed? |
+
Run the following command to determine if the libreport-plugin-rhtsupport package is installed:
+$ rpm -q libreport-plugin-rhtsupport Is it the case that the package is installed? |
Configure the operating system to disable non-essential capabilities. |
-
The tuned package can be removed with the following command:
+ | The libreport-plugin-rhtsupport package can be removed with the following command:
-$ sudo yum erase tuned |
-
medium |
+$ sudo yum erase libreport-plugin-rhtsupport
+
low |
|
|
|
@@ -20581,24 +20585,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
-
CCE-82907-7: Uninstall abrt-cli Package |
+
CCE-82988-7: Disable chrony daemon from acting as server |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
-
The abrt-cli package can be removed with the following command:
-
-$ sudo yum erase abrt-cli |
+
The port option in /etc/chrony.conf can be set to
+0 to make chrony daemon to never open any listening port
+for server operation and to operate strictly in a client-only mode. |
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
-
Run the following command to determine if the abrt-cli package is installed:
-$ rpm -q abrt-cli Is it the case that the package is installed? |
+
Verify Red Hat Enterprise Linux 8 disables the chrony daemon from acting as a server with the following command:
+$ grep -w port /etc/chrony.conf
+port 0 Is it the case that the "port" option is not set to "0", is commented out, or is missing? |
Configure the operating system to disable non-essential capabilities. |
-
The abrt-cli package can be removed with the following command:
-
-$ sudo yum erase abrt-cli |
+
The port option in /etc/chrony.conf can be set to
+0 to make chrony daemon to never open any listening port
+for server operation and to operate strictly in a client-only mode. |
low |
|
|
@@ -20611,25 +20616,35 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
-
CCE-82182-7: Uninstall telnet-server Package |
+
CCE-80948-3: Uninstall Automatic Bug Reporting Tool (abrt) |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
-
The telnet-server package can be removed with the following command:
+ | The Automatic Bug Reporting Tool (abrt) collects
+and reports crash data when an application crash is detected. Using a variety
+of plugins, abrt can email crash reports to system administrators, log crash
+reports to files, or forward crash reports to a centralized issue tracking
+system such as RHTSupport.
+The abrt package can be removed with the following command:
-$ sudo yum erase telnet-server |
+$ sudo yum erase abrt
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
-
Run the following command to determine if the telnet-server package is installed:
-$ rpm -q telnet-server Is it the case that the package is installed? |
+
Run the following command to determine if the abrt package is installed:
+$ rpm -q abrt Is it the case that the package is installed? |
Configure the operating system to disable non-essential capabilities. |
-
The telnet-server package can be removed with the following command:
+ | The Automatic Bug Reporting Tool (abrt) collects
+and reports crash data when an application crash is detected. Using a variety
+of plugins, abrt can email crash reports to system administrators, log crash
+reports to files, or forward crash reports to a centralized issue tracking
+system such as RHTSupport.
+The abrt package can be removed with the following command:
-$ sudo yum erase telnet-server |
-
high |
+$ sudo yum erase abrt
+
medium |
|
|
|
@@ -20641,24 +20656,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
-
CCE-82926-7: Uninstall abrt-addon-kerneloops Package |
+
CCE-82005-0: Disable IEEE 1394 (FireWire) Support |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
-
The abrt-addon-kerneloops package can be removed with the following command:
-
-$ sudo yum erase abrt-addon-kerneloops |
+
The IEEE 1394 (FireWire) is a serial bus standard for
+high-speed real-time communication.
+
+To configure the system to prevent the firewire-core
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/firewire-core.conf:
+install firewire-core /bin/true
+
+To configure the system to prevent the firewire-core from being used,
+add the following line to file /etc/modprobe.d/firewire-core.conf:
+blacklist firewire-core |
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
-
Run the following command to determine if the abrt-addon-kerneloops package is installed:
-$ rpm -q abrt-addon-kerneloops Is it the case that the package is installed? |
+
+If the system is configured to prevent the loading of the firewire-core kernel module,
+it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
+These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
+
+These lines can also instruct the module loading system to ignore the firewire-core kernel module via blacklist keyword.
+
+Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
+$ grep -r firewire-core /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
Configure the operating system to disable non-essential capabilities. |
-
The abrt-addon-kerneloops package can be removed with the following command:
-
-$ sudo yum erase abrt-addon-kerneloops |
+
The IEEE 1394 (FireWire) is a serial bus standard for
+high-speed real-time communication.
+
+To configure the system to prevent the firewire-core
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/firewire-core.conf:
+install firewire-core /bin/true
+
+To configure the system to prevent the firewire-core from being used,
+add the following line to file /etc/modprobe.d/firewire-core.conf:
+blacklist firewire-core |
low |
|
|
@@ -20695,6 +20731,36 @@
|
+
+ | CCI-000381 |
+ SRG-OS-000095-GPOS-00049 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured to disable non-essential capabilities. |
+
+ CCE-82946-5: Uninstall iprutils Package |
+
+ It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
+
+Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
+
+Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
+ The iprutils package can be removed with the following command:
+
+$ sudo yum erase iprutils |
+ Applicable - Configurable |
+ Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
+ Run the following command to determine if the iprutils package is installed:
+$ rpm -q iprutils Is it the case that the package is installed? |
+ Configure the operating system to disable non-essential capabilities. |
+ The iprutils package can be removed with the following command:
+
+$ sudo yum erase iprutils |
+ medium |
+ |
+ |
+ |
+
+
| CCI-000381 |
SRG-OS-000095-GPOS-00049 |
@@ -20732,25 +20798,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-89201-8: Uninstall libreport-plugin-logger Package |
+ CCE-82904-4: Uninstall tuned Package |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The libreport-plugin-logger package can be removed with the following command:
+ | The tuned package can be removed with the following command:
-$ sudo yum erase libreport-plugin-logger |
+$ sudo yum erase tuned
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
- Run the following command to determine if the libreport-plugin-logger package is installed:
-$ rpm -q libreport-plugin-logger Is it the case that the package is installed? |
+ Run the following command to determine if the tuned package is installed:
+$ rpm -q tuned Is it the case that the package is installed? |
Configure the operating system to disable non-essential capabilities. |
- The libreport-plugin-logger package can be removed with the following command:
+ | The tuned package can be removed with the following command:
-$ sudo yum erase libreport-plugin-logger |
- low |
+$ sudo yum erase tuned
+ medium |
|
|
|
@@ -20762,48 +20828,50 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-82297-3: Disable TIPC Support |
+ CCE-80834-5: Disable SCTP Support |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The Transparent Inter-Process Communication (TIPC) protocol
-is designed to provide communications between nodes in a
-cluster.
+ | The Stream Control Transmission Protocol (SCTP) is a
+transport layer protocol, designed to support the idea of
+message-oriented communication, with several streams of messages
+within one connection.
-To configure the system to prevent the tipc
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/tipc.conf:
-install tipc /bin/true
+To configure the system to prevent the sctp
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/sctp.conf:
+install sctp /bin/true
-To configure the system to prevent the tipc from being used,
-add the following line to file /etc/modprobe.d/tipc.conf:
-blacklist tipc |
+To configure the system to prevent the sctp from being used,
+add the following line to file /etc/modprobe.d/sctp.conf:
+blacklist sctp
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
-If the system is configured to prevent the loading of the tipc kernel module,
+If the system is configured to prevent the loading of the sctp kernel module,
it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
-These lines can also instruct the module loading system to ignore the tipc kernel module via blacklist keyword.
+These lines can also instruct the module loading system to ignore the sctp kernel module via blacklist keyword.
Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
-$ grep -r tipc /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
+$ grep -r sctp /etc/modprobe.conf /etc/modprobe.d
Is it the case that no line is returned?
Configure the operating system to disable non-essential capabilities. |
- The Transparent Inter-Process Communication (TIPC) protocol
-is designed to provide communications between nodes in a
-cluster.
+ | The Stream Control Transmission Protocol (SCTP) is a
+transport layer protocol, designed to support the idea of
+message-oriented communication, with several streams of messages
+within one connection.
-To configure the system to prevent the tipc
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/tipc.conf:
-install tipc /bin/true
+To configure the system to prevent the sctp
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/sctp.conf:
+install sctp /bin/true
-To configure the system to prevent the tipc from being used,
-add the following line to file /etc/modprobe.d/tipc.conf:
-blacklist tipc |
- low |
+To configure the system to prevent the sctp from being used,
+add the following line to file /etc/modprobe.d/sctp.conf:
+blacklist sctp
+ medium |
|
|
|
@@ -20815,108 +20883,48 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-82946-5: Uninstall iprutils Package |
+ CCE-82028-2: Disable ATM Support |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The iprutils package can be removed with the following command:
-
-$ sudo yum erase iprutils |
- Applicable - Configurable |
- Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
- Run the following command to determine if the iprutils package is installed:
-$ rpm -q iprutils Is it the case that the package is installed? |
- Configure the operating system to disable non-essential capabilities. |
- The iprutils package can be removed with the following command:
-
-$ sudo yum erase iprutils |
- medium |
- |
- |
- |
-
-
-
- | CCI-000381 |
- SRG-OS-000095-GPOS-00049 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured to disable non-essential capabilities. |
-
- CCE-82194-2: Enable Kernel Page-Table Isolation (KPTI) |
-
- It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
+ | The Asynchronous Transfer Mode (ATM) is a protocol operating on
+network, data link, and physical layers, based on virtual circuits
+and virtual paths.
-Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
+To configure the system to prevent the atm
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/atm.conf:
+install atm /bin/true
-Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- To enable Kernel page-table isolation,
-add the argument pti=on to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that pti=on is added as a kernel command line
-argument to newly installed kernels, add pti=on to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... pti=on ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="pti=on" |
+To configure the system to prevent the atm from being used,
+add the following line to file /etc/modprobe.d/atm.conf:
+blacklist atm
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes pti=on,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*pti=on.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*pti=on.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'pti=on'
-The command should not return any output. Is it the case that Kernel page-table isolation is not enabled? |
- Configure the operating system to disable non-essential capabilities. |
- To enable Kernel page-table isolation,
-add the argument pti=on to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that pti=on is added as a kernel command line
-argument to newly installed kernels, add pti=on to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... pti=on ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="pti=on" |
- low |
- |
- |
- |
-
-
-
- | CCI-000381 |
- SRG-OS-000095-GPOS-00049 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured to disable non-essential capabilities. |
+
+If the system is configured to prevent the loading of the atm kernel module,
+it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
+These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
- | CCE-82988-7: Disable chrony daemon from acting as server |
+These lines can also instruct the module loading system to ignore the atm kernel module via blacklist keyword.
- It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
+Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
+$ grep -r atm /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
+ Configure the operating system to disable non-essential capabilities. |
+ The Asynchronous Transfer Mode (ATM) is a protocol operating on
+network, data link, and physical layers, based on virtual circuits
+and virtual paths.
-Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
+To configure the system to prevent the atm
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/atm.conf:
+install atm /bin/true
-Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The port option in /etc/chrony.conf can be set to
-0 to make chrony daemon to never open any listening port
-for server operation and to operate strictly in a client-only mode. |
- Applicable - Configurable |
- Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 disables the chrony daemon from acting as a server with the following command:
-$ grep -w port /etc/chrony.conf
-port 0 Is it the case that the "port" option is not set to "0", is commented out, or is missing? |
- Configure the operating system to disable non-essential capabilities. |
- The port option in /etc/chrony.conf can be set to
-0 to make chrony daemon to never open any listening port
-for server operation and to operate strictly in a client-only mode. |
- low |
+To configure the system to prevent the atm from being used,
+add the following line to file /etc/modprobe.d/atm.conf:
+blacklist atm
+ medium |
|
|
|
@@ -20958,49 +20966,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-80834-5: Disable SCTP Support |
+ CCE-82943-2: Uninstall gssproxy Package |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The Stream Control Transmission Protocol (SCTP) is a
-transport layer protocol, designed to support the idea of
-message-oriented communication, with several streams of messages
-within one connection.
-
-To configure the system to prevent the sctp
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/sctp.conf:
-install sctp /bin/true
-
-To configure the system to prevent the sctp from being used,
-add the following line to file /etc/modprobe.d/sctp.conf:
-blacklist sctp |
+ The gssproxy package can be removed with the following command:
+
+$ sudo yum erase gssproxy |
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
-
-If the system is configured to prevent the loading of the sctp kernel module,
-it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
-These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
-
-These lines can also instruct the module loading system to ignore the sctp kernel module via blacklist keyword.
-
-Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
-$ grep -r sctp /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
+ Run the following command to determine if the gssproxy package is installed:
+$ rpm -q gssproxy Is it the case that the package is installed? |
Configure the operating system to disable non-essential capabilities. |
- The Stream Control Transmission Protocol (SCTP) is a
-transport layer protocol, designed to support the idea of
-message-oriented communication, with several streams of messages
-within one connection.
-
-To configure the system to prevent the sctp
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/sctp.conf:
-install sctp /bin/true
-
-To configure the system to prevent the sctp from being used,
-add the following line to file /etc/modprobe.d/sctp.conf:
-blacklist sctp |
+ The gssproxy package can be removed with the following command:
+
+$ sudo yum erase gssproxy |
medium |
|
|
@@ -21013,24 +20996,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-82910-1: Uninstall abrt-plugin-sosreport Package |
+ CCE-89201-8: Uninstall libreport-plugin-logger Package |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The abrt-plugin-sosreport package can be removed with the following command:
+ | The libreport-plugin-logger package can be removed with the following command:
-$ sudo yum erase abrt-plugin-sosreport |
+$ sudo yum erase libreport-plugin-logger
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
- Run the following command to determine if the abrt-plugin-sosreport package is installed:
-$ rpm -q abrt-plugin-sosreport Is it the case that the package is installed? |
+ Run the following command to determine if the libreport-plugin-logger package is installed:
+$ rpm -q libreport-plugin-logger Is it the case that the package is installed? |
Configure the operating system to disable non-essential capabilities. |
- The abrt-plugin-sosreport package can be removed with the following command:
+ | The libreport-plugin-logger package can be removed with the following command:
-$ sudo yum erase abrt-plugin-sosreport |
+$ sudo yum erase libreport-plugin-logger
low |
|
|
@@ -21096,24 +21079,20 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-82184-3: Uninstall rsh-server Package |
+ CCE-82414-4: Uninstall vsftpd Package |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The rsh-server package can be removed with the following command:
-
-$ sudo yum erase rsh-server |
+ The vsftpd package can be removed with the following command: $ sudo yum erase vsftpd |
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
- Run the following command to determine if the rsh-server package is installed:
-$ rpm -q rsh-server Is it the case that the package is installed? |
+ Run the following command to determine if the vsftpd package is installed:
+$ rpm -q vsftpd Is it the case that the package is installed? |
Configure the operating system to disable non-essential capabilities. |
- The rsh-server package can be removed with the following command:
-
-$ sudo yum erase rsh-server |
+ The vsftpd package can be removed with the following command: $ sudo yum erase vsftpd |
high |
|
|
@@ -21126,45 +21105,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-82005-0: Disable IEEE 1394 (FireWire) Support |
+ CCE-82907-7: Uninstall abrt-cli Package |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The IEEE 1394 (FireWire) is a serial bus standard for
-high-speed real-time communication.
-
-To configure the system to prevent the firewire-core
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/firewire-core.conf:
-install firewire-core /bin/true
-
-To configure the system to prevent the firewire-core from being used,
-add the following line to file /etc/modprobe.d/firewire-core.conf:
-blacklist firewire-core |
+ The abrt-cli package can be removed with the following command:
+
+$ sudo yum erase abrt-cli |
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
-
-If the system is configured to prevent the loading of the firewire-core kernel module,
-it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
-These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
-
-These lines can also instruct the module loading system to ignore the firewire-core kernel module via blacklist keyword.
-
-Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
-$ grep -r firewire-core /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
+ Run the following command to determine if the abrt-cli package is installed:
+$ rpm -q abrt-cli Is it the case that the package is installed? |
Configure the operating system to disable non-essential capabilities. |
- The IEEE 1394 (FireWire) is a serial bus standard for
-high-speed real-time communication.
-
-To configure the system to prevent the firewire-core
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/firewire-core.conf:
-install firewire-core /bin/true
-
-To configure the system to prevent the firewire-core from being used,
-add the following line to file /etc/modprobe.d/firewire-core.conf:
-blacklist firewire-core |
+ The abrt-cli package can be removed with the following command:
+
+$ sudo yum erase abrt-cli |
low |
|
|
@@ -21177,29 +21135,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-81039-0: Uninstall Sendmail Package |
+ CCE-82910-1: Uninstall abrt-plugin-sosreport Package |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- Sendmail is not the default mail transfer agent and is
-not installed by default.
-The sendmail package can be removed with the following command:
+ | The abrt-plugin-sosreport package can be removed with the following command:
-$ sudo yum erase sendmail |
+$ sudo yum erase abrt-plugin-sosreport
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
- Run the following command to determine if the sendmail package is installed:
-$ rpm -q sendmail Is it the case that the package is installed? |
+ Run the following command to determine if the abrt-plugin-sosreport package is installed:
+$ rpm -q abrt-plugin-sosreport Is it the case that the package is installed? |
Configure the operating system to disable non-essential capabilities. |
- Sendmail is not the default mail transfer agent and is
-not installed by default.
-The sendmail package can be removed with the following command:
+ | The abrt-plugin-sosreport package can be removed with the following command:
-$ sudo yum erase sendmail |
- medium |
+$ sudo yum erase abrt-plugin-sosreport
+ low |
|
|
|
@@ -21211,35 +21165,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-80948-3: Uninstall Automatic Bug Reporting Tool (abrt) |
+ CCE-82182-7: Uninstall telnet-server Package |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The Automatic Bug Reporting Tool (abrt) collects
-and reports crash data when an application crash is detected. Using a variety
-of plugins, abrt can email crash reports to system administrators, log crash
-reports to files, or forward crash reports to a centralized issue tracking
-system such as RHTSupport.
-The abrt package can be removed with the following command:
+ | The telnet-server package can be removed with the following command:
-$ sudo yum erase abrt |
+$ sudo yum erase telnet-server
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
- Run the following command to determine if the abrt package is installed:
-$ rpm -q abrt Is it the case that the package is installed? |
+ Run the following command to determine if the telnet-server package is installed:
+$ rpm -q telnet-server Is it the case that the package is installed? |
Configure the operating system to disable non-essential capabilities. |
- The Automatic Bug Reporting Tool (abrt) collects
-and reports crash data when an application crash is detected. Using a variety
-of plugins, abrt can email crash reports to system administrators, log crash
-reports to files, or forward crash reports to a centralized issue tracking
-system such as RHTSupport.
-The abrt package can be removed with the following command:
+ | The telnet-server package can be removed with the following command:
-$ sudo yum erase abrt |
- medium |
+$ sudo yum erase telnet-server
+ high |
|
|
|
@@ -21251,21 +21195,56 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-82414-4: Uninstall vsftpd Package |
+ CCE-81031-7: Disable Mounting of cramfs |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The vsftpd package can be removed with the following command: $ sudo yum erase vsftpd |
+
+To configure the system to prevent the cramfs
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/cramfs.conf:
+install cramfs /bin/true
+
+To configure the system to prevent the cramfs from being used,
+add the following line to file /etc/modprobe.d/cramfs.conf:
+blacklist cramfs
+
+This effectively prevents usage of this uncommon filesystem.
+
+The cramfs filesystem type is a compressed read-only
+Linux filesystem embedded in small footprint systems. A
+cramfs image can be used without having to first
+decompress the image. |
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
- Run the following command to determine if the vsftpd package is installed:
-$ rpm -q vsftpd Is it the case that the package is installed? |
+
+If the system is configured to prevent the loading of the cramfs kernel module,
+it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
+These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
+
+These lines can also instruct the module loading system to ignore the cramfs kernel module via blacklist keyword.
+
+Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
+$ grep -r cramfs /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
Configure the operating system to disable non-essential capabilities. |
- The vsftpd package can be removed with the following command: $ sudo yum erase vsftpd |
- high |
+
+To configure the system to prevent the cramfs
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/cramfs.conf:
+install cramfs /bin/true
+
+To configure the system to prevent the cramfs from being used,
+add the following line to file /etc/modprobe.d/cramfs.conf:
+blacklist cramfs
+
+This effectively prevents usage of this uncommon filesystem.
+
+The cramfs filesystem type is a compressed read-only
+Linux filesystem embedded in small footprint systems. A
+cramfs image can be used without having to first
+decompress the image. |
+ low |
|
|
|
@@ -21277,48 +21256,48 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-82028-2: Disable ATM Support |
+ CCE-82297-3: Disable TIPC Support |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The Asynchronous Transfer Mode (ATM) is a protocol operating on
-network, data link, and physical layers, based on virtual circuits
-and virtual paths.
+ | The Transparent Inter-Process Communication (TIPC) protocol
+is designed to provide communications between nodes in a
+cluster.
-To configure the system to prevent the atm
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/atm.conf:
-install atm /bin/true
+To configure the system to prevent the tipc
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/tipc.conf:
+install tipc /bin/true
-To configure the system to prevent the atm from being used,
-add the following line to file /etc/modprobe.d/atm.conf:
-blacklist atm |
+To configure the system to prevent the tipc from being used,
+add the following line to file /etc/modprobe.d/tipc.conf:
+blacklist tipc
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
-If the system is configured to prevent the loading of the atm kernel module,
+If the system is configured to prevent the loading of the tipc kernel module,
it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
-These lines can also instruct the module loading system to ignore the atm kernel module via blacklist keyword.
+These lines can also instruct the module loading system to ignore the tipc kernel module via blacklist keyword.
Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
-$ grep -r atm /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
+$ grep -r tipc /etc/modprobe.conf /etc/modprobe.d
Is it the case that no line is returned?
Configure the operating system to disable non-essential capabilities. |
- The Asynchronous Transfer Mode (ATM) is a protocol operating on
-network, data link, and physical layers, based on virtual circuits
-and virtual paths.
+ | The Transparent Inter-Process Communication (TIPC) protocol
+is designed to provide communications between nodes in a
+cluster.
-To configure the system to prevent the atm
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/atm.conf:
-install atm /bin/true
+To configure the system to prevent the tipc
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/tipc.conf:
+install tipc /bin/true
-To configure the system to prevent the atm from being used,
-add the following line to file /etc/modprobe.d/atm.conf:
-blacklist atm |
- medium |
+To configure the system to prevent the tipc from being used,
+add the following line to file /etc/modprobe.d/tipc.conf:
+blacklist tipc
+ low |
|
|
|
@@ -21330,25 +21309,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-82943-2: Uninstall gssproxy Package |
+ CCE-82919-2: Uninstall abrt-addon-ccpp Package |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The gssproxy package can be removed with the following command:
+ | The abrt-addon-ccpp package can be removed with the following command:
-$ sudo yum erase gssproxy |
+$ sudo yum erase abrt-addon-ccpp
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
- Run the following command to determine if the gssproxy package is installed:
-$ rpm -q gssproxy Is it the case that the package is installed? |
+ Run the following command to determine if the abrt-addon-ccpp package is installed:
+$ rpm -q abrt-addon-ccpp Is it the case that the package is installed? |
Configure the operating system to disable non-essential capabilities. |
- The gssproxy package can be removed with the following command:
+ | The abrt-addon-ccpp package can be removed with the following command:
-$ sudo yum erase gssproxy |
- medium |
+$ sudo yum erase abrt-addon-ccpp
+ low |
|
|
|
@@ -21360,56 +21339,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-81031-7: Disable Mounting of cramfs |
+ CCE-82184-3: Uninstall rsh-server Package |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
-
-To configure the system to prevent the cramfs
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/cramfs.conf:
-install cramfs /bin/true
-
-To configure the system to prevent the cramfs from being used,
-add the following line to file /etc/modprobe.d/cramfs.conf:
-blacklist cramfs
-
-This effectively prevents usage of this uncommon filesystem.
-
-The cramfs filesystem type is a compressed read-only
-Linux filesystem embedded in small footprint systems. A
-cramfs image can be used without having to first
-decompress the image. |
+ The rsh-server package can be removed with the following command:
+
+$ sudo yum erase rsh-server |
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
-
-If the system is configured to prevent the loading of the cramfs kernel module,
-it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
-These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
-
-These lines can also instruct the module loading system to ignore the cramfs kernel module via blacklist keyword.
-
-Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
-$ grep -r cramfs /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
+ Run the following command to determine if the rsh-server package is installed:
+$ rpm -q rsh-server Is it the case that the package is installed? |
Configure the operating system to disable non-essential capabilities. |
-
-To configure the system to prevent the cramfs
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/cramfs.conf:
-install cramfs /bin/true
-
-To configure the system to prevent the cramfs from being used,
-add the following line to file /etc/modprobe.d/cramfs.conf:
-blacklist cramfs
-
-This effectively prevents usage of this uncommon filesystem.
-
-The cramfs filesystem type is a compressed read-only
-Linux filesystem embedded in small footprint systems. A
-cramfs image can be used without having to first
-decompress the image. |
- low |
+ The rsh-server package can be removed with the following command:
+
+$ sudo yum erase rsh-server |
+ high |
|
|
|
@@ -21421,94 +21369,86 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured to disable non-essential capabilities. |
- CCE-82919-2: Uninstall abrt-addon-ccpp Package |
+ CCE-82194-2: Enable Kernel Page-Table Isolation (KPTI) |
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
- The abrt-addon-ccpp package can be removed with the following command:
-
-$ sudo yum erase abrt-addon-ccpp |
+ To enable Kernel page-table isolation,
+add the argument pti=on to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that pti=on is added as a kernel command line
+argument to newly installed kernels, add pti=on to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... pti=on ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="pti=on" |
Applicable - Configurable |
Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
- Run the following command to determine if the abrt-addon-ccpp package is installed:
-$ rpm -q abrt-addon-ccpp Is it the case that the package is installed? |
- Configure the operating system to disable non-essential capabilities. |
- The abrt-addon-ccpp package can be removed with the following command:
-
-$ sudo yum erase abrt-addon-ccpp |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes pti=on,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*pti=on.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*pti=on.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'pti=on'
+The command should not return any output. Is it the case that Kernel page-table isolation is not enabled? |
+ Configure the operating system to disable non-essential capabilities. |
+ To enable Kernel page-table isolation,
+add the argument pti=on to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that pti=on is added as a kernel command line
+argument to newly installed kernels, add pti=on to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... pti=on ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="pti=on" |
low |
|
|
|
-
-
-
-
-
- | CCI-000382 |
- SRG-OS-000096-GPOS-00050 |
+ CCI-000381 |
+ SRG-OS-000095-GPOS-00049 |
TBD - Assigned by DISA after STIG release |
- The operating system must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. |
+ The operating system must be configured to disable non-essential capabilities. |
- CCE-82998-6: Install firewalld Package |
+ CCE-82926-7: Uninstall abrt-addon-kerneloops Package |
- In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.
+ | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
-Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.
+Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
-To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues. |
- The firewalld package can be installed with the following command:
+Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. |
+ The abrt-addon-kerneloops package can be removed with the following command:
-$ sudo yum install firewalld |
+$ sudo yum erase abrt-addon-kerneloops
Applicable - Configurable |
- Verify the operating system is configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. If it does not, this is a finding. |
- Run the following command to determine if the firewalld package is installed: $ rpm -q firewalld Is it the case that the package is not installed? |
- Configure the operating system to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. |
- The firewalld package can be installed with the following command:
+ | Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding. |
+ Run the following command to determine if the abrt-addon-kerneloops package is installed:
+$ rpm -q abrt-addon-kerneloops Is it the case that the package is installed? |
+ Configure the operating system to disable non-essential capabilities. |
+ The abrt-addon-kerneloops package can be removed with the following command:
-$ sudo yum install firewalld |
- medium |
+$ sudo yum erase abrt-addon-kerneloops
+ low |
|
|
|
-
- | CCI-000382 |
- SRG-OS-000096-GPOS-00050 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. |
- CCE-82840-0: Disable network management of chrony daemon |
- In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.
-Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.
-To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues. |
- The cmdport option in /etc/chrony.conf can be set to
-0 to stop chrony daemon from listening on the UDP port 323
-for management connections made by chronyc. |
- Applicable - Configurable |
- Verify the operating system is configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 disables network management of the chrony daemon with the following command:
-$ grep -w cmdport /etc/chrony.conf
-cmdport 0 Is it the case that the "cmdport" option is not set to "0", is commented out, or is missing? |
- Configure the operating system to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. |
- The cmdport option in /etc/chrony.conf can be set to
-0 to stop chrony daemon from listening on the UDP port 323
-for management connections made by chronyc. |
- low |
- |
- |
- |
-
| CCI-000382 |
@@ -21575,6 +21515,37 @@
|
+
+ | CCI-000382 |
+ SRG-OS-000096-GPOS-00050 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. |
+
+ CCE-82840-0: Disable network management of chrony daemon |
+
+ In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.
+
+Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.
+
+To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues. |
+ The cmdport option in /etc/chrony.conf can be set to
+0 to stop chrony daemon from listening on the UDP port 323
+for management connections made by chronyc. |
+ Applicable - Configurable |
+ Verify the operating system is configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 disables network management of the chrony daemon with the following command:
+$ grep -w cmdport /etc/chrony.conf
+cmdport 0 Is it the case that the "cmdport" option is not set to "0", is commented out, or is missing? |
+ Configure the operating system to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. |
+ The cmdport option in /etc/chrony.conf can be set to
+0 to stop chrony daemon from listening on the UDP port 323
+for management connections made by chronyc. |
+ low |
+ |
+ |
+ |
+
+
| CCI-000382 |
SRG-OS-000096-GPOS-00050 |
@@ -21615,6 +21586,35 @@
|
+
+ | CCI-000382 |
+ SRG-OS-000096-GPOS-00050 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. |
+
+ CCE-82998-6: Install firewalld Package |
+
+ In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.
+
+Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.
+
+To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues. |
+ The firewalld package can be installed with the following command:
+
+$ sudo yum install firewalld |
+ Applicable - Configurable |
+ Verify the operating system is configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. If it does not, this is a finding. |
+ Run the following command to determine if the firewalld package is installed: $ rpm -q firewalld Is it the case that the package is not installed? |
+ Configure the operating system to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. |
+ The firewalld package can be installed with the following command:
+
+$ sudo yum install firewalld |
+ medium |
+ |
+ |
+ |
+
+
@@ -21782,6 +21782,80 @@
+
+ | CCI-000766 |
+ SRG-OS-000106-GPOS-00053 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must use multifactor authentication for network access to non-privileged accounts. |
+
+ CCE-80909-5: Enable Smartcards in SSSD |
+
+ To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system.
+
+Multifactor authentication uses two or more factors to achieve authentication.
+
+Factors include:
+1) Something you know (e.g., password/PIN);
+2) Something you have (e.g., cryptographic identification device, token); and
+3) Something you are (e.g., biometric).
+
+A non-privileged account is any information system account with authorizations of a non-privileged user.
+
+Network access is any access to an application by a user (or process acting on behalf of a user) where said access is obtained through a network connection.
+
+The DoD CAC with DoD-approved PKI is an example of multifactor authentication. |
+ SSSD should be configured to authenticate access to the system using smart cards.
+To enable smart cards in SSSD, set pam_cert_auth to True under the
+[pam] section in /etc/sssd/sssd.conf. For example:
+[pam]
+pam_cert_auth = True
+
+
+Add or update "pam_sss.so" line in auth section of "/etc/pam.d/system-auth" file to include
+"try_cert_auth" or "require_cert_auth" option, like in the following example:
+
+/etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_auth
+
+Also add or update "pam_sss.so" line in auth section of "/etc/pam.d/smartcard-auth" file to
+include the "allow_missing_name" option, like in the following example:
+/etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name |
+ Applicable - Configurable |
+ Verify the operating system uses multifactor authentication for network access to non-privileged accounts. If it does not, this is a finding. |
+ To verify that smart cards are enabled in SSSD, run the following command:
+$ sudo grep pam_cert_auth /etc/sssd/sssd.conf
+If configured properly, output should be
+pam_cert_auth = True
+
+
+To verify that smart cards are enabled in PAM files, run the following command:
+$ sudo grep -e "auth.*pam_sss\.so.*\(allow_missing_name\|try_cert_auth\)" /etc/pam.d/smartcard-auth /etc/pam.d/system-auth
+If configured properly, output should be
+
+/etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name
+/etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_auth
+ Is it the case that smart cards are not enabled in SSSD? |
+ Configure the operating system to use multifactor authentication for network access to non-privileged accounts. |
+ SSSD should be configured to authenticate access to the system using smart cards.
+To enable smart cards in SSSD, set pam_cert_auth to True under the
+[pam] section in /etc/sssd/sssd.conf. For example:
+[pam]
+pam_cert_auth = True
+
+
+Add or update "pam_sss.so" line in auth section of "/etc/pam.d/system-auth" file to include
+"try_cert_auth" or "require_cert_auth" option, like in the following example:
+
+/etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_auth
+
+Also add or update "pam_sss.so" line in auth section of "/etc/pam.d/smartcard-auth" file to
+include the "allow_missing_name" option, like in the following example:
+/etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name |
+ medium |
+ |
+ |
+ |
+
+
| CCI-000766 |
SRG-OS-000106-GPOS-00053 |
@@ -21847,26 +21921,31 @@
|
+
+
+
+
+
- | CCI-000766 |
- SRG-OS-000106-GPOS-00053 |
+ CCI-000767 |
+ SRG-OS-000107-GPOS-00054 |
TBD - Assigned by DISA after STIG release |
- The operating system must use multifactor authentication for network access to non-privileged accounts. |
+ The operating system must use multifactor authentication for local access to privileged accounts. |
CCE-80909-5: Enable Smartcards in SSSD |
- To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system.
+ | To assure accountability and prevent unauthenticated access, privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system.
-Multifactor authentication uses two or more factors to achieve authentication.
+Multifactor authentication is defined as using two or more factors to achieve authentication.
Factors include:
-1) Something you know (e.g., password/PIN);
+1) Something you know (e.g., password/PIN);
2) Something you have (e.g., cryptographic identification device, token); and
3) Something you are (e.g., biometric).
-A non-privileged account is any information system account with authorizations of a non-privileged user.
+A privileged account is defined as an operating system account with authorizations of a privileged user.
-Network access is any access to an application by a user (or process acting on behalf of a user) where said access is obtained through a network connection.
+Local access is defined as access to an organizational information system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network.
The DoD CAC with DoD-approved PKI is an example of multifactor authentication. |
SSSD should be configured to authenticate access to the system using smart cards.
@@ -21885,7 +21964,7 @@
include the "allow_missing_name" option, like in the following example:
/etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name |
Applicable - Configurable |
- Verify the operating system uses multifactor authentication for network access to non-privileged accounts. If it does not, this is a finding. |
+ Verify the operating system uses multifactor authentication for local access to privileged accounts. If it does not, this is a finding. |
To verify that smart cards are enabled in SSSD, run the following command:
$ sudo grep pam_cert_auth /etc/sssd/sssd.conf
If configured properly, output should be
@@ -21899,7 +21978,7 @@
/etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name
/etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_auth
Is it the case that smart cards are not enabled in SSSD? |
- Configure the operating system to use multifactor authentication for network access to non-privileged accounts. |
+ Configure the operating system to use multifactor authentication for local access to privileged accounts. |
SSSD should be configured to authenticate access to the system using smart cards.
To enable smart cards in SSSD, set pam_cert_auth to True under the
[pam] section in /etc/sssd/sssd.conf. For example:
@@ -21927,23 +22006,23 @@
|
- | CCI-000767 |
- SRG-OS-000107-GPOS-00054 |
+ CCI-000768 |
+ SRG-OS-000108-GPOS-00055 |
TBD - Assigned by DISA after STIG release |
- The operating system must use multifactor authentication for local access to privileged accounts. |
+ The operating system must use multifactor authentication for local access to non-privileged accounts. |
CCE-80909-5: Enable Smartcards in SSSD |
- To assure accountability and prevent unauthenticated access, privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system.
+ | To assure accountability, prevent unauthenticated access, and prevent misuse of the system, non-privileged users must utilize multifactor authentication for local access.
Multifactor authentication is defined as using two or more factors to achieve authentication.
Factors include:
1) Something you know (e.g., password/PIN);
-2) Something you have (e.g., cryptographic identification device, token); and
+2) Something you have (e.g., cryptographic identification device or token); and
3) Something you are (e.g., biometric).
-A privileged account is defined as an operating system account with authorizations of a privileged user.
+A non-privileged account is defined as an operating system account with authorizations of a regular or non-privileged user.
Local access is defined as access to an organizational information system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network.
@@ -21964,7 +22043,7 @@
include the "allow_missing_name" option, like in the following example:
/etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name |
Applicable - Configurable |
- Verify the operating system uses multifactor authentication for local access to privileged accounts. If it does not, this is a finding. |
+ Verify the operating system uses multifactor authentication for local access to non-privileged accounts. If it does not, this is a finding. |
To verify that smart cards are enabled in SSSD, run the following command:
$ sudo grep pam_cert_auth /etc/sssd/sssd.conf
If configured properly, output should be
@@ -21978,86 +22057,7 @@
/etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name
/etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_auth
Is it the case that smart cards are not enabled in SSSD? |
- Configure the operating system to use multifactor authentication for local access to privileged accounts. |
- SSSD should be configured to authenticate access to the system using smart cards.
-To enable smart cards in SSSD, set pam_cert_auth to True under the
-[pam] section in /etc/sssd/sssd.conf. For example:
-[pam]
-pam_cert_auth = True
-
-
-Add or update "pam_sss.so" line in auth section of "/etc/pam.d/system-auth" file to include
-"try_cert_auth" or "require_cert_auth" option, like in the following example:
-
-/etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_auth
-
-Also add or update "pam_sss.so" line in auth section of "/etc/pam.d/smartcard-auth" file to
-include the "allow_missing_name" option, like in the following example:
-/etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name |
- medium |
- |
- |
- |
-
-
-
-
-
-
-
-
- | CCI-000768 |
- SRG-OS-000108-GPOS-00055 |
- TBD - Assigned by DISA after STIG release |
- The operating system must use multifactor authentication for local access to non-privileged accounts. |
-
- CCE-80909-5: Enable Smartcards in SSSD |
-
- To assure accountability, prevent unauthenticated access, and prevent misuse of the system, non-privileged users must utilize multifactor authentication for local access.
-
-Multifactor authentication is defined as using two or more factors to achieve authentication.
-
-Factors include:
-1) Something you know (e.g., password/PIN);
-2) Something you have (e.g., cryptographic identification device or token); and
-3) Something you are (e.g., biometric).
-
-A non-privileged account is defined as an operating system account with authorizations of a regular or non-privileged user.
-
-Local access is defined as access to an organizational information system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network.
-
-The DoD CAC with DoD-approved PKI is an example of multifactor authentication. |
- SSSD should be configured to authenticate access to the system using smart cards.
-To enable smart cards in SSSD, set pam_cert_auth to True under the
-[pam] section in /etc/sssd/sssd.conf. For example:
-[pam]
-pam_cert_auth = True
-
-
-Add or update "pam_sss.so" line in auth section of "/etc/pam.d/system-auth" file to include
-"try_cert_auth" or "require_cert_auth" option, like in the following example:
-
-/etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_auth
-
-Also add or update "pam_sss.so" line in auth section of "/etc/pam.d/smartcard-auth" file to
-include the "allow_missing_name" option, like in the following example:
-/etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name |
- Applicable - Configurable |
- Verify the operating system uses multifactor authentication for local access to non-privileged accounts. If it does not, this is a finding. |
- To verify that smart cards are enabled in SSSD, run the following command:
-$ sudo grep pam_cert_auth /etc/sssd/sssd.conf
-If configured properly, output should be
-pam_cert_auth = True
-
-
-To verify that smart cards are enabled in PAM files, run the following command:
-$ sudo grep -e "auth.*pam_sss\.so.*\(allow_missing_name\|try_cert_auth\)" /etc/pam.d/smartcard-auth /etc/pam.d/system-auth
-If configured properly, output should be
-
-/etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name
-/etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_auth
- Is it the case that smart cards are not enabled in SSSD? |
- Configure the operating system to use multifactor authentication for local access to non-privileged accounts. |
+ Configure the operating system to use multifactor authentication for local access to non-privileged accounts. |
SSSD should be configured to authenticate access to the system using smart cards.
To enable smart cards in SSSD, set pam_cert_auth to True under the
[pam] section in /etc/sssd/sssd.conf. For example:
@@ -22193,6 +22193,63 @@
+ |
+ | CCI-000778 |
+ SRG-OS-000114-GPOS-00059 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must uniquely identify peripherals before establishing a connection. |
+
+ CCE-80835-2: Disable Modprobe Loading of USB Storage Driver |
+
+ Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
+
+Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers. |
+ 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 the file /etc/modprobe.d/usb-storage.conf:
+install usb-storage /bin/true
+
+To configure the system to prevent the usb-storage from being used,
+add the following line to file /etc/modprobe.d/usb-storage.conf:
+blacklist usb-storage
+
+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. |
+ Applicable - Configurable |
+ Verify the operating system uniquely identifies peripherals before establishing a connection. If it does not, this is a finding. |
+
+If the system is configured to prevent the loading of the usb-storage kernel module,
+it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
+These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
+
+These lines can also instruct the module loading system to ignore the usb-storage kernel module via blacklist keyword.
+
+Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
+$ grep -r usb-storage /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
+ Configure the operating system to uniquely identify peripherals before establishing a connection. |
+ 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 the file /etc/modprobe.d/usb-storage.conf:
+install usb-storage /bin/true
+
+To configure the system to prevent the usb-storage from being used,
+add the following line to file /etc/modprobe.d/usb-storage.conf:
+blacklist usb-storage
+
+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. |
+ medium |
+ |
+ |
+ |
+
+
| CCI-000778 |
SRG-OS-000114-GPOS-00059 |
@@ -22256,63 +22313,6 @@
|
-
- | CCI-000778 |
- SRG-OS-000114-GPOS-00059 |
- TBD - Assigned by DISA after STIG release |
- The operating system must uniquely identify peripherals before establishing a connection. |
-
- CCE-80835-2: Disable Modprobe Loading of USB Storage Driver |
-
- Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
-
-Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers. |
- 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 the file /etc/modprobe.d/usb-storage.conf:
-install usb-storage /bin/true
-
-To configure the system to prevent the usb-storage from being used,
-add the following line to file /etc/modprobe.d/usb-storage.conf:
-blacklist usb-storage
-
-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. |
- Applicable - Configurable |
- Verify the operating system uniquely identifies peripherals before establishing a connection. If it does not, this is a finding. |
-
-If the system is configured to prevent the loading of the usb-storage kernel module,
-it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
-These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
-
-These lines can also instruct the module loading system to ignore the usb-storage kernel module via blacklist keyword.
-
-Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
-$ grep -r usb-storage /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
- Configure the operating system to uniquely identify peripherals before establishing a connection. |
- 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 the file /etc/modprobe.d/usb-storage.conf:
-install usb-storage /bin/true
-
-To configure the system to prevent the usb-storage from being used,
-add the following line to file /etc/modprobe.d/usb-storage.conf:
-blacklist usb-storage
-
-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. |
- medium |
- |
- |
- |
-
-
@@ -22377,47 +22377,66 @@
TBD - Assigned by DISA after STIG release |
The operating system must use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
-
CCE-83484-6: Verify All Account Password Hashes are Shadowed with SHA512 |
+
CCE-80936-8: Configure Kerberos to use System Crypto Policy |
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.
Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system. |
-
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. |
+
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+Kerberos is supported by crypto policy, but it's configuration may be
+set up to ignore it.
+To check that Crypto Policies settings for Kerberos are configured correctly, examine that there is a symlink at
+/etc/krb5.conf.d/crypto-policies targeting /etc/cypto-policies/back-ends/krb5.config.
+If the symlink exists, Kerberos is configured to use the system-wide crypto policy settings. |
Applicable - Configurable |
Verify the operating system uses mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. If it does not, this is a finding. |
-
Verify that the interactive user account passwords are using a strong
-password hash with the following command:
+ | Check that the symlink exists and target the correct Kerberos crypto policy, with the following command:
+file /etc/krb5.conf.d/crypto-policies
+If command ouput shows the following line, Kerberos is configured to use the system-wide crypto policy.
+/etc/krb5.conf.d/crypto-policies: symbolic link to /etc/crypto-policies/back-ends/krb5.config Is it the case that the symlink does not exist or points to a different target? |
+
Configure the operating system to use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
+
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+Kerberos is supported by crypto policy, but it's configuration may be
+set up to ignore it.
+To check that Crypto Policies settings for Kerberos are configured correctly, examine that there is a symlink at
+/etc/krb5.conf.d/crypto-policies targeting /etc/cypto-policies/back-ends/krb5.config.
+If the symlink exists, Kerberos is configured to use the system-wide crypto policy settings. |
+
high |
+
|
+
|
+
|
+
-
$ sudo cut -d: -f2 /etc/shadow
+
+ | CCI-000803 |
+ SRG-OS-000120-GPOS-00061 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
-$6$kcOnRq/5$NUEYPuyL.wghQwWssXRcLRFiiru7f5JPV6GaJhNC2aK5F3PZpE/BCCtwrxRc/AInKMNX3CdMw11m9STiql12f/
+ CCE-82859-0: Ensure rsyslog-gnutls is installed |
-Password hashes ! or * indicate inactive accounts not
-available for logon and are not evaluated. Is it the case that any interactive user password hash does not begin with "$6"?
+ Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.
+
+Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
+
+FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system. |
+ TLS protocol support for rsyslog is installed.
+
+The rsyslog-gnutls package can be installed with the following command:
+
+$ sudo yum install rsyslog-gnutls |
+ Applicable - Configurable |
+ Verify the operating system uses mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. If it does not, this is a finding. |
+ Run the following command to determine if the rsyslog-gnutls package is installed:
+$ rpm -q rsyslog-gnutls Is it the case that the package is installed? |
Configure the operating system to use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
- 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. |
+ TLS protocol support for rsyslog is installed.
+
+The rsyslog-gnutls package can be installed with the following command:
+
+$ sudo yum install rsyslog-gnutls |
medium |
|
|
@@ -22478,45 +22497,6 @@
|
-
- | CCI-000803 |
- SRG-OS-000120-GPOS-00061 |
- TBD - Assigned by DISA after STIG release |
- The operating system must use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
-
- CCE-89707-4: Set Password Hashing Rounds in /etc/login.defs |
-
- Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.
-
-Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
-
-FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system. |
- 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. |
- Applicable - Configurable |
- Verify the operating system uses mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. If it does not, this is a finding. |
- Inspect /etc/login.defs and ensure that if eihter
-SHA_CRYPT_MIN_ROUNDS or SHA_CRYPT_MAX_ROUNDS
-are set, they must have the minimum value of 5000. Is it the case that it does not? |
- Configure the operating system to use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
- 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. |
- medium |
- |
- |
- |
-
-
| CCI-000803 |
SRG-OS-000120-GPOS-00061 |
@@ -22564,28 +22544,51 @@
TBD - Assigned by DISA after STIG release |
The operating system must use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
- CCE-82859-0: Ensure rsyslog-gnutls is installed |
+ CCE-80893-1: Set PAM''s Password Hashing Algorithm |
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.
Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system. |
- TLS protocol support for rsyslog is installed.
+ | The PAM system service can be configured to only store encrypted
+representations of passwords. In "/etc/pam.d/system-auth", 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:
+
-The rsyslog-gnutls package can be installed with the following command:
-
-$ sudo yum install rsyslog-gnutls |
+password sufficient 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.
Applicable - Configurable |
Verify the operating system uses mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. If it does not, this is a finding. |
- Run the following command to determine if the rsyslog-gnutls package is installed:
-$ rpm -q rsyslog-gnutls Is it the case that the package is installed? |
+ Inspect the password section of /etc/pam.d/system-auth
+and ensure that the pam_unix.so module is configured to use the argument
+sha512:
+
+$ sudo grep "^password.*pam_unix\.so.*sha512" /etc/pam.d/system-auth
+
+password sufficient pam_unix.so sha512 Is it the case that "sha512" is missing, or is commented out? |
Configure the operating system to use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
- TLS protocol support for rsyslog is installed.
+ | The PAM system service can be configured to only store encrypted
+representations of passwords. In "/etc/pam.d/system-auth", 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:
+
-The rsyslog-gnutls package can be installed with the following command:
-
-$ sudo yum install rsyslog-gnutls |
+password sufficient 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.
medium |
|
|
@@ -22598,24 +22601,33 @@
TBD - Assigned by DISA after STIG release |
The operating system must use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
- CCE-82931-7: Uninstall krb5-workstation Package |
+ CCE-89707-4: Set Password Hashing Rounds in /etc/login.defs |
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.
Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system. |
- The krb5-workstation package can be removed with the following command:
-
-$ sudo yum erase krb5-workstation |
+ 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. |
Applicable - Configurable |
Verify the operating system uses mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. If it does not, this is a finding. |
- Run the following command to determine if the krb5-workstation package is installed:
-$ rpm -q krb5-workstation Is it the case that the package is installed? |
+ Inspect /etc/login.defs and ensure that if eihter
+SHA_CRYPT_MIN_ROUNDS or SHA_CRYPT_MAX_ROUNDS
+are set, they must have the minimum value of 5000. Is it the case that it does not? |
Configure the operating system to use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
- The krb5-workstation package can be removed with the following command:
-
-$ sudo yum erase krb5-workstation |
+ 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. |
medium |
|
|
@@ -22628,33 +22640,30 @@
TBD - Assigned by DISA after STIG release |
The operating system must use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
- CCE-80936-8: Configure Kerberos to use System Crypto Policy |
+ CCE-82175-1: Disable Kerberos by removing host keytab |
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.
Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system. |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-Kerberos is supported by crypto policy, but it's configuration may be
-set up to ignore it.
-To check that Crypto Policies settings for Kerberos are configured correctly, examine that there is a symlink at
-/etc/krb5.conf.d/crypto-policies targeting /etc/cypto-policies/back-ends/krb5.config.
-If the symlink exists, Kerberos is configured to use the system-wide crypto policy settings. |
+ Kerberos is not an approved key distribution method for
+Common Criteria. To prevent using Kerberos by system daemons,
+remove the Kerberos keytab files, especially
+/etc/krb5.keytab. |
Applicable - Configurable |
Verify the operating system uses mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. If it does not, this is a finding. |
- Check that the symlink exists and target the correct Kerberos crypto policy, with the following command:
-file /etc/krb5.conf.d/crypto-policies
-If command ouput shows the following line, Kerberos is configured to use the system-wide crypto policy.
-/etc/krb5.conf.d/crypto-policies: symbolic link to /etc/crypto-policies/back-ends/krb5.config Is it the case that the symlink does not exist or points to a different target? |
+ Run the following command to see if there are some keytabs
+that would potentially allow the use of Kerberos by system daemons.
+$ ls -la /etc/*.keytab
+The expected result is
+ls: cannot access '/etc/*.keytab': No such file or directory Is it the case that a keytab file is present on the system? |
Configure the operating system to use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-Kerberos is supported by crypto policy, but it's configuration may be
-set up to ignore it.
-To check that Crypto Policies settings for Kerberos are configured correctly, examine that there is a symlink at
-/etc/krb5.conf.d/crypto-policies targeting /etc/cypto-policies/back-ends/krb5.config.
-If the symlink exists, Kerberos is configured to use the system-wide crypto policy settings. |
- high |
+ Kerberos is not an approved key distribution method for
+Common Criteria. To prevent using Kerberos by system daemons,
+remove the Kerberos keytab files, especially
+/etc/krb5.keytab. |
+ medium |
|
|
|
@@ -22666,51 +22675,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
- CCE-80893-1: Set PAM''s Password Hashing Algorithm |
+ CCE-82931-7: Uninstall krb5-workstation Package |
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.
Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system. |
- The PAM system service can be configured to only store encrypted
-representations of passwords. In "/etc/pam.d/system-auth", 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 sufficient 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. |
+ The krb5-workstation package can be removed with the following command:
+
+$ sudo yum erase krb5-workstation |
Applicable - Configurable |
Verify the operating system uses mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. If it does not, this is a finding. |
- Inspect the password section of /etc/pam.d/system-auth
-and ensure that the pam_unix.so module is configured to use the argument
-sha512:
-
-$ sudo grep "^password.*pam_unix\.so.*sha512" /etc/pam.d/system-auth
-
-password sufficient pam_unix.so sha512 Is it the case that "sha512" is missing, or is commented out? |
+ Run the following command to determine if the krb5-workstation package is installed:
+$ rpm -q krb5-workstation Is it the case that the package is installed? |
Configure the operating system to use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
- The PAM system service can be configured to only store encrypted
-representations of passwords. In "/etc/pam.d/system-auth", 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 sufficient 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. |
+ The krb5-workstation package can be removed with the following command:
+
+$ sudo yum erase krb5-workstation |
medium |
|
|
@@ -22723,29 +22705,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
- CCE-82175-1: Disable Kerberos by removing host keytab |
+ CCE-83484-6: Verify All Account Password Hashes are Shadowed with SHA512 |
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.
Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system. |
- Kerberos is not an approved key distribution method for
-Common Criteria. To prevent using Kerberos by system daemons,
-remove the Kerberos keytab files, especially
-/etc/krb5.keytab. |
+ 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. |
Applicable - Configurable |
Verify the operating system uses mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. If it does not, this is a finding. |
- Run the following command to see if there are some keytabs
-that would potentially allow the use of Kerberos by system daemons.
-$ ls -la /etc/*.keytab
-The expected result is
-ls: cannot access '/etc/*.keytab': No such file or directory Is it the case that a keytab file is present on the system? |
+ Verify 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. Is it the case that any interactive user password hash does not begin with "$6"? |
Configure the operating system to use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
- Kerberos is not an approved key distribution method for
-Common Criteria. To prevent using Kerberos by system daemons,
-remove the Kerberos keytab files, especially
-/etc/krb5.keytab. |
+ 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. |
medium |
|
|
@@ -22797,30 +22797,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must provide an audit reduction capability that supports on-demand reporting requirements. |
- CCE-81043-2: Ensure the audit Subsystem is Installed |
-
- The ability to generate on-demand reports, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents.
-
-Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. The report generation capability provided by the application must support on-demand (i.e., customizable, ad hoc, and as-needed) reports. |
- The audit package should be installed. |
- Applicable - Configurable |
- Verify the operating system provides an audit reduction capability that supports on-demand reporting requirements. If it does not, this is a finding. |
- Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Configure the operating system to provide an audit reduction capability that supports on-demand reporting requirements. |
- The audit package should be installed. |
- medium |
- |
- |
- |
-
-
-
- | CCI-001876 |
- SRG-OS-000122-GPOS-00063 |
- TBD - Assigned by DISA after STIG release |
- The operating system must provide an audit reduction capability that supports on-demand reporting requirements. |
-
- CCE-80872-5: Enable auditd Service |
+ CCE-80872-5: Enable auditd Service |
The ability to generate on-demand reports, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents.
@@ -22852,6 +22829,29 @@
| |
+
+ | CCI-001876 |
+ SRG-OS-000122-GPOS-00063 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must provide an audit reduction capability that supports on-demand reporting requirements. |
+
+ CCE-81043-2: Ensure the audit Subsystem is Installed |
+
+ The ability to generate on-demand reports, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents.
+
+Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. The report generation capability provided by the application must support on-demand (i.e., customizable, ad hoc, and as-needed) reports. |
+ The audit package should be installed. |
+ Applicable - Configurable |
+ Verify the operating system provides an audit reduction capability that supports on-demand reporting requirements. If it does not, this is a finding. |
+ Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+ Configure the operating system to provide an audit reduction capability that supports on-demand reporting requirements. |
+ The audit package should be installed. |
+ medium |
+ |
+ |
+ |
+
+
@@ -22918,36 +22918,68 @@
TBD - Assigned by DISA after STIG release |
The operating system must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
- CCE-85899-3: Configure SSH Server to Use FIPS 140-2 Validated MACs: opensshserver.config |
+ CCE-84255-9: Configure OpenSSL library to use TLS Encryption |
If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the system. The act of managing systems and applications includes the ability to access sensitive application information, such as system configuration details, diagnostic information, user information, and potentially sensitive application data.
Some maintenance and test tools are either standalone devices with their own operating systems or are applications bundled with an operating system.
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric. |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
-set up incorrectly.
+ | Crypto Policies are means of enforcing certain cryptographic settings for
+selected applications including OpenSSL. OpenSSL is by default configured to
+modify its configuration based on currently configured Crypto Policy.
+Editing the Crypto Policy back-end is not recommended.
-To check that Crypto Policies settings are configured correctly, ensure that
-/etc/crypto-policies/back-ends/opensshserver.config contains the following
-text and is not commented out:
--oMACS= |
+Check the crypto-policies(7) man page and choose a policy that configures TLS
+protocol to version 1.2 or higher, for example DEFAULT, FUTURE or FIPS policy.
+Or create and apply a custom policy that restricts minimum TLS version to 1.2.
+
+For example for versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch
+this is expected:
+
+$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
+
+MinProtocol = TLSv1.2
+
+
+Or for version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer this is
+expected:
+
+$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
+
+TLS.MinProtocol = TLSv1.2
+DTLS.MinProtocol = DTLSv1.2
Applicable - Configurable |
Verify the operating system employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To verify if the OpenSSH server uses defined MACs in the Crypto Policy, run:
-$ grep -Po '(-oMACs=\S+)' /etc/crypto-policies/back-ends/opensshserver.config
-and verify that the line matches:
--oMACS= Is it the case that Crypto Policy for OpenSSH Server is not configured correctly? |
+ To verify if the OpenSSL uses defined TLS Crypto Policy, run:
+$ grep -P '^(TLS\.)?MinProtocol' /etc/crypto-policies/back-ends/opensslcnf.config
+and verify that the value is
+TLSv1.2 Is it the case that cryptographic policy for openssl is not configured or is configured incorrectly? |
Configure the operating system to employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
-set up incorrectly.
+ | Crypto Policies are means of enforcing certain cryptographic settings for
+selected applications including OpenSSL. OpenSSL is by default configured to
+modify its configuration based on currently configured Crypto Policy.
+Editing the Crypto Policy back-end is not recommended.
-To check that Crypto Policies settings are configured correctly, ensure that
-/etc/crypto-policies/back-ends/opensshserver.config contains the following
-text and is not commented out:
--oMACS= |
+Check the crypto-policies(7) man page and choose a policy that configures TLS
+protocol to version 1.2 or higher, for example DEFAULT, FUTURE or FIPS policy.
+Or create and apply a custom policy that restricts minimum TLS version to 1.2.
+
+For example for versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch
+this is expected:
+
+$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
+
+MinProtocol = TLSv1.2
+
+
+Or for version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer this is
+expected:
+
+$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
+
+TLS.MinProtocol = TLSv1.2
+DTLS.MinProtocol = DTLSv1.2
medium |
|
|
@@ -23002,37 +23034,37 @@
TBD - Assigned by DISA after STIG release |
The operating system must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
- CCE-84027-2: Set kernel parameter 'crypto.fips_enabled' to 1 |
+ CCE-85870-4: Configure SSH Client to Use FIPS 140-2 Validated MACs: openssh.config |
If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the system. The act of managing systems and applications includes the ability to access sensitive application information, such as system configuration details, diagnostic information, user information, and potentially sensitive application data.
Some maintenance and test tools are either standalone devices with their own operating systems or are applications bundled with an operating system.
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric. |
- System running in FIPS mode is indicated by kernel parameter
-'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
-To enable FIPS mode, run the following command:
-fips-mode-setup --enable
+ | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
+set up incorrectly.
-To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
-parameters during system installation so key generation is done with FIPS-approved algorithms
-and continuous monitoring tests in place. |
+To check that Crypto Policies settings are configured correctly, ensure that
+/etc/crypto-policies/back-ends/openssh.config contains the following
+line and is not commented out:
+MACs
Applicable - Configurable |
Verify the operating system employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To verify that kernel parameter 'crypto.fips_enabled' is set properly, run the following command:
-sysctl crypto.fips_enabled
-The output should contain the following:
-crypto.fips_enabled = 1 Is it the case that crypto.fips_enabled is not 1? |
+ To verify if the OpenSSH client uses defined MACs in the Crypto Policy, run:
+$ grep -i macs /etc/crypto-policies/back-ends/openssh.config
+and verify that the line matches:
+MACs Is it the case that Crypto Policy for OpenSSH client is not configured correctly? |
Configure the operating system to employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
- System running in FIPS mode is indicated by kernel parameter
-'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
-To enable FIPS mode, run the following command:
-fips-mode-setup --enable
+ | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
+set up incorrectly.
-To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
-parameters during system installation so key generation is done with FIPS-approved algorithms
-and continuous monitoring tests in place. |
- high |
+To check that Crypto Policies settings are configured correctly, ensure that
+/etc/crypto-policies/back-ends/openssh.config contains the following
+line and is not commented out:
+MACs
+ medium |
|
|
|
@@ -23044,68 +23076,36 @@
TBD - Assigned by DISA after STIG release |
The operating system must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
- CCE-84255-9: Configure OpenSSL library to use TLS Encryption |
+ CCE-85899-3: Configure SSH Server to Use FIPS 140-2 Validated MACs: opensshserver.config |
If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the system. The act of managing systems and applications includes the ability to access sensitive application information, such as system configuration details, diagnostic information, user information, and potentially sensitive application data.
Some maintenance and test tools are either standalone devices with their own operating systems or are applications bundled with an operating system.
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric. |
- Crypto Policies are means of enforcing certain cryptographic settings for
-selected applications including OpenSSL. OpenSSL is by default configured to
-modify its configuration based on currently configured Crypto Policy.
-Editing the Crypto Policy back-end is not recommended.
-
-Check the crypto-policies(7) man page and choose a policy that configures TLS
-protocol to version 1.2 or higher, for example DEFAULT, FUTURE or FIPS policy.
-Or create and apply a custom policy that restricts minimum TLS version to 1.2.
-
-For example for versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch
-this is expected:
-
-$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
-
-MinProtocol = TLSv1.2
-
-
-Or for version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer this is
-expected:
-
-$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
+ | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
+set up incorrectly.
-TLS.MinProtocol = TLSv1.2
-DTLS.MinProtocol = DTLSv1.2 |
+To check that Crypto Policies settings are configured correctly, ensure that
+/etc/crypto-policies/back-ends/opensshserver.config contains the following
+text and is not commented out:
+-oMACS= |
Applicable - Configurable |
Verify the operating system employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To verify if the OpenSSL uses defined TLS Crypto Policy, run:
-$ grep -P '^(TLS\.)?MinProtocol' /etc/crypto-policies/back-ends/opensslcnf.config
-and verify that the value is
-TLSv1.2 Is it the case that cryptographic policy for openssl is not configured or is configured incorrectly? |
+ To verify if the OpenSSH server uses defined MACs in the Crypto Policy, run:
+$ grep -Po '(-oMACs=\S+)' /etc/crypto-policies/back-ends/opensshserver.config
+and verify that the line matches:
+-oMACS= Is it the case that Crypto Policy for OpenSSH Server is not configured correctly? |
Configure the operating system to employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
- Crypto Policies are means of enforcing certain cryptographic settings for
-selected applications including OpenSSL. OpenSSL is by default configured to
-modify its configuration based on currently configured Crypto Policy.
-Editing the Crypto Policy back-end is not recommended.
-
-Check the crypto-policies(7) man page and choose a policy that configures TLS
-protocol to version 1.2 or higher, for example DEFAULT, FUTURE or FIPS policy.
-Or create and apply a custom policy that restricts minimum TLS version to 1.2.
-
-For example for versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch
-this is expected:
-
-$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
-
-MinProtocol = TLSv1.2
-
-
-Or for version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer this is
-expected:
-
-$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
+ | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
+set up incorrectly.
-TLS.MinProtocol = TLSv1.2
-DTLS.MinProtocol = DTLSv1.2 |
+To check that Crypto Policies settings are configured correctly, ensure that
+/etc/crypto-policies/back-ends/opensshserver.config contains the following
+text and is not commented out:
+-oMACS= |
medium |
|
|
@@ -23118,37 +23118,37 @@
TBD - Assigned by DISA after STIG release |
The operating system must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
- CCE-85897-7: Configure SSH Server to Use FIPS 140-2 Validated Ciphers: opensshserver.config |
+ CCE-84027-2: Set kernel parameter 'crypto.fips_enabled' to 1 |
If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the system. The act of managing systems and applications includes the ability to access sensitive application information, such as system configuration details, diagnostic information, user information, and potentially sensitive application data.
Some maintenance and test tools are either standalone devices with their own operating systems or are applications bundled with an operating system.
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric. |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
-set up incorrectly.
+ | System running in FIPS mode is indicated by kernel parameter
+'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
+To enable FIPS mode, run the following command:
+fips-mode-setup --enable
-To check that Crypto Policies settings for ciphers are configured correctly, ensure that
-/etc/crypto-policies/back-ends/opensshserver.config contains the following
-text and is not commented out:
--oCiphers= |
+To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
+parameters during system installation so key generation is done with FIPS-approved algorithms
+and continuous monitoring tests in place.
Applicable - Configurable |
Verify the operating system employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To verify if the OpenSSH server uses defined ciphers in the Crypto Policy, run:
-$ grep -Po '(-oCiphers=\S+)' /etc/crypto-policies/back-ends/opensshserver.config
-and verify that the line matches:
--oCiphers= Is it the case that Crypto Policy for OpenSSH Server is not configured correctly? |
+ To verify that kernel parameter 'crypto.fips_enabled' is set properly, run the following command:
+sysctl crypto.fips_enabled
+The output should contain the following:
+crypto.fips_enabled = 1 Is it the case that crypto.fips_enabled is not 1? |
Configure the operating system to employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
-set up incorrectly.
+ | System running in FIPS mode is indicated by kernel parameter
+'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
+To enable FIPS mode, run the following command:
+fips-mode-setup --enable
-To check that Crypto Policies settings for ciphers are configured correctly, ensure that
-/etc/crypto-policies/back-ends/opensshserver.config contains the following
-text and is not commented out:
--oCiphers= |
- medium |
+To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
+parameters during system installation so key generation is done with FIPS-approved algorithms
+and continuous monitoring tests in place.
+ high |
|
|
|
@@ -23160,7 +23160,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
- CCE-85870-4: Configure SSH Client to Use FIPS 140-2 Validated MACs: openssh.config |
+ CCE-85897-7: Configure SSH Server to Use FIPS 140-2 Validated Ciphers: opensshserver.config |
If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the system. The act of managing systems and applications includes the ability to access sensitive application information, such as system configuration details, diagnostic information, user information, and potentially sensitive application data.
@@ -23171,25 +23171,25 @@
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
-To check that Crypto Policies settings are configured correctly, ensure that
-/etc/crypto-policies/back-ends/openssh.config contains the following
-line and is not commented out:
-MACs |
+To check that Crypto Policies settings for ciphers are configured correctly, ensure that
+/etc/crypto-policies/back-ends/opensshserver.config contains the following
+text and is not commented out:
+-oCiphers=
Applicable - Configurable |
Verify the operating system employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To verify if the OpenSSH client uses defined MACs in the Crypto Policy, run:
-$ grep -i macs /etc/crypto-policies/back-ends/openssh.config
+ | To verify if the OpenSSH server uses defined ciphers in the Crypto Policy, run:
+$ grep -Po '(-oCiphers=\S+)' /etc/crypto-policies/back-ends/opensshserver.config
and verify that the line matches:
-MACs Is it the case that Crypto Policy for OpenSSH client is not configured correctly? |
+-oCiphers=
Is it the case that Crypto Policy for OpenSSH Server is not configured correctly?
Configure the operating system to employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
-To check that Crypto Policies settings are configured correctly, ensure that
-/etc/crypto-policies/back-ends/openssh.config contains the following
-line and is not commented out:
-MACs |
+To check that Crypto Policies settings for ciphers are configured correctly, ensure that
+/etc/crypto-policies/back-ends/opensshserver.config contains the following
+text and is not commented out:
+-oCiphers=
medium |
|
|
@@ -23291,39 +23291,6 @@
|
-
- | CCI-001082 |
- SRG-OS-000132-GPOS-00067 |
- TBD - Assigned by DISA after STIG release |
- The operating system must separate user functionality (including user interface services) from operating system management functionality. |
-
- CCE-80913-7: Restrict Access to Kernel Message Buffer |
-
- Operating system management functionality includes functions necessary for administration and requires privileged user access. Allowing non-privileged users to access operating system management functionality capabilities increases the risk that non-privileged users may obtain elevated privileges.
-
-Operating system management functionality includes functions necessary to administer console, network components, workstations, or servers and typically requires privileged user access.
-
-The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, different TCP/UDP ports, virtualization techniques, combinations of these methods, or other methods, as appropriate.
-
-An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. This may include isolating the administrative interface on a different security domain and with additional access controls. |
- To set the runtime status of the kernel.dmesg_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.dmesg_restrict=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.dmesg_restrict = 1 |
- Applicable - Configurable |
- Verify the operating system separates user functionality (including user interface services) from operating system management functionality. If it does not, this is a finding. |
- The runtime status of the kernel.dmesg_restrict kernel parameter can be queried
-by running the following command:
-$ sysctl kernel.dmesg_restrict
-1.
- Is it the case that the correct value is not returned? |
- Configure the operating system to separate user functionality (including user interface services) from operating system management functionality. |
- To set the runtime status of the kernel.dmesg_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.dmesg_restrict=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.dmesg_restrict = 1 |
- low |
- |
- |
- |
-
-
| CCI-001082 |
SRG-OS-000132-GPOS-00067 |
@@ -23381,7 +23348,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must separate user functionality (including user interface services) from operating system management functionality. |
- CCE-80953-3: Restrict usage of ptrace to descendant processes |
+ CCE-80913-7: Restrict Access to Kernel Message Buffer |
Operating system management functionality includes functions necessary for administration and requires privileged user access. Allowing non-privileged users to access operating system management functionality capabilities increases the risk that non-privileged users may obtain elevated privileges.
@@ -23390,19 +23357,19 @@
The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, different TCP/UDP ports, virtualization techniques, combinations of these methods, or other methods, as appropriate.
An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. This may include isolating the administrative interface on a different security domain and with additional access controls. |
- To set the runtime status of the kernel.yama.ptrace_scope kernel parameter, run the following command: $ sudo sysctl -w kernel.yama.ptrace_scope=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.yama.ptrace_scope = 1 |
+ To set the runtime status of the kernel.dmesg_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.dmesg_restrict=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.dmesg_restrict = 1 |
Applicable - Configurable |
Verify the operating system separates user functionality (including user interface services) from operating system management functionality. If it does not, this is a finding. |
- The runtime status of the kernel.yama.ptrace_scope kernel parameter can be queried
+ | The runtime status of the kernel.dmesg_restrict kernel parameter can be queried
by running the following command:
-$ sysctl kernel.yama.ptrace_scope
+$ sysctl kernel.dmesg_restrict
1.
Is it the case that the correct value is not returned? |
Configure the operating system to separate user functionality (including user interface services) from operating system management functionality. |
- To set the runtime status of the kernel.yama.ptrace_scope kernel parameter, run the following command: $ sudo sysctl -w kernel.yama.ptrace_scope=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.yama.ptrace_scope = 1 |
- medium |
+ To set the runtime status of the kernel.dmesg_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.dmesg_restrict=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.dmesg_restrict = 1 |
+ low |
|
|
|
@@ -23441,47 +23408,44 @@
|
-
-
-
-
-
- | CCI-001084 |
- SRG-OS-000134-GPOS-00068 |
+ CCI-001082 |
+ SRG-OS-000132-GPOS-00067 |
TBD - Assigned by DISA after STIG release |
- The operating system must isolate security functions from nonsecurity functions. |
-
- CCE-80869-1: Ensure SELinux State is Enforcing |
+ The operating system must separate user functionality (including user interface services) from operating system management functionality. |
- An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions.
+ | CCE-80953-3: Restrict usage of ptrace to descendant processes |
-Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Operating systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code.
+ Operating system management functionality includes functions necessary for administration and requires privileged user access. Allowing non-privileged users to access operating system management functionality capabilities increases the risk that non-privileged users may obtain elevated privileges.
-Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of memory space and libraries. Operating systems restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities. |
- The SELinux state should be set to at
-system boot time. In the file /etc/selinux/config, add or correct the
-following line to configure the system to boot into enforcing mode:
-SELINUX= |
- Applicable - Configurable |
- Verify the operating system isolates security functions from nonsecurity functions. If it does not, this is a finding. |
- Ensure that Red Hat Enterprise Linux 8 verifies correct operation of security functions.
+Operating system management functionality includes functions necessary to administer console, network components, workstations, or servers and typically requires privileged user access.
-Check if "SELinux" is active and in "" mode with the following command:
+The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, different TCP/UDP ports, virtualization techniques, combinations of these methods, or other methods, as appropriate.
-$ sudo getenforce
- Is it the case that SELINUX is not set to enforcing? |
- Configure the operating system to isolate security functions from nonsecurity functions. |
- The SELinux state should be set to at
-system boot time. In the file /etc/selinux/config, add or correct the
-following line to configure the system to boot into enforcing mode:
-SELINUX= |
- high |
+An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. This may include isolating the administrative interface on a different security domain and with additional access controls.
+ To set the runtime status of the kernel.yama.ptrace_scope kernel parameter, run the following command: $ sudo sysctl -w kernel.yama.ptrace_scope=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.yama.ptrace_scope = 1 |
+ Applicable - Configurable |
+ Verify the operating system separates user functionality (including user interface services) from operating system management functionality. If it does not, this is a finding. |
+ The runtime status of the kernel.yama.ptrace_scope kernel parameter can be queried
+by running the following command:
+$ sysctl kernel.yama.ptrace_scope
+1.
+ Is it the case that the correct value is not returned? |
+ Configure the operating system to separate user functionality (including user interface services) from operating system management functionality. |
+ To set the runtime status of the kernel.yama.ptrace_scope kernel parameter, run the following command: $ sudo sysctl -w kernel.yama.ptrace_scope=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.yama.ptrace_scope = 1 |
+ medium |
|
|
|
+
+
+
+
+
| CCI-001084 |
SRG-OS-000134-GPOS-00068 |
@@ -23540,24 +23504,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must isolate security functions from nonsecurity functions. |
- CCE-82976-2: Install policycoreutils Package |
+ CCE-80946-7: Disable vsyscalls |
An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions.
Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Operating systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code.
Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of memory space and libraries. Operating systems restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities. |
- The policycoreutils package can be installed with the following command:
-
-$ sudo yum install policycoreutils |
+ To disable use of virtual syscalls,
+add the argument vsyscall=none to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that vsyscall=none is added as a kernel command line
+argument to newly installed kernels, add vsyscall=none to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... vsyscall=none ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="vsyscall=none" |
Applicable - Configurable |
Verify the operating system isolates security functions from nonsecurity functions. If it does not, this is a finding. |
- Run the following command to determine if the policycoreutils package is installed: $ rpm -q policycoreutils Is it the case that the policycoreutils package is not installed? |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes vsyscall=none,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*vsyscall=none.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*vsyscall=none.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'vsyscall=none'
+The command should not return any output. Is it the case that vsyscalls are enabled? |
Configure the operating system to isolate security functions from nonsecurity functions. |
- The policycoreutils package can be installed with the following command:
-
-$ sudo yum install policycoreutils |
- low |
+ To disable use of virtual syscalls,
+add the argument vsyscall=none to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that vsyscall=none is added as a kernel command line
+argument to newly installed kernels, add vsyscall=none to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... vsyscall=none ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="vsyscall=none" |
+ medium |
|
|
|
@@ -23621,47 +23608,60 @@
TBD - Assigned by DISA after STIG release |
The operating system must isolate security functions from nonsecurity functions. |
- CCE-80946-7: Disable vsyscalls |
+ CCE-80869-1: Ensure SELinux State is Enforcing |
An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions.
Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Operating systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code.
Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of memory space and libraries. Operating systems restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities. |
- To disable use of virtual syscalls,
-add the argument vsyscall=none to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that vsyscall=none is added as a kernel command line
-argument to newly installed kernels, add vsyscall=none to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... vsyscall=none ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="vsyscall=none" |
+ The SELinux state should be set to at
+system boot time. In the file /etc/selinux/config, add or correct the
+following line to configure the system to boot into enforcing mode:
+SELINUX= |
Applicable - Configurable |
Verify the operating system isolates security functions from nonsecurity functions. If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes vsyscall=none,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*vsyscall=none.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*vsyscall=none.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'vsyscall=none'
-The command should not return any output. Is it the case that vsyscalls are enabled? |
+ Ensure that Red Hat Enterprise Linux 8 verifies correct operation of security functions.
+
+Check if "SELinux" is active and in "" mode with the following command:
+
+$ sudo getenforce
+ Is it the case that SELINUX is not set to enforcing? |
Configure the operating system to isolate security functions from nonsecurity functions. |
- To disable use of virtual syscalls,
-add the argument vsyscall=none to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that vsyscall=none is added as a kernel command line
-argument to newly installed kernels, add vsyscall=none to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... vsyscall=none ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="vsyscall=none" |
- medium |
+ The SELinux state should be set to at
+system boot time. In the file /etc/selinux/config, add or correct the
+following line to configure the system to boot into enforcing mode:
+SELINUX= |
+ high |
+ |
+ |
+ |
+
+
+
+ | CCI-001084 |
+ SRG-OS-000134-GPOS-00068 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must isolate security functions from nonsecurity functions. |
+
+ CCE-82976-2: Install policycoreutils Package |
+
+ An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions.
+
+Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Operating systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code.
+
+Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of memory space and libraries. Operating systems restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities. |
+ The policycoreutils package can be installed with the following command:
+
+$ sudo yum install policycoreutils |
+ Applicable - Configurable |
+ Verify the operating system isolates security functions from nonsecurity functions. If it does not, this is a finding. |
+ Run the following command to determine if the policycoreutils package is installed: $ rpm -q policycoreutils Is it the case that the policycoreutils package is not installed? |
+ Configure the operating system to isolate security functions from nonsecurity functions. |
+ The policycoreutils package can be installed with the following command:
+
+$ sudo yum install policycoreutils |
+ low |
|
|
|
@@ -23678,16 +23678,47 @@
TBD - Assigned by DISA after STIG release |
Operating systems must prevent unauthorized and unintended information transfer via shared system resources. |
- CCE-81054-9: Disallow kernel profiling by unprivileged users |
+ CCE-83375-6: Ensure All World-Writable Directories Are Owned by root User |
Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection.
This requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DoD or other government agencies.
There may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components. |
- To set the runtime status of the kernel.perf_event_paranoid kernel parameter, run the following command: $ sudo sysctl -w kernel.perf_event_paranoid=2
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.perf_event_paranoid = 2 |
- Applicable - Configurable |
+ All directories in local partitions which are world-writable should be owned by root.
+If any world-writable directories are not owned by root, this should be investigated.
+Following this, the files should be deleted or assigned to root user. |
+ Applicable - Configurable |
+ Verify operating systems prevents unauthorized and unintended information transfer via shared system resources. If it does not, this is a finding. |
+ The following command will discover and print world-writable directories that
+are not owned by root. Run it once for each local partition PART:
+$ sudo find PART -xdev -type d -perm -0002 -uid +0 -print Is it the case that there are world-writable directories not owned by root? |
+ Configure operating systems to prevent unauthorized and unintended information transfer via shared system resources. |
+ All directories in local partitions which are world-writable should be owned by root.
+If any world-writable directories are not owned by root, this should be investigated.
+Following this, the files should be deleted or assigned to root user. |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-001090 |
+ SRG-OS-000138-GPOS-00069 |
+ TBD - Assigned by DISA after STIG release |
+ Operating systems must prevent unauthorized and unintended information transfer via shared system resources. |
+
+ CCE-81054-9: Disallow kernel profiling by unprivileged users |
+
+ Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection.
+
+This requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DoD or other government agencies.
+
+There may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components. |
+ To set the runtime status of the kernel.perf_event_paranoid kernel parameter, run the following command: $ sudo sysctl -w kernel.perf_event_paranoid=2
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.perf_event_paranoid = 2 |
+ Applicable - Configurable |
Verify operating systems prevents unauthorized and unintended information transfer via shared system resources. If it does not, this is a finding. |
The runtime status of the kernel.perf_event_paranoid kernel parameter can be queried
by running the following command:
@@ -23794,37 +23825,6 @@
| |
-
- | CCI-001090 |
- SRG-OS-000138-GPOS-00069 |
- TBD - Assigned by DISA after STIG release |
- Operating systems must prevent unauthorized and unintended information transfer via shared system resources. |
-
- CCE-83375-6: Ensure All World-Writable Directories Are Owned by root User |
-
- Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection.
-
-This requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DoD or other government agencies.
-
-There may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components. |
- All directories in local partitions which are world-writable should be owned by root.
-If any world-writable directories are not owned by root, this should be investigated.
-Following this, the files should be deleted or assigned to root user. |
- Applicable - Configurable |
- Verify operating systems prevents unauthorized and unintended information transfer via shared system resources. If it does not, this is a finding. |
- The following command will discover and print world-writable directories that
-are not owned by root. Run it once for each local partition PART:
-$ sudo find PART -xdev -type d -perm -0002 -uid +0 -print Is it the case that there are world-writable directories not owned by root? |
- Configure operating systems to prevent unauthorized and unintended information transfer via shared system resources. |
- All directories in local partitions which are world-writable should be owned by root.
-If any world-writable directories are not owned by root, this should be investigated.
-Following this, the files should be deleted or assigned to root user. |
- medium |
- |
- |
- |
-
-
@@ -23854,6 +23854,63 @@
+
+ | CCI-001133 |
+ SRG-OS-000163-GPOS-00072 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must terminate all network connections associated with a communications session at the end of the session, or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity; and for user sessions (non-privileged session), the session must be terminated after 15 minutes of inactivity, except to fulfill documented and validated mission requirements. |
+
+ CCE-80907-9: Set SSH Client Alive Count Max |
+
+ Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element.
+
+Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session. |
+ 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 unresponsive
+and terminated.
+For SSH earlier than v8.2, a ClientAliveCountMax value of 0
+causes a timeout precisely when the ClientAliveInterval is set.
+Starting with v8.2, a value of 0 disables the timeout functionality
+completely. If the option is set to a number greater than 0, then
+the session will be disconnected after
+ClientAliveInterval * ClientAliveCountMax seconds without receiving
+a keep alive message. |
+ Applicable - Configurable |
+ Verify the operating system terminates all network connections associated with a communications session at the end of the session, or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity; and for user sessions (non-privileged session), the session must be terminated after 15 minutes of inactivity, except to fulfill documented and validated mission requirements.
+
+If it does not, this is a finding. |
+ To ensure ClientAliveInterval is set correctly, run the following command:
+$ sudo grep ClientAliveCountMax /etc/ssh/sshd_config
+If properly configured, the output should be:
+ClientAliveCountMax
+For SSH earlier than v8.2, a ClientAliveCountMax value of 0 causes a timeout precisely when
+the ClientAliveInterval is set. Starting with v8.2, a value of 0 disables the timeout
+functionality completely.
+If the option is set to a number greater than 0, then the session will be disconnected after
+ClientAliveInterval * ClientAliveCountMax seconds without receiving a keep alive message. Is it the case that it is commented out or not configured properly? |
+ Configure the operating system to terminate all network connections associated with a communications session at the end of the session, or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity; and for user sessions (non-privileged session), the session must be terminated after 15 minutes of inactivity, except to fulfill documented and validated mission requirements. |
+ 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 unresponsive
+and terminated.
+For SSH earlier than v8.2, a ClientAliveCountMax value of 0
+causes a timeout precisely when the ClientAliveInterval is set.
+Starting with v8.2, a value of 0 disables the timeout functionality
+completely. If the option is set to a number greater than 0, then
+the session will be disconnected after
+ClientAliveInterval * ClientAliveCountMax seconds without receiving
+a keep alive message. |
+ medium |
+ |
+ |
+ |
+
+
| CCI-001133 |
SRG-OS-000163-GPOS-00072 |
@@ -23942,63 +23999,6 @@
|
-
- | CCI-001133 |
- SRG-OS-000163-GPOS-00072 |
- TBD - Assigned by DISA after STIG release |
- The operating system must terminate all network connections associated with a communications session at the end of the session, or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity; and for user sessions (non-privileged session), the session must be terminated after 15 minutes of inactivity, except to fulfill documented and validated mission requirements. |
-
- CCE-80907-9: Set SSH Client Alive Count Max |
-
- Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element.
-
-Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session. |
- 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 unresponsive
-and terminated.
-For SSH earlier than v8.2, a ClientAliveCountMax value of 0
-causes a timeout precisely when the ClientAliveInterval is set.
-Starting with v8.2, a value of 0 disables the timeout functionality
-completely. If the option is set to a number greater than 0, then
-the session will be disconnected after
-ClientAliveInterval * ClientAliveCountMax seconds without receiving
-a keep alive message. |
- Applicable - Configurable |
- Verify the operating system terminates all network connections associated with a communications session at the end of the session, or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity; and for user sessions (non-privileged session), the session must be terminated after 15 minutes of inactivity, except to fulfill documented and validated mission requirements.
-
-If it does not, this is a finding. |
- To ensure ClientAliveInterval is set correctly, run the following command:
-$ sudo grep ClientAliveCountMax /etc/ssh/sshd_config
-If properly configured, the output should be:
-ClientAliveCountMax
-For SSH earlier than v8.2, a ClientAliveCountMax value of 0 causes a timeout precisely when
-the ClientAliveInterval is set. Starting with v8.2, a value of 0 disables the timeout
-functionality completely.
-If the option is set to a number greater than 0, then the session will be disconnected after
-ClientAliveInterval * ClientAliveCountMax seconds without receiving a keep alive message. Is it the case that it is commented out or not configured properly? |
- Configure the operating system to terminate all network connections associated with a communications session at the end of the session, or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity; and for user sessions (non-privileged session), the session must be terminated after 15 minutes of inactivity, except to fulfill documented and validated mission requirements. |
- 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 unresponsive
-and terminated.
-For SSH earlier than v8.2, a ClientAliveCountMax value of 0
-causes a timeout precisely when the ClientAliveInterval is set.
-Starting with v8.2, a value of 0 disables the timeout functionality
-completely. If the option is set to a number greater than 0, then
-the session will be disconnected after
-ClientAliveInterval * ClientAliveCountMax seconds without receiving
-a keep alive message. |
- medium |
- |
- |
- |
-
-
@@ -24130,31 +24130,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where Endpoint Security Solution (ESS) is used; 30 days, for any additional internal network scans not covered by ESS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP). |
- CCE-86260-7: Install McAfee Endpoint Security for Linux (ENSL) |
+ CCE-86261-5: Ensure McAfee Endpoint Security for Linux (ENSL) is running |
Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws.
To support this requirement, the operating system may have an integrated solution incorporating continuous scanning using ESS and periodic scanning using other tools, as specified in the requirement. |
Install McAfee Endpoint Security for Linux antivirus software
which is provided for DoD systems and uses signatures to search for the
-presence of viruses on the filesystem.
-
-The McAfeeTP package can be installed with the following command:
-
-$ sudo yum install McAfeeTP |
+presence of viruses on the filesystem.
Applicable - Configurable |
Verify the operating system employs automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where ESS is used; 30 days, for any additional internal network scans not covered by ESS; and annually, for external scans by CNDSP.
If it does not, this is a finding. |
- Run the following command to determine if the McAfeeTP package is installed: $ rpm -q McAfeeTP Is it the case that the package is not installed? |
+ To verify that McAfee Endpoint Security for Linux is
+running, run the following command:
+$ sudo ps -ef | grep -i mfetpd Is it the case that virus scanning software is not running? |
Configure the operating system to employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where ESS is used; 30 days, for any additional internal network scans not covered by ESS; and annually, for external scans by CNDSP. |
Install McAfee Endpoint Security for Linux antivirus software
which is provided for DoD systems and uses signatures to search for the
-presence of viruses on the filesystem.
-
-The McAfeeTP package can be installed with the following command:
-
-$ sudo yum install McAfeeTP |
+presence of viruses on the filesystem.
medium |
|
|
@@ -24167,25 +24161,31 @@
TBD - Assigned by DISA after STIG release |
The operating system must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where Endpoint Security Solution (ESS) is used; 30 days, for any additional internal network scans not covered by ESS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP). |
- CCE-86261-5: Ensure McAfee Endpoint Security for Linux (ENSL) is running |
+ CCE-86260-7: Install McAfee Endpoint Security for Linux (ENSL) |
Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws.
To support this requirement, the operating system may have an integrated solution incorporating continuous scanning using ESS and periodic scanning using other tools, as specified in the requirement. |
Install McAfee Endpoint Security for Linux antivirus software
which is provided for DoD systems and uses signatures to search for the
-presence of viruses on the filesystem. |
+presence of viruses on the filesystem.
+
+The McAfeeTP package can be installed with the following command:
+
+$ sudo yum install McAfeeTP
Applicable - Configurable |
Verify the operating system employs automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where ESS is used; 30 days, for any additional internal network scans not covered by ESS; and annually, for external scans by CNDSP.
If it does not, this is a finding. |
- To verify that McAfee Endpoint Security for Linux is
-running, run the following command:
-$ sudo ps -ef | grep -i mfetpd Is it the case that virus scanning software is not running? |
+ Run the following command to determine if the McAfeeTP package is installed: $ rpm -q McAfeeTP Is it the case that the package is not installed? |
Configure the operating system to employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where ESS is used; 30 days, for any additional internal network scans not covered by ESS; and annually, for external scans by CNDSP. |
Install McAfee Endpoint Security for Linux antivirus software
which is provided for DoD systems and uses signatures to search for the
-presence of viruses on the filesystem. |
+presence of viruses on the filesystem.
+
+The McAfeeTP package can be installed with the following command:
+
+$ sudo yum install McAfeeTP
medium |
|
|
@@ -24221,6 +24221,49 @@
+
+ | CCI-001314 |
+ SRG-OS-000206-GPOS-00084 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must reveal error messages only to authorized users. |
+
+ CCE-88226-6: System Audit Directories Must Be Owned By Root |
+
+ Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.
+
+The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. |
+ All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
+
+To properly set the owner of /var/log/audit, run the command:
+$ sudo chown root /var/log/audit |
+ Applicable - Configurable |
+ Verify the operating system reveals error messages only to authorized users. If it does not, this is a finding. |
+ Determine where the audit logs are stored with the following command:
+
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+
+log_file = /var/log/audit/audit.log
+
+Determine the owner of the audit log directory by using the output of the above command
+(default: "/var/log/audit/"). Run the following command with the correct audit log directory
+path:
+
+$ sudo ls -ld /var/log/audit
+
+drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit
+
+The audit log directory must be owned by "root" Is it the case that the directory is not owned by root? |
+ Configure the operating system to reveal error messages only to authorized users. |
+ All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
+
+To properly set the owner of /var/log/audit, run the command:
+$ sudo chown root /var/log/audit |
+ medium |
+ |
+ |
+ |
+
+
| CCI-001314 |
SRG-OS-000206-GPOS-00084 |
@@ -24254,21 +24297,56 @@
TBD - Assigned by DISA after STIG release |
The operating system must reveal error messages only to authorized users. |
- CCE-83659-3: Verify Group Who Owns /var/log Directory |
+ CCE-88227-4: System Audit Logs Must Be Group Owned By Root |
Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. |
- To properly set the group owner of /var/log, run the command: $ sudo chgrp root /var/log |
+ All audit logs must be group owned by root user. The path for audit log can
+be configured via log_file parameter in /etc/audit/auditd.conf
+or, by default, the path for audit log is /var/log/audit/ .
+
+To properly set the group owner of /var/log/audit/*, run the command:
+$ sudo chgrp root /var/log/audit/*
+
+If log_group in /etc/audit/auditd.conf is set to a group other
+than the root group account, change the group ownership of the audit logs
+to this specific group. |
Applicable - Configurable |
Verify the operating system reveals error messages only to authorized users. If it does not, this is a finding. |
- To check the group ownership of /var/log,
-run the command:
-$ ls -lL /var/log
-If properly configured, the output should indicate the following group-owner:
-root Is it the case that /var/log does not have a group owner of root? |
+ Check group owners of the system audit logs.
+
+First, determine where the audit log file is located.
+
+$ sudo grep -iw ^log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
+
+The log_file option specifies the audit log file path.
+If the log_file option isn't defined, check all files within /var/log/audit directory.
+
+
+Then, determine the audit log group by running the following command:
+$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
+
+
+Then, check that the audit log file is owned by the correct group.
+Run the following command to display the owner of the audit log file:
+
+$ sudo stat -c "%n %G" log_file
+
+
+The audit log file must be owned by the log_group or by root if the log_group is not specified. Is it the case that audit log files are owned by incorrect group? |
Configure the operating system to reveal error messages only to authorized users. |
- To properly set the group owner of /var/log, run the command: $ sudo chgrp root /var/log |
+ All audit logs must be group owned by root user. The path for audit log can
+be configured via log_file parameter in /etc/audit/auditd.conf
+or, by default, the path for audit log is /var/log/audit/ .
+
+To properly set the group owner of /var/log/audit/*, run the command:
+$ sudo chgrp root /var/log/audit/*
+
+If log_group in /etc/audit/auditd.conf is set to a group other
+than the root group account, change the group ownership of the audit logs
+to this specific group. |
medium |
|
|
@@ -24281,21 +24359,33 @@
TBD - Assigned by DISA after STIG release |
The operating system must reveal error messages only to authorized users. |
- CCE-83660-1: Verify Group Who Owns /var/log/messages File |
+ CCE-88228-2: System Audit Logs Must Be Owned By Root |
Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. |
- To properly set the group owner of /var/log/messages, run the command: $ sudo chgrp root /var/log/messages |
+ All audit logs must be owned by root user. The path for audit log can be
+configured via log_file parameter in /etc/audit/auditd.conf
+or by default, the path for audit log is /var/log/audit/ .
+
+To properly set the owner of /var/log/audit/*, run the command:
+$ sudo chown root /var/log/audit/* |
Applicable - Configurable |
Verify the operating system reveals error messages only to authorized users. If it does not, this is a finding. |
- To check the group ownership of /var/log/messages,
-run the command:
-$ ls -lL /var/log/messages
-If properly configured, the output should indicate the following group-owner:
-root Is it the case that /var/log/messages does not have a group owner of root? |
+ Verify the audit logs are owned by "root". First, determine where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
+Using the location of the audit log file, determine if the audit log is owned by "root" using the following command:
+$ sudo stat -c "%n %U" /var/log/audit/audit.log
+Audit logs must be owned by user root.
+If the log_file isn't defined in /etc/audit/auditd.conf, check all files in /var/log/audit/ directory instead. Is it the case that the audit log is not owned by root? |
Configure the operating system to reveal error messages only to authorized users. |
- To properly set the group owner of /var/log/messages, run the command: $ sudo chgrp root /var/log/messages |
+ All audit logs must be owned by root user. The path for audit log can be
+configured via log_file parameter in /etc/audit/auditd.conf
+or by default, the path for audit log is /var/log/audit/ .
+
+To properly set the owner of /var/log/audit/*, run the command:
+$ sudo chown root /var/log/audit/* |
medium |
|
|
@@ -24353,25 +24443,21 @@
TBD - Assigned by DISA after STIG release |
The operating system must reveal error messages only to authorized users. |
- CCE-83663-5: Verify Permissions on /var/log Directory |
+ CCE-83661-9: Verify User Who Owns /var/log Directory |
Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. |
-
-To properly set the permissions of /var/log, run the command:
-$ sudo chmod 0755 /var/log |
+ To properly set the owner of /var/log, run the command: $ sudo chown root /var/log |
Applicable - Configurable |
Verify the operating system reveals error messages only to authorized users. If it does not, this is a finding. |
- To check the permissions of /var/log,
+ | To check the ownership of /var/log,
run the command:
-$ ls -l /var/log
-If properly configured, the output should indicate the following permissions:
-drwxr-xr-x Is it the case that /var/log does not have unix mode drwxr-xr-x? |
+$ ls -lL /var/log
+If properly configured, the output should indicate the following owner:
+root Is it the case that /var/log does not have an owner of root?
Configure the operating system to reveal error messages only to authorized users. |
-
-To properly set the permissions of /var/log, run the command:
-$ sudo chmod 0755 /var/log |
+ To properly set the owner of /var/log, run the command: $ sudo chown root /var/log |
medium |
|
|
@@ -24384,75 +24470,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must reveal error messages only to authorized users. |
- CCE-80819-6: System Audit Logs Must Have Mode 0640 or Less Permissive |
+ CCE-83665-0: Verify Permissions on /var/log/messages File |
Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. |
-Determine where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
-Configure the audit log to be protected from unauthorized read access by setting the correct
-permissive mode with the following command:
-$ sudo chmod 0600 audit_log_file
-By default, audit_log_file is "/var/log/audit/audit.log". |
+To properly set the permissions of /var/log/messages, run the command:
+$ sudo chmod 0640 /var/log/messages
Applicable - Configurable |
Verify the operating system reveals error messages only to authorized users. If it does not, this is a finding. |
- Run the following command to check the mode of the system audit logs:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file=/var/log/audit/audit.log
-$ sudo stat -c "%n %a" /var/log/audit/*
-$ sudo ls -l /var/log/audit
-Audit logs must be mode 0640 or less permissive. Is it the case that any permissions are more permissive? |
+ To check the permissions of /var/log/messages,
+run the command:
+$ ls -l /var/log/messages
+If properly configured, the output should indicate the following permissions:
+-rw-r----- Is it the case that /var/log/messages does not have unix mode -rw-r-----? |
Configure the operating system to reveal error messages only to authorized users. |
-Determine where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
-Configure the audit log to be protected from unauthorized read access by setting the correct
-permissive mode with the following command:
-$ sudo chmod 0600 audit_log_file
-By default, audit_log_file is "/var/log/audit/audit.log". |
- medium |
- |
- |
- |
-
-
-
- | CCI-001314 |
- SRG-OS-000206-GPOS-00084 |
- TBD - Assigned by DISA after STIG release |
- The operating system must reveal error messages only to authorized users. |
-
- CCE-88228-2: System Audit Logs Must Be Owned By Root |
-
- Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.
-
-The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. |
- All audit logs must be owned by root user. The path for audit log can be
-configured via log_file parameter in /etc/audit/auditd.conf
-or by default, the path for audit log is /var/log/audit/ .
-
-To properly set the owner of /var/log/audit/*, run the command:
-$ sudo chown root /var/log/audit/* |
- Applicable - Configurable |
- Verify the operating system reveals error messages only to authorized users. If it does not, this is a finding. |
- Verify the audit logs are owned by "root". First, determine where the audit logs are stored with the following command:
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
-Using the location of the audit log file, determine if the audit log is owned by "root" using the following command:
-$ sudo stat -c "%n %U" /var/log/audit/audit.log
-Audit logs must be owned by user root.
-If the log_file isn't defined in /etc/audit/auditd.conf, check all files in /var/log/audit/ directory instead. Is it the case that the audit log is not owned by root? |
- Configure the operating system to reveal error messages only to authorized users. |
- All audit logs must be owned by root user. The path for audit log can be
-configured via log_file parameter in /etc/audit/auditd.conf
-or by default, the path for audit log is /var/log/audit/ .
-
-To properly set the owner of /var/log/audit/*, run the command:
-$ sudo chown root /var/log/audit/* |
+To properly set the permissions of /var/log/messages, run the command:
+$ sudo chmod 0640 /var/log/messages
medium |
|
|
@@ -24465,25 +24501,21 @@
TBD - Assigned by DISA after STIG release |
The operating system must reveal error messages only to authorized users. |
- CCE-83665-0: Verify Permissions on /var/log/messages File |
+ CCE-83660-1: Verify Group Who Owns /var/log/messages File |
Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. |
-
-To properly set the permissions of /var/log/messages, run the command:
-$ sudo chmod 0640 /var/log/messages |
+ To properly set the group owner of /var/log/messages, run the command: $ sudo chgrp root /var/log/messages |
Applicable - Configurable |
Verify the operating system reveals error messages only to authorized users. If it does not, this is a finding. |
- To check the permissions of /var/log/messages,
+ | To check the group ownership of /var/log/messages,
run the command:
-$ ls -l /var/log/messages
-If properly configured, the output should indicate the following permissions:
--rw-r----- Is it the case that /var/log/messages does not have unix mode -rw-r-----? |
+$ ls -lL /var/log/messages
+If properly configured, the output should indicate the following group-owner:
+root Is it the case that /var/log/messages does not have a group owner of root?
Configure the operating system to reveal error messages only to authorized users. |
-
-To properly set the permissions of /var/log/messages, run the command:
-$ sudo chmod 0640 /var/log/messages |
+ To properly set the group owner of /var/log/messages, run the command: $ sudo chgrp root /var/log/messages |
medium |
|
|
@@ -24496,56 +24528,21 @@
TBD - Assigned by DISA after STIG release |
The operating system must reveal error messages only to authorized users. |
- CCE-88227-4: System Audit Logs Must Be Group Owned By Root |
+ CCE-83659-3: Verify Group Who Owns /var/log Directory |
Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. |
- All audit logs must be group owned by root user. The path for audit log can
-be configured via log_file parameter in /etc/audit/auditd.conf
-or, by default, the path for audit log is /var/log/audit/ .
-
-To properly set the group owner of /var/log/audit/*, run the command:
-$ sudo chgrp root /var/log/audit/*
-
-If log_group in /etc/audit/auditd.conf is set to a group other
-than the root group account, change the group ownership of the audit logs
-to this specific group. |
+ To properly set the group owner of /var/log, run the command: $ sudo chgrp root /var/log |
Applicable - Configurable |
Verify the operating system reveals error messages only to authorized users. If it does not, this is a finding. |
- Check group owners of the system audit logs.
-
-First, determine where the audit log file is located.
-
-$ sudo grep -iw ^log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
-
-The log_file option specifies the audit log file path.
-If the log_file option isn't defined, check all files within /var/log/audit directory.
-
-
-Then, determine the audit log group by running the following command:
-$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf
-
-
-Then, check that the audit log file is owned by the correct group.
-Run the following command to display the owner of the audit log file:
-
-$ sudo stat -c "%n %G" log_file
-
-
-The audit log file must be owned by the log_group or by root if the log_group is not specified. Is it the case that audit log files are owned by incorrect group? |
+ To check the group ownership of /var/log,
+run the command:
+$ ls -lL /var/log
+If properly configured, the output should indicate the following group-owner:
+root Is it the case that /var/log does not have a group owner of root? |
Configure the operating system to reveal error messages only to authorized users. |
- All audit logs must be group owned by root user. The path for audit log can
-be configured via log_file parameter in /etc/audit/auditd.conf
-or, by default, the path for audit log is /var/log/audit/ .
-
-To properly set the group owner of /var/log/audit/*, run the command:
-$ sudo chgrp root /var/log/audit/*
-
-If log_group in /etc/audit/auditd.conf is set to a group other
-than the root group account, change the group ownership of the audit logs
-to this specific group. |
+ To properly set the group owner of /var/log, run the command: $ sudo chgrp root /var/log |
medium |
|
|
@@ -24558,37 +24555,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must reveal error messages only to authorized users. |
- CCE-88226-6: System Audit Directories Must Be Owned By Root |
+ CCE-83663-5: Verify Permissions on /var/log Directory |
Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. |
- All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-
-To properly set the owner of /var/log/audit, run the command:
-$ sudo chown root /var/log/audit |
+
+To properly set the permissions of /var/log, run the command:
+$ sudo chmod 0755 /var/log |
Applicable - Configurable |
Verify the operating system reveals error messages only to authorized users. If it does not, this is a finding. |
- Determine where the audit logs are stored with the following command:
-
-$ sudo grep -iw log_file /etc/audit/auditd.conf
-
-log_file = /var/log/audit/audit.log
-
-Determine the owner of the audit log directory by using the output of the above command
-(default: "/var/log/audit/"). Run the following command with the correct audit log directory
-path:
-
-$ sudo ls -ld /var/log/audit
-
-drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit
-
-The audit log directory must be owned by "root" Is it the case that the directory is not owned by root? |
+ To check the permissions of /var/log,
+run the command:
+$ ls -l /var/log
+If properly configured, the output should indicate the following permissions:
+drwxr-xr-x Is it the case that /var/log does not have unix mode drwxr-xr-x? |
Configure the operating system to reveal error messages only to authorized users. |
- All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/ .
-
-To properly set the owner of /var/log/audit, run the command:
-$ sudo chown root /var/log/audit |
+
+To properly set the permissions of /var/log, run the command:
+$ sudo chmod 0755 /var/log |
medium |
|
|
@@ -24601,21 +24586,36 @@
TBD - Assigned by DISA after STIG release |
The operating system must reveal error messages only to authorized users. |
- CCE-83661-9: Verify User Who Owns /var/log Directory |
+ CCE-80819-6: System Audit Logs Must Have Mode 0640 or Less Permissive |
Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. |
- To properly set the owner of /var/log, run the command: $ sudo chown root /var/log |
+
+Determine where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
+Configure the audit log to be protected from unauthorized read access by setting the correct
+permissive mode with the following command:
+$ sudo chmod 0600 audit_log_file
+By default, audit_log_file is "/var/log/audit/audit.log". |
Applicable - Configurable |
Verify the operating system reveals error messages only to authorized users. If it does not, this is a finding. |
- To check the ownership of /var/log,
-run the command:
-$ ls -lL /var/log
-If properly configured, the output should indicate the following owner:
-root Is it the case that /var/log does not have an owner of root? |
+ Run the following command to check the mode of the system audit logs:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file=/var/log/audit/audit.log
+$ sudo stat -c "%n %a" /var/log/audit/*
+$ sudo ls -l /var/log/audit
+Audit logs must be mode 0640 or less permissive. Is it the case that any permissions are more permissive? |
Configure the operating system to reveal error messages only to authorized users. |
- To properly set the owner of /var/log, run the command: $ sudo chown root /var/log |
+
+Determine where the audit logs are stored with the following command:
+$ sudo grep -iw log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
+Configure the audit log to be protected from unauthorized read access by setting the correct
+permissive mode with the following command:
+$ sudo chmod 0600 audit_log_file
+By default, audit_log_file is "/var/log/audit/audit.log". |
medium |
|
|
@@ -24633,7 +24633,7 @@
TBD - Assigned by DISA after STIG release |
Any publically accessible connection to the operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. |
- CCE-80763-6: Modify the System Login Banner |
+ CCE-80768-5: Enable GNOME3 Login Warning Banner |
Display of a standardized and approved use notification before granting access to the publicly accessible operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
@@ -24658,38 +24658,20 @@
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've readconsent to terms in IS user agreem't." |
-
-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:
+ | 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.
-I've read & consent to terms in IS user agreem't. |
+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.
Applicable - Configurable |
Verify any publically accessible connection to the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
@@ -24714,9 +24696,12 @@
"I've read & consent to terms in IS user agreem't."
If it does not, this is a finding. |
- To check if the system login banner is compliant,
-run the following command:
-$ cat /etc/issue Is it the case that it does not display the required banner? |
+ To ensure a login warning banner is enabled, run the following:
+$ grep banner-message-enable /etc/dconf/db/gdm.d/*
+If properly configured, the output should be true.
+To ensure a login warning banner is locked and cannot be changed by a user, run the following:
+$ grep banner-message-enable /etc/dconf/db/gdm.d/locks/*
+If properly configured, the output should be /org/gnome/login-screen/banner-message-enable. Is it the case that it is not? |
Configure any publically accessible connection to the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:
@@ -24738,38 +24723,20 @@
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've read & consent to terms in IS user agreem't." |
-
-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:
+ | 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.
-I've read & consent to terms in IS user agreem't. |
+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.
medium |
|
|
@@ -24782,7 +24749,7 @@
TBD - Assigned by DISA after STIG release |
Any publically accessible connection to the operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. |
- CCE-80905-3: Enable SSH Warning Banner |
+ CCE-80770-1: Set the GNOME3 Login Warning Banner Text |
Display of a standardized and approved use notification before granting access to the publicly accessible operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
@@ -24807,15 +24774,24 @@
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've readconsent to terms in IS user agreem't." |
- To enable the warning banner and ensure it is consistent
-across the system, add or correct the following line in
-
+ | 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/ssh/sshd_config:
+/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
-Banner /etc/issue
-Another section contains information on how to create an
-appropriate system-wide warning banner. |
+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.
Applicable - Configurable |
Verify any publically accessible connection to the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
@@ -24840,12 +24816,13 @@
"I've read & consent to terms in IS user agreem't."
If it does not, this is a finding. |
- To determine how the SSH daemon's Banner option is set, run the following command:
-
-$ sudo grep -i Banner /etc/ssh/sshd_config
-
-If a line indicating /etc/issue is returned, then the required value is set.
- Is it the case that the required value is not set? |
+
+To ensure the login warning banner text is properly set, run the following:
+$ grep banner-message-text /etc/dconf/db/gdm.d/*
+If properly configured, the proper banner text will appear.
+To ensure the login warning banner text is locked and cannot be changed by a user, run the following:
+$ grep banner-message-text /etc/dconf/db/gdm.d/locks/*
+If properly configured, the output should be /org/gnome/login-screen/banner-message-text. Is it the case that it does not? |
Configure any publically accessible connection to the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:
@@ -24867,15 +24844,24 @@
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've read & consent to terms in IS user agreem't." |
- To enable the warning banner and ensure it is consistent
-across the system, add or correct the following line in
-
+ | 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/ssh/sshd_config:
+/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
-Banner /etc/issue
-Another section contains information on how to create an
-appropriate system-wide warning banner. |
+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.
medium |
|
|
@@ -24888,7 +24874,7 @@
TBD - Assigned by DISA after STIG release |
Any publically accessible connection to the operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. |
- CCE-80768-5: Enable GNOME3 Login Warning Banner |
+ CCE-80905-3: Enable SSH Warning Banner |
Display of a standardized and approved use notification before granting access to the publicly accessible operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
@@ -24913,20 +24899,15 @@
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've readconsent to terms in IS user agreem't." |
- 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. |
+ 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. |
Applicable - Configurable |
Verify any publically accessible connection to the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
@@ -24951,12 +24932,12 @@
"I've read & consent to terms in IS user agreem't."
If it does not, this is a finding. |
- To ensure a login warning banner is enabled, run the following:
-$ grep banner-message-enable /etc/dconf/db/gdm.d/*
-If properly configured, the output should be true.
-To ensure a login warning banner is locked and cannot be changed by a user, run the following:
-$ grep banner-message-enable /etc/dconf/db/gdm.d/locks/*
-If properly configured, the output should be /org/gnome/login-screen/banner-message-enable. Is it the case that it is not? |
+ To determine how the SSH daemon's Banner option is set, run the following command:
+
+$ sudo grep -i Banner /etc/ssh/sshd_config
+
+If a line indicating /etc/issue is returned, then the required value is set.
+ Is it the case that the required value is not set? |
Configure any publically accessible connection to the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:
@@ -24978,20 +24959,15 @@
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've read & consent to terms in IS user agreem't." |
- 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. |
+ 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. |
medium |
|
|
@@ -25004,7 +24980,7 @@
TBD - Assigned by DISA after STIG release |
Any publically accessible connection to the operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. |
- CCE-80770-1: Set the GNOME3 Login Warning Banner Text |
+ CCE-80763-6: Modify the System Login Banner |
Display of a standardized and approved use notification before granting access to the publicly accessible operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
@@ -25029,24 +25005,38 @@
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've readconsent to terms in IS user agreem't." |
- 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
+ |
+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.
-/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. |
+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.
Applicable - Configurable |
Verify any publically accessible connection to the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
@@ -25071,13 +25061,9 @@
"I've read & consent to terms in IS user agreem't."
If it does not, this is a finding. |
-
-To ensure the login warning banner text is properly set, run the following:
-$ grep banner-message-text /etc/dconf/db/gdm.d/*
-If properly configured, the proper banner text will appear.
-To ensure the login warning banner text is locked and cannot be changed by a user, run the following:
-$ grep banner-message-text /etc/dconf/db/gdm.d/locks/*
-If properly configured, the output should be /org/gnome/login-screen/banner-message-text. Is it the case that it does not? |
+ To check if the system login banner is compliant,
+run the following command:
+$ cat /etc/issue Is it the case that it does not display the required banner? |
Configure any publically accessible connection to the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:
@@ -25099,24 +25085,38 @@
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:
"I've read & consent to terms in IS user agreem't." |
- 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
+ |
+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.
-/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. |
+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.
medium |
|
|
@@ -25134,7 +25134,52 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account modifications. |
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+
+ Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to modify an existing account. Auditing account modification actions provides logging that can be used for forensic purposes.
+
+To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
+ At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
+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:
+-w /etc/sudoers -p wa -k actions |
+ Applicable - Configurable |
+ Verify the operating system automatically audits account modification. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+
+$ sudo auditctl -l | grep /etc/sudoers
+
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to automatically audit account modification. |
+ At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
+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:
+-w /etc/sudoers -p wa -k actions |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-001403 |
+ SRG-OS-000239-GPOS-00089 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must audit all account modifications. |
+
+ CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to modify an existing account. Auditing account modification actions provides logging that can be used for forensic purposes.
@@ -25145,21 +25190,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system automatically audits account modification. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+$ sudo auditctl -l | grep -E '(/etc/shadow)'
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account modification. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -25167,14 +25212,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -25187,7 +25232,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account modifications. |
- CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to modify an existing account. Auditing account modification actions provides logging that can be used for forensic purposes.
@@ -25198,21 +25243,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/shadow -p wa -k audit_rules_usergroup_modification
+-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/shadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system automatically audits account modification. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/shadow)'
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
--w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account modification. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -25220,14 +25265,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/shadow -p wa -k audit_rules_usergroup_modification
+-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/shadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -25285,39 +25330,49 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account modifications. |
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+ CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to modify an existing account. Auditing account modification actions provides logging that can be used for forensic purposes.
To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
Applicable - Configurable |
Verify the operating system automatically audits account modification. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-$ sudo auditctl -l | grep /etc/sudoers
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes?
Configure the operating system to automatically audit account modification. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
medium |
|
|
@@ -25430,73 +25485,63 @@
|
+
+
+
+
+
- | CCI-001403 |
- SRG-OS-000239-GPOS-00089 |
+ CCI-001404 |
+ SRG-OS-000240-GPOS-00090 |
TBD - Assigned by DISA after STIG release |
- The operating system must audit all account modifications. |
+ The operating system must audit all account disabling actions. |
- CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
+ CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
- Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to modify an existing account. Auditing account modification actions provides logging that can be used for forensic purposes.
+ | When operating system accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account disabling actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
-To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
- 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
-
+To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
+ At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers -p wa -k actions
Applicable - Configurable |
- Verify the operating system automatically audits account modification. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+ | Verify the operating system automatically audits account disabling actions. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
--w /etc/gshadow -p wa -k identity
+$ sudo auditctl -l | grep /etc/sudoers
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
- Configure the operating system to automatically audit account modification. |
- 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
-
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to automatically audit account disabling actions. |
+ At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers -p wa -k actions
medium |
|
|
|
-
-
-
-
-
| CCI-001404 |
SRG-OS-000240-GPOS-00090 |
TBD - Assigned by DISA after STIG release |
The operating system must audit all account disabling actions. |
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
When operating system accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account disabling actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
@@ -25507,21 +25552,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system automatically audits account disabling actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+$ sudo auditctl -l | grep -E '(/etc/shadow)'
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account disabling actions. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -25529,14 +25574,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -25549,7 +25594,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account disabling actions. |
- CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
When operating system accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account disabling actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
@@ -25560,21 +25605,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/shadow -p wa -k audit_rules_usergroup_modification
+-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/shadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system automatically audits account disabling actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/shadow)'
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
--w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account disabling actions. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -25582,14 +25627,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/shadow -p wa -k audit_rules_usergroup_modification
+-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/shadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -25647,39 +25692,49 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account disabling actions. |
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+ CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
When operating system accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account disabling actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
Applicable - Configurable |
Verify the operating system automatically audits account disabling actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-$ sudo auditctl -l | grep /etc/sudoers
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes?
Configure the operating system to automatically audit account disabling actions. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
medium |
|
|
@@ -25792,15 +25847,65 @@
|
+
+
+
+
+
- | CCI-001404 |
- SRG-OS-000240-GPOS-00090 |
+ CCI-001405 |
+ SRG-OS-000241-GPOS-00091 |
TBD - Assigned by DISA after STIG release |
- The operating system must audit all account disabling actions. |
+ The operating system must audit all account removal actions. |
- CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
+ CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
- When operating system accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account disabling actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
+ | When operating system accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account removal actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
+
+To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
+ At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
+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:
+-w /etc/sudoers -p wa -k actions |
+ Applicable - Configurable |
+ Verify the operating system automatically audits account removal actions. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+
+$ sudo auditctl -l | grep /etc/sudoers
+
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to automatically audit account removal actions. |
+ At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
+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:
+-w /etc/sudoers -p wa -k actions |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-001405 |
+ SRG-OS-000241-GPOS-00091 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must audit all account removal actions. |
+
+ CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
+
+ When operating system accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account removal actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
If the auditd daemon is configured to use the
@@ -25809,49 +25914,42 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification
+-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/gshadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
- Verify the operating system automatically audits account disabling actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+ | Verify the operating system automatically audits account removal actions. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
--w /etc/gshadow -p wa -k identity
+$ sudo auditctl -l | grep -E '(/etc/shadow)'
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
- Configure the operating system to automatically audit account disabling actions. |
+-w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out?
+ Configure the operating system to automatically audit account removal actions. |
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
+-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/gshadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
|
-
-
-
-
-
| CCI-001405 |
SRG-OS-000241-GPOS-00091 |
@@ -25911,70 +26009,17 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account removal actions. |
- CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
+ CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
When operating system accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account removal actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
- 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 |
- Applicable - Configurable |
- Verify the operating system automatically audits account removal actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/shadow)'
-
--w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
- Configure the operating system to automatically audit account removal actions. |
- 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-001405 |
- SRG-OS-000241-GPOS-00091 |
- TBD - Assigned by DISA after STIG release |
- The operating system must audit all account removal actions. |
-
- CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
-
- When operating system accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account removal actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
-
-To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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:
@@ -26009,52 +26054,7 @@
| TBD - Assigned by DISA after STIG release |
The operating system must audit all account removal actions. |
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
-
- When operating system accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account removal actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
-
-To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
-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:
--w /etc/sudoers -p wa -k actions |
- Applicable - Configurable |
- Verify the operating system automatically audits account removal actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-
-$ sudo auditctl -l | grep /etc/sudoers
-
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to automatically audit account removal actions. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
-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:
--w /etc/sudoers -p wa -k actions |
- medium |
- |
- |
- |
-
-
-
- | CCI-001405 |
- SRG-OS-000241-GPOS-00091 |
- TBD - Assigned by DISA after STIG release |
- The operating system must audit all account removal actions. |
-
- CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+ CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
When operating system accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account removal actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
@@ -26065,21 +26065,23 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system automatically audits account removal actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
--w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes?
Configure the operating system to automatically audit account removal actions. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -26087,14 +26089,14 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -26107,7 +26109,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account removal actions. |
- CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+ CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
When operating system accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account removal actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
@@ -26118,21 +26120,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/group -p wa -k audit_rules_usergroup_modification
+-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/group -p wa -k audit_rules_usergroup_modification |
+-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system automatically audits account removal actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/group)'
+$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
--w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account removal actions. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -26140,14 +26142,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/group -p wa -k audit_rules_usergroup_modification
+-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/group -p wa -k audit_rules_usergroup_modification |
+-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -26160,7 +26162,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account removal actions. |
- CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
+ CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
When operating system accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must audit account removal actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.
@@ -26171,23 +26173,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification
+-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/gshadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/group -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system automatically audits account removal actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
--w /etc/gshadow -p wa -k identity
+$ sudo auditctl -l | grep -E '(/etc/group)'
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
+-w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account removal actions. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -26195,14 +26195,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification
+-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/gshadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/group -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -26262,37 +26262,111 @@
TBD - Assigned by DISA after STIG release |
The operating system must implement cryptography to protect the integrity of remote access sessions. |
- CCE-80938-4: Configure OpenSSL library to use System Crypto Policy |
+ CCE-84255-9: Configure OpenSSL library to use TLS Encryption |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-OpenSSL is supported by crypto policy, but the OpenSSL configuration may be
-set up to ignore it.
-To check that Crypto Policies settings are configured correctly, you have to examine the OpenSSL config file
-available under /etc/pki/tls/openssl.cnf.
-This file has the ini format, and it enables crypto policy support
-if there is a [ crypto_policy ] section that contains the .include /etc/crypto-policies/back-ends/opensslcnf.config directive. |
+ Crypto Policies are means of enforcing certain cryptographic settings for
+selected applications including OpenSSL. OpenSSL is by default configured to
+modify its configuration based on currently configured Crypto Policy.
+Editing the Crypto Policy back-end is not recommended.
+
+Check the crypto-policies(7) man page and choose a policy that configures TLS
+protocol to version 1.2 or higher, for example DEFAULT, FUTURE or FIPS policy.
+Or create and apply a custom policy that restricts minimum TLS version to 1.2.
+
+For example for versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch
+this is expected:
+
+$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
+
+MinProtocol = TLSv1.2
+
+
+Or for version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer this is
+expected:
+
+$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
+
+TLS.MinProtocol = TLSv1.2
+DTLS.MinProtocol = DTLSv1.2 |
Applicable - Configurable |
Verify the operating system implements cryptography to protect the integrity of remote access sessions. If it does not, this is a finding. |
- To verify that OpenSSL uses the system crypto policy, check out that the OpenSSL config file
-/etc/pki/tls/openssl.cnf contains the [ crypto_policy ] section with the
-.include /etc/crypto-policies/back-ends/opensslcnf.config directive:
+ | To verify if the OpenSSL uses defined TLS Crypto Policy, run:
+$ grep -P '^(TLS\.)?MinProtocol' /etc/crypto-policies/back-ends/opensslcnf.config
+and verify that the value is
+TLSv1.2 Is it the case that cryptographic policy for openssl is not configured or is configured incorrectly? |
+ Configure the operating system to implement cryptography to protect the integrity of remote access sessions. |
+ Crypto Policies are means of enforcing certain cryptographic settings for
+selected applications including OpenSSL. OpenSSL is by default configured to
+modify its configuration based on currently configured Crypto Policy.
+Editing the Crypto Policy back-end is not recommended.
-$ sudo grep '\.include\s* /etc/crypto-policies/back-ends/opensslcnf.config$' /etc/pki/tls/openssl.cnf . Is it the case that the OpenSSL config file doesn't contain the whole section,
-or the section doesn't contain the .include /etc/crypto-policies/back-ends/opensslcnf.config directive? |
+Check the crypto-policies(7) man page and choose a policy that configures TLS
+protocol to version 1.2 or higher, for example DEFAULT, FUTURE or FIPS policy.
+Or create and apply a custom policy that restricts minimum TLS version to 1.2.
+
+For example for versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch
+this is expected:
+
+$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
+
+MinProtocol = TLSv1.2
+
+
+Or for version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer this is
+expected:
+
+$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
+
+TLS.MinProtocol = TLSv1.2
+DTLS.MinProtocol = DTLSv1.2
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-001453 |
+ SRG-OS-000250-GPOS-00093 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must implement cryptography to protect the integrity of remote access sessions. |
+
+ CCE-85902-5: Configure SSH Client to Use FIPS 140-2 Validated Ciphers: openssh.config |
+
+ Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
+
+Remote access (e.g., RDP) is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+
+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. |
+ Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
+set up incorrectly.
+
+To check that Crypto Policies settings for ciphers are configured correctly, ensure that
+/etc/crypto-policies/back-ends/openssh.config contains the following
+line and is not commented out:
+Ciphers |
+ Applicable - Configurable |
+ Verify the operating system implements cryptography to protect the integrity of remote access sessions. If it does not, this is a finding. |
+ To verify if the OpenSSH client uses defined Cipher suite in the Crypto Policy, run:
+$ grep -i ciphers /etc/crypto-policies/back-ends/openssh.config
+and verify that the line matches:
+Ciphers Is it the case that Crypto Policy for OpenSSH client is not configured correctly? |
Configure the operating system to implement cryptography to protect the integrity of remote access sessions. |
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-OpenSSL is supported by crypto policy, but the OpenSSL configuration may be
-set up to ignore it.
-To check that Crypto Policies settings are configured correctly, you have to examine the OpenSSL config file
-available under /etc/pki/tls/openssl.cnf.
-This file has the ini format, and it enables crypto policy support
-if there is a [ crypto_policy ] section that contains the .include /etc/crypto-policies/back-ends/opensslcnf.config directive. |
- medium |
+OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
+set up incorrectly.
+
+To check that Crypto Policies settings for ciphers are configured correctly, ensure that
+/etc/crypto-policies/back-ends/openssh.config contains the following
+line and is not commented out:
+Ciphers
+ high |
|
|
|
@@ -26304,7 +26378,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must implement cryptography to protect the integrity of remote access sessions. |
- CCE-85899-3: Configure SSH Server to Use FIPS 140-2 Validated MACs: opensshserver.config |
+ CCE-85870-4: Configure SSH Client to Use FIPS 140-2 Validated MACs: openssh.config |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
@@ -26316,24 +26390,24 @@
set up incorrectly.
To check that Crypto Policies settings are configured correctly, ensure that
-/etc/crypto-policies/back-ends/opensshserver.config contains the following
-text and is not commented out:
--oMACS= |
+/etc/crypto-policies/back-ends/openssh.config contains the following
+line and is not commented out:
+MACs
Applicable - Configurable |
Verify the operating system implements cryptography to protect the integrity of remote access sessions. If it does not, this is a finding. |
- To verify if the OpenSSH server uses defined MACs in the Crypto Policy, run:
-$ grep -Po '(-oMACs=\S+)' /etc/crypto-policies/back-ends/opensshserver.config
+ | To verify if the OpenSSH client uses defined MACs in the Crypto Policy, run:
+$ grep -i macs /etc/crypto-policies/back-ends/openssh.config
and verify that the line matches:
--oMACS= Is it the case that Crypto Policy for OpenSSH Server is not configured correctly? |
+MACs
Is it the case that Crypto Policy for OpenSSH client is not configured correctly?
Configure the operating system to implement cryptography to protect the integrity of remote access sessions. |
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
To check that Crypto Policies settings are configured correctly, ensure that
-/etc/crypto-policies/back-ends/opensshserver.config contains the following
-text and is not commented out:
--oMACS= |
+/etc/crypto-policies/back-ends/openssh.config contains the following
+line and is not commented out:
+MACs
medium |
|
|
@@ -26346,33 +26420,36 @@
TBD - Assigned by DISA after STIG release |
The operating system must implement cryptography to protect the integrity of remote access sessions. |
- CCE-86059-3: Use Only FIPS 140-2 Validated Key Exchange Algorithms |
+ CCE-80938-4: Configure OpenSSL library to use System Crypto Policy |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. |
- Limit the key exchange algorithms to those which are FIPS-approved.
-Add or modify the following line in /etc/crypto-policies/back-ends/opensshserver.config
-CRYPTO_POLICY='-oKexAlgorithms=ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512'
-This rule ensures that only the key exchange algorithms mentioned
-above (or their subset) are configured for use, keeping the given
-order of algorithms. |
+ Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+OpenSSL is supported by crypto policy, but the OpenSSL configuration may be
+set up to ignore it.
+To check that Crypto Policies settings are configured correctly, you have to examine the OpenSSL config file
+available under /etc/pki/tls/openssl.cnf.
+This file has the ini format, and it enables crypto policy support
+if there is a [ crypto_policy ] section that contains the .include /etc/crypto-policies/back-ends/opensslcnf.config directive. |
Applicable - Configurable |
Verify the operating system implements cryptography to protect the integrity of remote access sessions. If it does not, this is a finding. |
- Only FIPS-approved key exchange algorithms must be used. To verify that only FIPS-approved
-key exchange algorithms are in use, run the following command:
-$ sudo grep -i kexalgorithms /etc/crypto-policies/back-ends/opensshserver.config
-The output should contain only following algorithms (or a subset) in the exact order:
-CRYPTO_POLICY='-oKexAlgorithms=ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512' Is it the case that KexAlgorithms option is commented out, contains non-approved algorithms, or the FIPS-approved algorithms are not in the exact order? |
+ To verify that OpenSSL uses the system crypto policy, check out that the OpenSSL config file
+/etc/pki/tls/openssl.cnf contains the [ crypto_policy ] section with the
+.include /etc/crypto-policies/back-ends/opensslcnf.config directive:
+
+$ sudo grep '\.include\s* /etc/crypto-policies/back-ends/opensslcnf.config$' /etc/pki/tls/openssl.cnf . Is it the case that the OpenSSL config file doesn't contain the whole section,
+or the section doesn't contain the .include /etc/crypto-policies/back-ends/opensslcnf.config directive? |
Configure the operating system to implement cryptography to protect the integrity of remote access sessions. |
- Limit the key exchange algorithms to those which are FIPS-approved.
-Add or modify the following line in /etc/crypto-policies/back-ends/opensshserver.config
-CRYPTO_POLICY='-oKexAlgorithms=ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512'
-This rule ensures that only the key exchange algorithms mentioned
-above (or their subset) are configured for use, keeping the given
-order of algorithms. |
+ Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+OpenSSL is supported by crypto policy, but the OpenSSL configuration may be
+set up to ignore it.
+To check that Crypto Policies settings are configured correctly, you have to examine the OpenSSL config file
+available under /etc/pki/tls/openssl.cnf.
+This file has the ini format, and it enables crypto policy support
+if there is a [ crypto_policy ] section that contains the .include /etc/crypto-policies/back-ends/opensslcnf.config directive. |
medium |
|
|
@@ -26385,7 +26462,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must implement cryptography to protect the integrity of remote access sessions. |
- CCE-85902-5: Configure SSH Client to Use FIPS 140-2 Validated Ciphers: openssh.config |
+ CCE-85899-3: Configure SSH Server to Use FIPS 140-2 Validated MACs: opensshserver.config |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
@@ -26396,26 +26473,26 @@
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
-To check that Crypto Policies settings for ciphers are configured correctly, ensure that
-/etc/crypto-policies/back-ends/openssh.config contains the following
-line and is not commented out:
-Ciphers |
+To check that Crypto Policies settings are configured correctly, ensure that
+/etc/crypto-policies/back-ends/opensshserver.config contains the following
+text and is not commented out:
+-oMACS=
Applicable - Configurable |
Verify the operating system implements cryptography to protect the integrity of remote access sessions. If it does not, this is a finding. |
- To verify if the OpenSSH client uses defined Cipher suite in the Crypto Policy, run:
-$ grep -i ciphers /etc/crypto-policies/back-ends/openssh.config
+ | To verify if the OpenSSH server uses defined MACs in the Crypto Policy, run:
+$ grep -Po '(-oMACs=\S+)' /etc/crypto-policies/back-ends/opensshserver.config
and verify that the line matches:
-Ciphers Is it the case that Crypto Policy for OpenSSH client is not configured correctly? |
+-oMACS=
Is it the case that Crypto Policy for OpenSSH Server is not configured correctly?
Configure the operating system to implement cryptography to protect the integrity of remote access sessions. |
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
-To check that Crypto Policies settings for ciphers are configured correctly, ensure that
-/etc/crypto-policies/back-ends/openssh.config contains the following
-line and is not commented out:
-Ciphers |
- high |
+To check that Crypto Policies settings are configured correctly, ensure that
+/etc/crypto-policies/back-ends/opensshserver.config contains the following
+text and is not commented out:
+-oMACS=
+ medium |
|
|
|
@@ -26469,110 +26546,33 @@
TBD - Assigned by DISA after STIG release |
The operating system must implement cryptography to protect the integrity of remote access sessions. |
- CCE-84254-2: Configure GnuTLS library to use DoD-approved TLS Encryption |
-
- Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
-
-Remote access (e.g., RDP) is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
-
-Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-GnuTLS is supported by system crypto policy, but the GnuTLS configuration may be
-set up to ignore it.
-
-To check that Crypto Policies settings are configured correctly, ensure that
-/etc/crypto-policies/back-ends/gnutls.config contains the following
-line and is not commented out:
-+VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0 |
- Applicable - Configurable |
- Verify the operating system implements cryptography to protect the integrity of remote access sessions. If it does not, this is a finding. |
- To verify if GnuTLS uses defined DoD-approved TLS Crypto Policy, run:
-$ sudo grep
-'+VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0'
-/etc/crypto-policies/back-ends/gnutls.config and verify that a match exists. Is it the case that cryptographic policy for gnutls is not configured or is configured incorrectly? |
- Configure the operating system to implement cryptography to protect the integrity of remote access sessions. |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-GnuTLS is supported by system crypto policy, but the GnuTLS configuration may be
-set up to ignore it.
-
-To check that Crypto Policies settings are configured correctly, ensure that
-/etc/crypto-policies/back-ends/gnutls.config contains the following
-line and is not commented out:
-+VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0 |
- medium |
- |
- |
- |
-
-
-
- | CCI-001453 |
- SRG-OS-000250-GPOS-00093 |
- TBD - Assigned by DISA after STIG release |
- The operating system must implement cryptography to protect the integrity of remote access sessions. |
-
- CCE-84255-9: Configure OpenSSL library to use TLS Encryption |
+ CCE-86059-3: Use Only FIPS 140-2 Validated Key Exchange Algorithms |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. |
- Crypto Policies are means of enforcing certain cryptographic settings for
-selected applications including OpenSSL. OpenSSL is by default configured to
-modify its configuration based on currently configured Crypto Policy.
-Editing the Crypto Policy back-end is not recommended.
-
-Check the crypto-policies(7) man page and choose a policy that configures TLS
-protocol to version 1.2 or higher, for example DEFAULT, FUTURE or FIPS policy.
-Or create and apply a custom policy that restricts minimum TLS version to 1.2.
-
-For example for versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch
-this is expected:
-
-$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
-
-MinProtocol = TLSv1.2
-
-
-Or for version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer this is
-expected:
-
-$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
-
-TLS.MinProtocol = TLSv1.2
-DTLS.MinProtocol = DTLSv1.2 |
+ Limit the key exchange algorithms to those which are FIPS-approved.
+Add or modify the following line in /etc/crypto-policies/back-ends/opensshserver.config
+CRYPTO_POLICY='-oKexAlgorithms=ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512'
+This rule ensures that only the key exchange algorithms mentioned
+above (or their subset) are configured for use, keeping the given
+order of algorithms. |
Applicable - Configurable |
Verify the operating system implements cryptography to protect the integrity of remote access sessions. If it does not, this is a finding. |
- To verify if the OpenSSL uses defined TLS Crypto Policy, run:
-$ grep -P '^(TLS\.)?MinProtocol' /etc/crypto-policies/back-ends/opensslcnf.config
-and verify that the value is
-TLSv1.2 Is it the case that cryptographic policy for openssl is not configured or is configured incorrectly? |
+ Only FIPS-approved key exchange algorithms must be used. To verify that only FIPS-approved
+key exchange algorithms are in use, run the following command:
+$ sudo grep -i kexalgorithms /etc/crypto-policies/back-ends/opensshserver.config
+The output should contain only following algorithms (or a subset) in the exact order:
+CRYPTO_POLICY='-oKexAlgorithms=ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512' Is it the case that KexAlgorithms option is commented out, contains non-approved algorithms, or the FIPS-approved algorithms are not in the exact order? |
Configure the operating system to implement cryptography to protect the integrity of remote access sessions. |
- Crypto Policies are means of enforcing certain cryptographic settings for
-selected applications including OpenSSL. OpenSSL is by default configured to
-modify its configuration based on currently configured Crypto Policy.
-Editing the Crypto Policy back-end is not recommended.
-
-Check the crypto-policies(7) man page and choose a policy that configures TLS
-protocol to version 1.2 or higher, for example DEFAULT, FUTURE or FIPS policy.
-Or create and apply a custom policy that restricts minimum TLS version to 1.2.
-
-For example for versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch
-this is expected:
-
-$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
-
-MinProtocol = TLSv1.2
-
-
-Or for version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer this is
-expected:
-
-$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
-
-TLS.MinProtocol = TLSv1.2
-DTLS.MinProtocol = DTLSv1.2 |
+ Limit the key exchange algorithms to those which are FIPS-approved.
+Add or modify the following line in /etc/crypto-policies/back-ends/opensshserver.config
+CRYPTO_POLICY='-oKexAlgorithms=ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512'
+This rule ensures that only the key exchange algorithms mentioned
+above (or their subset) are configured for use, keeping the given
+order of algorithms. |
medium |
|
|
@@ -26627,7 +26627,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must implement cryptography to protect the integrity of remote access sessions. |
- CCE-85870-4: Configure SSH Client to Use FIPS 140-2 Validated MACs: openssh.config |
+ CCE-84254-2: Configure GnuTLS library to use DoD-approved TLS Encryption |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
@@ -26635,28 +26635,28 @@
Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. |
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
-set up incorrectly.
+GnuTLS is supported by system crypto policy, but the GnuTLS configuration may be
+set up to ignore it.
To check that Crypto Policies settings are configured correctly, ensure that
-/etc/crypto-policies/back-ends/openssh.config contains the following
+/etc/crypto-policies/back-ends/gnutls.config contains the following
line and is not commented out:
-MACs |
++VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0
Applicable - Configurable |
Verify the operating system implements cryptography to protect the integrity of remote access sessions. If it does not, this is a finding. |
- To verify if the OpenSSH client uses defined MACs in the Crypto Policy, run:
-$ grep -i macs /etc/crypto-policies/back-ends/openssh.config
-and verify that the line matches:
-MACs Is it the case that Crypto Policy for OpenSSH client is not configured correctly? |
+ To verify if GnuTLS uses defined DoD-approved TLS Crypto Policy, run:
+$ sudo grep
+'+VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0'
+/etc/crypto-policies/back-ends/gnutls.config and verify that a match exists. Is it the case that cryptographic policy for gnutls is not configured or is configured incorrectly? |
Configure the operating system to implement cryptography to protect the integrity of remote access sessions. |
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
-set up incorrectly.
+GnuTLS is supported by system crypto policy, but the GnuTLS configuration may be
+set up to ignore it.
To check that Crypto Policies settings are configured correctly, ensure that
-/etc/crypto-policies/back-ends/openssh.config contains the following
+/etc/crypto-policies/back-ends/gnutls.config contains the following
line and is not commented out:
-MACs |
++VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0
medium |
|
|
@@ -26674,43 +26674,31 @@
TBD - Assigned by DISA after STIG release |
The operating system must initiate session audits at system start-up. |
- CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
+ CCE-80872-5: Enable auditd Service |
If auditing is enabled late in the start-up process, the actions of some start-up processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created. |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ 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 |
Applicable - Configurable |
Verify the operating system initiates session audits at system start-up. If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes audit_backlog_limit=8192,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
-The command should not return any output. Is it the case that audit backlog limit is not configured? |
+
+
+Run the following command to determine the current status of the
+auditd service:
+$ sudo systemctl is-active auditd
+If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
Configure the operating system to initiate session audits at system start-up. |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
- low |
+ 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 |
+ medium |
|
|
|
@@ -26743,31 +26731,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must initiate session audits at system start-up. |
- CCE-80872-5: Enable auditd Service |
+ CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
If auditing is enabled late in the start-up process, the actions of some start-up processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created. |
- 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 |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
Applicable - Configurable |
Verify the operating system initiates session audits at system start-up. If it does not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-auditd service:
-$ sudo systemctl is-active auditd
-If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes audit_backlog_limit=8192,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
+The command should not return any output. Is it the case that audit backlog limit is not configured? |
Configure the operating system to initiate session audits at system start-up. |
- 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 |
- medium |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ low |
|
|
|
@@ -26826,6 +26826,42 @@
+
+ | CCI-001487 |
+ SRG-OS-000255-GPOS-00096 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must produce audit records containing information to establish the identity of any individual or process associated with the event. |
+
+ CCE-80872-5: Enable auditd Service |
+
+ Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine responsibility for the potentially harmful event. |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system produces audit records containing information to establish the identity of any individual or process associated with the event. If it does not, this is a finding. |
+
+
+Run the following command to determine the current status of the
+auditd service:
+$ sudo systemctl is-active auditd
+If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
+ Configure the operating system to produce audit records containing information to establish the identity of any individual or process associated with the event. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
| CCI-001487 |
SRG-OS-000255-GPOS-00096 |
@@ -26879,42 +26915,6 @@
|
-
- | CCI-001487 |
- SRG-OS-000255-GPOS-00096 |
- TBD - Assigned by DISA after STIG release |
- The operating system must produce audit records containing information to establish the identity of any individual or process associated with the event. |
-
- CCE-80872-5: Enable auditd Service |
-
- Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine responsibility for the potentially harmful event. |
- 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 |
- Applicable - Configurable |
- Verify the operating system produces audit records containing information to establish the identity of any individual or process associated with the event. If it does not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-auditd service:
-$ sudo systemctl is-active auditd
-If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
- Configure the operating system to produce audit records containing information to establish the identity of any individual or process associated with the event. |
- 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 |
- medium |
- |
- |
- |
-
-
@@ -26926,7 +26926,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit tools from unauthorized access. |
- CCE-86259-9: Audit Tools Must Be Owned by Root |
+ CCE-86239-1: Audit Tools Must Be Group-owned by Root |
Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information.
@@ -26937,14 +26937,14 @@
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.
-Audit tools must have the correct owner. |
+Audit tools must have the correct group owner.
Applicable - Configurable |
Verify the operating system protects audit tools from unauthorized access. If it does not, this is a finding. |
- Verify the audit tools are owned by "root" to prevent any unauthorized access, deletion, or modification.
+ | Verify the audit tools are group-owned by "root" to prevent any unauthorized access, deletion, or modification.
-Check the owner of each audit tool by running the following command:
+Check the group-owner of each audit tool by running the following command:
-$ sudo stat -c "%U %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules
+$ sudo stat -c "%G %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules
root /sbin/auditctl
root /sbin/aureport
@@ -26952,13 +26952,13 @@
root /sbin/autrace
root /sbin/auditd
root /sbin/rsyslogd
-root /sbin/augenrules Is it the case that any audit tools are not owned by root? |
+root /sbin/augenrules Is it the case that any audit tools are not group-owned by root?
Configure the operating system to protect audit tools from unauthorized access. |
Red Hat Enterprise Linux 8 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys, to make access decisions regarding the access to audit tools.
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.
-Audit tools must have the correct owner. |
+Audit tools must have the correct group owner.
medium |
|
|
@@ -27008,7 +27008,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit tools from unauthorized access. |
- CCE-86239-1: Audit Tools Must Be Group-owned by Root |
+ CCE-86259-9: Audit Tools Must Be Owned by Root |
Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information.
@@ -27019,14 +27019,14 @@
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.
-Audit tools must have the correct group owner. |
+Audit tools must have the correct owner.
Applicable - Configurable |
Verify the operating system protects audit tools from unauthorized access. If it does not, this is a finding. |
- Verify the audit tools are group-owned by "root" to prevent any unauthorized access, deletion, or modification.
+ | Verify the audit tools are owned by "root" to prevent any unauthorized access, deletion, or modification.
-Check the group-owner of each audit tool by running the following command:
+Check the owner of each audit tool by running the following command:
-$ sudo stat -c "%G %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules
+$ sudo stat -c "%U %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules
root /sbin/auditctl
root /sbin/aureport
@@ -27034,13 +27034,13 @@
root /sbin/autrace
root /sbin/auditd
root /sbin/rsyslogd
-root /sbin/augenrules Is it the case that any audit tools are not group-owned by root? |
+root /sbin/augenrules Is it the case that any audit tools are not owned by root?
Configure the operating system to protect audit tools from unauthorized access. |
Red Hat Enterprise Linux 8 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys, to make access decisions regarding the access to audit tools.
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.
-Audit tools must have the correct group owner. |
+Audit tools must have the correct owner.
medium |
|
|
@@ -27058,7 +27058,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit tools from unauthorized modification. |
- CCE-86259-9: Audit Tools Must Be Owned by Root |
+ CCE-86239-1: Audit Tools Must Be Group-owned by Root |
Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information.
@@ -27069,14 +27069,14 @@
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.
-Audit tools must have the correct owner. |
+Audit tools must have the correct group owner.
Applicable - Configurable |
Verify the operating system protects audit tools from unauthorized modification. If it does not, this is a finding. |
- Verify the audit tools are owned by "root" to prevent any unauthorized access, deletion, or modification.
+ | Verify the audit tools are group-owned by "root" to prevent any unauthorized access, deletion, or modification.
-Check the owner of each audit tool by running the following command:
+Check the group-owner of each audit tool by running the following command:
-$ sudo stat -c "%U %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules
+$ sudo stat -c "%G %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules
root /sbin/auditctl
root /sbin/aureport
@@ -27084,13 +27084,13 @@
root /sbin/autrace
root /sbin/auditd
root /sbin/rsyslogd
-root /sbin/augenrules Is it the case that any audit tools are not owned by root? |
+root /sbin/augenrules Is it the case that any audit tools are not group-owned by root?
Configure the operating system to protect audit tools from unauthorized modification. |
Red Hat Enterprise Linux 8 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys, to make access decisions regarding the access to audit tools.
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.
-Audit tools must have the correct owner. |
+Audit tools must have the correct group owner.
medium |
|
|
@@ -27140,7 +27140,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit tools from unauthorized modification. |
- CCE-86239-1: Audit Tools Must Be Group-owned by Root |
+ CCE-86259-9: Audit Tools Must Be Owned by Root |
Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information.
@@ -27151,14 +27151,14 @@
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.
-Audit tools must have the correct group owner. |
+Audit tools must have the correct owner.
Applicable - Configurable |
Verify the operating system protects audit tools from unauthorized modification. If it does not, this is a finding. |
- Verify the audit tools are group-owned by "root" to prevent any unauthorized access, deletion, or modification.
+ | Verify the audit tools are owned by "root" to prevent any unauthorized access, deletion, or modification.
-Check the group-owner of each audit tool by running the following command:
+Check the owner of each audit tool by running the following command:
-$ sudo stat -c "%G %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules
+$ sudo stat -c "%U %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules
root /sbin/auditctl
root /sbin/aureport
@@ -27166,13 +27166,13 @@
root /sbin/autrace
root /sbin/auditd
root /sbin/rsyslogd
-root /sbin/augenrules Is it the case that any audit tools are not group-owned by root? |
+root /sbin/augenrules Is it the case that any audit tools are not owned by root?
Configure the operating system to protect audit tools from unauthorized modification. |
Red Hat Enterprise Linux 8 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys, to make access decisions regarding the access to audit tools.
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.
-Audit tools must have the correct group owner. |
+Audit tools must have the correct owner.
medium |
|
|
@@ -27190,7 +27190,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit tools from unauthorized deletion. |
- CCE-86259-9: Audit Tools Must Be Owned by Root |
+ CCE-86239-1: Audit Tools Must Be Group-owned by Root |
Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information.
@@ -27201,14 +27201,14 @@
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.
-Audit tools must have the correct owner. |
+Audit tools must have the correct group owner.
Applicable - Configurable |
Verify the operating system protects audit tools from unauthorized deletion. If it does not, this is a finding. |
- Verify the audit tools are owned by "root" to prevent any unauthorized access, deletion, or modification.
+ | Verify the audit tools are group-owned by "root" to prevent any unauthorized access, deletion, or modification.
-Check the owner of each audit tool by running the following command:
+Check the group-owner of each audit tool by running the following command:
-$ sudo stat -c "%U %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules
+$ sudo stat -c "%G %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules
root /sbin/auditctl
root /sbin/aureport
@@ -27216,13 +27216,13 @@
root /sbin/autrace
root /sbin/auditd
root /sbin/rsyslogd
-root /sbin/augenrules Is it the case that any audit tools are not owned by root? |
+root /sbin/augenrules Is it the case that any audit tools are not group-owned by root?
Configure the operating system to protect audit tools from unauthorized deletion. |
Red Hat Enterprise Linux 8 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys, to make access decisions regarding the access to audit tools.
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.
-Audit tools must have the correct owner. |
+Audit tools must have the correct group owner.
medium |
|
|
@@ -27272,7 +27272,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect audit tools from unauthorized deletion. |
- CCE-86239-1: Audit Tools Must Be Group-owned by Root |
+ CCE-86259-9: Audit Tools Must Be Owned by Root |
Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information.
@@ -27283,14 +27283,14 @@
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.
-Audit tools must have the correct group owner. |
+Audit tools must have the correct owner.
Applicable - Configurable |
Verify the operating system protects audit tools from unauthorized deletion. If it does not, this is a finding. |
- Verify the audit tools are group-owned by "root" to prevent any unauthorized access, deletion, or modification.
+ | Verify the audit tools are owned by "root" to prevent any unauthorized access, deletion, or modification.
-Check the group-owner of each audit tool by running the following command:
+Check the owner of each audit tool by running the following command:
-$ sudo stat -c "%G %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules
+$ sudo stat -c "%U %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules
root /sbin/auditctl
root /sbin/aureport
@@ -27298,13 +27298,13 @@
root /sbin/autrace
root /sbin/auditd
root /sbin/rsyslogd
-root /sbin/augenrules Is it the case that any audit tools are not group-owned by root? |
+root /sbin/augenrules Is it the case that any audit tools are not owned by root?
Configure the operating system to protect audit tools from unauthorized deletion. |
Red Hat Enterprise Linux 8 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys, to make access decisions regarding the access to audit tools.
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.
-Audit tools must have the correct group owner. |
+Audit tools must have the correct owner.
medium |
|
|
@@ -27316,57 +27316,6 @@
-
- | CCI-001499 |
- SRG-OS-000259-GPOS-00100 |
- TBD - Assigned by DISA after STIG release |
- The operating system must limit privileges to change software resident within software libraries. |
-
- CCE-80815-4: Verify that Shared Library Files Have Restrictive Permissions |
-
- 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 libraries that 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 shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. |
- 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 |
- Applicable - Configurable |
- Verify the operating system limits privileges to change software resident within software libraries. If it does not, this is a finding. |
- Verify the system-wide shared library files contained in the following directories have mode "755" or less permissive with the following command:
-
-$ sudo find -L /lib /lib64 /usr/lib /usr/lib64 -perm /022 -type f -exec ls -l {} \; Is it the case that any system-wide shared library file is found to be group-writable or world-writable? |
- Configure the operating system to limit privileges to change software resident within software libraries. |
- 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 |
- medium |
- |
- |
- |
-
-
| CCI-001499 |
SRG-OS-000259-GPOS-00100 |
@@ -27468,12 +27417,12 @@
TBD - Assigned by DISA after STIG release |
The operating system must limit privileges to change software resident within software libraries. |
- CCE-88692-9: Verify that Shared Library Directories Have Restrictive Permissions |
+ CCE-80815-4: Verify that Shared Library Files Have Restrictive Permissions |
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 libraries that 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 shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. |
- System-wide shared library directories, which contain are linked to executables
+ | 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
@@ -27482,24 +27431,18 @@
/usr/lib64
Kernel modules, which can be added to the kernel during runtime, are
-stored in /lib/modules. All sub-directories in these directories
+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 DIR |
+$ sudo chmod go-w FILE
Applicable - Configurable |
Verify the operating system limits privileges to change software resident within software libraries. If it does not, this is a finding. |
- Shared libraries are stored in the following directories:
-/lib
-/lib64
-/usr/lib
-/usr/lib64
-
-To find shared libraries that are group-writable or world-writable,
-run the following command for each directory DIR which contains shared libraries:
-$ sudo find -L DIR -perm /022 -type d Is it the case that any of these files are group-writable or world-writable? |
+ Verify the system-wide shared library files contained in the following directories have mode "755" or less permissive with the following command:
+
+$ sudo find -L /lib /lib64 /usr/lib /usr/lib64 -perm /022 -type f -exec ls -l {} \; Is it the case that any system-wide shared library file is found to be group-writable or world-writable? |
Configure the operating system to limit privileges to change software resident within software libraries. |
- System-wide shared library directories, which contain are linked to executables
+ | 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
@@ -27508,62 +27451,11 @@
/usr/lib64
Kernel modules, which can be added to the kernel during runtime, are
-stored in /lib/modules. All sub-directories in these directories
+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 DIR |
- medium |
- |
- |
- |
-
-
-
- | CCI-001499 |
- SRG-OS-000259-GPOS-00100 |
- TBD - Assigned by DISA after STIG release |
- The operating system must limit privileges to change software resident within software libraries. |
-
- CCE-86519-6: Verify that system commands files are group owned by root or a system account |
-
- 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 libraries that 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 shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. |
- 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,
-or a system account.
-If the directory, or any file in these directories, is found to be owned
-by a group other than root or a a system account correct its ownership
-with the following command:
-$ sudo chgrp root FILE |
- Applicable - Configurable |
- Verify the operating system limits privileges to change software resident within software libraries. If it does not, this is a finding. |
- Verify the system commands contained in the following directories are group-owned by "root", or a required system account, with the following command:
-
-$ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -exec ls -l {} \; Is it the case that any system commands are returned and is not group-owned by a required system account? |
- Configure the operating system to limit privileges to change software resident within software libraries. |
- 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,
-or a system account.
-If the directory, or any file in these directories, is found to be owned
-by a group other than root or a a system account correct its ownership
-with the following command:
-$ sudo chgrp root FILE |
+$ sudo chmod go-w FILE
medium |
|
|
@@ -27576,7 +27468,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must limit privileges to change software resident within software libraries. |
- CCE-89021-0: Verify that Shared Library Directories Have Root Ownership |
+ CCE-85894-4: Verify that Shared Library Directories Have Root Group Ownership |
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.
@@ -27591,15 +27483,17 @@
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
+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 chown root DIR |
+$ sudo chgrp root DIR
Applicable - Configurable |
Verify the operating system limits privileges to change software resident within software libraries. If it does not, this is a finding. |
- Verify the system-wide shared library directories are owned by "root" with the following command:
+ | Verify the system-wide shared library directories are group-owned by "root" with the following command:
-$ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -user root -type d -exec stat -c "%n %U" '{}' \; Is it the case that any system-wide shared library directory is not owned by root? |
+$ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -group root -type d -exec stat -c "%n %G" '{}' \;
+
+If any system-wide shared library directory is returned and is not group-owned by a required system account, this is a finding. Is it the case that any system-wide shared library directory is returned and is not group-owned by a required system account?
Configure the operating system to limit privileges to change software resident within software libraries. |
System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
@@ -27611,10 +27505,10 @@
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
+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 chown root DIR |
+$ sudo chgrp root DIR
medium |
|
|
@@ -27727,7 +27621,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must limit privileges to change software resident within software libraries. |
- CCE-85894-4: Verify that Shared Library Directories Have Root Group Ownership |
+ CCE-89021-0: Verify that Shared Library Directories Have Root Ownership |
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.
@@ -27742,17 +27636,15 @@
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
+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 |
+$ sudo chown root DIR
Applicable - Configurable |
Verify the operating system limits privileges to change software resident within software libraries. If it does not, this is a finding. |
- Verify the system-wide shared library directories are group-owned by "root" with the following command:
-
-$ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -group root -type d -exec stat -c "%n %G" '{}' \;
+ | Verify the system-wide shared library directories are owned by "root" with the following command:
-If any system-wide shared library directory is returned and is not group-owned by a required system account, this is a finding. Is it the case that any system-wide shared library directory is returned and is not group-owned by a required system account? |
+$ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -user root -type d -exec stat -c "%n %U" '{}' \; Is it the case that any system-wide shared library directory is not owned by root?
Configure the operating system to limit privileges to change software resident within software libraries. |
System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
@@ -27764,10 +27656,118 @@
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
+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 |
+$ sudo chown root DIR
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-001499 |
+ SRG-OS-000259-GPOS-00100 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must limit privileges to change software resident within software libraries. |
+
+ CCE-86519-6: Verify that system commands files are group owned by root or a system account |
+
+ 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 libraries that 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 shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. |
+ 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,
+or a system account.
+If the directory, or any file in these directories, is found to be owned
+by a group other than root or a a system account correct its ownership
+with the following command:
+$ sudo chgrp root FILE |
+ Applicable - Configurable |
+ Verify the operating system limits privileges to change software resident within software libraries. If it does not, this is a finding. |
+ Verify the system commands contained in the following directories are group-owned by "root", or a required system account, with the following command:
+
+$ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -exec ls -l {} \; Is it the case that any system commands are returned and is not group-owned by a required system account? |
+ Configure the operating system to limit privileges to change software resident within software libraries. |
+ 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,
+or a system account.
+If the directory, or any file in these directories, is found to be owned
+by a group other than root or a a system account correct its ownership
+with the following command:
+$ sudo chgrp root FILE |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-001499 |
+ SRG-OS-000259-GPOS-00100 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must limit privileges to change software resident within software libraries. |
+
+ CCE-88692-9: Verify that Shared Library Directories Have Restrictive Permissions |
+
+ 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 libraries that 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 shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system limits privileges to change software resident within software libraries. If it does not, this is a finding. |
+ Shared libraries are stored in the following directories:
+/lib
+/lib64
+/usr/lib
+/usr/lib64
+
+To find shared libraries that are group-writable or world-writable,
+run the following command for each directory DIR which contains shared libraries:
+$ sudo find -L DIR -perm /022 -type d Is it the case that any of these files are group-writable or world-writable? |
+ Configure the operating system to limit privileges to change software resident within software libraries. |
+ 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 |
medium |
|
|
@@ -28166,60 +28166,6 @@
-
- | CCI-002361 |
- SRG-OS-000279-GPOS-00109 |
- TBD - Assigned by DISA after STIG release |
- The operating system must automatically terminate a user session after inactivity time-outs have expired or at shutdown. |
-
- CCE-80906-1: Set SSH Client Alive Interval |
-
- Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions.
-
-Session termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated.
-
-Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use.
-
-This capability is typically reserved for specific operating system functionality where the system owner, data owner, or organization requires additional assurance. |
- SSH allows administrators to set a network responsiveness timeout interval.
-After this interval has passed, the unresponsive client will be automatically logged out.
-
-To set this timeout interval, edit the following line in /etc/ssh/sshd_config as
-follows:
-ClientAliveInterval
-
-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. |
- Applicable - Configurable |
- Verify the operating system automatically terminates a user session after inactivity time-outs have expired or at shutdown. If it does not, this is a finding. |
- Run the following command to see what the timeout interval is:
-$ sudo grep ClientAliveInterval /etc/ssh/sshd_config
-If properly configured, the output should be:
-ClientAliveInterval Is it the case that it is commented out or not configured properly? |
- Configure the operating system to automatically terminate a user session after inactivity time-outs have expired or at shutdown. |
- SSH allows administrators to set a network responsiveness timeout interval.
-After this interval has passed, the unresponsive client will be automatically logged out.
-
-To set this timeout interval, edit the following line in /etc/ssh/sshd_config as
-follows:
-ClientAliveInterval
-
-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. |
- medium |
- |
- |
- |
-
-
| CCI-002361 |
SRG-OS-000279-GPOS-00109 |
@@ -28279,6 +28225,60 @@
|
+
+ | CCI-002361 |
+ SRG-OS-000279-GPOS-00109 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must automatically terminate a user session after inactivity time-outs have expired or at shutdown. |
+
+ CCE-80906-1: Set SSH Client Alive Interval |
+
+ Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions.
+
+Session termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated.
+
+Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use.
+
+This capability is typically reserved for specific operating system functionality where the system owner, data owner, or organization requires additional assurance. |
+ SSH allows administrators to set a network responsiveness timeout interval.
+After this interval has passed, the unresponsive client will be automatically logged out.
+
+To set this timeout interval, edit the following line in /etc/ssh/sshd_config as
+follows:
+ClientAliveInterval
+
+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. |
+ Applicable - Configurable |
+ Verify the operating system automatically terminates a user session after inactivity time-outs have expired or at shutdown. If it does not, this is a finding. |
+ Run the following command to see what the timeout interval is:
+$ sudo grep ClientAliveInterval /etc/ssh/sshd_config
+If properly configured, the output should be:
+ClientAliveInterval Is it the case that it is commented out or not configured properly? |
+ Configure the operating system to automatically terminate a user session after inactivity time-outs have expired or at shutdown. |
+ SSH allows administrators to set a network responsiveness timeout interval.
+After this interval has passed, the unresponsive client will be automatically logged out.
+
+To set this timeout interval, edit the following line in /etc/ssh/sshd_config as
+follows:
+ClientAliveInterval
+
+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. |
+ medium |
+ |
+ |
+ |
+
+
@@ -28332,35 +28332,6 @@
-
- | CCI-002314 |
- SRG-OS-000297-GPOS-00115 |
- TBD - Assigned by DISA after STIG release |
- The operating system must control remote access methods. |
-
- CCE-82998-6: Install firewalld Package |
-
- Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best.
-
-Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
-
-Operating system functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets). |
- The firewalld package can be installed with the following command:
-
-$ sudo yum install firewalld |
- Applicable - Configurable |
- Verify the operating system controls remote access methods. If it does not, this is a finding. |
- Run the following command to determine if the firewalld package is installed: $ rpm -q firewalld Is it the case that the package is not installed? |
- Configure the operating system to control remote access methods. |
- The firewalld package can be installed with the following command:
-
-$ sudo yum install firewalld |
- medium |
- |
- |
- |
-
-
| CCI-002314 |
SRG-OS-000297-GPOS-00115 |
@@ -28435,6 +28406,35 @@
|
+
+ | CCI-002314 |
+ SRG-OS-000297-GPOS-00115 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must control remote access methods. |
+
+ CCE-82998-6: Install firewalld Package |
+
+ Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+
+Operating system functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets). |
+ The firewalld package can be installed with the following command:
+
+$ sudo yum install firewalld |
+ Applicable - Configurable |
+ Verify the operating system controls remote access methods. If it does not, this is a finding. |
+ Run the following command to determine if the firewalld package is installed: $ rpm -q firewalld Is it the case that the package is not installed? |
+ Configure the operating system to control remote access methods. |
+ The firewalld package can be installed with the following command:
+
+$ sudo yum install firewalld |
+ medium |
+ |
+ |
+ |
+
+
@@ -28625,47 +28625,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account enabling actions. |
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes.
To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
- 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
-
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers -p wa -k actions
Applicable - Configurable |
Verify the operating system automatically audits account enabling actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+$ sudo auditctl -l | grep /etc/sudoers
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account enabling actions. |
- 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
-
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers -p wa -k actions
medium |
|
|
@@ -28731,97 +28723,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account enabling actions. |
- CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
-
- Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes.
-
-To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
-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:
--w /etc/sudoers.d/ -p wa -k actions |
- Applicable - Configurable |
- Verify the operating system automatically audits account enabling actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-
-$ sudo auditctl -l | grep/etc/sudoers.d
-
--w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to automatically audit account enabling actions. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
-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:
--w /etc/sudoers.d/ -p wa -k actions |
- medium |
- |
- |
- |
-
-
-
- | CCI-002130 |
- SRG-OS-000303-GPOS-00120 |
- TBD - Assigned by DISA after STIG release |
- The operating system must audit all account enabling actions. |
-
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
-
- Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes.
-
-To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
-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:
--w /etc/sudoers -p wa -k actions |
- Applicable - Configurable |
- Verify the operating system automatically audits account enabling actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-
-$ sudo auditctl -l | grep /etc/sudoers
-
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to automatically audit account enabling actions. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
-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:
--w /etc/sudoers -p wa -k actions |
- medium |
- |
- |
- |
-
-
-
- | CCI-002130 |
- SRG-OS-000303-GPOS-00120 |
- TBD - Assigned by DISA after STIG release |
- The operating system must audit all account enabling actions. |
-
- CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes.
@@ -28832,21 +28734,21 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system automatically audits account enabling actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
--w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account enabling actions. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -28854,14 +28756,14 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -28874,47 +28776,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all account enabling actions. |
- CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+ CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes.
To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
- 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
-
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers.d/ -p wa -k actions
Applicable - Configurable |
Verify the operating system automatically audits account enabling actions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/group)'
+$ sudo auditctl -l | grep/etc/sudoers.d
--w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to automatically audit account enabling actions. |
- 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
-
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers.d/ -p wa -k actions
medium |
|
|
@@ -28976,22 +28870,68 @@
|
+
+ | CCI-002130 |
+ SRG-OS-000303-GPOS-00120 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must audit all account enabling actions. |
+
+ CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+ Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes.
+To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system automatically audits account enabling actions. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+-w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to automatically audit account enabling actions. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
- | CCI-002132 |
- SRG-OS-000304-GPOS-00121 |
+ CCI-002130 |
+ SRG-OS-000303-GPOS-00120 |
TBD - Assigned by DISA after STIG release |
- The operating system must notify system administrators and ISSOs of account enabling actions. |
-
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ The operating system must audit all account enabling actions. |
- Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable an existing disabled account. Sending notification of account enabling actions to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.
+ | CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
-In order to detect and respond to events that affect user accessibility and application processing, operating systems must audit account enabling actions and, as required, notify the appropriate individuals so they can investigate the event.
+ Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes.
To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
If the auditd daemon is configured to use the
@@ -29000,49 +28940,101 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/group -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
- Verify the operating system notifies the System Administrator and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify the operating system automatically audits account enabling actions. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+$ sudo auditctl -l | grep -E '(/etc/group)'
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to notify the System Administrator(s) and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. |
+-w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
+ Configure the operating system to automatically audit account enabling actions. |
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
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/group -p wa -k audit_rules_usergroup_modification
medium |
|
|
|
+
+
+
+
+
| CCI-002132 |
SRG-OS-000304-GPOS-00121 |
TBD - Assigned by DISA after STIG release |
The operating system must notify system administrators and ISSOs of account enabling actions. |
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+
+ Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable an existing disabled account. Sending notification of account enabling actions to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.
+
+In order to detect and respond to events that affect user accessibility and application processing, operating systems must audit account enabling actions and, as required, notify the appropriate individuals so they can investigate the event.
+
+To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
+ At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
+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:
+-w /etc/sudoers -p wa -k actions |
+ Applicable - Configurable |
+ Verify the operating system notifies the System Administrator and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+
+$ sudo auditctl -l | grep /etc/sudoers
+
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to notify the System Administrator(s) and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. |
+ At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
+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:
+-w /etc/sudoers -p wa -k actions |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-002132 |
+ SRG-OS-000304-GPOS-00121 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must notify system administrators and ISSOs of account enabling actions. |
+
+ CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable an existing disabled account. Sending notification of account enabling actions to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.
@@ -29055,21 +29047,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system notifies the System Administrator and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+$ sudo auditctl -l | grep -E '(/etc/shadow)'
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out?
Configure the operating system to notify the System Administrator(s) and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -29077,14 +29069,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -29097,7 +29089,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must notify system administrators and ISSOs of account enabling actions. |
- CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable an existing disabled account. Sending notification of account enabling actions to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.
@@ -29110,21 +29102,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/shadow -p wa -k audit_rules_usergroup_modification
+-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/shadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system notifies the System Administrator and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/shadow)'
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
--w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to notify the System Administrator(s) and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -29132,14 +29124,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/shadow -p wa -k audit_rules_usergroup_modification
+-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/shadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -29152,41 +29144,49 @@
TBD - Assigned by DISA after STIG release |
The operating system must notify system administrators and ISSOs of account enabling actions. |
- CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable an existing disabled account. Sending notification of account enabling actions to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.
In order to detect and respond to events that affect user accessibility and application processing, operating systems must audit account enabling actions and, as required, notify the appropriate individuals so they can investigate the event.
To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
+ | 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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers.d/ -p wa -k actions |
+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
Applicable - Configurable |
Verify the operating system notifies the System Administrator and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-$ sudo auditctl -l | grep/etc/sudoers.d
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
--w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to notify the System Administrator(s) and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
+ | 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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers.d/ -p wa -k actions |
+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
medium |
|
|
@@ -29199,7 +29199,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must notify system administrators and ISSOs of account enabling actions. |
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+ CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable an existing disabled account. Sending notification of account enabling actions to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.
@@ -29211,29 +29211,29 @@
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:
--w /etc/sudoers -p wa -k actions
+-w /etc/sudoers.d/ -p wa -k actions
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:
--w /etc/sudoers -p wa -k actions |
+-w /etc/sudoers.d/ -p wa -k actions
Applicable - Configurable |
Verify the operating system notifies the System Administrator and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-$ sudo auditctl -l | grep /etc/sudoers
+$ sudo auditctl -l | grep/etc/sudoers.d
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to notify the System Administrator(s) and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. |
At a minimum, the audit system should collect administrator actions
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:
--w /etc/sudoers -p wa -k actions
+-w /etc/sudoers.d/ -p wa -k actions
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:
--w /etc/sudoers -p wa -k actions |
+-w /etc/sudoers.d/ -p wa -k actions
medium |
|
|
@@ -29246,7 +29246,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must notify system administrators and ISSOs of account enabling actions. |
- CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+ CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable an existing disabled account. Sending notification of account enabling actions to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.
@@ -29259,21 +29259,23 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system notifies the System Administrator and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
--w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes?
Configure the operating system to notify the System Administrator(s) and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -29281,14 +29283,14 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -29301,7 +29303,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must notify system administrators and ISSOs of account enabling actions. |
- CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+ CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable an existing disabled account. Sending notification of account enabling actions to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.
@@ -29314,21 +29316,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/group -p wa -k audit_rules_usergroup_modification
+-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/group -p wa -k audit_rules_usergroup_modification |
+-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system notifies the System Administrator and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/group)'
+$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
--w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to notify the System Administrator(s) and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -29336,14 +29338,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/group -p wa -k audit_rules_usergroup_modification
+-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/group -p wa -k audit_rules_usergroup_modification |
+-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -29356,7 +29358,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must notify system administrators and ISSOs of account enabling actions. |
- CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
+ CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to enable an existing disabled account. Sending notification of account enabling actions to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.
@@ -29369,23 +29371,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification
+-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/gshadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/group -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system notifies the System Administrator and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
--w /etc/gshadow -p wa -k identity
+$ sudo auditctl -l | grep -E '(/etc/group)'
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
+-w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to notify the System Administrator(s) and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -29393,14 +29393,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification
+-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/gshadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/group -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -29418,23 +29418,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must allow operating system admins to pass information to any other operating system admin or user. |
- CCE-81030-9: Enable Kernel Parameter to Enforce DAC on Symlinks |
+ CCE-81027-5: Enable Kernel Parameter to Enforce DAC on Hardlinks |
Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions.
When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control. |
- To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
+ To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
Applicable - Configurable |
Verify the operating system allows operating system admins to pass information to any other operating system admin or user. If it does not, this is a finding. |
- The runtime status of the fs.protected_symlinks kernel parameter can be queried
+ | The runtime status of the fs.protected_hardlinks kernel parameter can be queried
by running the following command:
-$ sysctl fs.protected_symlinks
+$ sysctl fs.protected_hardlinks
1.
Is it the case that the correct value is not returned? |
Configure the operating system to allow operating system admins to pass information to any other operating system admin or user. |
- To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
+ To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
medium |
|
|
@@ -29447,23 +29447,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must allow operating system admins to pass information to any other operating system admin or user. |
- CCE-81027-5: Enable Kernel Parameter to Enforce DAC on Hardlinks |
+ CCE-81030-9: Enable Kernel Parameter to Enforce DAC on Symlinks |
Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions.
When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control. |
- To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
+ To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
Applicable - Configurable |
Verify the operating system allows operating system admins to pass information to any other operating system admin or user. If it does not, this is a finding. |
- The runtime status of the fs.protected_hardlinks kernel parameter can be queried
+ | The runtime status of the fs.protected_symlinks kernel parameter can be queried
by running the following command:
-$ sysctl fs.protected_hardlinks
+$ sysctl fs.protected_symlinks
1.
Is it the case that the correct value is not returned? |
Configure the operating system to allow operating system admins to pass information to any other operating system admin or user. |
- To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
+ To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
medium |
|
|
@@ -29481,23 +29481,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must allow operating system admins to grant their privileges to other operating system admins. |
- CCE-81030-9: Enable Kernel Parameter to Enforce DAC on Symlinks |
+ CCE-81027-5: Enable Kernel Parameter to Enforce DAC on Hardlinks |
Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions.
When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control. |
- To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
+ To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
Applicable - Configurable |
Verify the operating system allows operating system admins to grant their privileges to other operating system admins. If it does not, this is a finding. |
- The runtime status of the fs.protected_symlinks kernel parameter can be queried
+ | The runtime status of the fs.protected_hardlinks kernel parameter can be queried
by running the following command:
-$ sysctl fs.protected_symlinks
+$ sysctl fs.protected_hardlinks
1.
Is it the case that the correct value is not returned? |
Configure the operating system to allow operating system admins to grant their privileges to other operating system admins. |
- To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
+ To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
medium |
|
|
@@ -29510,23 +29510,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must allow operating system admins to grant their privileges to other operating system admins. |
- CCE-81027-5: Enable Kernel Parameter to Enforce DAC on Hardlinks |
+ CCE-81030-9: Enable Kernel Parameter to Enforce DAC on Symlinks |
Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions.
When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control. |
- To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
+ To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
Applicable - Configurable |
Verify the operating system allows operating system admins to grant their privileges to other operating system admins. If it does not, this is a finding. |
- The runtime status of the fs.protected_hardlinks kernel parameter can be queried
+ | The runtime status of the fs.protected_symlinks kernel parameter can be queried
by running the following command:
-$ sysctl fs.protected_hardlinks
+$ sysctl fs.protected_symlinks
1.
Is it the case that the correct value is not returned? |
Configure the operating system to allow operating system admins to grant their privileges to other operating system admins. |
- To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
+ To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
medium |
|
|
@@ -29562,6 +29562,117 @@
+
+ | CCI-002235 |
+ SRG-OS-000324-GPOS-00125 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
+
+ CCE-81027-5: Enable Kernel Parameter to Enforce DAC on Hardlinks |
+
+ Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
+
+Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. |
+ To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
+ Applicable - Configurable |
+ Verify that the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. If it does not, this is a finding. |
+ The runtime status of the fs.protected_hardlinks kernel parameter can be queried
+by running the following command:
+$ sysctl fs.protected_hardlinks
+1.
+ Is it the case that the correct value is not returned? |
+ Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
+ To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-002235 |
+ SRG-OS-000324-GPOS-00125 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
+
+ CCE-81030-9: Enable Kernel Parameter to Enforce DAC on Symlinks |
+
+ Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
+
+Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. |
+ To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
+ Applicable - Configurable |
+ Verify that the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. If it does not, this is a finding. |
+ The runtime status of the fs.protected_symlinks kernel parameter can be queried
+by running the following command:
+$ sysctl fs.protected_symlinks
+1.
+ Is it the case that the correct value is not returned? |
+ Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
+ To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-002235 |
+ SRG-OS-000324-GPOS-00125 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
+
+ CCE-80785-9: Disable Ctrl-Alt-Del Reboot Activation |
+
+ Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
+
+Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. |
+ 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. |
+ Applicable - Configurable |
+ Verify that the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. If it does not, this is a finding. |
+ To ensure the system is configured to mask the Ctrl-Alt-Del sequence, Check
+that the ctrl-alt-del.target is masked and not active with the following
+command:
+sudo systemctl status ctrl-alt-del.target
+The output should indicate that the target is masked and not active. It
+might resemble following output:
+ctrl-alt-del.target
+Loaded: masked (/dev/null; bad)
+Active: inactive (dead) Is it the case that the system is configured to reboot when Ctrl-Alt-Del is pressed? |
+ Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
+ 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. |
+ high |
+ |
+ |
+ |
+
+
| CCI-002235 |
SRG-OS-000324-GPOS-00125 |
@@ -29631,24 +29742,64 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
- CCE-81030-9: Enable Kernel Parameter to Enforce DAC on Symlinks |
+ CCE-82361-7: Prevent user from disabling the screen lock |
Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. |
- To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
+ The tmux terminal multiplexer is used to implement
+automatic session locking. It should not be listed in
+/etc/shells. |
Applicable - Configurable |
Verify that the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. If it does not, this is a finding. |
- The runtime status of the fs.protected_symlinks kernel parameter can be queried
-by running the following command:
-$ sysctl fs.protected_symlinks
-1.
- Is it the case that the correct value is not returned? |
+ To verify that tmux is not listed as allowed shell on the system
+run the following command:
+$ grep 'tmux$' /etc/shells
+The output should be empty. Is it the case that tmux is listed in /etc/shells? |
Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
- To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
- medium |
+ The tmux terminal multiplexer is used to implement
+automatic session locking. It should not be listed in
+/etc/shells. |
+ low |
+ |
+ |
+ |
+
+
+
+ | CCI-002235 |
+ SRG-OS-000324-GPOS-00125 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
+
+ CCE-80784-2: Disable Ctrl-Alt-Del Burst Action |
+
+ Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
+
+Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. |
+ By default, SystemD will reboot the system if the Ctrl-Alt-Del
+key sequence is pressed Ctrl-Alt-Delete more than 7 times in 2 seconds.
+
+To configure the system to ignore the CtrlAltDelBurstAction
+
+setting, add or modify the following to /etc/systemd/system.conf:
+CtrlAltDelBurstAction=none |
+ Applicable - Configurable |
+ Verify that the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. If it does not, this is a finding. |
+ To ensure the system is configured to ignore the Ctrl-Alt-Del setting,
+enter the following command:
+$ sudo grep -i ctrlaltdelburstaction /etc/systemd/system.conf
+The output should return:
+CtrlAltDelBurstAction=none Is it the case that the system is configured to reboot when Ctrl-Alt-Del is pressed more than 7 times in 2 seconds.? |
+ Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
+ By default, SystemD will reboot the system if the Ctrl-Alt-Del
+key sequence is pressed Ctrl-Alt-Delete more than 7 times in 2 seconds.
+
+To configure the system to ignore the CtrlAltDelBurstAction
+
+setting, add or modify the following to /etc/systemd/system.conf:
+CtrlAltDelBurstAction=none |
+ high |
|
|
|
@@ -29709,157 +29860,6 @@
|
-
- | CCI-002235 |
- SRG-OS-000324-GPOS-00125 |
- TBD - Assigned by DISA after STIG release |
- The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
-
- CCE-80784-2: Disable Ctrl-Alt-Del Burst Action |
-
- Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
-
-Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. |
- By default, SystemD will reboot the system if the Ctrl-Alt-Del
-key sequence is pressed Ctrl-Alt-Delete more than 7 times in 2 seconds.
-
-To configure the system to ignore the CtrlAltDelBurstAction
-
-setting, add or modify the following to /etc/systemd/system.conf:
-CtrlAltDelBurstAction=none |
- Applicable - Configurable |
- Verify that the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. If it does not, this is a finding. |
- To ensure the system is configured to ignore the Ctrl-Alt-Del setting,
-enter the following command:
-$ sudo grep -i ctrlaltdelburstaction /etc/systemd/system.conf
-The output should return:
-CtrlAltDelBurstAction=none Is it the case that the system is configured to reboot when Ctrl-Alt-Del is pressed more than 7 times in 2 seconds.? |
- Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
- By default, SystemD will reboot the system if the Ctrl-Alt-Del
-key sequence is pressed Ctrl-Alt-Delete more than 7 times in 2 seconds.
-
-To configure the system to ignore the CtrlAltDelBurstAction
-
-setting, add or modify the following to /etc/systemd/system.conf:
-CtrlAltDelBurstAction=none |
- high |
- |
- |
- |
-
-
-
- | CCI-002235 |
- SRG-OS-000324-GPOS-00125 |
- TBD - Assigned by DISA after STIG release |
- The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
-
- CCE-80785-9: Disable Ctrl-Alt-Del Reboot Activation |
-
- Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
-
-Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. |
- 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. |
- Applicable - Configurable |
- Verify that the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. If it does not, this is a finding. |
- To ensure the system is configured to mask the Ctrl-Alt-Del sequence, Check
-that the ctrl-alt-del.target is masked and not active with the following
-command:
-sudo systemctl status ctrl-alt-del.target
-The output should indicate that the target is masked and not active. It
-might resemble following output:
-ctrl-alt-del.target
-Loaded: masked (/dev/null; bad)
-Active: inactive (dead) Is it the case that the system is configured to reboot when Ctrl-Alt-Del is pressed? |
- Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
- 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. |
- high |
- |
- |
- |
-
-
-
- | CCI-002235 |
- SRG-OS-000324-GPOS-00125 |
- TBD - Assigned by DISA after STIG release |
- The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
-
- CCE-81027-5: Enable Kernel Parameter to Enforce DAC on Hardlinks |
-
- Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
-
-Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. |
- To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
- Applicable - Configurable |
- Verify that the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. If it does not, this is a finding. |
- The runtime status of the fs.protected_hardlinks kernel parameter can be queried
-by running the following command:
-$ sysctl fs.protected_hardlinks
-1.
- Is it the case that the correct value is not returned? |
- Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
- To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
- medium |
- |
- |
- |
-
-
-
- | CCI-002235 |
- SRG-OS-000324-GPOS-00125 |
- TBD - Assigned by DISA after STIG release |
- The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
-
- CCE-82361-7: Prevent user from disabling the screen lock |
-
- Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
-
-Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. |
- The tmux terminal multiplexer is used to implement
-automatic session locking. It should not be listed in
-/etc/shells. |
- Applicable - Configurable |
- Verify that the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. If it does not, this is a finding. |
- To verify that tmux is not listed as allowed shell on the system
-run the following command:
-$ grep 'tmux$' /etc/shells
-The output should be empty. Is it the case that tmux is listed in /etc/shells? |
- Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
- The tmux terminal multiplexer is used to implement
-automatic session locking. It should not be listed in
-/etc/shells. |
- low |
- |
- |
- |
-
-
@@ -30112,84 +30112,32 @@
TBD - Assigned by DISA after STIG release |
The operating system must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes occur. |
- CCE-80669-5: Set Interval For Counting Failed Password Attempts |
+ CCE-80668-7: Configure the root Account for Failed Password Attempts |
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account. |
- Utilizing pam_faillock.so, the fail_interval directive configures the system
-to lock out an account after a number of incorrect login attempts within a specified time
-period.
-
-Ensure that the file /etc/security/faillock.conf contains the following entry:
-fail_interval = <interval-in-seconds> where interval-in-seconds is or greater.
-
+ | This rule configures the system to lock out the root account after a number of
+incorrect login attempts using pam_faillock.so.
-In order to avoid errors when manually editing these files, it is
+pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
+defined to work as expected. In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig,
depending on the OS version. |
Applicable - Configurable |
Verify the operating system automatically locks an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made. If it does not, this is a finding. |
- To ensure the failed password attempt policy is configured correctly, run the following command:
-
-$ grep fail_interval /etc/security/faillock.conf
-The output should show fail_interval = <interval-in-seconds> where interval-in-seconds is or greater. Is it the case that the "fail_interval" option is not set to ""
-or less (but not "0"), the line is commented out, or the line is missing? |
- Configure the operating system to automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made. |
- Utilizing pam_faillock.so, the fail_interval directive configures the system
-to lock out an account after a number of incorrect login attempts within a specified time
-period.
-
-Ensure that the file /etc/security/faillock.conf contains the following entry:
-fail_interval = <interval-in-seconds> where interval-in-seconds is or greater.
-
-
-In order to avoid errors when manually editing these files, it is
-recommended to use the appropriate tools, such as authselect or authconfig,
-depending on the OS version. |
- medium |
- |
- |
- |
-
-
-
- | CCI-002238 |
- SRG-OS-000329-GPOS-00128 |
- TBD - Assigned by DISA after STIG release |
- The operating system must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes occur. |
-
- CCE-86067-6: Lock Accounts Must Persist |
-
- By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account. |
- This rule ensures that the system lock out accounts using pam_faillock.so persist
-after system reboot. From "pam_faillock" man pages:
-Note that the default directory that "pam_faillock" uses is usually cleared on system
-boot so the access will be reenabled after system reboot. If that is undesirable, a different
-tally directory must be set with the "dir" option.
+ | Verify Red Hat Enterprise Linux 8 is configured to lock the root account after
+unsuccessful logon attempts with the command:
-pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
-defined to work as expected. In order to avoid errors when manually editing these files, it is
-recommended to use the appropriate tools, such as authselect or authconfig,
-depending on the OS version.
-The chosen profile expects the directory to be . |
- Applicable - Configurable |
- Verify the operating system automatically locks an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made. If it does not, this is a finding. |
- To ensure the tally directory is configured correctly, run the following command:
-$ sudo grep 'dir =' /etc/security/faillock.conf
-The output should show that dir is set to something other than "/var/run/faillock" Is it the case that the "dir" option is not set to a non-default documented tally log directory, is missing or commented out? |
+$ grep even_deny_root /etc/security/faillock.conf
+even_deny_root Is it the case that the "even_deny_root" option is not set, is missing or commented out?
Configure the operating system to automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made. |
- This rule ensures that the system lock out accounts using pam_faillock.so persist
-after system reboot. From "pam_faillock" man pages:
-Note that the default directory that "pam_faillock" uses is usually cleared on system
-boot so the access will be reenabled after system reboot. If that is undesirable, a different
-tally directory must be set with the "dir" option.
+ | This rule configures the system to lock out the root account after a number of
+incorrect login attempts using pam_faillock.so.
pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig,
-depending on the OS version.
-
-The chosen profile expects the directory to be . |
+depending on the OS version.
medium |
|
|
@@ -30260,30 +30208,37 @@
TBD - Assigned by DISA after STIG release |
The operating system must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes occur. |
- CCE-80668-7: Configure the root Account for Failed Password Attempts |
+ CCE-80669-5: Set Interval For Counting Failed Password Attempts |
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account. |
- This rule configures the system to lock out the root account after a number of
-incorrect login attempts using pam_faillock.so.
+ | Utilizing pam_faillock.so, the fail_interval directive configures the system
+to lock out an account after a number of incorrect login attempts within a specified time
+period.
-pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
-defined to work as expected. In order to avoid errors when manually editing these files, it is
+Ensure that the file /etc/security/faillock.conf contains the following entry:
+fail_interval = <interval-in-seconds> where interval-in-seconds is or greater.
+
+
+In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig,
depending on the OS version. |
Applicable - Configurable |
Verify the operating system automatically locks an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 is configured to lock the root account after
-unsuccessful logon attempts with the command:
-
+ | To ensure the failed password attempt policy is configured correctly, run the following command:
-$ grep even_deny_root /etc/security/faillock.conf
-even_deny_root Is it the case that the "even_deny_root" option is not set, is missing or commented out? |
+$ grep fail_interval /etc/security/faillock.conf
+The output should show fail_interval = <interval-in-seconds> where interval-in-seconds is or greater. Is it the case that the "fail_interval" option is not set to ""
+or less (but not "0"), the line is commented out, or the line is missing?
Configure the operating system to automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made. |
- This rule configures the system to lock out the root account after a number of
-incorrect login attempts using pam_faillock.so.
+ | Utilizing pam_faillock.so, the fail_interval directive configures the system
+to lock out an account after a number of incorrect login attempts within a specified time
+period.
-pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
-defined to work as expected. In order to avoid errors when manually editing these files, it is
+Ensure that the file /etc/security/faillock.conf contains the following entry:
+fail_interval = <interval-in-seconds> where interval-in-seconds is or greater.
+
+
+In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig,
depending on the OS version. |
medium |
@@ -30292,34 +30247,56 @@
|
-
-
-
-
-
- | CCI-001914 |
- SRG-OS-000337-GPOS-00129 |
+ CCI-002238 |
+ SRG-OS-000329-GPOS-00128 |
TBD - Assigned by DISA after STIG release |
- The operating system must provide the capability for assigned IMOs/ISSOs or designated SAs to change the auditing to be performed on all operating system components, based on all selectable event criteria in near real time. |
+ The operating system must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes occur. |
- CCE-81043-2: Ensure the audit Subsystem is Installed |
+ CCE-86067-6: Lock Accounts Must Persist |
- If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not be able to effectively respond, and important forensic information may be lost.
+ | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account. |
+ This rule ensures that the system lock out accounts using pam_faillock.so persist
+after system reboot. From "pam_faillock" man pages:
+Note that the default directory that "pam_faillock" uses is usually cleared on system
+boot so the access will be reenabled after system reboot. If that is undesirable, a different
+tally directory must be set with the "dir" option.
-This requirement enables organizations to extend or limit auditing as necessary to meet organizational requirements. Auditing that is limited to conserve information system resources may be extended to address certain threat situations. In addition, auditing may be limited to a specific set of events to facilitate audit reduction, analysis, and reporting. |
- The audit package should be installed. |
+pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
+defined to work as expected. In order to avoid errors when manually editing these files, it is
+recommended to use the appropriate tools, such as authselect or authconfig,
+depending on the OS version.
+
+The chosen profile expects the directory to be .
Applicable - Configurable |
- Verify the operating system provides the capability for assigned IMOs/ISSOs or designated SAs to change the auditing to be performed on all operating system components, based on all selectable event criteria in near real time. If it does not, this is a finding. |
- Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Configure the operating system to provide the capability for assigned IMOs/ISSOs or designated SAs to change the auditing to be performed on all operating system components, based on all selectable event criteria in near real time. |
- The audit package should be installed. |
+ Verify the operating system automatically locks an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made. If it does not, this is a finding. |
+ To ensure the tally directory is configured correctly, run the following command:
+$ sudo grep 'dir =' /etc/security/faillock.conf
+The output should show that dir is set to something other than "/var/run/faillock" Is it the case that the "dir" option is not set to a non-default documented tally log directory, is missing or commented out? |
+ Configure the operating system to automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made. |
+ This rule ensures that the system lock out accounts using pam_faillock.so persist
+after system reboot. From "pam_faillock" man pages:
+Note that the default directory that "pam_faillock" uses is usually cleared on system
+boot so the access will be reenabled after system reboot. If that is undesirable, a different
+tally directory must be set with the "dir" option.
+
+pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
+defined to work as expected. In order to avoid errors when manually editing these files, it is
+recommended to use the appropriate tools, such as authselect or authconfig,
+depending on the OS version.
+
+The chosen profile expects the directory to be . |
medium |
|
|
|
+
+
+
+
+
| CCI-001914 |
SRG-OS-000337-GPOS-00129 |
@@ -30358,6 +30335,29 @@
|
+
+ | CCI-001914 |
+ SRG-OS-000337-GPOS-00129 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must provide the capability for assigned IMOs/ISSOs or designated SAs to change the auditing to be performed on all operating system components, based on all selectable event criteria in near real time. |
+
+ CCE-81043-2: Ensure the audit Subsystem is Installed |
+
+ If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not be able to effectively respond, and important forensic information may be lost.
+
+This requirement enables organizations to extend or limit auditing as necessary to meet organizational requirements. Auditing that is limited to conserve information system resources may be extended to address certain threat situations. In addition, auditing may be limited to a specific set of events to facilitate audit reduction, analysis, and reporting. |
+ The audit package should be installed. |
+ Applicable - Configurable |
+ Verify the operating system provides the capability for assigned IMOs/ISSOs or designated SAs to change the auditing to be performed on all operating system components, based on all selectable event criteria in near real time. If it does not, this is a finding. |
+ Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+ Configure the operating system to provide the capability for assigned IMOs/ISSOs or designated SAs to change the auditing to be performed on all operating system components, based on all selectable event criteria in near real time. |
+ The audit package should be installed. |
+ medium |
+ |
+ |
+ |
+
+
@@ -30413,6 +30413,42 @@
|
+
+ | CCI-001849 |
+ SRG-OS-000341-GPOS-00132 |
+ TBD - Assigned by DISA after STIG release |
+ The 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. |
+
+ CCE-80854-3: Ensure /var/log/audit Located On Separate Partition |
+
+ In order to ensure operating systems have a sufficient storage capacity in which to write the audit logs, operating systems need to be able to allocate audit record storage capacity.
+
+The task of allocating audit record storage capacity is usually performed during initial installation of the operating system. |
+ 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. |
+ Applicable - Configurable |
+ Verify the operating system allocates audit record storage capacity to store at least one week's worth of audit records, when audit records are not immediately sent to a central audit record storage facility. If it does not, this is a finding. |
+ Verify that a separate file system/partition has been created for /var/log/audit with the following command:
+
+$ mountpoint /var/log/audit
+ Is it the case that "/var/log/audit is not a mountpoint" is returned? |
+ Configure the operating system to allocate audit record storage capacity to store at least one week's worth of audit records, when audit records are not immediately sent to a central audit record storage facility. |
+ 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. |
+ low |
+ |
+ |
+ |
+
+
| CCI-001849 |
SRG-OS-000341-GPOS-00132 |
@@ -30495,42 +30531,6 @@
|
-
- | CCI-001849 |
- SRG-OS-000341-GPOS-00132 |
- TBD - Assigned by DISA after STIG release |
- The 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. |
-
- CCE-80854-3: Ensure /var/log/audit Located On Separate Partition |
-
- In order to ensure operating systems have a sufficient storage capacity in which to write the audit logs, operating systems need to be able to allocate audit record storage capacity.
-
-The task of allocating audit record storage capacity is usually performed during initial installation of the operating system. |
- 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. |
- Applicable - Configurable |
- Verify the operating system allocates audit record storage capacity to store at least one week's worth of audit records, when audit records are not immediately sent to a central audit record storage facility. If it does not, this is a finding. |
- Verify that a separate file system/partition has been created for /var/log/audit with the following command:
-
-$ mountpoint /var/log/audit
- Is it the case that "/var/log/audit is not a mountpoint" is returned? |
- Configure the operating system to allocate audit record storage capacity to store at least one week's worth of audit records, when audit records are not immediately sent to a central audit record storage facility. |
- 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. |
- low |
- |
- |
- |
-
-
@@ -30618,7 +30618,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must off-load audit records onto a different system or media from the system being audited. |
- CCE-86339-9: Ensure Rsyslog Authenticates Off-Loaded Audit Records |
+ CCE-86098-1: Ensure Rsyslog Encrypts Off-Loaded Audit Records |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
@@ -30629,14 +30629,17 @@
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.
-When using rsyslogd to off-load logs the remote system must be authenticated. |
+When using rsyslogd to off-load logs off a encrpytion system must be used.
Applicable - Configurable |
Verify the operating system off-loads audit records onto a different system or media from the system being audited. If it does not, this is a finding. |
- Verify the operating system authenticates the remote logging server for off-loading audit logs with the following command:
+ | Verify the operating system encrypts audit records off-loaded onto a different system
+or media from the system being audited with the following commands:
-$ sudo grep -i '$ActionSendStreamDriverAuthMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf
-The output should be
-$/etc/rsyslog.conf:$ActionSendStreamDriverAuthMode x509/name Is it the case that $ActionSendStreamDriverAuthMode in /etc/rsyslog.conf is not set to x509/name? |
+$ sudo grep -i '$ActionSendStreamDriverMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf
+
+The output should be:
+
+/etc/rsyslog.conf:$ActionSendStreamDriverMode 1
Is it the case that rsyslogd ActionSendStreamDriverMode is not set to 1?
Configure the operating system to off-load audit records onto a different system or media from the system being audited. |
Rsyslogd is a system utility providing support for message logging. Support
for both internet and UNIX domain sockets enables this utility to support both local
@@ -30644,7 +30647,79 @@
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.
-When using rsyslogd to off-load logs the remote system must be authenticated. |
+When using rsyslogd to off-load logs off a encrpytion system must be used.
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-001851 |
+ SRG-OS-000342-GPOS-00133 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must off-load audit records onto a different system or media from the system being audited. |
+
+ CCE-80863-4: Ensure Logs Sent To Remote Host |
+
+ 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. |
+ 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 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:
+*.* @
+
+To use TCP for log message delivery:
+*.* @@
+
+To use RELP for log message delivery:
+*.* :omrelp:
+
+There must be a resolvable DNS CNAME or Alias record set to "" for logs to be sent correctly to the centralized logging utility. |
+ Applicable - Configurable |
+ Verify the operating system off-loads audit records onto a different system or media from the system being audited. If it does not, this is a finding. |
+ To ensure logs are sent to a remote host, examine the file
+/etc/rsyslog.conf.
+If using UDP, a line similar to the following should be present:
+ *.* @
+If using TCP, a line similar to the following should be present:
+ *.* @@
+If using RELP, a line similar to the following should be present:
+ *.* :omrelp: Is it the case that no evidence that the audit logs are being off-loaded to another system or media? |
+ Configure the operating system to off-load audit records onto a different system or media from the system being audited. |
+ 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 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:
+*.* @
+
+To use TCP for log message delivery:
+*.* @@
+
+To use RELP for log message delivery:
+*.* :omrelp:
+
+There must be a resolvable DNS CNAME or Alias record set to "" for logs to be sent correctly to the centralized logging utility. |
medium |
|
|
@@ -30690,18 +30765,57 @@
TBD - Assigned by DISA after STIG release |
The operating system must off-load audit records onto a different system or media from the system being audited. |
- CCE-84005-8: Configure a Sufficiently Large Partition for Audit Logs |
+ CCE-86339-9: Ensure Rsyslog Authenticates Off-Loaded Audit Records |
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. |
- The Red Hat Enterprise Linux 8 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.
+ | Rsyslogd is a system utility providing support for message logging. Support
+for both internet and UNIX domain sockets enables this utility to support both local
+and remote logging. Couple this utility with gnutls (which is a secure communications
+library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
+encrypt and off-load auditing.
-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
+When using rsyslogd to off-load logs the remote system must be authenticated. |
+ Applicable - Configurable |
+ Verify the operating system off-loads audit records onto a different system or media from the system being audited. If it does not, this is a finding. |
+ Verify the operating system authenticates the remote logging server for off-loading audit logs with the following command:
+
+$ sudo grep -i '$ActionSendStreamDriverAuthMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf
+The output should be
+$/etc/rsyslog.conf:$ActionSendStreamDriverAuthMode x509/name Is it the case that $ActionSendStreamDriverAuthMode in /etc/rsyslog.conf is not set to x509/name? |
+ Configure the operating system to off-load audit records onto a different system or media from the system being audited. |
+ Rsyslogd is a system utility providing support for message logging. Support
+for both internet and UNIX domain sockets enables this utility to support both local
+and remote logging. Couple this utility with gnutls (which is a secure communications
+library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
+encrypt and off-load auditing.
+
+When using rsyslogd to off-load logs the remote system must be authenticated. |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-001851 |
+ SRG-OS-000342-GPOS-00133 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must off-load audit records onto a different system or media from the system being audited. |
+
+ CCE-84005-8: Configure a Sufficiently Large Partition for Audit Logs |
+
+ 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. |
+ The Red Hat Enterprise Linux 8 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.
@@ -30766,120 +30880,6 @@
| |
-
- | CCI-001851 |
- SRG-OS-000342-GPOS-00133 |
- TBD - Assigned by DISA after STIG release |
- The operating system must off-load audit records onto a different system or media from the system being audited. |
-
- CCE-80863-4: Ensure Logs Sent To Remote Host |
-
- 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. |
- 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 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:
-*.* @
-
-To use TCP for log message delivery:
-*.* @@
-
-To use RELP for log message delivery:
-*.* :omrelp:
-
-There must be a resolvable DNS CNAME or Alias record set to "" for logs to be sent correctly to the centralized logging utility. |
- Applicable - Configurable |
- Verify the operating system off-loads audit records onto a different system or media from the system being audited. If it does not, this is a finding. |
- To ensure logs are sent to a remote host, examine the file
-/etc/rsyslog.conf.
-If using UDP, a line similar to the following should be present:
- *.* @
-If using TCP, a line similar to the following should be present:
- *.* @@
-If using RELP, a line similar to the following should be present:
- *.* :omrelp: Is it the case that no evidence that the audit logs are being off-loaded to another system or media? |
- Configure the operating system to off-load audit records onto a different system or media from the system being audited. |
- 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 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:
-*.* @
-
-To use TCP for log message delivery:
-*.* @@
-
-To use RELP for log message delivery:
-*.* :omrelp:
-
-There must be a resolvable DNS CNAME or Alias record set to "" for logs to be sent correctly to the centralized logging utility. |
- medium |
- |
- |
- |
-
-
-
- | CCI-001851 |
- SRG-OS-000342-GPOS-00133 |
- TBD - Assigned by DISA after STIG release |
- The operating system must off-load audit records onto a different system or media from the system being audited. |
-
- CCE-86098-1: Ensure Rsyslog Encrypts Off-Loaded Audit Records |
-
- 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. |
- Rsyslogd is a system utility providing support for message logging. Support
-for both internet and UNIX domain sockets enables this utility to support both local
-and remote logging. Couple this utility with gnutls (which is a secure communications
-library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
-encrypt and off-load auditing.
-
-When using rsyslogd to off-load logs off a encrpytion system must be used. |
- Applicable - Configurable |
- Verify the operating system off-loads audit records onto a different system or media from the system being audited. If it does not, this is a finding. |
- Verify the operating system encrypts audit records off-loaded onto a different system
-or media from the system being audited with the following commands:
-
-$ sudo grep -i '$ActionSendStreamDriverMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf
-
-The output should be:
-
-/etc/rsyslog.conf:$ActionSendStreamDriverMode 1 Is it the case that rsyslogd ActionSendStreamDriverMode is not set to 1? |
- Configure the operating system to off-load audit records onto a different system or media from the system being audited. |
- Rsyslogd is a system utility providing support for message logging. Support
-for both internet and UNIX domain sockets enables this utility to support both local
-and remote logging. Couple this utility with gnutls (which is a secure communications
-library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
-encrypt and off-load auditing.
-
-When using rsyslogd to off-load logs off a encrpytion system must be used. |
- medium |
- |
- |
- |
-
-
@@ -30891,31 +30891,27 @@
TBD - Assigned by DISA after STIG release |
The operating system must immediately notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity. |
- CCE-86055-1: Configure auditd space_left on Low Disk Space |
+ CCE-80678-6: Configure auditd mail_acct Action on Low Disk Space |
If security personnel are not notified immediately when storage volume reaches 75% utilization, they are unable to plan for audit record storage capacity expansion. |
- 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 PERCENTAGE appropriately:
-space_left = PERCENTAGE%
-Set this value to at least 25 to cause the system to
-notify the user of an issue. |
+ 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 = |
Applicable - Configurable |
Verify the operating system immediately notifies the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 takes action when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to notify the SA and/or ISSO (at a minimum) in the event of an audit processing failure with the following command:
-$ sudo grep -w space_left /etc/audit/auditd.conf
+$ sudo grep action_mail_acct /etc/audit/auditd.conf
-space_left = % Is it the case that the value of the "space_left" keyword is not set to % of the storage volume allocated to audit logs, or if the line is commented out, ask the System Administrator to indicate how the system is providing real-time alerts to the SA and ISSO. If the "space_left" value is not configured to the correct value? |
+action_mail_acct =
Is it the case that the value of the "action_mail_acct" keyword is not set to "
" and/or other accounts for security personnel, the "action_mail_acct" keyword is missing, or the retuned line is commented out, ask the system administrator to indicate how they and the ISSO are notified of an audit process failure. If there is no evidence of the proper personnel being notified of an audit processing failure?
Configure the operating system to immediately notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity. |
-
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 PERCENTAGE appropriately:
-space_left = PERCENTAGE%
-Set this value to at least 25 to cause the system to
-notify the user of an issue. |
+
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 = |
medium |
|
|
@@ -30989,27 +30985,31 @@
TBD - Assigned by DISA after STIG release |
The operating system must immediately notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity. |
-
CCE-80678-6: Configure auditd mail_acct Action on Low Disk Space |
+
CCE-86055-1: Configure auditd space_left on Low Disk Space |
If security personnel are not notified immediately when storage volume reaches 75% utilization, they are unable to plan for audit record storage capacity expansion. |
-
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 = |
+
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 PERCENTAGE appropriately:
+space_left = PERCENTAGE%
+Set this value to at least 25 to cause the system to
+notify the user of an issue. |
Applicable - Configurable |
Verify the operating system immediately notifies the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity. If it does not, this is a finding. |
-
Verify that Red Hat Enterprise Linux 8 is configured to notify the SA and/or ISSO (at a minimum) in the event of an audit processing failure with the following command:
+ | Verify Red Hat Enterprise Linux 8 takes action when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity with the following command:
-$ sudo grep action_mail_acct /etc/audit/auditd.conf
+$ sudo grep -w space_left /etc/audit/auditd.conf
-action_mail_acct = Is it the case that the value of the "action_mail_acct" keyword is not set to "" and/or other accounts for security personnel, the "action_mail_acct" keyword is missing, or the retuned line is commented out, ask the system administrator to indicate how they and the ISSO are notified of an audit process failure. If there is no evidence of the proper personnel being notified of an audit processing failure? |
+
space_left = %
Is it the case that the value of the "space_left" keyword is not set to
% of the storage volume allocated to audit logs, or if the line is commented out, ask the System Administrator to indicate how the system is providing real-time alerts to the SA and ISSO. If the "space_left" value is not configured to the correct value?
Configure the operating system to immediately notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity. |
-
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 = |
+
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 PERCENTAGE appropriately:
+space_left = PERCENTAGE%
+Set this value to at least 25 to cause the system to
+notify the user of an issue. |
medium |
|
|
@@ -31045,29 +31045,6 @@
-
- | CCI-001875 |
- SRG-OS-000348-GPOS-00136 |
- TBD - Assigned by DISA after STIG release |
- The operating system must provide an audit reduction capability that supports on-demand audit review and analysis. |
-
- CCE-81043-2: Ensure the audit Subsystem is Installed |
-
- The ability to perform on-demand audit review and analysis, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports, as needed, to better handle larger-scale or more complex security incidents.
-
-Audit reduction is a technique used to reduce the volume of audit records in order to facilitate a manual review. Audit reduction does not alter original audit records. The report generation capability provided by the application must support on-demand (i.e., customizable, ad hoc, and as-needed) reports. |
- The audit package should be installed. |
- Applicable - Configurable |
- Verify the operating system provides an audit reduction capability that supports on-demand audit review and analysis. If it does not, this is a finding. |
- Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Configure the operating system to provide an audit reduction capability that supports on-demand audit review and analysis. |
- The audit package should be installed. |
- medium |
- |
- |
- |
-
-
| CCI-001875 |
SRG-OS-000348-GPOS-00136 |
@@ -31106,29 +31083,22 @@
|
-
-
-
-
-
- | CCI-001877 |
- SRG-OS-000349-GPOS-00137 |
+ CCI-001875 |
+ SRG-OS-000348-GPOS-00136 |
TBD - Assigned by DISA after STIG release |
- The operating system must provide an audit reduction capability that supports after-the-fact investigations of security incidents. |
+ The operating system must provide an audit reduction capability that supports on-demand audit review and analysis. |
CCE-81043-2: Ensure the audit Subsystem is Installed |
- If the audit reduction capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack or identify those responses for one. This capability is also required to comply with applicable Federal laws and DoD policies.
-
-Audit reduction capability must support after-the-fact investigations of security incidents either natively or through the use of third-party tools.
+ | The ability to perform on-demand audit review and analysis, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports, as needed, to better handle larger-scale or more complex security incidents.
-This requirement is specific to operating systems with audit reduction capabilities. |
+Audit reduction is a technique used to reduce the volume of audit records in order to facilitate a manual review. Audit reduction does not alter original audit records. The report generation capability provided by the application must support on-demand (i.e., customizable, ad hoc, and as-needed) reports.
The audit package should be installed. |
Applicable - Configurable |
- Verify the operating system provides an audit reduction capability that supports after-the-fact investigations of security incidents. If it does not, this is a finding. |
+ Verify the operating system provides an audit reduction capability that supports on-demand audit review and analysis. If it does not, this is a finding. |
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Configure the operating system to provide an audit reduction capability that supports after-the-fact investigations of security incidents. |
+ Configure the operating system to provide an audit reduction capability that supports on-demand audit review and analysis. |
The audit package should be installed. |
medium |
|
@@ -31136,6 +31106,11 @@
|
+
+
+
+
+
| CCI-001877 |
SRG-OS-000349-GPOS-00137 |
@@ -31176,27 +31151,24 @@
|
-
-
-
-
-
- | CCI-001878 |
- SRG-OS-000350-GPOS-00138 |
+ CCI-001877 |
+ SRG-OS-000349-GPOS-00137 |
TBD - Assigned by DISA after STIG release |
- The operating system must provide a report generation capability that supports on-demand audit review and analysis. |
+ The operating system must provide an audit reduction capability that supports after-the-fact investigations of security incidents. |
CCE-81043-2: Ensure the audit Subsystem is Installed |
- The report generation capability must support on-demand review and analysis in order to facilitate the organization's ability to generate incident reports, as needed, to better handle larger-scale or more complex security incidents.
+ | If the audit reduction capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack or identify those responses for one. This capability is also required to comply with applicable Federal laws and DoD policies.
-Report generation must be capable of generating on-demand (i.e., customizable, ad hoc, and as-needed) reports. On-demand reporting allows personnel to report issues more rapidly to more effectively meet reporting requirements. Collecting log data and aggregating it to present the data in a single, consolidated report achieves this objective. |
+Audit reduction capability must support after-the-fact investigations of security incidents either natively or through the use of third-party tools.
+
+This requirement is specific to operating systems with audit reduction capabilities.
The audit package should be installed. |
Applicable - Configurable |
- Verify the operating system provides a report generation capability that supports on-demand audit review and analysis. If it does not, this is a finding. |
+ Verify the operating system provides an audit reduction capability that supports after-the-fact investigations of security incidents. If it does not, this is a finding. |
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Configure the operating system to provide a report generation capability that supports on-demand audit review and analysis. |
+ Configure the operating system to provide an audit reduction capability that supports after-the-fact investigations of security incidents. |
The audit package should be installed. |
medium |
|
@@ -31204,6 +31176,11 @@
|
+
+
+
+
+
| CCI-001878 |
SRG-OS-000350-GPOS-00138 |
@@ -31242,27 +31219,22 @@
|
-
-
-
-
-
- | CCI-001879 |
- SRG-OS-000351-GPOS-00139 |
+ CCI-001878 |
+ SRG-OS-000350-GPOS-00138 |
TBD - Assigned by DISA after STIG release |
- The operating system must provide a report generation capability that supports on-demand reporting requirements. |
+ The operating system must provide a report generation capability that supports on-demand audit review and analysis. |
CCE-81043-2: Ensure the audit Subsystem is Installed |
- The report generation capability must support on-demand reporting in order to facilitate the organization's ability to generate incident reports, as needed, to better handle larger-scale or more complex security incidents.
+ | The report generation capability must support on-demand review and analysis in order to facilitate the organization's ability to generate incident reports, as needed, to better handle larger-scale or more complex security incidents.
Report generation must be capable of generating on-demand (i.e., customizable, ad hoc, and as-needed) reports. On-demand reporting allows personnel to report issues more rapidly to more effectively meet reporting requirements. Collecting log data and aggregating it to present the data in a single, consolidated report achieves this objective. |
The audit package should be installed. |
Applicable - Configurable |
- Verify the operating system provides a report generation capability that supports on-demand reporting requirements. If it does not, this is a finding. |
+ Verify the operating system provides a report generation capability that supports on-demand audit review and analysis. If it does not, this is a finding. |
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Ensure the operating system provides a report generation capability that supports on-demand reporting requirements. |
+ Configure the operating system to provide a report generation capability that supports on-demand audit review and analysis. |
The audit package should be installed. |
medium |
|
@@ -31270,6 +31242,11 @@
|
+
+
+
+
+
| CCI-001879 |
SRG-OS-000351-GPOS-00139 |
@@ -31308,27 +31285,22 @@
|
-
-
-
-
-
- | CCI-001880 |
- SRG-OS-000352-GPOS-00140 |
+ CCI-001879 |
+ SRG-OS-000351-GPOS-00139 |
TBD - Assigned by DISA after STIG release |
- The operating system must provide a report generation capability that supports after-the-fact investigations of security incidents. |
+ The operating system must provide a report generation capability that supports on-demand reporting requirements. |
CCE-81043-2: Ensure the audit Subsystem is Installed |
- If the report generation capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack or identify those responses for one. This capability is also required to comply with applicable Federal laws and DoD policies.
+ | The report generation capability must support on-demand reporting in order to facilitate the organization's ability to generate incident reports, as needed, to better handle larger-scale or more complex security incidents.
-The report generation capability must support after-the-fact investigations of security incidents either natively or through the use of third-party tools. |
+Report generation must be capable of generating on-demand (i.e., customizable, ad hoc, and as-needed) reports. On-demand reporting allows personnel to report issues more rapidly to more effectively meet reporting requirements. Collecting log data and aggregating it to present the data in a single, consolidated report achieves this objective.
The audit package should be installed. |
Applicable - Configurable |
- Verify the operating system provides a report generation capability that supports after-the-fact investigations of security incidents. If it does not, this is a finding. |
+ Verify the operating system provides a report generation capability that supports on-demand reporting requirements. If it does not, this is a finding. |
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Ensure the operating system provides a report generation capability that supports after-the-fact investigations of security incidents. |
+ Ensure the operating system provides a report generation capability that supports on-demand reporting requirements. |
The audit package should be installed. |
medium |
|
@@ -31336,6 +31308,11 @@
|
+
+
+
+
+
| CCI-001880 |
SRG-OS-000352-GPOS-00140 |
@@ -31374,29 +31351,22 @@
|
-
-
-
-
-
- | CCI-001881 |
- SRG-OS-000353-GPOS-00141 |
+ CCI-001880 |
+ SRG-OS-000352-GPOS-00140 |
TBD - Assigned by DISA after STIG release |
- The operating system must not alter original content or time ordering of audit records when it provides an audit reduction capability. |
+ The operating system must provide a report generation capability that supports after-the-fact investigations of security incidents. |
CCE-81043-2: Ensure the audit Subsystem is Installed |
- If the audit reduction capability alters the content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic analysis.
-
-Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. Time ordering refers to the chronological organization of records based on time stamps. The degree of time stamp precision can affect this.
+ | If the report generation capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack or identify those responses for one. This capability is also required to comply with applicable Federal laws and DoD policies.
-This requirement is specific to operating systems providing audit reduction capabilities. The audit reduction capability can be met either natively or through the use of third-party tools. |
+The report generation capability must support after-the-fact investigations of security incidents either natively or through the use of third-party tools.
The audit package should be installed. |
Applicable - Configurable |
- Verify the operating system does not alter original content or time ordering of audit records when it provides an audit reduction capability. If it does not, this is a finding. |
+ Verify the operating system provides a report generation capability that supports after-the-fact investigations of security incidents. If it does not, this is a finding. |
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Configure the operating system to not alter original content or time ordering of audit records when it provides an audit reduction capability. |
+ Ensure the operating system provides a report generation capability that supports after-the-fact investigations of security incidents. |
The audit package should be installed. |
medium |
|
@@ -31404,6 +31374,11 @@
|
+
+
+
+
+
| CCI-001881 |
SRG-OS-000353-GPOS-00141 |
@@ -31444,29 +31419,24 @@
|
-
-
-
-
-
- | CCI-001882 |
- SRG-OS-000354-GPOS-00142 |
+ CCI-001881 |
+ SRG-OS-000353-GPOS-00141 |
TBD - Assigned by DISA after STIG release |
- The operating system must not alter original content or time ordering of audit records when it provides a report generation capability. |
+ The operating system must not alter original content or time ordering of audit records when it provides an audit reduction capability. |
CCE-81043-2: Ensure the audit Subsystem is Installed |
- If the report generation capability alters the content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic analysis.
+ | If the audit reduction capability alters the content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic analysis.
-Time ordering refers to the chronological organization of records based on time stamps. The degree of time stamp precision can affect this.
+Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. Time ordering refers to the chronological organization of records based on time stamps. The degree of time stamp precision can affect this.
-This requirement is specific to operating systems providing report generation capabilities. The report generation capability can be met either natively or through the use of third-party tools. |
+This requirement is specific to operating systems providing audit reduction capabilities. The audit reduction capability can be met either natively or through the use of third-party tools.
The audit package should be installed. |
Applicable - Configurable |
- Verify the operating system does not alter original content or time ordering of audit records when it provides a report generation capability. If it does not, this is a finding. |
+ Verify the operating system does not alter original content or time ordering of audit records when it provides an audit reduction capability. If it does not, this is a finding. |
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Configure the operating system to not alter original content or time ordering of audit records when it provides a report generation capability. |
+ Configure the operating system to not alter original content or time ordering of audit records when it provides an audit reduction capability. |
The audit package should be installed. |
medium |
|
@@ -31474,6 +31444,11 @@
|
+
+
+
+
+
| CCI-001882 |
SRG-OS-000354-GPOS-00142 |
@@ -31514,11 +31489,63 @@
|
+
+ | CCI-001882 |
+ SRG-OS-000354-GPOS-00142 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must not alter original content or time ordering of audit records when it provides a report generation capability. |
+
+ CCE-81043-2: Ensure the audit Subsystem is Installed |
+
+ If the report generation capability alters the content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic analysis.
+
+Time ordering refers to the chronological organization of records based on time stamps. The degree of time stamp precision can affect this.
+
+This requirement is specific to operating systems providing report generation capabilities. The report generation capability can be met either natively or through the use of third-party tools. |
+ The audit package should be installed. |
+ Applicable - Configurable |
+ Verify the operating system does not alter original content or time ordering of audit records when it provides a report generation capability. If it does not, this is a finding. |
+ Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+ Configure the operating system to not alter original content or time ordering of audit records when it provides a report generation capability. |
+ The audit package should be installed. |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-001891 |
+ SRG-OS-000355-GPOS-00143 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). |
+
+ CCE-86077-5: Ensure Chrony is only configured with the server directive |
+
+ Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate.
+
+Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network.
+
+Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). |
+ Check that Chrony only has time sources configured with the server directive. |
+ Applicable - Configurable |
+ Verify the operating system, for networked systems, compares internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). If it does not, this is a finding. |
+ Run the following command and verify that time sources are only configured with server directive:
+# grep -E "^(server|pool)" /etc/chrony.conf
+A line with the appropriate server should be returned, any line returned starting with pool is a finding. Is it the case that an authoritative remote time server is not configured or configured with pool directive? |
+ Configure the operating system to, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). |
+ Check that Chrony only has time sources configured with the server directive. |
+ medium |
+ |
+ |
+ |
+
+
| CCI-001891 |
SRG-OS-000355-GPOS-00143 |
@@ -31564,26 +31591,31 @@
|
+
+
+
+
+
- | CCI-001891 |
- SRG-OS-000355-GPOS-00143 |
+ CCI-002046 |
+ SRG-OS-000356-GPOS-00144 |
TBD - Assigned by DISA after STIG release |
- The operating system must, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). |
+ The operating system must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second. |
CCE-86077-5: Ensure Chrony is only configured with the server directive |
- Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate.
+ | Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events.
-Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network.
+Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider setting time periods for different types of systems (e.g., financial, legal, or mission-critical systems).
-Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). |
+Organizations should also consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). This requirement is related to the comparison done every 24 hours in SRG-OS-000355 because a comparison must be done in order to determine the time difference.
Check that Chrony only has time sources configured with the server directive. |
Applicable - Configurable |
- Verify the operating system, for networked systems, compares internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). If it does not, this is a finding. |
+ Verify the operating system synchronizes internal information system clocks to the authoritative time source when the time difference is greater than one second. If it does not, this is a finding. |
Run the following command and verify that time sources are only configured with server directive:
# grep -E "^(server|pool)" /etc/chrony.conf
A line with the appropriate server should be returned, any line returned starting with pool is a finding. Is it the case that an authoritative remote time server is not configured or configured with pool directive? |
- Configure the operating system to, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). |
+ Configure the operating system to synchronize internal information system clocks to the authoritative time source when the time difference is greater than the organization-defined time period. |
Check that Chrony only has time sources configured with the server directive. |
medium |
|
@@ -31591,11 +31623,6 @@
|
-
-
-
-
-
| CCI-002046 |
SRG-OS-000356-GPOS-00144 |
@@ -31641,33 +31668,6 @@
|
-
- | CCI-002046 |
- SRG-OS-000356-GPOS-00144 |
- TBD - Assigned by DISA after STIG release |
- The operating system must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second. |
-
- CCE-86077-5: Ensure Chrony is only configured with the server directive |
-
- Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events.
-
-Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider setting time periods for different types of systems (e.g., financial, legal, or mission-critical systems).
-
-Organizations should also consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). This requirement is related to the comparison done every 24 hours in SRG-OS-000355 because a comparison must be done in order to determine the time difference. |
- Check that Chrony only has time sources configured with the server directive. |
- Applicable - Configurable |
- Verify the operating system synchronizes internal information system clocks to the authoritative time source when the time difference is greater than one second. If it does not, this is a finding. |
- Run the following command and verify that time sources are only configured with server directive:
-# grep -E "^(server|pool)" /etc/chrony.conf
-A line with the appropriate server should be returned, any line returned starting with pool is a finding. Is it the case that an authoritative remote time server is not configured or configured with pool directive? |
- Configure the operating system to synchronize internal information system clocks to the authoritative time source when the time difference is greater than the organization-defined time period. |
- Check that Chrony only has time sources configured with the server directive. |
- medium |
- |
- |
- |
-
-
@@ -31679,17 +31679,32 @@
TBD - Assigned by DISA after STIG release |
The operating system must record time stamps for audit records that meet a minimum granularity of one second for a minimum degree of precision. |
-
CCE-81043-2: Ensure the audit Subsystem is Installed |
+
CCE-80872-5: Enable auditd Service |
Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records.
Time stamps generated by the operating system include date and time. Granularity of time measurements refers to the degree of synchronization between information system clocks and reference clocks. |
-
The audit package should be installed. |
+
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 |
Applicable - Configurable |
Verify the operating system records time stamps for audit records that meet a minimum granularity of one second for a minimum degree of precision. If it does not, this is a finding. |
-
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+
+
+Run the following command to determine the current status of the
+auditd service:
+$ sudo systemctl is-active auditd
+If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
Configure the operating system to record time stamps for audit records that meet a minimum granularity of one second for a minimum degree of precision. |
-
The audit package should be installed. |
+
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 |
medium |
|
|
@@ -31702,32 +31717,17 @@
TBD - Assigned by DISA after STIG release |
The operating system must record time stamps for audit records that meet a minimum granularity of one second for a minimum degree of precision. |
-
CCE-80872-5: Enable auditd Service |
+
CCE-81043-2: Ensure the audit Subsystem is Installed |
Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records.
Time stamps generated by the operating system include date and time. Granularity of time measurements refers to the degree of synchronization between information system clocks and reference clocks. |
-
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 |
+
The audit package should be installed. |
Applicable - Configurable |
Verify the operating system records time stamps for audit records that meet a minimum granularity of one second for a minimum degree of precision. If it does not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-auditd service:
-$ sudo systemctl is-active auditd
-If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
+
Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
Configure the operating system to record time stamps for audit records that meet a minimum granularity of one second for a minimum degree of precision. |
-
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 |
+
The audit package should be installed. |
medium |
|
|
@@ -31739,6 +31739,31 @@
+
+ | CCI-001890 |
+ SRG-OS-000359-GPOS-00146 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). |
+
+ CCE-86077-5: Ensure Chrony is only configured with the server directive |
+
+ If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
+
+Time stamps generated by the operating system include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. |
+ Check that Chrony only has time sources configured with the server directive. |
+ Applicable - Configurable |
+ Verify the operating system records time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). If it does not, this is a finding. |
+ Run the following command and verify that time sources are only configured with server directive:
+# grep -E "^(server|pool)" /etc/chrony.conf
+A line with the appropriate server should be returned, any line returned starting with pool is a finding. Is it the case that an authoritative remote time server is not configured or configured with pool directive? |
+ Configure the operating system to record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). |
+ Check that Chrony only has time sources configured with the server directive. |
+ medium |
+ |
+ |
+ |
+
+
| CCI-001890 |
SRG-OS-000359-GPOS-00146 |
@@ -31782,31 +31807,6 @@
|
-
- | CCI-001890 |
- SRG-OS-000359-GPOS-00146 |
- TBD - Assigned by DISA after STIG release |
- The operating system must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). |
-
- CCE-86077-5: Ensure Chrony is only configured with the server directive |
-
- If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
-
-Time stamps generated by the operating system include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. |
- Check that Chrony only has time sources configured with the server directive. |
- Applicable - Configurable |
- Verify the operating system records time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). If it does not, this is a finding. |
- Run the following command and verify that time sources are only configured with server directive:
-# grep -E "^(server|pool)" /etc/chrony.conf
-A line with the appropriate server should be returned, any line returned starting with pool is a finding. Is it the case that an authoritative remote time server is not configured or configured with pool directive? |
- Configure the operating system to record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). |
- Check that Chrony only has time sources configured with the server directive. |
- medium |
- |
- |
- |
-
-
@@ -31862,35 +31862,6 @@
-
- | CCI-001744 |
- SRG-OS-000363-GPOS-00150 |
- TBD - Assigned by DISA after STIG release |
- The operating system must notify designated personnel if baseline configurations are changed in an unauthorized manner. |
-
- CCE-87036-0: The mailx Package Is Installed |
-
- Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating system. Changes to operating system configurations can have unintended side effects, some of which may be 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 operating system. The operating system's IMO/ISSO and SAs must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item. |
- A mail server is required for sending emails.
-The mailx package can be installed with the following command:
-
-$ sudo yum install mailx |
- Applicable - Configurable |
- Verify the operating system notifies designated personnel if baseline configurations are changed in an unauthorized manner. If it does not, this is a finding. |
- Run the following command to determine if the mailx package is installed: $ rpm -q mailx Is it the case that the package is not installed? |
- Configure the operating system to notify designated personnel if baseline configurations are changed in an unauthorized manner. |
- A mail server is required for sending emails.
-The mailx package can be installed with the following command:
-
-$ sudo yum install mailx |
- medium |
- |
- |
- |
-
-
| CCI-001744 |
SRG-OS-000363-GPOS-00150 |
@@ -31931,6 +31902,35 @@
|
+
+ | CCI-001744 |
+ SRG-OS-000363-GPOS-00150 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must notify designated personnel if baseline configurations are changed in an unauthorized manner. |
+
+ CCE-87036-0: The mailx Package Is Installed |
+
+ Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating system. Changes to operating system configurations can have unintended side effects, some of which may be 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 operating system. The operating system's IMO/ISSO and SAs must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item. |
+ A mail server is required for sending emails.
+The mailx package can be installed with the following command:
+
+$ sudo yum install mailx |
+ Applicable - Configurable |
+ Verify the operating system notifies designated personnel if baseline configurations are changed in an unauthorized manner. If it does not, this is a finding. |
+ Run the following command to determine if the mailx package is installed: $ rpm -q mailx Is it the case that the package is not installed? |
+ Configure the operating system to notify designated personnel if baseline configurations are changed in an unauthorized manner. |
+ A mail server is required for sending emails.
+The mailx package can be installed with the following command:
+
+$ sudo yum install mailx |
+ medium |
+ |
+ |
+ |
+
+
@@ -32049,29 +32049,6 @@
-
- | CCI-001814 |
- SRG-OS-000365-GPOS-00152 |
- TBD - Assigned by DISA after STIG release |
- The operating system must audit the enforcement actions used to restrict access associated with changes to the system. |
-
- CCE-81043-2: Ensure the audit Subsystem is Installed |
-
- Without auditing the enforcement of access restrictions against changes to the application configuration, it will be difficult to identify attempted attacks and an audit trail will not be available for forensic investigation for after-the-fact actions.
-
-Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact. |
- The audit package should be installed. |
- Applicable - Configurable |
- Verify the operating system audits the enforcement actions used to restrict access associated with changes to the system. If it does not, this is a finding. |
- Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
- Configure the operating system to audit the enforcement actions used to restrict access associated with changes to the system. |
- The audit package should be installed. |
- medium |
- |
- |
- |
-
-
| CCI-001814 |
SRG-OS-000365-GPOS-00152 |
@@ -32110,85 +32087,33 @@
|
-
-
-
-
-
- | CCI-001749 |
- SRG-OS-000366-GPOS-00153 |
+ CCI-001814 |
+ SRG-OS-000365-GPOS-00152 |
TBD - Assigned by DISA after STIG release |
- The operating system must prevent the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. |
-
- CCE-80792-5: Ensure gpgcheck Enabled for All yum Package Repositories |
+ The operating system must audit the enforcement actions used to restrict access associated with changes to the system. |
- Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor.
+ | CCE-81043-2: Ensure the audit Subsystem is Installed |
-Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization.
+ Without auditing the enforcement of access restrictions against changes to the application configuration, it will be difficult to identify attempted attacks and an audit trail will not be available for forensic investigation for after-the-fact actions.
-Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA. |
- To ensure signature checking is not disabled for
-any repos, remove any lines from files in /etc/yum.repos.d of the form:
-gpgcheck=0 |
+Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.
+ The audit package should be installed. |
Applicable - Configurable |
- Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. If it does not, this is a finding. |
- To determine whether yum has been configured to disable
-gpgcheck for any repos, inspect all files in
-/etc/yum.repos.d and ensure the following does not appear in any
-sections:
-gpgcheck=0
-A value of 0 indicates that gpgcheck has been disabled for that repo. Is it the case that GPG checking is disabled? |
- Configure the operating system to prevent the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. |
- To ensure signature checking is not disabled for
-any repos, remove any lines from files in /etc/yum.repos.d of the form:
-gpgcheck=0 |
- high |
+ Verify the operating system audits the enforcement actions used to restrict access associated with changes to the system. If it does not, this is a finding. |
+ Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+ Configure the operating system to audit the enforcement actions used to restrict access associated with changes to the system. |
+ The audit package should be installed. |
+ medium |
|
|
|
-
- | CCI-001749 |
- SRG-OS-000366-GPOS-00153 |
- TBD - Assigned by DISA after STIG release |
- The operating system must prevent the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. |
- CCE-80790-9: Ensure gpgcheck Enabled In Main yum Configuration |
-
- Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor.
-
-Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization.
-
-Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA. |
- The gpgcheck option controls whether
-RPM packages' signatures are always checked prior to installation.
-To configure yum to check package signatures before installing
-them, ensure the following line appears in /etc/yum.conf in
-the [main] section:
-gpgcheck=1 |
- Applicable - Configurable |
- Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. If it does not, this is a finding. |
- Verify that yum verifies the signature of packages from a repository prior to install with the following command:
-$ grep gpgcheck /etc/yum.conf
-gpgcheck=1
-If "gpgcheck" is not set to "1", or if the option is missing or commented out, ask the System Administrator how the certificates for patches and other operating system components are verified. Is it the case that there is no process to validate certificates that is approved by the organization? |
- Configure the operating system to prevent the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. |
- The gpgcheck option controls whether
-RPM packages' signatures are always checked prior to installation.
-To configure yum to check package signatures before installing
-them, ensure the following line appears in /etc/yum.conf in
-the [main] section:
-gpgcheck=1 |
- high |
- |
- |
- |
-
| CCI-001749 |
@@ -32248,6 +32173,40 @@
|
+
+ | CCI-001749 |
+ SRG-OS-000366-GPOS-00153 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must prevent the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. |
+
+ CCE-80792-5: Ensure gpgcheck Enabled for All yum Package Repositories |
+
+ Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor.
+
+Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization.
+
+Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA. |
+ To ensure signature checking is not disabled for
+any repos, remove any lines from files in /etc/yum.repos.d of the form:
+gpgcheck=0 |
+ Applicable - Configurable |
+ Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. If it does not, this is a finding. |
+ To determine whether yum has been configured to disable
+gpgcheck for any repos, inspect all files in
+/etc/yum.repos.d and ensure the following does not appear in any
+sections:
+gpgcheck=0
+A value of 0 indicates that gpgcheck has been disabled for that repo. Is it the case that GPG checking is disabled? |
+ Configure the operating system to prevent the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. |
+ To ensure signature checking is not disabled for
+any repos, remove any lines from files in /etc/yum.repos.d of the form:
+gpgcheck=0 |
+ high |
+ |
+ |
+ |
+
+
| CCI-001749 |
SRG-OS-000366-GPOS-00153 |
@@ -32283,6 +32242,47 @@
|
+
+ | CCI-001749 |
+ SRG-OS-000366-GPOS-00153 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must prevent the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. |
+
+ CCE-80790-9: Ensure gpgcheck Enabled In Main yum Configuration |
+
+ Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor.
+
+Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization.
+
+Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA. |
+ The gpgcheck option controls whether
+RPM packages' signatures are always checked prior to installation.
+To configure yum to check package signatures before installing
+them, ensure the following line appears in /etc/yum.conf in
+the [main] section:
+gpgcheck=1 |
+ Applicable - Configurable |
+ Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. If it does not, this is a finding. |
+ Verify that yum verifies the signature of packages from a repository prior to install with the following command:
+
+$ grep gpgcheck /etc/yum.conf
+
+gpgcheck=1
+
+If "gpgcheck" is not set to "1", or if the option is missing or commented out, ask the System Administrator how the certificates for patches and other operating system components are verified. Is it the case that there is no process to validate certificates that is approved by the organization? |
+ Configure the operating system to prevent the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. |
+ The gpgcheck option controls whether
+RPM packages' signatures are always checked prior to installation.
+To configure yum to check package signatures before installing
+them, ensure the following line appears in /etc/yum.conf in
+the [main] section:
+gpgcheck=1 |
+ high |
+ |
+ |
+ |
+
+
| CCI-001749 |
SRG-OS-000366-GPOS-00153 |
@@ -32325,30 +32325,37 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82249-4: Enable the File Access Policy Service |
+ CCE-82080-3: Add nodev Option to /var/log/audit |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The File Access Policy service should be enabled.
-
-The fapolicyd service can be enabled with the following command:
-$ sudo systemctl enable fapolicyd.service |
+ The nodev mount option can be used to prevent device files from
+being created in /var/log/audit.
+Legitimate character and block devices should exist only in
+the /dev directory on the root partition or within chroot
+jails built for system services.
+Add the nodev option to the fourth column of
+/etc/fstab for the line which controls mounting of
+/var/log/audit. |
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-fapolicyd service:
-$ sudo systemctl is-active fapolicyd
-If the service is running, it should return the following: active Is it the case that the service is not enabled? |
+ Verify the nodev option is configured for the /var/log/audit mount point,
+ run the following command:
+ $ sudo mount | grep '\s/var/log/audit\s'
+ . . . /var/log/audit . . . nodev . . .
+ Is it the case that the "/var/log/audit" file system does not have the "nodev" option set? |
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The File Access Policy service should be enabled.
-
-The fapolicyd service can be enabled with the following command:
-$ sudo systemctl enable fapolicyd.service |
+ The nodev mount option can be used to prevent device files from
+being created in /var/log/audit.
+Legitimate character and block devices should exist only in
+the /dev directory on the root partition or within chroot
+jails built for system services.
+Add the nodev option to the fourth column of
+/etc/fstab for the line which controls mounting of
+/var/log/audit. |
medium |
|
|
@@ -32361,37 +32368,33 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82077-9: Add nodev Option to /var/log |
+ CCE-80839-4: Add nosuid Option to /dev/shm |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The nodev mount option can be used to prevent device files from
-being created in /var/log.
-Legitimate character and block devices should exist only in
-the /dev directory on the root partition or within chroot
-jails built for system services.
-Add the nodev option to the fourth column of
+ | The nosuid mount option can be used to prevent execution
+of setuid programs in /dev/shm. The SUID and SGID permissions should not
+be required in these world-writable directories.
+Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/log. |
+/dev/shm.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the nodev option is configured for the /var/log mount point,
+ | Verify the nosuid option is configured for the /dev/shm mount point,
run the following command:
- $ sudo mount | grep '\s/var/log\s'
- . . . /var/log . . . nodev . . .
- Is it the case that the "/var/log" file system does not have the "nodev" option set? |
+ $ sudo mount | grep '\s/dev/shm\s'
+ . . . /dev/shm . . . nosuid . . .
+ Is it the case that the "/dev/shm" file system does not have the "nosuid" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The nodev mount option can be used to prevent device files from
-being created in /var/log.
-Legitimate character and block devices should exist only in
-the /dev directory on the root partition or within chroot
-jails built for system services.
-Add the nodev option to the fourth column of
+ | The nosuid mount option can be used to prevent execution
+of setuid programs in /dev/shm. The SUID and SGID permissions should not
+be required in these world-writable directories.
+Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/log. |
+/dev/shm.
medium |
|
|
@@ -32404,33 +32407,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-80837-8: Add nodev Option to /dev/shm |
+ CCE-82191-8: Install fapolicyd Package |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The nodev mount option can be used to prevent creation of device
-files in /dev/shm. Legitimate character and block devices should
-not exist within temporary directories like /dev/shm.
-Add the nodev option to the fourth column of
-/etc/fstab for the line which controls mounting of
-/dev/shm. |
+ The fapolicyd package can be installed with the following command:
+
+$ sudo yum install fapolicyd |
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the nodev option is configured for the /dev/shm mount point,
- run the following command:
- $ sudo mount | grep '\s/dev/shm\s'
- . . . /dev/shm . . . nodev . . .
- Is it the case that the "/dev/shm" file system does not have the "nodev" option set? |
+ Run the following command to determine if the fapolicyd package is installed: $ rpm -q fapolicyd Is it the case that the fapolicyd package is not installed? |
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The nodev mount option can be used to prevent creation of device
-files in /dev/shm. Legitimate character and block devices should
-not exist within temporary directories like /dev/shm.
-Add the nodev option to the fourth column of
-/etc/fstab for the line which controls mounting of
-/dev/shm. |
+ The fapolicyd package can be installed with the following command:
+
+$ sudo yum install fapolicyd |
medium |
|
|
@@ -32443,7 +32436,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82065-4: Add nosuid Option to /var/log |
+ CCE-81033-3: Add nosuid Option to /boot |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
@@ -32451,25 +32444,25 @@
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
The nosuid mount option can be used to prevent
-execution of setuid programs in /var/log. The SUID and SGID permissions
-should not be required in directories containing log files.
+execution of setuid programs in /boot. The SUID and SGID permissions
+should not be required on the boot partition.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/log. |
+/boot.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the nosuid option is configured for the /var/log mount point,
+ | Verify the nosuid option is configured for the /boot mount point,
run the following command:
- $ sudo mount | grep '\s/var/log\s'
- . . . /var/log . . . nosuid . . .
- Is it the case that the "/var/log" file system does not have the "nosuid" option set? |
+ $ sudo mount | grep '\s/boot\s'
+ . . . /boot . . . nosuid . . .
+ Is it the case that the "/boot" file system does not have the "nosuid" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
The nosuid mount option can be used to prevent
-execution of setuid programs in /var/log. The SUID and SGID permissions
-should not be required in directories containing log files.
+execution of setuid programs in /boot. The SUID and SGID permissions
+should not be required on the boot partition.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/log. |
+/boot.
medium |
|
|
@@ -32482,7 +32475,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-80838-6: Add noexec Option to /dev/shm |
+ CCE-82151-2: Add noexec Option to /var/tmp |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
@@ -32490,27 +32483,23 @@
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
The noexec mount option can be used to prevent binaries
-from being executed out of /dev/shm.
-It can be dangerous to allow the execution of binaries
-from world-writable temporary storage directories such as /dev/shm.
+from being executed out of /var/tmp.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
-/dev/shm. |
+/var/tmp.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the noexec option is configured for the /dev/shm mount point,
+ | Verify the noexec option is configured for the /var/tmp mount point,
run the following command:
- $ sudo mount | grep '\s/dev/shm\s'
- . . . /dev/shm . . . noexec . . .
- Is it the case that the "/dev/shm" file system does not have the "noexec" option set? |
+ $ sudo mount | grep '\s/var/tmp\s'
+ . . . /var/tmp . . . noexec . . .
+ Is it the case that the "/var/tmp" file system does not have the "noexec" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
The noexec mount option can be used to prevent binaries
-from being executed out of /dev/shm.
-It can be dangerous to allow the execution of binaries
-from world-writable temporary storage directories such as /dev/shm.
+from being executed out of /var/tmp.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
-/dev/shm. |
+/var/tmp.
medium |
|
|
@@ -32523,31 +32512,33 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82008-4: Add noexec Option to /var/log |
+ CCE-81050-7: Add nosuid Option to /home |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The noexec mount option can be used to prevent binaries
-from being executed out of /var/log.
-Add the noexec option to the fourth column of
+ | 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
-/var/log. |
+/home.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the noexec option is configured for the /var/log mount point,
+ | Verify the nosuid option is configured for the /home mount point,
run the following command:
- $ sudo mount | grep '\s/var/log\s'
- . . . /var/log . . . noexec . . .
- Is it the case that the "/var/log" file system does not have the "noexec" option set? |
+ $ sudo mount | grep '\s/home\s'
+ . . . /home . . . nosuid . . .
+ Is it the case that the "/home" file system does not have the "nosuid" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The noexec mount option can be used to prevent binaries
-from being executed out of /var/log.
-Add the noexec option to the fourth column of
+ | 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
-/var/log. |
+/home.
medium |
|
|
@@ -32560,33 +32551,37 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82623-0: Add nodev Option to /tmp |
+ CCE-86478-5: Configure Fapolicy Module to Employ a Deny-all, Permit-by-exception Policy to Allow the Execution of Authorized Software Programs. |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The nodev mount option can be used to prevent device files from
-being created in /tmp. Legitimate character and block devices
-should not exist within temporary directories like /tmp.
-Add the nodev option to the fourth column of
-/etc/fstab for the line which controls mounting of
-/tmp. |
+ The Fapolicy module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and to prevent unauthorized software from running. |
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the nodev option is configured for the /tmp mount point,
- run the following command:
- $ sudo mount | grep '\s/tmp\s'
- . . . /tmp . . . nodev . . .
- Is it the case that the "/tmp" file system does not have the "nodev" option set? |
+ Verify the Red Hat Enterprise Linux 8 "fapolicyd" employs a deny-all, permit-by-exception policy.
+
+Check that "fapolicyd" is in enforcement mode with the following command:
+
+$ sudo grep permissive /etc/fapolicyd/fapolicyd.conf
+
+permissive = 0
+
+Check that fapolicyd employs a deny-all policy on system mounts with the following commands:
+
+For RHEL 8.5 systems and older:
+$ sudo tail /etc/fapolicyd/fapolicyd.rules
+
+For RHEL 8.6 systems and newer:
+$ sudo tail /etc/fapolicyd/compiled.rules
+
+allow exe=/usr/bin/python3.7 : ftype=text/x-python
+deny_audit perm=any pattern=ld_so : all
+deny perm=any all : all Is it the case that fapolicyd is not running in enforcement mode with a deny-all, permit-by-exception policy? |
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The nodev mount option can be used to prevent device files from
-being created in /tmp. Legitimate character and block devices
-should not exist within temporary directories like /tmp.
-Add the nodev option to the fourth column of
-/etc/fstab for the line which controls mounting of
-/tmp. |
+ The Fapolicy module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and to prevent unauthorized software from running. |
medium |
|
|
@@ -32599,7 +32594,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82975-4: Add noexec Option to /var/log/audit |
+ CCE-82139-7: Add noexec Option to /tmp |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
@@ -32607,23 +32602,23 @@
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
The noexec mount option can be used to prevent binaries
-from being executed out of /var/log/audit.
+from being executed out of /tmp.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/log/audit. |
+/tmp.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the noexec option is configured for the /var/log/audit mount point,
+ | Verify the noexec option is configured for the /tmp mount point,
run the following command:
- $ sudo mount | grep '\s/var/log/audit\s'
- . . . /var/log/audit . . . noexec . . .
- Is it the case that the "/var/log/audit" file system does not have the "noexec" option set? |
+ $ sudo mount | grep '\s/tmp\s'
+ . . . /tmp . . . noexec . . .
+ Is it the case that the "/tmp" file system does not have the "noexec" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
The noexec mount option can be used to prevent binaries
-from being executed out of /var/log/audit.
+from being executed out of /tmp.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/log/audit. |
+/tmp.
medium |
|
|
@@ -32636,7 +32631,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82154-6: Add nosuid Option to /var/tmp |
+ CCE-82921-8: Add nosuid Option to /var/log/audit |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
@@ -32644,25 +32639,25 @@
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
The nosuid mount option can be used to prevent
-execution of setuid programs in /var/tmp. The SUID and SGID permissions
-should not be required in these world-writable directories.
+execution of setuid programs in /var/log/audit. The SUID and SGID permissions
+should not be required in directories containing audit log files.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/tmp. |
+/var/log/audit.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the nosuid option is configured for the /var/tmp mount point,
+ | Verify the nosuid option is configured for the /var/log/audit mount point,
run the following command:
- $ sudo mount | grep '\s/var/tmp\s'
- . . . /var/tmp . . . nosuid . . .
- Is it the case that the "/var/tmp" file system does not have the "nosuid" option set? |
+ $ sudo mount | grep '\s/var/log/audit\s'
+ . . . /var/log/audit . . . nosuid . . .
+ Is it the case that the "/var/log/audit" file system does not have the "nosuid" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
The nosuid mount option can be used to prevent
-execution of setuid programs in /var/tmp. The SUID and SGID permissions
-should not be required in these world-writable directories.
+execution of setuid programs in /var/log/audit. The SUID and SGID permissions
+should not be required in directories containing audit log files.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/tmp. |
+/var/log/audit.
medium |
|
|
@@ -32675,7 +32670,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82921-8: Add nosuid Option to /var/log/audit |
+ CCE-82065-4: Add nosuid Option to /var/log |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
@@ -32683,25 +32678,25 @@
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
The nosuid mount option can be used to prevent
-execution of setuid programs in /var/log/audit. The SUID and SGID permissions
-should not be required in directories containing audit log files.
+execution of setuid programs in /var/log. The SUID and SGID permissions
+should not be required in directories containing log files.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/log/audit. |
+/var/log.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the nosuid option is configured for the /var/log/audit mount point,
+ | Verify the nosuid option is configured for the /var/log mount point,
run the following command:
- $ sudo mount | grep '\s/var/log/audit\s'
- . . . /var/log/audit . . . nosuid . . .
- Is it the case that the "/var/log/audit" file system does not have the "nosuid" option set? |
+ $ sudo mount | grep '\s/var/log\s'
+ . . . /var/log . . . nosuid . . .
+ Is it the case that the "/var/log" file system does not have the "nosuid" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
The nosuid mount option can be used to prevent
-execution of setuid programs in /var/log/audit. The SUID and SGID permissions
-should not be required in directories containing audit log files.
+execution of setuid programs in /var/log. The SUID and SGID permissions
+should not be required in directories containing log files.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/log/audit. |
+/var/log.
medium |
|
|
@@ -32714,31 +32709,33 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82151-2: Add noexec Option to /var/tmp |
+ CCE-82623-0: Add nodev Option to /tmp |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The noexec mount option can be used to prevent binaries
-from being executed out of /var/tmp.
-Add the noexec option to the fourth column of
+ | The nodev mount option can be used to prevent device files from
+being created in /tmp. Legitimate character and block devices
+should not exist within temporary directories like /tmp.
+Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/tmp. |
+/tmp.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the noexec option is configured for the /var/tmp mount point,
+ | Verify the nodev option is configured for the /tmp mount point,
run the following command:
- $ sudo mount | grep '\s/var/tmp\s'
- . . . /var/tmp . . . noexec . . .
- Is it the case that the "/var/tmp" file system does not have the "noexec" option set? |
+ $ sudo mount | grep '\s/tmp\s'
+ . . . /tmp . . . nodev . . .
+ Is it the case that the "/tmp" file system does not have the "nodev" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The noexec mount option can be used to prevent binaries
-from being executed out of /var/tmp.
-Add the noexec option to the fourth column of
+ | The nodev mount option can be used to prevent device files from
+being created in /tmp. Legitimate character and block devices
+should not exist within temporary directories like /tmp.
+Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/tmp. |
+/tmp.
medium |
|
|
@@ -32751,31 +32748,33 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82139-7: Add noexec Option to /tmp |
+ CCE-82068-8: Add nodev Option to /var/tmp |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The noexec mount option can be used to prevent binaries
-from being executed out of /tmp.
-Add the noexec option to the fourth column of
+ | The nodev mount option can be used to prevent device files from
+being created in /var/tmp. Legitimate character and block devices
+should not exist within temporary directories like /var/tmp.
+Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
-/tmp. |
+/var/tmp.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the noexec option is configured for the /tmp mount point,
+ | Verify the nodev option is configured for the /var/tmp mount point,
run the following command:
- $ sudo mount | grep '\s/tmp\s'
- . . . /tmp . . . noexec . . .
- Is it the case that the "/tmp" file system does not have the "noexec" option set? |
+ $ sudo mount | grep '\s/var/tmp\s'
+ . . . /var/tmp . . . nodev . . .
+ Is it the case that the "/var/tmp" file system does not have the "nodev" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The noexec mount option can be used to prevent binaries
-from being executed out of /tmp.
-Add the noexec option to the fourth column of
+ | The nodev mount option can be used to prevent device files from
+being created in /var/tmp. Legitimate character and block devices
+should not exist within temporary directories like /var/tmp.
+Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
-/tmp. |
+/var/tmp.
medium |
|
|
@@ -32788,36 +32787,35 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82069-6: Add nodev Option to Non-Root Local Partitions |
+ CCE-80838-6: Add noexec Option to /dev/shm |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The nodev mount option prevents files from being interpreted as
-character or block devices. Legitimate character and block devices should
-exist only in the /dev directory on the root partition or within
-chroot jails built for system services.
-Add the nodev option to the fourth column of
+ | The noexec mount option can be used to prevent binaries
+from being executed out of /dev/shm.
+It can be dangerous to allow the execution of binaries
+from world-writable temporary storage directories such as /dev/shm.
+Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
-
- any non-root local partitions. |
+/dev/shm.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- To verify the nodev option is configured for non-root local partitions, run the following command:
-$ sudo mount | grep '^/dev\S* on /\S' | grep --invert-match 'nodev'
-The output shows local non-root partitions mounted without the nodev option, and there should be no output at all.
- Is it the case that some mounts appear among output lines? |
+ Verify the noexec option is configured for the /dev/shm mount point,
+ run the following command:
+ $ sudo mount | grep '\s/dev/shm\s'
+ . . . /dev/shm . . . noexec . . .
+ Is it the case that the "/dev/shm" file system does not have the "noexec" option set? |
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The nodev mount option prevents files from being interpreted as
-character or block devices. Legitimate character and block devices should
-exist only in the /dev directory on the root partition or within
-chroot jails built for system services.
-Add the nodev option to the fourth column of
+ | The noexec mount option can be used to prevent binaries
+from being executed out of /dev/shm.
+It can be dangerous to allow the execution of binaries
+from world-writable temporary storage directories such as /dev/shm.
+Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
-
- any non-root local partitions. |
+/dev/shm.
medium |
|
|
@@ -32830,7 +32828,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82140-5: Add nosuid Option to /tmp |
+ CCE-82154-6: Add nosuid Option to /var/tmp |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
@@ -32838,25 +32836,25 @@
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
The nosuid mount option can be used to prevent
-execution of setuid programs in /tmp. The SUID and SGID permissions
+execution of setuid programs in /var/tmp. The SUID and SGID permissions
should not be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
-/tmp. |
+/var/tmp.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the nosuid option is configured for the /tmp mount point,
+ | Verify the nosuid option is configured for the /var/tmp mount point,
run the following command:
- $ sudo mount | grep '\s/tmp\s'
- . . . /tmp . . . nosuid . . .
- Is it the case that the "/tmp" file system does not have the "nosuid" option set? |
+ $ sudo mount | grep '\s/var/tmp\s'
+ . . . /var/tmp . . . nosuid . . .
+ Is it the case that the "/var/tmp" file system does not have the "nosuid" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
The nosuid mount option can be used to prevent
-execution of setuid programs in /tmp. The SUID and SGID permissions
+execution of setuid programs in /var/tmp. The SUID and SGID permissions
should not be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
-/tmp. |
+/var/tmp.
medium |
|
|
@@ -32869,33 +32867,31 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-81033-3: Add nosuid Option to /boot |
+ CCE-82008-4: Add noexec Option to /var/log |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The nosuid mount option can be used to prevent
-execution of setuid programs in /boot. The SUID and SGID permissions
-should not be required on the boot partition.
-Add the nosuid option to the fourth column of
+ | The noexec mount option can be used to prevent binaries
+from being executed out of /var/log.
+Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
-/boot. |
+/var/log.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the nosuid option is configured for the /boot mount point,
+ | Verify the noexec option is configured for the /var/log mount point,
run the following command:
- $ sudo mount | grep '\s/boot\s'
- . . . /boot . . . nosuid . . .
- Is it the case that the "/boot" file system does not have the "nosuid" option set? |
+ $ sudo mount | grep '\s/var/log\s'
+ . . . /var/log . . . noexec . . .
+ Is it the case that the "/var/log" file system does not have the "noexec" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The nosuid mount option can be used to prevent
-execution of setuid programs in /boot. The SUID and SGID permissions
-should not be required on the boot partition.
-Add the nosuid option to the fourth column of
+ | The noexec mount option can be used to prevent binaries
+from being executed out of /var/log.
+Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
-/boot. |
+/var/log.
medium |
|
|
@@ -32908,33 +32904,36 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82068-8: Add nodev Option to /var/tmp |
+ CCE-82069-6: Add nodev Option to Non-Root Local Partitions |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The nodev mount option can be used to prevent device files from
-being created in /var/tmp. Legitimate character and block devices
-should not exist within temporary directories like /var/tmp.
+ | The nodev mount option prevents files from being interpreted as
+character or block devices. Legitimate character and block devices should
+exist only in the /dev directory on the root partition or within
+chroot jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/tmp. |
+
+ any non-root local partitions.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the nodev option is configured for the /var/tmp mount point,
- run the following command:
- $ sudo mount | grep '\s/var/tmp\s'
- . . . /var/tmp . . . nodev . . .
- Is it the case that the "/var/tmp" file system does not have the "nodev" option set? |
+ To verify the nodev option is configured for non-root local partitions, run the following command:
+$ sudo mount | grep '^/dev\S* on /\S' | grep --invert-match 'nodev'
+The output shows local non-root partitions mounted without the nodev option, and there should be no output at all.
+ Is it the case that some mounts appear among output lines? |
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The nodev mount option can be used to prevent device files from
-being created in /var/tmp. Legitimate character and block devices
-should not exist within temporary directories like /var/tmp.
+ | The nodev mount option prevents files from being interpreted as
+character or block devices. Legitimate character and block devices should
+exist only in the /dev directory on the root partition or within
+chroot jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
-/var/tmp. |
+
+ any non-root local partitions.
medium |
|
|
@@ -32947,31 +32946,31 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-80839-4: Add nosuid Option to /dev/shm |
+ CCE-80837-8: Add nodev Option to /dev/shm |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The nosuid mount option can be used to prevent execution
-of setuid programs in /dev/shm. The SUID and SGID permissions should not
-be required in these world-writable directories.
-Add the nosuid option to the fourth column of
+ | The nodev mount option can be used to prevent creation of device
+files in /dev/shm. Legitimate character and block devices should
+not exist within temporary directories like /dev/shm.
+Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/dev/shm. |
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the nosuid option is configured for the /dev/shm mount point,
+ | Verify the nodev option is configured for the /dev/shm mount point,
run the following command:
$ sudo mount | grep '\s/dev/shm\s'
- . . . /dev/shm . . . nosuid . . .
- Is it the case that the "/dev/shm" file system does not have the "nosuid" option set? |
+ . . . /dev/shm . . . nodev . . .
+ Is it the case that the "/dev/shm" file system does not have the "nodev" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The nosuid mount option can be used to prevent execution
-of setuid programs in /dev/shm. The SUID and SGID permissions should not
-be required in these world-writable directories.
-Add the nosuid option to the fourth column of
+ | The nodev mount option can be used to prevent creation of device
+files in /dev/shm. Legitimate character and block devices should
+not exist within temporary directories like /dev/shm.
+Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/dev/shm. |
medium |
@@ -32986,23 +32985,37 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82191-8: Install fapolicyd Package |
+ CCE-82077-9: Add nodev Option to /var/log |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The fapolicyd package can be installed with the following command:
-
-$ sudo yum install fapolicyd |
- Applicable - Configurable |
+ The nodev mount option can be used to prevent device files from
+being created in /var/log.
+Legitimate character and block devices should exist only in
+the /dev directory on the root partition or within chroot
+jails built for system services.
+Add the nodev option to the fourth column of
+/etc/fstab for the line which controls mounting of
+/var/log. |
+ Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Run the following command to determine if the fapolicyd package is installed: $ rpm -q fapolicyd Is it the case that the fapolicyd package is not installed? |
+ Verify the nodev option is configured for the /var/log mount point,
+ run the following command:
+ $ sudo mount | grep '\s/var/log\s'
+ . . . /var/log . . . nodev . . .
+ Is it the case that the "/var/log" file system does not have the "nodev" option set? |
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The fapolicyd package can be installed with the following command:
-
-$ sudo yum install fapolicyd |
+ The nodev mount option can be used to prevent device files from
+being created in /var/log.
+Legitimate character and block devices should exist only in
+the /dev directory on the root partition or within chroot
+jails built for system services.
+Add the nodev option to the fourth column of
+/etc/fstab for the line which controls mounting of
+/var/log. |
medium |
|
|
@@ -33015,7 +33028,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-81050-7: Add nosuid Option to /home |
+ CCE-82140-5: Add nosuid Option to /tmp |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
@@ -33023,68 +33036,25 @@
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
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.
+execution of setuid programs in /tmp. The SUID and SGID permissions
+should not be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
-/home. |
+/tmp.
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the nosuid option is configured for the /home mount point,
+ | Verify the nosuid option is configured for the /tmp mount point,
run the following command:
- $ sudo mount | grep '\s/home\s'
- . . . /home . . . nosuid . . .
- Is it the case that the "/home" file system does not have the "nosuid" option set? |
+ $ sudo mount | grep '\s/tmp\s'
+ . . . /tmp . . . nosuid . . .
+ Is it the case that the "/tmp" file system does not have the "nosuid" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
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.
+execution of setuid programs in /tmp. The SUID and SGID permissions
+should not be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
-/home. |
- medium |
- |
- |
- |
-
-
-
- | CCI-001764 |
- SRG-OS-000368-GPOS-00154 |
- TBD - Assigned by DISA after STIG release |
- The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
-
- CCE-86478-5: Configure Fapolicy Module to Employ a Deny-all, Permit-by-exception Policy to Allow the Execution of Authorized Software Programs. |
-
- Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
-
-Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
-
-Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The Fapolicy module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and to prevent unauthorized software from running. |
- Applicable - Configurable |
- Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the Red Hat Enterprise Linux 8 "fapolicyd" employs a deny-all, permit-by-exception policy.
-
-Check that "fapolicyd" is in enforcement mode with the following command:
-
-$ sudo grep permissive /etc/fapolicyd/fapolicyd.conf
-
-permissive = 0
-
-Check that fapolicyd employs a deny-all policy on system mounts with the following commands:
-
-For RHEL 8.5 systems and older:
-$ sudo tail /etc/fapolicyd/fapolicyd.rules
-
-For RHEL 8.6 systems and newer:
-$ sudo tail /etc/fapolicyd/compiled.rules
-
-allow exe=/usr/bin/python3.7 : ftype=text/x-python
-deny_audit perm=any pattern=ld_so : all
-deny perm=any all : all Is it the case that fapolicyd is not running in enforcement mode with a deny-all, permit-by-exception policy? |
- Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The Fapolicy module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and to prevent unauthorized software from running. |
+/tmp.
medium |
|
|
@@ -33097,35 +33067,29 @@
TBD - Assigned by DISA after STIG release |
The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- CCE-82080-3: Add nodev Option to /var/log/audit |
+ CCE-82975-4: Add noexec Option to /var/log/audit |
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles). |
- The nodev mount option can be used to prevent device files from
-being created in /var/log/audit.
-Legitimate character and block devices should exist only in
-the /dev directory on the root partition or within chroot
-jails built for system services.
-Add the nodev option to the fourth column of
+ | The noexec mount option can be used to prevent binaries
+from being executed out of /var/log/audit.
+Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log/audit. |
Applicable - Configurable |
Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
- Verify the nodev option is configured for the /var/log/audit mount point,
+ | Verify the noexec option is configured for the /var/log/audit mount point,
run the following command:
$ sudo mount | grep '\s/var/log/audit\s'
- . . . /var/log/audit . . . nodev . . .
- Is it the case that the "/var/log/audit" file system does not have the "nodev" option set? |
+ . . . /var/log/audit . . . noexec . . .
+ Is it the case that the "/var/log/audit" file system does not have the "noexec" option set?
Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
- The nodev mount option can be used to prevent device files from
-being created in /var/log/audit.
-Legitimate character and block devices should exist only in
-the /dev directory on the root partition or within chroot
-jails built for system services.
-Add the nodev option to the fourth column of
+ | The noexec mount option can be used to prevent binaries
+from being executed out of /var/log/audit.
+Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log/audit. |
medium |
@@ -33134,39 +33098,32 @@
|
-
-
-
-
-
- | CCI-001774 |
- SRG-OS-000370-GPOS-00155 |
+ CCI-001764 |
+ SRG-OS-000368-GPOS-00154 |
TBD - Assigned by DISA after STIG release |
- The operating system must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. |
+ The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
CCE-82249-4: Enable the File Access Policy Service |
- Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities.
-
-The organization must identify authorized software programs and permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting.
+ | Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system-level.
-Verification of white-listed software occurs prior to execution or at system startup.
+Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.
-This requirement applies to operating system programs, functions, and services designed to manage system processes and configurations (e.g., group policies). |
+Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).
The File Access Policy service should be enabled.
The fapolicyd service can be enabled with the following command:
$ sudo systemctl enable fapolicyd.service |
Applicable - Configurable |
- Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. If it does not, this is a finding. |
+ Verify the operating system prevents program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. If it does not, this is a finding. |
Run the following command to determine the current status of the
fapolicyd service:
$ sudo systemctl is-active fapolicyd
If the service is running, it should return the following: active Is it the case that the service is not enabled? |
- Configure the operating system to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. |
+ Configure the operating system to prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. |
The File Access Policy service should be enabled.
The fapolicyd service can be enabled with the following command:
@@ -33177,6 +33134,11 @@
| |
+
+
+
+
+
| CCI-001774 |
SRG-OS-000370-GPOS-00155 |
@@ -33253,42 +33215,49 @@
|
+
+ | CCI-001774 |
+ SRG-OS-000370-GPOS-00155 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. |
+ CCE-82249-4: Enable the File Access Policy Service |
+ Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities.
+The organization must identify authorized software programs and permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting.
+Verification of white-listed software occurs prior to execution or at system startup.
- |
- | CCI-002038 |
- SRG-OS-000373-GPOS-00156 |
- TBD - Assigned by DISA after STIG release |
- The operating system must require users to re-authenticate for privilege escalation. |
+This requirement applies to operating system programs, functions, and services designed to manage system processes and configurations (e.g., group policies).
+ The File Access Policy service should be enabled.
- | CCE-82202-3: Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticate |
+The fapolicyd service can be enabled with the following command:
+$ sudo systemctl enable fapolicyd.service
+ Applicable - Configurable |
+ Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. If it does not, this is a finding. |
+
- | Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
+Run the following command to determine the current status of the
+fapolicyd service:
+$ sudo systemctl is-active fapolicyd
+If the service is running, it should return the following: active Is it the case that the service is not enabled? |
+ Configure the operating system to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. |
+ The File Access Policy service should be enabled.
-When operating systems provide the capability to escalate a functional capability, it is critical the user re-authenticate. |
- 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/. |
- Applicable - Configurable |
- Verify the operating system requires users to re-authenticate for privilege escalation. If it does not, this is a finding. |
- To determine if !authenticate has not been configured for sudo, run the following command:
-$ sudo grep -r \!authenticate /etc/sudoers /etc/sudoers.d/
-The command should return no output. Is it the case that !authenticate is specified in the sudo config files? |
- Configure the operating system to require users to re-authenticate for privilege escalation. |
- 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/. |
+The fapolicyd service can be enabled with the following command:
+$ sudo systemctl enable fapolicyd.service
medium |
|
|
|
+
+
+
+
+
| CCI-002038 |
SRG-OS-000373-GPOS-00156 |
@@ -33337,25 +33306,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must require users to re-authenticate for privilege escalation. |
- CCE-86319-1: Disallow Configuration to Bypass Password Requirements for Privilege Escalation |
+ CCE-82202-3: Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticate |
Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the capability to escalate a functional capability, it is critical the user re-authenticate. |
- Verify the operating system is not configured to bypass password requirements for privilege
-escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
-$ sudo grep pam_succeed_if /etc/pam.d/sudo
-If any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
+ 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/. |
Applicable - Configurable |
Verify the operating system requires users to re-authenticate for privilege escalation. If it does not, this is a finding. |
- Verify the operating system is not configured to bypass password requirements for privilege
-escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
-$ sudo grep pam_succeed_if /etc/pam.d/sudo Is it the case that system is configured to bypass password requirements for privilege escalation? |
+ To determine if !authenticate has not been configured for sudo, run the following command:
+$ sudo grep -r \!authenticate /etc/sudoers /etc/sudoers.d/
+The command should return no output. Is it the case that !authenticate is specified in the sudo config files? |
Configure the operating system to require users to re-authenticate for privilege escalation. |
- Verify the operating system is not configured to bypass password requirements for privilege
-escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
-$ sudo grep pam_succeed_if /etc/pam.d/sudo
-If any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
+ 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/. |
medium |
|
|
@@ -33395,42 +33364,42 @@
|
-
-
-
-
-
| CCI-002038 |
- SRG-OS-000373-GPOS-00157 |
+ SRG-OS-000373-GPOS-00156 |
TBD - Assigned by DISA after STIG release |
- The operating system must require users to re-authenticate when changing roles. |
+ The operating system must require users to re-authenticate for privilege escalation. |
- CCE-82202-3: Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticate |
+ CCE-86319-1: Disallow Configuration to Bypass Password Requirements for Privilege Escalation |
Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
-When operating systems provide the capability to change security roles, it is critical the user re-authenticate. |
- 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/. |
+When operating systems provide the capability to escalate a functional capability, it is critical the user re-authenticate.
+ Verify the operating system is not configured to bypass password requirements for privilege
+escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
+$ sudo grep pam_succeed_if /etc/pam.d/sudo
+If any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
Applicable - Configurable |
- Verify the operating system requires users to re-authenticate when changing roles. If it does not, this is a finding. |
- To determine if !authenticate has not been configured for sudo, run the following command:
-$ sudo grep -r \!authenticate /etc/sudoers /etc/sudoers.d/
-The command should return no output. Is it the case that !authenticate is specified in the sudo config files? |
- Configure the operating system to require users to re-authenticate when changing roles. |
- 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/. |
+ Verify the operating system requires users to re-authenticate for privilege escalation. If it does not, this is a finding. |
+ Verify the operating system is not configured to bypass password requirements for privilege
+escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
+$ sudo grep pam_succeed_if /etc/pam.d/sudo Is it the case that system is configured to bypass password requirements for privilege escalation? |
+ Configure the operating system to require users to re-authenticate for privilege escalation. |
+ Verify the operating system is not configured to bypass password requirements for privilege
+escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
+$ sudo grep pam_succeed_if /etc/pam.d/sudo
+If any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
medium |
|
|
|
+
+
+
+
+
| CCI-002038 |
SRG-OS-000373-GPOS-00157 |
@@ -33479,25 +33448,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must require users to re-authenticate when changing roles. |
- CCE-86319-1: Disallow Configuration to Bypass Password Requirements for Privilege Escalation |
+ CCE-82202-3: Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticate |
Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the capability to change security roles, it is critical the user re-authenticate. |
- Verify the operating system is not configured to bypass password requirements for privilege
-escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
-$ sudo grep pam_succeed_if /etc/pam.d/sudo
-If any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
+ 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/. |
Applicable - Configurable |
Verify the operating system requires users to re-authenticate when changing roles. If it does not, this is a finding. |
- Verify the operating system is not configured to bypass password requirements for privilege
-escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
-$ sudo grep pam_succeed_if /etc/pam.d/sudo Is it the case that system is configured to bypass password requirements for privilege escalation? |
+ To determine if !authenticate has not been configured for sudo, run the following command:
+$ sudo grep -r \!authenticate /etc/sudoers /etc/sudoers.d/
+The command should return no output. Is it the case that !authenticate is specified in the sudo config files? |
Configure the operating system to require users to re-authenticate when changing roles. |
- Verify the operating system is not configured to bypass password requirements for privilege
-escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
-$ sudo grep pam_succeed_if /etc/pam.d/sudo
-If any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
+ 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/. |
medium |
|
|
@@ -33537,42 +33506,42 @@
|
-
-
-
-
-
| CCI-002038 |
- SRG-OS-000373-GPOS-00158 |
+ SRG-OS-000373-GPOS-00157 |
TBD - Assigned by DISA after STIG release |
- The operating system must require users to re-authenticate when changing authenticators. |
+ The operating system must require users to re-authenticate when changing roles. |
- CCE-82202-3: Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticate |
+ CCE-86319-1: Disallow Configuration to Bypass Password Requirements for Privilege Escalation |
Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
-When operating systems provide the capability to change user authenticators, it is critical the user re-authenticate. |
- 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/. |
+When operating systems provide the capability to change security roles, it is critical the user re-authenticate.
+ Verify the operating system is not configured to bypass password requirements for privilege
+escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
+$ sudo grep pam_succeed_if /etc/pam.d/sudo
+If any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
Applicable - Configurable |
- Verify the operating system requires users to re-authenticate when changing authenticators. If it does not, this is a finding. |
- To determine if !authenticate has not been configured for sudo, run the following command:
-$ sudo grep -r \!authenticate /etc/sudoers /etc/sudoers.d/
-The command should return no output. Is it the case that !authenticate is specified in the sudo config files? |
- Configure the operating system to require users to re-authenticate when changing authenticators. |
- 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/. |
+ Verify the operating system requires users to re-authenticate when changing roles. If it does not, this is a finding. |
+ Verify the operating system is not configured to bypass password requirements for privilege
+escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
+$ sudo grep pam_succeed_if /etc/pam.d/sudo Is it the case that system is configured to bypass password requirements for privilege escalation? |
+ Configure the operating system to require users to re-authenticate when changing roles. |
+ Verify the operating system is not configured to bypass password requirements for privilege
+escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
+$ sudo grep pam_succeed_if /etc/pam.d/sudo
+If any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
medium |
|
|
|
+
+
+
+
+
| CCI-002038 |
SRG-OS-000373-GPOS-00158 |
@@ -33621,25 +33590,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must require users to re-authenticate when changing authenticators. |
- CCE-86319-1: Disallow Configuration to Bypass Password Requirements for Privilege Escalation |
+ CCE-82202-3: Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticate |
Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the capability to change user authenticators, it is critical the user re-authenticate. |
- Verify the operating system is not configured to bypass password requirements for privilege
-escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
-$ sudo grep pam_succeed_if /etc/pam.d/sudo
-If any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
+ 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/. |
Applicable - Configurable |
Verify the operating system requires users to re-authenticate when changing authenticators. If it does not, this is a finding. |
- Verify the operating system is not configured to bypass password requirements for privilege
-escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
-$ sudo grep pam_succeed_if /etc/pam.d/sudo Is it the case that system is configured to bypass password requirements for privilege escalation? |
+ To determine if !authenticate has not been configured for sudo, run the following command:
+$ sudo grep -r \!authenticate /etc/sudoers /etc/sudoers.d/
+The command should return no output. Is it the case that !authenticate is specified in the sudo config files? |
Configure the operating system to require users to re-authenticate when changing authenticators. |
- Verify the operating system is not configured to bypass password requirements for privilege
-escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
-$ sudo grep pam_succeed_if /etc/pam.d/sudo
-If any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
+ 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/. |
medium |
|
|
@@ -33679,6 +33648,37 @@
|
+
+ | CCI-002038 |
+ SRG-OS-000373-GPOS-00158 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must require users to re-authenticate when changing authenticators. |
+
+ CCE-86319-1: Disallow Configuration to Bypass Password Requirements for Privilege Escalation |
+
+ Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
+
+When operating systems provide the capability to change user authenticators, it is critical the user re-authenticate. |
+ Verify the operating system is not configured to bypass password requirements for privilege
+escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
+$ sudo grep pam_succeed_if /etc/pam.d/sudo
+If any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
+ Applicable - Configurable |
+ Verify the operating system requires users to re-authenticate when changing authenticators. If it does not, this is a finding. |
+ Verify the operating system is not configured to bypass password requirements for privilege
+escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
+$ sudo grep pam_succeed_if /etc/pam.d/sudo Is it the case that system is configured to bypass password requirements for privilege escalation? |
+ Configure the operating system to require users to re-authenticate when changing authenticators. |
+ Verify the operating system is not configured to bypass password requirements for privilege
+escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
+$ sudo grep pam_succeed_if /etc/pam.d/sudo
+If any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
+ medium |
+ |
+ |
+ |
+
+
@@ -33714,7 +33714,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must implement multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. |
-
CCE-84029-8: Install Smart Card Packages For Multifactor Authentication |
+
CCE-80846-9: Install the opensc Package For Multifactor Authentication |
Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
@@ -33727,25 +33727,18 @@
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).
Requires further clarification from NIST. |
-
Configure the operating system to implement multifactor authentication by
-installing the required package with the following command:
-
-The openssl-pkcs11 package can be installed with the following command:
+ |
+The opensc package can be installed with the following command:
-$ sudo yum install openssl-pkcs11 |
+$ sudo yum install opensc
Applicable - Configurable |
Verify the operating system implements multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. If it does not, this is a finding. |
-
Check that Red Hat Enterprise Linux 8 has the packages for smart card support installed.
-
-Run the following command to determine if the openssl-pkcs11 package is installed:
-$ rpm -q openssl-pkcs11 Is it the case that smartcard software is not installed? |
+
Run the following command to determine if the opensc package is installed: $ rpm -q opensc Is it the case that the package is not installed? |
Configure the operating system to implement multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. |
-
Configure the operating system to implement multifactor authentication by
-installing the required package with the following command:
-
-The openssl-pkcs11 package can be installed with the following command:
+ |
+The opensc package can be installed with the following command:
-$ sudo yum install openssl-pkcs11 |
+$ sudo yum install opensc
medium |
|
|
@@ -33758,7 +33751,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must implement multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. |
-
CCE-86120-3: Certificate status checking in SSSD |
+
CCE-84029-8: Install Smart Card Packages For Multifactor Authentication |
Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
@@ -33771,61 +33764,25 @@
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).
Requires further clarification from NIST. |
-
Multifactor solutions that require devices separate from information systems gaining access include,
-for example, hardware tokens providing time-based or challenge-response authenticators and smart cards.
-Configuring certificate_verification to ocsp_dgst= ensures that certificates for
-multifactor solutions are checked via Online Certificate Status Protocol (OCSP). |
-
Applicable - Configurable |
-
Verify the operating system implements multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. If it does not, this is a finding. |
-
Check to see if Online Certificate Status Protocol (OCSP)
-is enabled and using the proper digest value on the system with the following command:
-$ sudo grep certificate_verification /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf | grep -v "^#"
-If configured properly, output should look like
-
- certificate_verification = ocsp_dgst=
- Is it the case that certificate_verification in sssd is not configured? |
-
Configure the operating system to implement multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. |
-
Multifactor solutions that require devices separate from information systems gaining access include,
-for example, hardware tokens providing time-based or challenge-response authenticators and smart cards.
-Configuring certificate_verification to ocsp_dgst= ensures that certificates for
-multifactor solutions are checked via Online Certificate Status Protocol (OCSP). |
-
medium |
-
|
-
|
-
|
-
-
-
- | CCI-001948 |
- SRG-OS-000375-GPOS-00160 |
- TBD - Assigned by DISA after STIG release |
- The operating system must implement multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. |
-
- CCE-80846-9: Install the opensc Package For Multifactor Authentication |
-
- Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
-
-Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
-
-A privileged account is defined as an information system account with authorizations of a privileged user.
-
-Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
-
-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).
+ | Configure the operating system to implement multifactor authentication by
+installing the required package with the following command:
-Requires further clarification from NIST. |
-
-The opensc package can be installed with the following command:
+The openssl-pkcs11 package can be installed with the following command:
-$ sudo yum install opensc |
+$ sudo yum install openssl-pkcs11
Applicable - Configurable |
Verify the operating system implements multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. If it does not, this is a finding. |
- Run the following command to determine if the opensc package is installed: $ rpm -q opensc Is it the case that the package is not installed? |
+ Check that Red Hat Enterprise Linux 8 has the packages for smart card support installed.
+
+Run the following command to determine if the openssl-pkcs11 package is installed:
+$ rpm -q openssl-pkcs11 Is it the case that smartcard software is not installed? |
Configure the operating system to implement multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. |
-
-The opensc package can be installed with the following command:
+ | Configure the operating system to implement multifactor authentication by
+installing the required package with the following command:
+
+The openssl-pkcs11 package can be installed with the following command:
-$ sudo yum install opensc |
+$ sudo yum install openssl-pkcs11
medium |
|
|
@@ -33903,39 +33860,82 @@
|
-
-
-
-
-
- | CCI-001953 |
- SRG-OS-000376-GPOS-00161 |
+ CCI-001948 |
+ SRG-OS-000375-GPOS-00160 |
TBD - Assigned by DISA after STIG release |
- The operating system must accept Personal Identity Verification (PIV) credentials. |
-
- CCE-80846-9: Install the opensc Package For Multifactor Authentication |
+ The operating system must implement multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. |
- The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access.
+ | CCE-86120-3: Certificate status checking in SSSD |
-DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems.
-
-The opensc package can be installed with the following command:
-
-$ sudo yum install opensc |
- Applicable - Configurable |
- Verify the operating system accepts Personal Identity Verification (PIV) credentials. If it does not, this is a finding. |
- Run the following command to determine if the opensc package is installed: $ rpm -q opensc Is it the case that the package is not installed? |
- Configure the operating system to accept Personal Identity Verification (PIV) credentials. |
-
-The opensc package can be installed with the following command:
-
-$ sudo yum install opensc |
- medium |
- |
- |
- |
-
+
Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
+
+Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
+
+A privileged account is defined as an information system account with authorizations of a privileged user.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+
+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).
+
+Requires further clarification from NIST. |
+
Multifactor solutions that require devices separate from information systems gaining access include,
+for example, hardware tokens providing time-based or challenge-response authenticators and smart cards.
+Configuring certificate_verification to ocsp_dgst= ensures that certificates for
+multifactor solutions are checked via Online Certificate Status Protocol (OCSP). |
+
Applicable - Configurable |
+
Verify the operating system implements multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. If it does not, this is a finding. |
+
Check to see if Online Certificate Status Protocol (OCSP)
+is enabled and using the proper digest value on the system with the following command:
+$ sudo grep certificate_verification /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf | grep -v "^#"
+If configured properly, output should look like
+
+ certificate_verification = ocsp_dgst=
+ Is it the case that certificate_verification in sssd is not configured? |
+
Configure the operating system to implement multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. |
+
Multifactor solutions that require devices separate from information systems gaining access include,
+for example, hardware tokens providing time-based or challenge-response authenticators and smart cards.
+Configuring certificate_verification to ocsp_dgst= ensures that certificates for
+multifactor solutions are checked via Online Certificate Status Protocol (OCSP). |
+
medium |
+
|
+
|
+
|
+
+
+
+
+
+
+
+
+ | CCI-001953 |
+ SRG-OS-000376-GPOS-00161 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must accept Personal Identity Verification (PIV) credentials. |
+
+ CCE-80846-9: Install the opensc Package For Multifactor Authentication |
+
+ The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access.
+
+DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems. |
+
+The opensc package can be installed with the following command:
+
+$ sudo yum install opensc |
+ Applicable - Configurable |
+ Verify the operating system accepts Personal Identity Verification (PIV) credentials. If it does not, this is a finding. |
+ Run the following command to determine if the opensc package is installed: $ rpm -q opensc Is it the case that the package is not installed? |
+ Configure the operating system to accept Personal Identity Verification (PIV) credentials. |
+
+The opensc package can be installed with the following command:
+
+$ sudo yum install opensc |
+ medium |
+ |
+ |
+ |
+
@@ -34024,57 +34024,58 @@
TBD - Assigned by DISA after STIG release |
The operating system must authenticate peripherals before establishing a connection. |
-
CCE-80873-3: Disable the Automounter |
+
CCE-83774-0: Generate USBGuard Policy |
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers. |
-
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 |
+
By default USBGuard when enabled prevents access to all USB devices and this lead
+to inaccessible system if they use USB mouse/keyboard. To prevent this scenario,
+the initial policy configuration must be generated based on current connected USB
+devices. |
Applicable - Configurable |
Verify the operating system authenticates peripherals before establishing a connection. If it does not, this is a finding. |
-
To check that the autofs service is disabled in system boot configuration,
-run the following command:
-$ sudo systemctl is-enabled autofs
-Output should indicate the autofs service has either not been installed,
-or has been disabled at all runlevels, as shown in the example below:
-$ sudo systemctl is-enabled autofs
disabled
+ | Verify the USBGuard has a policy configured with the following command:
-Run the following command to verify autofs is not active (i.e. not running) through current runtime configuration:
-$ sudo systemctl is-active autofs
+$ usbguard list-rules
-If the service is not running the command will return the following output:
-inactive
+allow id 1d6b:0001 serial
-The service will also be masked, to check that the autofs is masked, run the following command:
-$ sudo systemctl show autofs | grep "LoadState\|UnitFileState"
+If the command does not return results or an error is returned, ask the SA to indicate how unauthorized peripherals are being blocked. Is it the case that there is no evidence that unauthorized peripherals are being blocked before establishing a connection? |
+
Configure the operating system to authenticate peripherals before establishing a connection. |
+
By default USBGuard when enabled prevents access to all USB devices and this lead
+to inaccessible system if they use USB mouse/keyboard. To prevent this scenario,
+the initial policy configuration must be generated based on current connected USB
+devices. |
+
medium |
+
|
+
|
+
|
+
-If the service is masked the command will return the following outputs:
+
+ | CCI-001958 |
+ SRG-OS-000378-GPOS-00163 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must authenticate peripherals before establishing a connection. |
-LoadState=masked
+ CCE-82959-8: Install usbguard Package |
-UnitFileState=masked
Is it the case that the "autofs" is loaded and not masked?
- Configure the operating system to authenticate peripherals before establishing a connection. |
- 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.
-
+ | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
-The autofs service can be disabled with the following command:
-$ sudo systemctl mask --now autofs.service |
+Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers.
+
+The usbguard package can be installed with the following command:
+
+$ sudo yum install usbguard |
+ Applicable - Configurable |
+ Verify the operating system authenticates peripherals before establishing a connection. If it does not, this is a finding. |
+ Run the following command to determine if the usbguard package is installed: $ rpm -q usbguard Is it the case that the package is not installed? |
+ Configure the operating system to authenticate peripherals before establishing a connection. |
+
+The usbguard package can be installed with the following command:
+
+$ sudo yum install usbguard |
medium |
|
|
@@ -34178,58 +34179,57 @@
TBD - Assigned by DISA after STIG release |
The operating system must authenticate peripherals before establishing a connection. |
- CCE-83774-0: Generate USBGuard Policy |
+ CCE-80873-3: Disable the Automounter |
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers. |
- By default USBGuard when enabled prevents access to all USB devices and this lead
-to inaccessible system if they use USB mouse/keyboard. To prevent this scenario,
-the initial policy configuration must be generated based on current connected USB
-devices. |
+ 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 |
Applicable - Configurable |
Verify the operating system authenticates peripherals before establishing a connection. If it does not, this is a finding. |
- Verify the USBGuard has a policy configured with the following command:
-
-$ usbguard list-rules
+ | To check that the autofs service is disabled in system boot configuration,
+run the following command:
+$ sudo systemctl is-enabled autofs
+Output should indicate the autofs service has either not been installed,
+or has been disabled at all runlevels, as shown in the example below:
+$ sudo systemctl is-enabled autofs
disabled
-allow id 1d6b:0001 serial
+Run the following command to verify autofs is not active (i.e. not running) through current runtime configuration:
+$ sudo systemctl is-active autofs
-If the command does not return results or an error is returned, ask the SA to indicate how unauthorized peripherals are being blocked. Is it the case that there is no evidence that unauthorized peripherals are being blocked before establishing a connection? |
- Configure the operating system to authenticate peripherals before establishing a connection. |
- By default USBGuard when enabled prevents access to all USB devices and this lead
-to inaccessible system if they use USB mouse/keyboard. To prevent this scenario,
-the initial policy configuration must be generated based on current connected USB
-devices. |
- medium |
- |
- |
- |
-
+If the service is not running the command will return the following output:
+
inactive
-
- | CCI-001958 |
- SRG-OS-000378-GPOS-00163 |
- TBD - Assigned by DISA after STIG release |
- The operating system must authenticate peripherals before establishing a connection. |
+The service will also be masked, to check that the autofs is masked, run the following command:
+$ sudo systemctl show autofs | grep "LoadState\|UnitFileState"
- CCE-82959-8: Install usbguard Package |
+If the service is masked the command will return the following outputs:
- Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
+LoadState=masked
-Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers. |
-
-The usbguard package can be installed with the following command:
-
-$ sudo yum install usbguard |
- Applicable - Configurable |
- Verify the operating system authenticates peripherals before establishing a connection. If it does not, this is a finding. |
- Run the following command to determine if the usbguard package is installed: $ rpm -q usbguard Is it the case that the package is not installed? |
+UnitFileState=masked
Is it the case that the "autofs" is loaded and not masked?
Configure the operating system to authenticate peripherals before establishing a connection. |
-
-The usbguard package can be installed with the following command:
-
-$ sudo yum install usbguard |
+ 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 |
medium |
|
|
@@ -34408,7 +34408,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-85944-7: Record Any Attempts to Run ssh-agent |
+ CCE-80700-8: Record Any Attempts to Run semanage |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -34418,33 +34418,33 @@
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
At a minimum, the audit system should collect any execution attempt
-of the ssh-agent command for all users and root. If the auditd
+of the semanage 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
+-a always,exit -F path=/usr/sbin/semanage -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/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
-$ sudo auditctl -l | grep ssh-agent
+$ sudo auditctl -l | grep semanage
--a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
At a minimum, the audit system should collect any execution attempt
-of the ssh-agent command for all users and root. If the auditd
+of the semanage 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
+-a always,exit -F path=/usr/sbin/semanage -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/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -34457,7 +34457,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80730-5: Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
+ CCE-80989-7: Ensure auditd Collects Information on the Use of Privileged Commands - mount |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -34471,33 +34471,29 @@
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/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "mount" command with the following command:
-$ sudo auditctl -l | grep pam_timestamp_check
+$ sudo auditctl -l | grep mount
--a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
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/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -34559,56 +34555,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80728-9: Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
-
- If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
-
-This requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.
-
-Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
-
-This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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 |
- Applicable - Configurable |
- Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "gpasswd" command with the following command:
-
-$ sudo auditctl -l | grep gpasswd
-
--a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-002884 |
- SRG-OS-000392-GPOS-00172 |
- TBD - Assigned by DISA after STIG release |
- The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
-
- CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
+ CCE-80731-3: Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -34622,29 +34569,29 @@
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
+-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/su -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "passwd" command with the following command:
-$ sudo auditctl -l | grep su
+$ sudo auditctl -l | grep passwd
--a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
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
+-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/su -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -34657,7 +34604,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
+ CCE-80872-5: Enable auditd Service |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -34666,71 +34613,27 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | The auditd service is an essential userspace component of
+the Linux Auditing System, as it is responsible for writing audit records to
+disk.
-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 |
+The auditd service can be enabled with the following command:
+$ sudo systemctl enable auditd.service
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r truncate /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep truncate /etc/audit/audit.rules
-
-The output should be the following:
+ |
--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+Run the following command to determine the current status of the
+auditd service:
+$ sudo systemctl is-active auditd
+If the service is running, it should return the following: active
Is it the case that the auditd service is not running?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | The auditd service is an essential userspace component of
+the Linux Auditing System, as it is responsible for writing audit records to
+disk.
-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 |
+The auditd service can be enabled with the following command:
+$ sudo systemctl enable auditd.service
medium |
|
|
@@ -34743,7 +34646,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80729-7: Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
+ CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -34752,34 +34655,42 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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 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 |
+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_mod
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "newgrp" command with the following command:
-
-$ sudo auditctl -l | grep newgrp
-
--a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+chown system call, run the following command:
+$ sudo grep "chown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | 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 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 |
+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_mod
medium |
|
|
@@ -34792,7 +34703,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
+ CCE-80701-6: Record Any Attempts to Run setsebool |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -34801,65 +34712,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 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
+-a always,exit -F path=/usr/sbin/setsebool -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 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=access |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r open_by_handle_at /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep open_by_handle_at /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep setsebool
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 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
+-a always,exit -F path=/usr/sbin/setsebool -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 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=access |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -34872,7 +34752,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
+ CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -34881,91 +34761,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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_mod |
- Applicable - Configurable |
- Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-lchown system call, run the following command:
-$ sudo grep "lchown" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-002884 |
- SRG-OS-000392-GPOS-00172 |
- TBD - Assigned by DISA after STIG release |
- The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
-
- CCE-89455-0: Ensure auditd Collects Information on the Use of Privileged Commands - kmod |
-
- If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
-
-This requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.
-
-Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
-
-This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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/kmod -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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-w /etc/sudoers -p wa -k actions
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "kmod" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-$ sudo auditctl -l | grep kmod
+$ sudo auditctl -l | grep /etc/sudoers
--a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-kmod Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers -p wa -k actions
medium |
|
|
@@ -34978,7 +34801,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -34993,21 +34816,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+$ sudo auditctl -l | grep -E '(/etc/shadow)'
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -35015,14 +34838,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -35035,7 +34858,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80733-9: Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
+ CCE-89455-0: Ensure auditd Collects Information on the Use of Privileged Commands - kmod |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35049,29 +34872,29 @@
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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/bin/kmod -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postqueue" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "kmod" command with the following command:
-$ sudo auditctl -l | grep postqueue
+$ sudo auditctl -l | grep kmod
--a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-kmod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/bin/kmod -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -35084,7 +34907,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-89446-9: Record Any Attempts to Run chacl |
+ CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35093,34 +34916,50 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 lines to
+utility to read audit rules during daemon startup, add the following line 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 |
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
-
-$ sudo auditctl -l | grep chacl
-
--a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fsetxattr system call, run the following command:
+$ sudo grep "fsetxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | 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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 lines to
+utility to read audit rules during daemon startup, add the following line 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 |
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -35133,7 +34972,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80740-4: Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
+ CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35142,34 +34981,50 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
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 |
+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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command:
-
-$ sudo auditctl -l | grep unix_chkpwd
-
--a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+setxattr system call, run the following command:
+$ sudo grep "setxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
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 |
+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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -35182,7 +35037,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
+ CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35191,34 +35046,71 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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 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 |
+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=access
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-$ sudo auditctl -l | grep usermod
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r truncate /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep truncate /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | 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 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 |
+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=access
medium |
|
|
@@ -35231,7 +35123,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
+ CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35240,34 +35132,144 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+
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 |
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
+ | To determine if the system is configured to audit calls to the
+removexattr system call, run the following command:
+$ sudo grep "removexattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
+ 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+ medium |
+ |
+ |
+ |
+
-$ sudo auditctl -l | grep sudo
+
+ | CCI-002884 |
+ SRG-OS-000392-GPOS-00172 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
--a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out?
+ CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
+
+ If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
+
+This requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.
+
+Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
+
+This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
+ 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 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=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=access |
+ Applicable - Configurable |
+ Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
+
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
+
+$ sudo grep -r ftruncate /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep ftruncate /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | 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 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=access
+
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 |
+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=access
medium |
|
|
@@ -35280,7 +35282,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80726-3: Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
+ CCE-80732-1: Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35294,29 +35296,29 @@
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
+-a always,exit -F path=/usr/sbin/postdrop -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 |
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chsh" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postdrop" command with the following command:
-$ sudo auditctl -l | grep chsh
+$ sudo auditctl -l | grep postdrop
--a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
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
+-a always,exit -F path=/usr/sbin/postdrop -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 |
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -35329,7 +35331,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
+ CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35344,17 +35346,17 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-unlink system call, run the following command:
-$ sudo grep "unlink" /etc/audit/audit.*
+unlinkat system call, run the following command:
+$ sudo grep "unlinkat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
@@ -35364,12 +35366,12 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -35382,7 +35384,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80741-2: Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
+ CCE-80728-9: Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35396,82 +35398,29 @@
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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "userhelper" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "gpasswd" command with the following command:
-$ sudo auditctl -l | grep userhelper
+$ sudo auditctl -l | grep gpasswd
--a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
- medium |
- |
- |
- |
-
-
-
- | CCI-002884 |
- SRG-OS-000392-GPOS-00172 |
- TBD - Assigned by DISA after STIG release |
- The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
-
- CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
-
- If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
-
-This requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.
-
-Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
-
-This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
- Applicable - Configurable |
- Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-finit_module system call, run the following command:
-$ sudo grep "finit_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -35484,7 +35433,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
+ CCE-80725-5: Ensure auditd Collects Information on the Use of Privileged Commands - chage |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35493,42 +35442,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
-
+ | 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 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 |
+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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chage" command with the following command:
-$ sudo auditctl -l | grep -E '(/etc/shadow)'
+$ sudo auditctl -l | grep chage
--w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
-
+ | 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 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 |
+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
medium |
|
|
@@ -35541,7 +35482,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80727-1: Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
+ CCE-81043-2: Ensure the audit Subsystem is Installed |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35550,34 +35491,12 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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 |
+ The audit package should be installed. |
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "crontab" command with the following command:
-
-$ sudo auditctl -l | grep crontab
-
--a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out? |
+ Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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 |
+ The audit package should be installed. |
medium |
|
|
@@ -35590,7 +35509,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80701-6: Record Any Attempts to Run setsebool |
+ CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35599,34 +35518,48 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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
+ | 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 path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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 lines to
+utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
-
-$ sudo auditctl -l | grep setsebool
-
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fchown system call, run the following command:
+$ sudo grep "fchown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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
+ | 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 path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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 lines to
+utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
medium |
|
|
@@ -35639,7 +35572,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
+ CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35653,60 +35586,60 @@
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
+-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 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
+-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 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
+-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 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 |
+-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=access
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r creat /etc/audit/rules.d
+$ sudo grep -r open_by_handle_at /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep creat /etc/audit/audit.rules
+$ sudo grep open_by_handle_at /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
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
+-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 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
+-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 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
+-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 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 |
+-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=access
medium |
|
|
@@ -35719,7 +35652,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80718-0: Record Attempts to Alter Logon and Logout Events - faillock |
+ CCE-80729-7: Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35728,38 +35661,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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 -p wa -k logins
+ | 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 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 -p wa -k logins |
+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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "newgrp" command with the following command:
-$ sudo auditctl -l | grep
+$ sudo auditctl -l | grep newgrp
--w -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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 -p wa -k logins
+ | 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 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 -p wa -k logins |
+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
medium |
|
|
@@ -35772,7 +35701,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80722-2: Ensure auditd Collects Information on Exporting to Media (successful) |
+ CCE-80741-2: Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35781,38 +35710,158 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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/userhelper -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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ Applicable - Configurable |
+ Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "userhelper" command with the following command:
+
+$ sudo auditctl -l | grep userhelper
+
+-a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
+ 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/userhelper -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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-002884 |
+ SRG-OS-000392-GPOS-00172 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
+
+ CCE-80740-4: Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
+
+ If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
+
+This requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.
+
+Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
+
+This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command:
+
+$ sudo auditctl -l | grep unix_chkpwd
+
+-a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-002884 |
+ SRG-OS-000392-GPOS-00172 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
+
+ CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
+
+ If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
+
+This requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.
+
+Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
+
+This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
+ 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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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, 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 |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-mount system call, run the following command:
-$ sudo grep "mount" /etc/audit/audit.*
+lremovexattr system call, run the following command:
+$ sudo grep "lremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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, 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 |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -35825,7 +35874,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
+ CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35835,41 +35884,41 @@
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
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
+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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchmod system call, run the following command:
-$ sudo grep "fchmod" /etc/audit/audit.*
+fchownat system call, run the following command:
+$ sudo grep "fchownat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
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
+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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -35882,7 +35931,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
+ CCE-89446-9: Record Any Attempts to Run chacl |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35891,40 +35940,35 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ 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 |
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes audit_backlog_limit=8192,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
-The command should not return any output. Is it the case that audit backlog limit is not configured? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
+
+$ sudo auditctl -l | grep chacl
+
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
- low |
+ 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 |
+ medium |
|
|
|
@@ -35936,7 +35980,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
+ CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35945,34 +35989,38 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- At a minimum, the audit system should collect administrator actions
+ | At a minimum, the audit system should collect file deletion 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:
--w /etc/sudoers.d/ -p wa -k actions
+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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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:
--w /etc/sudoers.d/ -p wa -k actions |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-
-$ sudo auditctl -l | grep/etc/sudoers.d
-
--w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+unlink system call, run the following command:
+$ sudo grep "unlink" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- At a minimum, the audit system should collect administrator actions
+ | At a minimum, the audit system should collect file deletion 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:
--w /etc/sudoers.d/ -p wa -k actions
+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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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:
--w /etc/sudoers.d/ -p wa -k actions |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -35985,7 +36033,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
+ CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -35999,66 +36047,66 @@
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
+-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 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=access
+-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 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
+-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 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=access |
+-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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r ftruncate /etc/audit/rules.d
+$ sudo grep -r open /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep ftruncate /etc/audit/audit.rules
+$ sudo grep open /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
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
+-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 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=access
+-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 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
+-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 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=access |
+-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
medium |
|
|
@@ -36071,7 +36119,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
+ CCE-80726-3: Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36080,42 +36128,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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 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_mod |
+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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchmodat system call, run the following command:
-$ sudo grep "fchmodat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chsh" command with the following command:
+
+$ sudo auditctl -l | grep chsh
+
+-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | 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 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_mod |
+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
medium |
|
|
@@ -36128,7 +36168,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
+ CCE-80739-6: Ensure auditd Collects Information on the Use of Privileged Commands - umount |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36137,42 +36177,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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 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_mod |
+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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchownat system call, run the following command:
-$ sudo grep "fchownat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "umount" command with the following command:
+
+$ sudo auditctl -l | grep umount
+
+-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | 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 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_mod |
+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
medium |
|
|
@@ -36185,7 +36217,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
+ CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36194,50 +36226,38 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+ | 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 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-setxattr system call, run the following command:
-$ sudo grep "setxattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
+
+$ sudo auditctl -l | grep /var/log/lastlog
+
+-w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+ | 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 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+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
medium |
|
|
@@ -36250,7 +36270,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+ CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36259,34 +36279,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 the following line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
-$ sudo auditctl -l | grep /etc/sudoers
+$ sudo auditctl -l | grep su
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 the following line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
medium |
|
|
@@ -36299,7 +36319,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80713-1: Ensure auditd Collects Information on Kernel Module Loading - init_module |
+ CCE-80727-1: Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36308,38 +36328,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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 auid>=1000 -F auid!=unset -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. |
+ 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 |
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-init_module system call, run the following command:
-$ sudo grep "init_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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 auid>=1000 -F auid!=unset -F key=modules
-
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "crontab" command with the following command:
-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.
+$ sudo auditctl -l | grep crontab
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules. |
+-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out?
+ Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
+ 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 |
medium |
|
|
@@ -36352,7 +36368,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36361,42 +36377,42 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+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 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_mod |
+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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-chmod system call, run the following command:
-$ sudo grep "chmod" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
+
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+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 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_mod |
+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
medium |
|
|
@@ -36409,7 +36425,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
+ CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36424,17 +36440,17 @@
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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-unlinkat system call, run the following command:
-$ sudo grep "unlinkat" /etc/audit/audit.*
+rename system call, run the following command:
+$ sudo grep "rename" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
@@ -36444,12 +36460,12 @@
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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -36462,7 +36478,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+ CCE-85944-7: Record Any Attempts to Run ssh-agent |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36471,42 +36487,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
-
+ | 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, in order to capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification |
+/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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command:
-$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+$ sudo auditctl -l | grep ssh-agent
--w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
-
+ | 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, in order to capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification |
+/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
medium |
|
|
@@ -36519,7 +36527,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-88437-9: Record Any Attempts to Run setfacl |
+ CCE-80713-1: Ensure auditd Collects Information on Kernel Module Loading - init_module |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36528,34 +36536,38 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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 |
+ 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 auid>=1000 -F auid!=unset -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. |
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfacl" command with the following command:
+ | To determine if the system is configured to audit calls to the
+init_module system call, run the following command:
+$ sudo grep "init_module" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
+ 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:
-$ sudo auditctl -l | grep setfacl
+-a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modules
--a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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 |
+
+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.
medium |
|
|
@@ -36568,7 +36580,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
+ CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36578,47 +36590,41 @@
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
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
-
+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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchown system call, run the following command:
-$ sudo grep "fchown" /etc/audit/audit.*
+fchmod system call, run the following command:
+$ sudo grep "fchmod" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
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
-
+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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -36631,7 +36637,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
+ CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36640,71 +36646,42 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- At a minimum, the audit system should collect unauthorized file
-accesses for all users and root. If the auditd daemon is configured
+ | 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 lines to a file with suffix
+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 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
-
+-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 lines to
+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 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 |
+-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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r openat /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep openat /etc/audit/audit.rules
-
-The output should be the following:
-
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+lchown system call, run the following command:
+$ sudo grep "lchown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- At a minimum, the audit system should collect unauthorized file
-accesses for all users and root. If the auditd daemon is configured
+ | 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 lines to a file with suffix
+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 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
-
+-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 lines to
+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 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 |
+-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
medium |
|
|
@@ -36717,7 +36694,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-81043-2: Ensure the audit Subsystem is Installed |
+ CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36726,12 +36703,38 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- The audit package should be installed. |
+ At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
+ To determine if the system is configured to audit calls to the
+renameat system call, run the following command:
+$ sudo grep "renameat" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- The audit package should be installed. |
+ At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
medium |
|
|
@@ -36744,7 +36747,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80725-5: Ensure auditd Collects Information on the Use of Privileged Commands - chage |
+ CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36753,34 +36756,65 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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 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 |
+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=access
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chage" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
-$ sudo auditctl -l | grep chage
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r creat /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep creat /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | 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 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 |
+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=access
medium |
|
|
@@ -36793,7 +36827,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+ CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36802,50 +36836,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
-If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
-If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-w /etc/sudoers.d/ -p wa -k actions
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-lsetxattr system call, run the following command:
-$ sudo grep "lsetxattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
+
+$ sudo auditctl -l | grep/etc/sudoers.d
+
+-w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
-If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
-If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-w /etc/sudoers.d/ -p wa -k actions
medium |
|
|
@@ -36858,7 +36876,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
+ CCE-80711-5: Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36867,50 +36885,38 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+ 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 auid>=1000 -F auid!=unset -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. |
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fsetxattr system call, run the following command:
-$ sudo grep "fsetxattr" /etc/audit/audit.*
+delete_module system call, run the following command:
+$ sudo grep "delete_module" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+ 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 auid>=1000 -F auid!=unset -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. |
medium |
|
|
@@ -36923,7 +36929,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80989-7: Ensure auditd Collects Information on the Use of Privileged Commands - mount |
+ CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36937,29 +36943,29 @@
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
+-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/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "mount" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
-$ sudo auditctl -l | grep mount
+$ sudo auditctl -l | grep usermod
--a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
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
+-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/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -36972,7 +36978,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
+ CCE-80718-0: Record Attempts to Alter Logon and Logout Events - faillock |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -36981,71 +36987,38 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
-
+ | 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 -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:
--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 |
+/etc/audit/audit.rules file in order to watch for unattempted manual
+edits of files involved in storing logon events:
+-w -p wa -k logins
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r open /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep open /etc/audit/audit.rules
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-w -p wa -k logins Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
-
+ | 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 -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:
--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 |
+/etc/audit/audit.rules file in order to watch for unattempted manual
+edits of files involved in storing logon events:
+-w -p wa -k logins
medium |
|
|
@@ -37058,7 +37031,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
+ CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37067,38 +37040,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-rename system call, run the following command:
-$ sudo grep "rename" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
+
+$ sudo auditctl -l | grep sudo
+
+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
@@ -37111,7 +37080,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80739-6: Ensure auditd Collects Information on the Use of Privileged Commands - umount |
+ CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37120,34 +37089,50 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
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 |
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "umount" command with the following command:
-
-$ sudo auditctl -l | grep umount
-
--a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+lsetxattr system call, run the following command:
+$ sudo grep "lsetxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
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 |
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -37160,7 +37145,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+ CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37169,42 +37154,71 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
-
+ | 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, in order to capture events that modify
-account changes:
-
--w /etc/group -p wa -k audit_rules_usergroup_modification |
+/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=access
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
-$ sudo auditctl -l | grep -E '(/etc/group)'
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r openat /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep openat /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
-
+ | 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, in order to capture events that modify
-account changes:
-
--w /etc/group -p wa -k audit_rules_usergroup_modification |
+/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=access
medium |
|
|
@@ -37270,7 +37284,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80731-3: Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
+ CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37279,83 +37293,42 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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 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 |
- Applicable - Configurable |
- Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "passwd" command with the following command:
-
-$ sudo auditctl -l | grep passwd
-
--a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-002884 |
- SRG-OS-000392-GPOS-00172 |
- TBD - Assigned by DISA after STIG release |
- The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
-
- CCE-80700-8: Record Any Attempts to Run semanage |
-
- If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
-
-This requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.
-
-Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
-
-This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -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
+utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
-
-$ sudo auditctl -l | grep semanage
-
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fchmodat system call, run the following command:
+$ sudo grep "fchmodat" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 lines to
+utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
medium |
|
|
@@ -37368,7 +37341,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
+ CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37380,55 +37353,57 @@
| 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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
+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
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-removexattr system call, run the following command:
-$ sudo grep "removexattr" /etc/audit/audit.*
+fremovexattr system call, run the following command:
+$ sudo grep "fremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
+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
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -37441,7 +37416,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
+ CCE-80722-2: Ensure auditd Collects Information on Exporting to Media (successful) |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37450,42 +37425,38 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured to
+ | 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:
--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
+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:
--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 |
+/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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-chown system call, run the following command:
-$ sudo grep "chown" /etc/audit/audit.*
+mount system call, run the following command:
+$ sudo grep "mount" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured to
+ | 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:
--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
+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:
--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 |
+/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
medium |
|
|
@@ -37498,7 +37469,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80711-5: Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
+ CCE-80733-9: Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37507,38 +37478,87 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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:
+ | 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/postqueue -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ Applicable - Configurable |
+ Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postqueue" command with the following command:
--a always,exit -F arch=ARCH -S delete_module -F auid>=1000 -F auid!=unset -F key=modules
+$ sudo auditctl -l | grep postqueue
+-a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
+ 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/postqueue -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ medium |
+ |
+ |
+ |
+
-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.
+
+ | CCI-002884 |
+ SRG-OS-000392-GPOS-00172 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules.
+ CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
+
+ If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
+
+This requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.
+
+Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
+
+This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
+ 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-delete_module system call, run the following command:
-$ sudo grep "delete_module" /etc/audit/audit.*
+finit_module system call, run the following command:
+$ sudo grep "finit_module" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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 auid>=1000 -F auid!=unset -F key=modules
-
+ | 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:
-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.
+-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -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:
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules. |
+-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -F key=modules
medium |
|
|
@@ -37551,7 +37571,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-82280-9: Record Any Attempts to Run setfiles |
+ CCE-88437-9: Record Any Attempts to Run setfacl |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37561,33 +37581,33 @@
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
At a minimum, the audit system should collect any execution attempt
-of the setfiles command for all users and root. If the auditd
+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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfacl" command with the following command:
-$ sudo auditctl -l | grep setfiles
+$ sudo auditctl -l | grep setfacl
--a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
At a minimum, the audit system should collect any execution attempt
-of the setfiles command for all users and root. If the auditd
+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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -37600,7 +37620,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
+ CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37609,61 +37629,40 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-lremovexattr system call, run the following command:
-$ sudo grep "lremovexattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes audit_backlog_limit=8192,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
+The command should not return any output. Is it the case that audit backlog limit is not configured? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
- medium |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ low |
|
|
|
@@ -37675,7 +37674,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
+ CCE-82280-9: Record Any Attempts to Run setfiles |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37684,44 +37683,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
-
+ | At a minimum, the audit system should collect any execution attempt
+of the setfiles 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/sbin/setfiles -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, in order to capture events that modify
-account changes:
-
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification |
+/etc/audit/audit.rules file:
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
--w /etc/gshadow -p wa -k identity
+$ sudo auditctl -l | grep setfiles
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
-
+ | At a minimum, the audit system should collect any execution attempt
+of the setfiles 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/sbin/setfiles -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, in order to capture events that modify
-account changes:
-
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification |
+/etc/audit/audit.rules file:
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -37734,7 +37723,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
+ CCE-80825-3: Enable Auditing for Processes Which Start Prior to the Audit Daemon |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37743,61 +37732,40 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
+ To ensure all processes can be audited, even those which start
+prior to the audit daemon, add the argument audit=1 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit=1 is added as a kernel command line
+argument to newly installed kernels, add audit=1 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit=1 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fremovexattr system call, run the following command:
-$ sudo grep "fremovexattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes audit=1,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit=1.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*audit=1.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'audit=1'
+The command should not return any output. Is it the case that auditing is not enabled at boot time? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
- medium |
+ To ensure all processes can be audited, even those which start
+prior to the audit daemon, add the argument audit=1 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit=1 is added as a kernel command line
+argument to newly installed kernels, add audit=1 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit=1 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
+ low |
|
|
|
@@ -37809,7 +37777,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
+ CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37818,80 +37786,42 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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 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 |
+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_mod
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
-
-$ sudo auditctl -l | grep /var/log/lastlog
-
--w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+chmod system call, run the following command:
+$ sudo grep "chmod" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | 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 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-002884 |
- SRG-OS-000392-GPOS-00172 |
- TBD - Assigned by DISA after STIG release |
- The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
-
- CCE-80872-5: Enable auditd Service |
-
- If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
-
-This requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.
-
-Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
-
-This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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 |
- Applicable - Configurable |
- Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-auditd service:
-$ sudo systemctl is-active auditd
-If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
- Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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 |
+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_mod
medium |
|
|
@@ -37904,7 +37834,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80698-4: Record Any Attempts to Run chcon |
+ CCE-89480-8: Ensure auditd Collects Information on the Use of Privileged Commands - unix_update |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37913,34 +37843,34 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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
+ | 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_update -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 |
+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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_update" command with the following command:
-$ sudo auditctl -l | grep chcon
+$ sudo auditctl -l | grep unix_update
--a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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
+ | 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_update -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 |
+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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -37953,7 +37883,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-89480-8: Ensure auditd Collects Information on the Use of Privileged Commands - unix_update |
+ CCE-80730-5: Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -37967,29 +37897,33 @@
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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/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=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/pam_timestamp_check
+-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_update" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command:
-$ sudo auditctl -l | grep unix_update
+$ sudo auditctl -l | grep pam_timestamp_check
--a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/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=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/pam_timestamp_check
+-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -38002,7 +37936,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80825-3: Enable Auditing for Processes Which Start Prior to the Audit Daemon |
+ CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -38011,40 +37945,45 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- To ensure all processes can be audited, even those which start
-prior to the audit daemon, add the argument audit=1 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit=1 is added as a kernel command line
-argument to newly installed kernels, add audit=1 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit=1 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
+ 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 |
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes audit=1,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit=1.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*audit=1.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'audit=1'
-The command should not return any output. Is it the case that auditing is not enabled at boot time? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- To ensure all processes can be audited, even those which start
-prior to the audit daemon, add the argument audit=1 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit=1 is added as a kernel command line
-argument to newly installed kernels, add audit=1 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit=1 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
- low |
+ 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 |
+ medium |
|
|
|
@@ -38056,7 +37995,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80732-1: Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
+ CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -38065,34 +38004,42 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- 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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 a line of the following
-form to /etc/audit/audit.rules:
--a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postdrop" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
-$ sudo auditctl -l | grep postdrop
+$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
--a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- 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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 a line of the following
-form to /etc/audit/audit.rules:
--a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
medium |
|
|
@@ -38105,7 +38052,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
+ CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
@@ -38114,132 +38061,101 @@
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch. |
- At a minimum, the audit system should collect file deletion events
-for all users and root. If the auditd daemon is configured to use the
+ | 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-renameat system call, run the following command:
-$ sudo grep "renameat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/group)'
+
+-w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- At a minimum, the audit system should collect file deletion events
-for all users and root. If the auditd daemon is configured to use the
+ | 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
|
-
-
-
-
-
- | CCI-002890 |
- SRG-OS-000393-GPOS-00173 |
+ CCI-002884 |
+ SRG-OS-000392-GPOS-00172 |
TBD - Assigned by DISA after STIG release |
- The operating system must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
+ The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. |
- CCE-85902-5: Configure SSH Client to Use FIPS 140-2 Validated Ciphers: openssh.config |
+ CCE-80698-4: Record Any Attempts to Run chcon |
- Privileged access contains control and configuration information and is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms, such as a hash function or digital signature, to protect integrity.
+ | If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.
-Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
+This requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.
-The operating system can meet this requirement through leveraging a cryptographic module. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system (e.g., the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch). |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
-set up incorrectly.
+Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
-To check that Crypto Policies settings for ciphers are configured correctly, ensure that
-/etc/crypto-policies/back-ends/openssh.config contains the following
-line and is not commented out:
-Ciphers |
+This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch.
+ 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 |
Applicable - Configurable |
- Verify the operating system implements cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. If it does not, this is a finding. |
- To verify if the OpenSSH client uses defined Cipher suite in the Crypto Policy, run:
-$ grep -i ciphers /etc/crypto-policies/back-ends/openssh.config
-and verify that the line matches:
-Ciphers Is it the case that Crypto Policy for OpenSSH client is not configured correctly? |
- Configure the operating system to implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
-set up incorrectly.
+ | Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
-To check that Crypto Policies settings for ciphers are configured correctly, ensure that
-/etc/crypto-policies/back-ends/openssh.config contains the following
-line and is not commented out:
-Ciphers |
- high |
+$ sudo auditctl -l | grep chcon
+
+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out?
+ Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions. |
+ 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 |
+ medium |
|
|
|
-
- | CCI-002890 |
- SRG-OS-000393-GPOS-00173 |
- TBD - Assigned by DISA after STIG release |
- The operating system must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
-
- CCE-84027-2: Set kernel parameter 'crypto.fips_enabled' to 1 |
-
- Privileged access contains control and configuration information and is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms, such as a hash function or digital signature, to protect integrity.
-Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
-The operating system can meet this requirement through leveraging a cryptographic module. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system (e.g., the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch). |
- System running in FIPS mode is indicated by kernel parameter
-'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
-To enable FIPS mode, run the following command:
-fips-mode-setup --enable
-To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
-parameters during system installation so key generation is done with FIPS-approved algorithms
-and continuous monitoring tests in place. |
- Applicable - Configurable |
- Verify the operating system implements cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. If it does not, this is a finding. |
- To verify that kernel parameter 'crypto.fips_enabled' is set properly, run the following command:
-sysctl crypto.fips_enabled
-The output should contain the following:
-crypto.fips_enabled = 1 Is it the case that crypto.fips_enabled is not 1? |
- Configure the operating system to implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
- System running in FIPS mode is indicated by kernel parameter
-'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
-To enable FIPS mode, run the following command:
-fips-mode-setup --enable
-To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
-parameters during system installation so key generation is done with FIPS-approved algorithms
-and continuous monitoring tests in place. |
- high |
- |
- |
- |
-
| CCI-002890 |
@@ -38360,26 +38276,19 @@
|
-
-
-
-
-
- | CCI-003123 |
- SRG-OS-000394-GPOS-00174 |
+ CCI-002890 |
+ SRG-OS-000393-GPOS-00173 |
TBD - Assigned by DISA after STIG release |
- The operating system must implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
+ The operating system must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
CCE-85902-5: Configure SSH Client to Use FIPS 140-2 Validated Ciphers: openssh.config |
- Privileged access contains control and configuration information and is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms such as encryption to protect confidentiality.
+ | Privileged access contains control and configuration information and is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms, such as a hash function or digital signature, to protect integrity.
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
-This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system (e.g., the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch).
-
-The operating system can meet this requirement through leveraging a cryptographic module. |
+The operating system can meet this requirement through leveraging a cryptographic module. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system (e.g., the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch).
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
@@ -38389,12 +38298,12 @@
line and is not commented out:
Ciphers |
Applicable - Configurable |
- Verify the operating system implements cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. If it does not, this is a finding. |
+ Verify the operating system implements cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. If it does not, this is a finding. |
To verify if the OpenSSH client uses defined Cipher suite in the Crypto Policy, run:
$ grep -i ciphers /etc/crypto-policies/back-ends/openssh.config
and verify that the line matches:
Ciphers Is it the case that Crypto Policy for OpenSSH client is not configured correctly? |
- Configure the operating system to implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
+ Configure the operating system to implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
@@ -38410,20 +38319,18 @@
|
- | CCI-003123 |
- SRG-OS-000394-GPOS-00174 |
+ CCI-002890 |
+ SRG-OS-000393-GPOS-00173 |
TBD - Assigned by DISA after STIG release |
- The operating system must implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
+ The operating system must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
CCE-84027-2: Set kernel parameter 'crypto.fips_enabled' to 1 |
- Privileged access contains control and configuration information and is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms such as encryption to protect confidentiality.
+ | Privileged access contains control and configuration information and is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms, such as a hash function or digital signature, to protect integrity.
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
-This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system (e.g., the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch).
-
-The operating system can meet this requirement through leveraging a cryptographic module. |
+The operating system can meet this requirement through leveraging a cryptographic module. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system (e.g., the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch).
System running in FIPS mode is indicated by kernel parameter
'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
To enable FIPS mode, run the following command:
@@ -38433,12 +38340,12 @@
parameters during system installation so key generation is done with FIPS-approved algorithms
and continuous monitoring tests in place. |
Applicable - Configurable |
- Verify the operating system implements cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. If it does not, this is a finding. |
+ Verify the operating system implements cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. If it does not, this is a finding. |
To verify that kernel parameter 'crypto.fips_enabled' is set properly, run the following command:
sysctl crypto.fips_enabled
The output should contain the following:
crypto.fips_enabled = 1 Is it the case that crypto.fips_enabled is not 1? |
- Configure the operating system to implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
+ Configure the operating system to implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
System running in FIPS mode is indicated by kernel parameter
'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
To enable FIPS mode, run the following command:
@@ -38453,6 +38360,11 @@
| |
+
+
+
+
+
| CCI-003123 |
SRG-OS-000394-GPOS-00174 |
@@ -38576,25 +38488,113 @@
|
+
+ | CCI-003123 |
+ SRG-OS-000394-GPOS-00174 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
+ CCE-85902-5: Configure SSH Client to Use FIPS 140-2 Validated Ciphers: openssh.config |
+ Privileged access contains control and configuration information and is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms such as encryption to protect confidentiality.
+Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
+This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system (e.g., the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch).
- |
- | CCI-002891 |
- SRG-OS-000395-GPOS-00175 |
- TBD - Assigned by DISA after STIG release |
- The operating system must verify remote disconnection at the termination of nonlocal maintenance and diagnostic sessions, when used for nonlocal maintenance sessions. |
-
- CCE-80906-1: Set SSH Client Alive Interval |
+The operating system can meet this requirement through leveraging a cryptographic module.
+ Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
+set up incorrectly.
- | If the remote connection is not closed and verified as closed, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Remote connections must be disconnected and verified as disconnected when nonlocal maintenance sessions have been terminated and are no longer available for use. |
- SSH allows administrators to set a network responsiveness timeout interval.
-After this interval has passed, the unresponsive client will be automatically logged out.
-
-To set this timeout interval, edit the following line in /etc/ssh/sshd_config as
-follows:
+To check that Crypto Policies settings for ciphers are configured correctly, ensure that
+/etc/crypto-policies/back-ends/openssh.config contains the following
+line and is not commented out:
+Ciphers |
+ Applicable - Configurable |
+ Verify the operating system implements cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. If it does not, this is a finding. |
+ To verify if the OpenSSH client uses defined Cipher suite in the Crypto Policy, run:
+$ grep -i ciphers /etc/crypto-policies/back-ends/openssh.config
+and verify that the line matches:
+Ciphers Is it the case that Crypto Policy for OpenSSH client is not configured correctly? |
+ Configure the operating system to implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
+ Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
+set up incorrectly.
+
+To check that Crypto Policies settings for ciphers are configured correctly, ensure that
+/etc/crypto-policies/back-ends/openssh.config contains the following
+line and is not commented out:
+Ciphers |
+ high |
+ |
+ |
+ |
+
+
+
+ | CCI-003123 |
+ SRG-OS-000394-GPOS-00174 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
+
+ CCE-84027-2: Set kernel parameter 'crypto.fips_enabled' to 1 |
+
+ Privileged access contains control and configuration information and is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms such as encryption to protect confidentiality.
+
+Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
+
+This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system (e.g., the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch).
+
+The operating system can meet this requirement through leveraging a cryptographic module. |
+ System running in FIPS mode is indicated by kernel parameter
+'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
+To enable FIPS mode, run the following command:
+fips-mode-setup --enable
+
+To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
+parameters during system installation so key generation is done with FIPS-approved algorithms
+and continuous monitoring tests in place. |
+ Applicable - Configurable |
+ Verify the operating system implements cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. If it does not, this is a finding. |
+ To verify that kernel parameter 'crypto.fips_enabled' is set properly, run the following command:
+sysctl crypto.fips_enabled
+The output should contain the following:
+crypto.fips_enabled = 1 Is it the case that crypto.fips_enabled is not 1? |
+ Configure the operating system to implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. |
+ System running in FIPS mode is indicated by kernel parameter
+'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
+To enable FIPS mode, run the following command:
+fips-mode-setup --enable
+
+To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
+parameters during system installation so key generation is done with FIPS-approved algorithms
+and continuous monitoring tests in place. |
+ high |
+ |
+ |
+ |
+
+
+
+
+
+
+
+
+ | CCI-002891 |
+ SRG-OS-000395-GPOS-00175 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must verify remote disconnection at the termination of nonlocal maintenance and diagnostic sessions, when used for nonlocal maintenance sessions. |
+
+ CCE-80906-1: Set SSH Client Alive Interval |
+
+ If the remote connection is not closed and verified as closed, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Remote connections must be disconnected and verified as disconnected when nonlocal maintenance sessions have been terminated and are no longer available for use. |
+ SSH allows administrators to set a network responsiveness timeout interval.
+After this interval has passed, the unresponsive client will be automatically logged out.
+
+To set this timeout interval, edit the following line in /etc/ssh/sshd_config as
+follows:
ClientAliveInterval
The timeout interval is given in seconds. For example, have a timeout
@@ -38684,44 +38684,6 @@
| |
-
- | CCI-002450 |
- SRG-OS-000396-GPOS-00176 |
- TBD - Assigned by DISA after STIG release |
- The operating system must implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. |
-
- CCE-84027-2: Set kernel parameter 'crypto.fips_enabled' to 1 |
-
- Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The operating system must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. |
- System running in FIPS mode is indicated by kernel parameter
-'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
-To enable FIPS mode, run the following command:
-fips-mode-setup --enable
-
-To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
-parameters during system installation so key generation is done with FIPS-approved algorithms
-and continuous monitoring tests in place. |
- Applicable - Configurable |
- Verify the operating system implements NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. If it does not, this is a finding. |
- To verify that kernel parameter 'crypto.fips_enabled' is set properly, run the following command:
-sysctl crypto.fips_enabled
-The output should contain the following:
-crypto.fips_enabled = 1 Is it the case that crypto.fips_enabled is not 1? |
- Configure the operating system to implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. |
- System running in FIPS mode is indicated by kernel parameter
-'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
-To enable FIPS mode, run the following command:
-fips-mode-setup --enable
-
-To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
-parameters during system installation so key generation is done with FIPS-approved algorithms
-and continuous monitoring tests in place. |
- high |
- |
- |
- |
-
-
| CCI-002450 |
SRG-OS-000396-GPOS-00176 |
@@ -38763,6 +38725,44 @@
|
+
+ | CCI-002450 |
+ SRG-OS-000396-GPOS-00176 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. |
+
+ CCE-84027-2: Set kernel parameter 'crypto.fips_enabled' to 1 |
+
+ Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The operating system must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. |
+ System running in FIPS mode is indicated by kernel parameter
+'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
+To enable FIPS mode, run the following command:
+fips-mode-setup --enable
+
+To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
+parameters during system installation so key generation is done with FIPS-approved algorithms
+and continuous monitoring tests in place. |
+ Applicable - Configurable |
+ Verify the operating system implements NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. If it does not, this is a finding. |
+ To verify that kernel parameter 'crypto.fips_enabled' is set properly, run the following command:
+sysctl crypto.fips_enabled
+The output should contain the following:
+crypto.fips_enabled = 1 Is it the case that crypto.fips_enabled is not 1? |
+ Configure the operating system to implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. |
+ System running in FIPS mode is indicated by kernel parameter
+'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
+To enable FIPS mode, run the following command:
+fips-mode-setup --enable
+
+To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
+parameters during system installation so key generation is done with FIPS-approved algorithms
+and continuous monitoring tests in place. |
+ high |
+ |
+ |
+ |
+
+
@@ -39014,37 +39014,31 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect the confidentiality and integrity of transmitted information. |
-
CCE-85902-5: Configure SSH Client to Use FIPS 140-2 Validated Ciphers: openssh.config |
+
CCE-82426-8: Enable the OpenSSH Service |
Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered.
This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification.
Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. |
-
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
-set up incorrectly.
+ | The SSH server service, sshd, is commonly needed.
-To check that Crypto Policies settings for ciphers are configured correctly, ensure that
-/etc/crypto-policies/back-ends/openssh.config contains the following
-line and is not commented out:
-Ciphers |
+The
sshd service can be enabled with the following command:
+
$ sudo systemctl enable sshd.service
Applicable - Configurable |
Verify the operating system protects the confidentiality and integrity of transmitted information. If it does not, this is a finding. |
-
To verify if the OpenSSH client uses defined Cipher suite in the Crypto Policy, run:
-$ grep -i ciphers /etc/crypto-policies/back-ends/openssh.config
-and verify that the line matches:
-Ciphers Is it the case that Crypto Policy for OpenSSH client is not configured correctly? |
+
+
+Run the following command to determine the current status of the
+sshd service:
+$ sudo systemctl is-active sshd
+If the service is running, it should return the following: active Is it the case that sshd service is disabled? |
Configure the operating system to protect the confidentiality and integrity of transmitted information. |
-
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
-set up incorrectly.
+ | The SSH server service, sshd, is commonly needed.
-To check that Crypto Policies settings for ciphers are configured correctly, ensure that
-/etc/crypto-policies/back-ends/openssh.config contains the following
-line and is not commented out:
-Ciphers |
-
high |
+The
sshd service can be enabled with the following command:
+
$ sudo systemctl enable sshd.service
+
medium |
|
|
|
@@ -39056,36 +39050,36 @@
TBD - Assigned by DISA after STIG release |
The operating system must protect the confidentiality and integrity of transmitted information. |
-
CCE-84027-2: Set kernel parameter 'crypto.fips_enabled' to 1 |
+
CCE-85902-5: Configure SSH Client to Use FIPS 140-2 Validated Ciphers: openssh.config |
Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered.
This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification.
Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. |
-
System running in FIPS mode is indicated by kernel parameter
-'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
-To enable FIPS mode, run the following command:
-fips-mode-setup --enable
+ | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
+set up incorrectly.
-To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
-parameters during system installation so key generation is done with FIPS-approved algorithms
-and continuous monitoring tests in place. |
+To check that Crypto Policies settings for ciphers are configured correctly, ensure that
+
/etc/crypto-policies/back-ends/openssh.config contains the following
+line and is not commented out:
+
Ciphers
Applicable - Configurable |
Verify the operating system protects the confidentiality and integrity of transmitted information. If it does not, this is a finding. |
-
To verify that kernel parameter 'crypto.fips_enabled' is set properly, run the following command:
-sysctl crypto.fips_enabled
-The output should contain the following:
-crypto.fips_enabled = 1 Is it the case that crypto.fips_enabled is not 1? |
+
To verify if the OpenSSH client uses defined Cipher suite in the Crypto Policy, run:
+$ grep -i ciphers /etc/crypto-policies/back-ends/openssh.config
+and verify that the line matches:
+Ciphers Is it the case that Crypto Policy for OpenSSH client is not configured correctly? |
Configure the operating system to protect the confidentiality and integrity of transmitted information. |
-
System running in FIPS mode is indicated by kernel parameter
-'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
-To enable FIPS mode, run the following command:
-fips-mode-setup --enable
+ | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
+set up incorrectly.
-To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
-parameters during system installation so key generation is done with FIPS-approved algorithms
-and continuous monitoring tests in place. |
+To check that Crypto Policies settings for ciphers are configured correctly, ensure that
+
/etc/crypto-policies/back-ends/openssh.config contains the following
+line and is not commented out:
+
Ciphers
high |
|
|
@@ -39138,84 +39132,6 @@
|
-
- | CCI-002418 |
- SRG-OS-000423-GPOS-00187 |
- TBD - Assigned by DISA after STIG release |
- The operating system must protect the confidentiality and integrity of transmitted information. |
-
- CCE-84254-2: Configure GnuTLS library to use DoD-approved TLS Encryption |
-
- Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered.
-
-This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification.
-
-Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-GnuTLS is supported by system crypto policy, but the GnuTLS configuration may be
-set up to ignore it.
-
-To check that Crypto Policies settings are configured correctly, ensure that
-/etc/crypto-policies/back-ends/gnutls.config contains the following
-line and is not commented out:
-+VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0 |
- Applicable - Configurable |
- Verify the operating system protects the confidentiality and integrity of transmitted information. If it does not, this is a finding. |
- To verify if GnuTLS uses defined DoD-approved TLS Crypto Policy, run:
-$ sudo grep
-'+VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0'
-/etc/crypto-policies/back-ends/gnutls.config and verify that a match exists. Is it the case that cryptographic policy for gnutls is not configured or is configured incorrectly? |
- Configure the operating system to protect the confidentiality and integrity of transmitted information. |
- Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
-GnuTLS is supported by system crypto policy, but the GnuTLS configuration may be
-set up to ignore it.
-
-To check that Crypto Policies settings are configured correctly, ensure that
-/etc/crypto-policies/back-ends/gnutls.config contains the following
-line and is not commented out:
-+VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0 |
- medium |
- |
- |
- |
-
-
-
- | CCI-002418 |
- SRG-OS-000423-GPOS-00187 |
- TBD - Assigned by DISA after STIG release |
- The operating system must protect the confidentiality and integrity of transmitted information. |
-
- CCE-82426-8: Enable the OpenSSH Service |
-
- Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered.
-
-This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification.
-
-Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. |
- The SSH server service, sshd, is commonly needed.
-
-The sshd service can be enabled with the following command:
-$ sudo systemctl enable sshd.service |
- Applicable - Configurable |
- Verify the operating system protects the confidentiality and integrity of transmitted information. If it does not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-sshd service:
-$ sudo systemctl is-active sshd
-If the service is running, it should return the following: active Is it the case that sshd service is disabled? |
- Configure the operating system to protect the confidentiality and integrity of transmitted information. |
- The SSH server service, sshd, is commonly needed.
-
-The sshd service can be enabled with the following command:
-$ sudo systemctl enable sshd.service |
- medium |
- |
- |
- |
-
-
| CCI-002418 |
SRG-OS-000423-GPOS-00187 |
@@ -39247,6 +39163,90 @@
|
+
+ | CCI-002418 |
+ SRG-OS-000423-GPOS-00187 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must protect the confidentiality and integrity of transmitted information. |
+
+ CCE-84027-2: Set kernel parameter 'crypto.fips_enabled' to 1 |
+
+ Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered.
+
+This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification.
+
+Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. |
+ System running in FIPS mode is indicated by kernel parameter
+'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
+To enable FIPS mode, run the following command:
+fips-mode-setup --enable
+
+To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
+parameters during system installation so key generation is done with FIPS-approved algorithms
+and continuous monitoring tests in place. |
+ Applicable - Configurable |
+ Verify the operating system protects the confidentiality and integrity of transmitted information. If it does not, this is a finding. |
+ To verify that kernel parameter 'crypto.fips_enabled' is set properly, run the following command:
+sysctl crypto.fips_enabled
+The output should contain the following:
+crypto.fips_enabled = 1 Is it the case that crypto.fips_enabled is not 1? |
+ Configure the operating system to protect the confidentiality and integrity of transmitted information. |
+ System running in FIPS mode is indicated by kernel parameter
+'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
+To enable FIPS mode, run the following command:
+fips-mode-setup --enable
+
+To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
+parameters during system installation so key generation is done with FIPS-approved algorithms
+and continuous monitoring tests in place. |
+ high |
+ |
+ |
+ |
+
+
+
+ | CCI-002418 |
+ SRG-OS-000423-GPOS-00187 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must protect the confidentiality and integrity of transmitted information. |
+
+ CCE-84254-2: Configure GnuTLS library to use DoD-approved TLS Encryption |
+
+ Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered.
+
+This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification.
+
+Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. |
+ Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+GnuTLS is supported by system crypto policy, but the GnuTLS configuration may be
+set up to ignore it.
+
+To check that Crypto Policies settings are configured correctly, ensure that
+/etc/crypto-policies/back-ends/gnutls.config contains the following
+line and is not commented out:
++VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0 |
+ Applicable - Configurable |
+ Verify the operating system protects the confidentiality and integrity of transmitted information. If it does not, this is a finding. |
+ To verify if GnuTLS uses defined DoD-approved TLS Crypto Policy, run:
+$ sudo grep
+'+VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0'
+/etc/crypto-policies/back-ends/gnutls.config and verify that a match exists. Is it the case that cryptographic policy for gnutls is not configured or is configured incorrectly? |
+ Configure the operating system to protect the confidentiality and integrity of transmitted information. |
+ Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
+GnuTLS is supported by system crypto policy, but the GnuTLS configuration may be
+set up to ignore it.
+
+To check that Crypto Policies settings are configured correctly, ensure that
+/etc/crypto-policies/back-ends/gnutls.config contains the following
+line and is not commented out:
++VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0 |
+ medium |
+ |
+ |
+ |
+
+
@@ -39449,6 +39449,42 @@
+
+ | CCI-002422 |
+ SRG-OS-000426-GPOS-00190 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must maintain the confidentiality and integrity of information during reception. |
+
+ CCE-82426-8: Enable the OpenSSH Service |
+
+ Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information.
+
+Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption.
+
+Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When receiving data, operating systems need to leverage protection mechanisms such as TLS, SSL VPNs, or IPSec. |
+ The SSH server service, sshd, is commonly needed.
+
+The sshd service can be enabled with the following command:
+$ sudo systemctl enable sshd.service |
+ Applicable - Configurable |
+ Verify the operating system maintains the confidentiality and integrity of information during reception. If it does not, this is a finding. |
+
+
+Run the following command to determine the current status of the
+sshd service:
+$ sudo systemctl is-active sshd
+If the service is running, it should return the following: active Is it the case that sshd service is disabled? |
+ Configure the operating system to maintain the confidentiality and integrity of information during reception. |
+ The SSH server service, sshd, is commonly needed.
+
+The sshd service can be enabled with the following command:
+$ sudo systemctl enable sshd.service |
+ medium |
+ |
+ |
+ |
+
+
| CCI-002422 |
SRG-OS-000426-GPOS-00190 |
@@ -39495,42 +39531,6 @@
|
-
- | CCI-002422 |
- SRG-OS-000426-GPOS-00190 |
- TBD - Assigned by DISA after STIG release |
- The operating system must maintain the confidentiality and integrity of information during reception. |
-
- CCE-82426-8: Enable the OpenSSH Service |
-
- Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information.
-
-Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption.
-
-Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When receiving data, operating systems need to leverage protection mechanisms such as TLS, SSL VPNs, or IPSec. |
- The SSH server service, sshd, is commonly needed.
-
-The sshd service can be enabled with the following command:
-$ sudo systemctl enable sshd.service |
- Applicable - Configurable |
- Verify the operating system maintains the confidentiality and integrity of information during reception. If it does not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-sshd service:
-$ sudo systemctl is-active sshd
-If the service is running, it should return the following: active Is it the case that sshd service is disabled? |
- Configure the operating system to maintain the confidentiality and integrity of information during reception. |
- The SSH server service, sshd, is commonly needed.
-
-The sshd service can be enabled with the following command:
-$ sudo systemctl enable sshd.service |
- medium |
- |
- |
- |
-
-
| CCI-002422 |
SRG-OS-000426-GPOS-00190 |
@@ -39591,48 +39591,6 @@
-
- | CCI-002824 |
- SRG-OS-000433-GPOS-00192 |
- TBD - Assigned by DISA after STIG release |
- The operating system must implement non-executable data to protect its memory from unauthorized code execution. |
-
- CCE-83918-3: Enable NX or XD Support in the BIOS |
-
- Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism.
-
-Examples of attacks are buffer overflow attacks. |
- Reboot the system and enter the BIOS or Setup configuration menu.
-Navigate the BIOS configuration menu and make sure that the option is enabled. The setting may be located
-under a Security section. Look for Execute Disable (XD) on Intel-based systems and No Execute (NX)
-on AMD-based systems. |
- Applicable - Configurable |
- Verify the operating system implements non-executable data to protect its memory from unauthorized code execution. If it does not, this is a finding. |
- Verify the NX (no-execution) bit flag is set on the system.
-
-Check that the no-execution bit flag is set with the following commands:
-
-$ sudo dmesg | grep NX
-
-[ 0.000000] NX (Execute Disable) protection: active
-
-If "dmesg" does not show "NX (Execute Disable) protection" active, check the cpuinfo settings with the following command:
-
-$ sudo grep flags /proc/cpuinfo
-flags : fpu vme de pse tsc ms nx rdtscp lm constant_ts
-
-The output should contain the "nx" flag. Is it the case that NX is disabled? |
- Configure the operating system to implement non-executable data to protect its memory from unauthorized code execution. |
- Reboot the system and enter the BIOS or Setup configuration menu.
-Navigate the BIOS configuration menu and make sure that the option is enabled. The setting may be located
-under a Security section. Look for Execute Disable (XD) on Intel-based systems and No Execute (NX)
-on AMD-based systems. |
- medium |
- |
- |
- |
-
-
| CCI-002824 |
SRG-OS-000433-GPOS-00192 |
@@ -39730,6 +39688,48 @@
|
+
+ | CCI-002824 |
+ SRG-OS-000433-GPOS-00192 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must implement non-executable data to protect its memory from unauthorized code execution. |
+
+ CCE-83918-3: Enable NX or XD Support in the BIOS |
+
+ Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism.
+
+Examples of attacks are buffer overflow attacks. |
+ Reboot the system and enter the BIOS or Setup configuration menu.
+Navigate the BIOS configuration menu and make sure that the option is enabled. The setting may be located
+under a Security section. Look for Execute Disable (XD) on Intel-based systems and No Execute (NX)
+on AMD-based systems. |
+ Applicable - Configurable |
+ Verify the operating system implements non-executable data to protect its memory from unauthorized code execution. If it does not, this is a finding. |
+ Verify the NX (no-execution) bit flag is set on the system.
+
+Check that the no-execution bit flag is set with the following commands:
+
+$ sudo dmesg | grep NX
+
+[ 0.000000] NX (Execute Disable) protection: active
+
+If "dmesg" does not show "NX (Execute Disable) protection" active, check the cpuinfo settings with the following command:
+
+$ sudo grep flags /proc/cpuinfo
+flags : fpu vme de pse tsc ms nx rdtscp lm constant_ts
+
+The output should contain the "nx" flag. Is it the case that NX is disabled? |
+ Configure the operating system to implement non-executable data to protect its memory from unauthorized code execution. |
+ Reboot the system and enter the BIOS or Setup configuration menu.
+Navigate the BIOS configuration menu and make sure that the option is enabled. The setting may be located
+under a Security section. Look for Execute Disable (XD) on Intel-based systems and No Execute (NX)
+on AMD-based systems. |
+ medium |
+ |
+ |
+ |
+
+
@@ -39861,6 +39861,33 @@
+
+ | CCI-002696 |
+ SRG-OS-000445-GPOS-00199 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must verify correct operation of all security functions. |
+
+ CCE-80844-4: Install AIDE |
+
+ Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters.
+
+This requirement applies to operating systems performing security function verification/testing and/or systems and environments that require this functionality. |
+ The aide package can be installed with the following command:
+
+$ sudo yum install aide |
+ Applicable - Configurable |
+ Verify the operating system verifies correct operation of all security functions. If it does not, this is a finding. |
+ Run the following command to determine if the aide package is installed: $ rpm -q aide Is it the case that the package is not installed? |
+ Configure the operating system to verify correct operation of all security functions. |
+ The aide package can be installed with the following command:
+
+$ sudo yum install aide |
+ medium |
+ |
+ |
+ |
+
+
| CCI-002696 |
SRG-OS-000445-GPOS-00199 |
@@ -39953,33 +39980,6 @@
|
-
- | CCI-002696 |
- SRG-OS-000445-GPOS-00199 |
- TBD - Assigned by DISA after STIG release |
- The operating system must verify correct operation of all security functions. |
-
- CCE-80844-4: Install AIDE |
-
- Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters.
-
-This requirement applies to operating systems performing security function verification/testing and/or systems and environments that require this functionality. |
- The aide package can be installed with the following command:
-
-$ sudo yum install aide |
- Applicable - Configurable |
- Verify the operating system verifies correct operation of all security functions. If it does not, this is a finding. |
- Run the following command to determine if the aide package is installed: $ rpm -q aide Is it the case that the package is not installed? |
- Configure the operating system to verify correct operation of all security functions. |
- The aide package can be installed with the following command:
-
-$ sudo yum install aide |
- medium |
- |
- |
- |
-
-
| CCI-002696 |
SRG-OS-000445-GPOS-00199 |
@@ -40128,76 +40128,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
+ CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | 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 lines to
+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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r truncate /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep truncate /etc/audit/audit.rules
-
-The output should be the following:
-
--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+chown system call, run the following command:
+$ sudo grep "chown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
- 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
-
+ | 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 lines to
+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 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 |
+-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
medium |
|
|
@@ -40210,70 +40181,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
+ CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect unauthorized file
-accesses for all users and root. If the auditd daemon is configured
+ | 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 lines to a file with suffix
+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 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
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 lines to
+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 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=access |
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r open_by_handle_at /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep open_by_handle_at /etc/audit/audit.rules
-
-The output should be the following:
-
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fsetxattr system call, run the following command:
+$ sudo grep "fsetxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
- At a minimum, the audit system should collect unauthorized file
-accesses for all users and root. If the auditd daemon is configured
+ | 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 lines to a file with suffix
+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 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
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 lines to
+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 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=access |
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -40286,7 +40242,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
+ CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -40296,20 +40252,24 @@
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
+-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lchown system call, run the following command:
-$ sudo grep "lchown" /etc/audit/audit.*
+setxattr system call, run the following command:
+$ sudo grep "setxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
@@ -40318,15 +40278,19 @@
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
+-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -40339,7 +40303,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
+ CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -40349,60 +40313,66 @@
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
+-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 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
+-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 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
+-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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r creat /etc/audit/rules.d
+$ sudo grep -r truncate /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep creat /etc/audit/audit.rules
+$ sudo grep truncate /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
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
+-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 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
+-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 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
+-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 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 |
+-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
medium |
|
|
@@ -40415,47 +40385,63 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
+ CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchmod system call, run the following command:
-$ sudo grep "fchmod" /etc/audit/audit.*
+removexattr system call, run the following command:
+$ sudo grep "removexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
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
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -40550,47 +40536,53 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
+ CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
+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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchmodat system call, run the following command:
-$ sudo grep "fchmodat" /etc/audit/audit.*
+fchown system call, run the following command:
+$ sudo grep "fchown" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
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
+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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -40603,47 +40595,70 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
+ CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured
+ | 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 line to a file with suffix
+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 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
+-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 line to
+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 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 |
+-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=access
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchownat system call, run the following command:
-$ sudo grep "fchownat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
+
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
+
+$ sudo grep -r open_by_handle_at /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep open_by_handle_at /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
- At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured
+ | 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 line to a file with suffix
+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 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
+-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 line to
+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 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 |
+-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=access
medium |
|
|
@@ -40656,55 +40671,65 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
+ CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured
+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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-setxattr system call, run the following command:
-$ sudo grep "setxattr" /etc/audit/audit.*
+lremovexattr system call, run the following command:
+$ sudo grep "lremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured
+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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -40717,60 +40742,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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_mod |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-chmod system call, run the following command:
-$ sudo grep "chmod" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
- 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_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000458-GPOS-00203 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
-
- CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
+ CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -40780,23 +40752,20 @@
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
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchown system call, run the following command:
-$ sudo grep "fchown" /etc/audit/audit.*
+fchownat system call, run the following command:
+$ sudo grep "fchownat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
@@ -40805,18 +40774,15 @@
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
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
-
+-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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -40829,7 +40795,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
+ CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -40839,66 +40805,66 @@
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
+-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 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
+-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 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
+-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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r openat /etc/audit/rules.d
+$ sudo grep -r open /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep openat /etc/audit/audit.rules
+$ sudo grep open /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
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
+-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 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
+-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 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
+-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 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 |
+-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
medium |
|
|
@@ -40911,55 +40877,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+ CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lsetxattr system call, run the following command:
-$ sudo grep "lsetxattr" /etc/audit/audit.*
+fchmod system call, run the following command:
+$ sudo grep "fchmod" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -40972,7 +40930,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
+ CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -40982,24 +40940,20 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fsetxattr system call, run the following command:
-$ sudo grep "fsetxattr" /etc/audit/audit.*
+lchown system call, run the following command:
+$ sudo grep "lchown" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
@@ -41008,19 +40962,15 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -41033,7 +40983,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
+ CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -41043,66 +40993,60 @@
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r open /etc/audit/rules.d
+$ sudo grep -r creat /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep open /etc/audit/audit.rules
+$ sudo grep creat /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
medium |
|
|
@@ -41115,63 +41059,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
+ CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-removexattr system call, run the following command:
-$ sudo grep "removexattr" /etc/audit/audit.*
+lsetxattr system call, run the following command:
+$ sudo grep "lsetxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -41184,47 +41120,76 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
+ CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 line to
+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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-chown system call, run the following command:
-$ sudo grep "chown" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
+
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
+
+$ sudo grep -r openat /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep openat /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
- 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
+ | 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 line to
+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 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 |
+-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
medium |
|
|
@@ -41237,65 +41202,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
+ CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lremovexattr system call, run the following command:
-$ sudo grep "lremovexattr" /etc/audit/audit.*
+fchmodat system call, run the following command:
+$ sudo grep "fchmodat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -41373,52 +41320,105 @@
|
-
-
-
-
-
| CCI-000172 |
- SRG-OS-000461-GPOS-00205 |
+ SRG-OS-000458-GPOS-00203 |
TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
+ The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. |
- CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
+ CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | 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 lines to
+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 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 |
+-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
Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r truncate /etc/audit/rules.d
+ | Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+chmod system call, run the following command:
+$ sudo grep "chmod" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur. |
+ 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_mod |
+ medium |
+ |
+ |
+ |
+
+
+
+
+
+
+
+
+ | CCI-000172 |
+ SRG-OS-000461-GPOS-00205 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
+
+ CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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=access |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
+
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
+
+$ sudo grep -r truncate /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
@@ -41466,7 +41466,7 @@
| TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
- CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
+ CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -41476,60 +41476,66 @@
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
+-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 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
+-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=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
+-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 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=access |
+-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=access
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r open_by_handle_at /etc/audit/rules.d
+$ sudo grep -r ftruncate /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep open_by_handle_at /etc/audit/audit.rules
+$ sudo grep ftruncate /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
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
+-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 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
+-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=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
+-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 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=access |
+-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=access
medium |
|
|
@@ -41542,7 +41548,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
- CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
+ CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -41552,60 +41558,60 @@
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
+-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 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
+-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 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
+-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 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 |
+-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=access
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r creat /etc/audit/rules.d
+$ sudo grep -r open_by_handle_at /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep creat /etc/audit/audit.rules
+$ sudo grep open_by_handle_at /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
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
+-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 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
+-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 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
+-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 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 |
+-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=access
medium |
|
|
@@ -41618,7 +41624,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
- CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
+ CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -41628,66 +41634,66 @@
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
+-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 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=access
+-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 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
+-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 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=access |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r ftruncate /etc/audit/rules.d
+$ sudo grep -r open /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep ftruncate /etc/audit/audit.rules
+$ sudo grep open /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
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
+-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 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=access
+-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 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
+-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 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=access |
+-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
medium |
|
|
@@ -41700,7 +41706,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
- CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
+ CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -41710,66 +41716,60 @@
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r openat /etc/audit/rules.d
+$ sudo grep -r creat /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep openat /etc/audit/audit.rules
+$ sudo grep creat /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
medium |
|
|
@@ -41782,7 +41782,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
- CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
+ CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -41792,66 +41792,66 @@
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
+-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 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
+-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 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
+-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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r open /etc/audit/rules.d
+$ sudo grep -r openat /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep open /etc/audit/audit.rules
+$ sudo grep openat /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
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
+-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 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
+-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 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
+-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 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 |
+-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
medium |
|
|
@@ -41869,39 +41869,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-85944-7: Record Any Attempts to Run ssh-agent |
+ CCE-80700-8: Record Any Attempts to Run semanage |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
At a minimum, the audit system should collect any execution attempt
-of the ssh-agent command for all users and root. If the auditd
+of the semanage 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
+-a always,exit -F path=/usr/sbin/semanage -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/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
-$ sudo auditctl -l | grep ssh-agent
+$ sudo auditctl -l | grep semanage
--a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
At a minimum, the audit system should collect any execution attempt
-of the ssh-agent command for all users and root. If the auditd
+of the semanage 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
+-a always,exit -F path=/usr/sbin/semanage -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/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -41914,7 +41914,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80730-5: Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
+ CCE-80989-7: Ensure auditd Collects Information on the Use of Privileged Commands - mount |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -41924,33 +41924,29 @@
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/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "mount" command with the following command:
-$ sudo auditctl -l | grep pam_timestamp_check
+$ sudo auditctl -l | grep mount
--a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -42008,7 +42004,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80728-9: Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
+ CCE-80731-3: Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -42018,29 +42014,29 @@
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
+-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/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "gpasswd" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "passwd" command with the following command:
-$ sudo auditctl -l | grep gpasswd
+$ sudo auditctl -l | grep passwd
--a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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
+-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/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -42053,39 +42049,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
+ CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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 |
+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_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
-
-$ sudo auditctl -l | grep su
-
--a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+chown system call, run the following command:
+$ sudo grep "chown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | 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 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 |
+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_mod
medium |
|
|
@@ -42098,76 +42102,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
+ CCE-80701-6: Record Any Attempts to Run setsebool |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 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
-
+-a always,exit -F path=/usr/sbin/setsebool -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 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 |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r truncate /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep truncate /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep setsebool
--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 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
-
+-a always,exit -F path=/usr/sbin/setsebool -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 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 |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -42180,39 +42147,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80729-7: Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
+ CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers -p wa -k actions
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "newgrp" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-$ sudo auditctl -l | grep newgrp
+$ sudo auditctl -l | grep /etc/sudoers
--a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers -p wa -k actions
medium |
|
|
@@ -42225,70 +42192,92 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
+ CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+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:
--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=access |
+/etc/audit/audit.rules file, in order to capture events that modify
+account changes:
+
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
+$ sudo auditctl -l | grep -E '(/etc/shadow)'
-$ sudo grep -r open_by_handle_at /etc/audit/rules.d
+-w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+ | CCI-000172 |
+ SRG-OS-000462-GPOS-00206 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
-$ sudo grep open_by_handle_at /etc/audit/audit.rules
+ CCE-89455-0: Ensure auditd Collects Information on the Use of Privileged Commands - kmod |
-The output should be the following:
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+Audit records can be generated from various components within the information system (e.g., module or policy filter).
+ 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/kmod -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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "kmod" command with the following command:
+
+$ sudo auditctl -l | grep kmod
+
+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-kmod Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | 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/kmod -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 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=access |
+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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -42301,7 +42290,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
+ CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -42311,20 +42300,24 @@
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
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lchown system call, run the following command:
-$ sudo grep "lchown" /etc/audit/audit.*
+fsetxattr system call, run the following command:
+$ sudo grep "fsetxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
@@ -42333,15 +42326,19 @@
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
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -42354,39 +42351,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-89455-0: Ensure auditd Collects Information on the Use of Privileged Commands - kmod |
+ CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "kmod" command with the following command:
-
-$ sudo auditctl -l | grep kmod
-
--a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-kmod Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+setxattr system call, run the following command:
+$ sudo grep "setxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
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/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -42399,92 +42412,76 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | 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, in order to capture events that modify
-account changes:
-
--w /etc/passwd -p wa -k audit_rules_usergroup_modification |
+/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=access
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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 |
- medium |
- |
- |
- |
-
+$ sudo grep -r truncate /etc/audit/rules.d
-
- | CCI-000172 |
- SRG-OS-000462-GPOS-00206 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
- CCE-80733-9: Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
+$ sudo grep truncate /etc/audit/audit.rules
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+The output should be the following:
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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/postqueue -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postqueue" command with the following command:
+-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+ 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
-$ sudo auditctl -l | grep postqueue
+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
--a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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/postqueue -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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=access
medium |
|
|
@@ -42497,39 +42494,63 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-89446-9: Record Any Attempts to Run chacl |
+ CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -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 lines to
+utility to read audit rules during daemon startup, add the following line 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 |
+-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
-
-$ sudo auditctl -l | grep chacl
-
--a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+removexattr system call, run the following command:
+$ sudo grep "removexattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -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 lines to
+utility to read audit rules during daemon startup, add the following line 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 |
+-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -42601,129 +42622,76 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80740-4: Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
+ CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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=access
+
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 |
+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=access
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
-$ sudo auditctl -l | grep unix_chkpwd
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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 |
- medium |
- |
- |
- |
-
+$ sudo grep -r ftruncate /etc/audit/rules.d
-
- | CCI-000172 |
- SRG-OS-000462-GPOS-00206 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
- CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
+$ sudo grep ftruncate /etc/audit/audit.rules
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+The output should be the following:
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
-
-$ sudo auditctl -l | grep usermod
-
--a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000462-GPOS-00206 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
-
- CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
+ 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
- | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+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=access
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
-
-$ sudo auditctl -l | grep sudo
+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
--a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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 |
+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=access
medium |
|
|
@@ -42736,7 +42704,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80726-3: Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
+ CCE-80732-1: Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -42746,29 +42714,29 @@
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
+-a always,exit -F path=/usr/sbin/postdrop -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 |
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chsh" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postdrop" command with the following command:
-$ sudo auditctl -l | grep chsh
+$ sudo auditctl -l | grep postdrop
--a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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
+-a always,exit -F path=/usr/sbin/postdrop -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 |
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -42781,7 +42749,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
+ CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -42792,17 +42760,17 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-unlink system call, run the following command:
-$ sudo grep "unlink" /etc/audit/audit.*
+unlinkat system call, run the following command:
+$ sudo grep "unlinkat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
@@ -42812,12 +42780,12 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -42830,7 +42798,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80741-2: Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
+ CCE-80728-9: Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -42840,131 +42808,29 @@
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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "userhelper" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "gpasswd" command with the following command:
-$ sudo auditctl -l | grep userhelper
+$ sudo auditctl -l | grep gpasswd
--a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000462-GPOS-00206 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
-
- CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-finit_module system call, run the following command:
-$ sudo grep "finit_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000462-GPOS-00206 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
-
- CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/shadow)'
-
--w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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 |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -42977,7 +42843,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80727-1: Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
+ CCE-80725-5: Ensure auditd Collects Information on the Use of Privileged Commands - chage |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -42987,29 +42853,29 @@
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
+-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/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "crontab" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chage" command with the following command:
-$ sudo auditctl -l | grep crontab
+$ sudo auditctl -l | grep chage
--a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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
+-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/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -43022,39 +42888,53 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80701-6: Record Any Attempts to Run setsebool |
+ CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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
+ | 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 path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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 lines to
+utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
-
-$ sudo auditctl -l | grep setsebool
-
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fchown system call, run the following command:
+$ sudo grep "fchown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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
+ | 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 path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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 lines to
+utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
medium |
|
|
@@ -43067,7 +42947,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
+ CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -43077,60 +42957,60 @@
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
+-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 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
+-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 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
+-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 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 |
+-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=access
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r creat /etc/audit/rules.d
+$ sudo grep -r open_by_handle_at /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep creat /etc/audit/audit.rules
+$ sudo grep open_by_handle_at /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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
+-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 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
+-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 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
+-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 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 |
+-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=access
medium |
|
|
@@ -43143,43 +43023,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80722-2: Ensure auditd Collects Information on Exporting to Media (successful) |
+ CCE-80729-7: Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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 |
+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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-mount system call, run the following command:
-$ sudo grep "mount" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "newgrp" command with the following command:
+
+$ sudo auditctl -l | grep newgrp
+
+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | 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 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 |
+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
medium |
|
|
@@ -43192,47 +43068,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
+ CCE-80741-2: Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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/userhelper -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 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_mod |
+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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchmod system call, run the following command:
-$ sudo grep "fchmod" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "userhelper" command with the following command:
+
+$ sudo auditctl -l | grep userhelper
+
+-a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | 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/userhelper -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 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_mod |
+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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -43245,89 +43113,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
+ CCE-80740-4: Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ 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 |
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes audit_backlog_limit=8192,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
-The command should not return any output. Is it the case that audit backlog limit is not configured? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
- low |
- |
- |
- |
-
+
Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command:
- |
- | CCI-000172 |
- SRG-OS-000462-GPOS-00206 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
-
- CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
-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:
--w /etc/sudoers.d/ -p wa -k actions |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-
-$ sudo auditctl -l | grep/etc/sudoers.d
+$ sudo auditctl -l | grep unix_chkpwd
--w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
+ | 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 the following line to
-/etc/audit/audit.rules file:
--w /etc/sudoers.d/ -p wa -k actions |
+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
medium |
|
|
@@ -43340,129 +43158,65 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
+ CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 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=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=access |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r ftruncate /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep ftruncate /etc/audit/audit.rules
-
-The output should be the following:
-
--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- At a minimum, the audit system should collect unauthorized file
-accesses for all users and root. If the auditd daemon is configured
+ | 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 lines to a file with suffix
+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 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=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=access |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000462-GPOS-00206 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
-
- CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchmodat system call, run the following command:
-$ sudo grep "fchmodat" /etc/audit/audit.*
+lremovexattr system call, run the following command:
+$ sudo grep "lremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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
+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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -43528,55 +43282,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
+ CCE-89446-9: Record Any Attempts to Run chacl |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+-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 line to
+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 setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-setxattr system call, run the following command:
-$ sudo grep "setxattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
+
+$ sudo auditctl -l | grep chacl
+
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | 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 arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
+-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 line to
+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 setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -43589,39 +43327,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+ CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect administrator actions
+ | At a minimum, the audit system should collect file deletion 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:
--w /etc/sudoers -p wa -k actions
+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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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:
--w /etc/sudoers -p wa -k actions |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-
-$ sudo auditctl -l | grep /etc/sudoers
-
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+unlink system call, run the following command:
+$ sudo grep "unlink" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- At a minimum, the audit system should collect administrator actions
+ | At a minimum, the audit system should collect file deletion 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:
--w /etc/sudoers -p wa -k actions
+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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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:
--w /etc/sudoers -p wa -k actions |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -43634,43 +43376,76 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80713-1: Ensure auditd Collects Information on Kernel Module Loading - init_module |
+ CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 auid>=1000 -F auid!=unset -F key=modules
+ | 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
-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 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 auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules. |
+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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-init_module system call, run the following command:
-$ sudo grep "init_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
--a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modules
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
+$ sudo grep -r open /etc/audit/rules.d
-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 to read audit rules during daemon startup, run the following command:
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules. |
+$ sudo grep open /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+ 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=access |
medium |
|
|
@@ -43683,47 +43458,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
+ CCE-80726-3: Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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_mod |
+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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-chmod system call, run the following command:
-$ sudo grep "chmod" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chsh" command with the following command:
+
+$ sudo auditctl -l | grep chsh
+
+-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | 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 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_mod |
+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
medium |
|
|
@@ -43736,43 +43503,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
+ CCE-80739-6: Ensure auditd Collects Information on the Use of Privileged Commands - umount |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file deletion 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-unlinkat system call, run the following command:
-$ sudo grep "unlinkat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "umount" command with the following command:
+
+$ sudo auditctl -l | grep umount
+
+-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- At a minimum, the audit system should collect file deletion 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
@@ -43785,47 +43548,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+ CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- If the auditd daemon is configured to use the
+ | 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 capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
-
+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 capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification |
+/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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+$ sudo auditctl -l | grep /var/log/lastlog
--w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- If the auditd daemon is configured to use the
+ | 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 capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
-
+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 capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification |
+/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
medium |
|
|
@@ -43838,39 +43597,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-88437-9: Record Any Attempts to Run setfacl |
+ CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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 |
+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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfacl" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
-$ sudo auditctl -l | grep setfacl
+$ sudo auditctl -l | grep su
--a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | 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 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 |
+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
medium |
|
|
@@ -43883,53 +43642,141 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
+ CCE-80727-1: Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "crontab" command with the following command:
-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
+$ sudo auditctl -l | grep crontab
+-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+ 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 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
+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 |
+ medium |
+ |
+ |
+ |
+
-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
+
+ | CCI-000172 |
+ SRG-OS-000462-GPOS-00206 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
+
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000462-GPOS-00206 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+
+ CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
+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 rename -F auid>=1000 -F auid!=unset -F key=delete |
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchown system call, run the following command:
-$ sudo grep "fchown" /etc/audit/audit.*
+rename system call, run the following command:
+$ sudo grep "rename" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
-
+ | At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
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_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -43942,76 +43789,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
+ CCE-85944-7: Record Any Attempts to Run ssh-agent |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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
-
+-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 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 |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r openat /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep openat /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep ssh-agent
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | 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 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
-
+-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 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 |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent
medium |
|
|
@@ -44024,39 +43834,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80725-5: Ensure auditd Collects Information on the Use of Privileged Commands - chage |
+ CCE-80713-1: Ensure auditd Collects Information on Kernel Module Loading - init_module |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 |
+ 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 auid>=1000 -F auid!=unset -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. |
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chage" command with the following command:
+ | To determine if the system is configured to audit calls to the
+init_module system call, run the following command:
+$ sudo grep "init_module" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+ 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:
-$ sudo auditctl -l | grep chage
+-a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modules
--a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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 |
+
+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.
medium |
|
|
@@ -44069,55 +43883,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+ CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lsetxattr system call, run the following command:
-$ sudo grep "lsetxattr" /etc/audit/audit.*
+fchmod system call, run the following command:
+$ sudo grep "fchmod" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -44130,7 +43936,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
+ CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -44140,24 +43946,20 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fsetxattr system call, run the following command:
-$ sudo grep "fsetxattr" /etc/audit/audit.*
+lchown system call, run the following command:
+$ sudo grep "lchown" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
@@ -44166,19 +43968,15 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -44191,39 +43989,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80989-7: Ensure auditd Collects Information on the Use of Privileged Commands - mount |
+ CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
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 |
+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 renameat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "mount" command with the following command:
-
-$ sudo auditctl -l | grep mount
-
--a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+renameat system call, run the following command:
+$ sudo grep "renameat" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
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 |
+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 renameat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -44236,7 +44038,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
+ CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -44246,66 +44048,60 @@
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r open /etc/audit/rules.d
+$ sudo grep -r creat /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep open /etc/audit/audit.rules
+$ sudo grep creat /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
medium |
|
|
@@ -44318,43 +44114,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
+ CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file deletion events
+ | At a minimum, the audit system should collect administrator actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-w /etc/sudoers.d/ -p wa -k actions
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-rename system call, run the following command:
-$ sudo grep "rename" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
+
+$ sudo auditctl -l | grep/etc/sudoers.d
+
+-w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- At a minimum, the audit system should collect file deletion events
+ | At a minimum, the audit system should collect administrator actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-w /etc/sudoers.d/ -p wa -k actions
medium |
|
|
@@ -44367,7 +44159,56 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80739-6: Ensure auditd Collects Information on the Use of Privileged Commands - umount |
+ CCE-80711-5: Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 auid>=1000 -F auid!=unset -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. |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+delete_module system call, run the following command:
+$ sudo grep "delete_module" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+ 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 auid>=1000 -F auid!=unset -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. |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000462-GPOS-00206 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+
+ CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -44377,29 +44218,29 @@
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
+-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/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "umount" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
-$ sudo auditctl -l | grep umount
+$ sudo auditctl -l | grep usermod
--a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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
+-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/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -44412,47 +44253,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+ CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | 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 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 |
+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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
-$ sudo auditctl -l | grep -E '(/etc/group)'
+$ sudo auditctl -l | grep sudo
--w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
-
+ | 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 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 |
+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
medium |
|
|
@@ -44465,43 +44298,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
+ CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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, setting ARCH to either b32 or b64 as
-appropriate for your system:
--a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-rmdir system call, run the following command:
-$ sudo grep "rmdir" /etc/audit/audit.*
+lsetxattr system call, run the following command:
+$ sudo grep "lsetxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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, setting ARCH to either b32 or b64 as
-appropriate for your system:
--a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -44514,39 +44359,76 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80731-3: Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
+ CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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 |
+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=access
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "passwd" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
-$ sudo auditctl -l | grep passwd
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r openat /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep openat /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | 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 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 |
+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=access
medium |
|
|
@@ -44559,39 +44441,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80700-8: Record Any Attempts to Run semanage |
+ CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
-
-$ sudo auditctl -l | grep semanage
-
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+rmdir system call, run the following command:
+$ sudo grep "rmdir" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -44604,63 +44490,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
+ CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-removexattr system call, run the following command:
-$ sudo grep "removexattr" /etc/audit/audit.*
+fchmodat system call, run the following command:
+$ sudo grep "fchmodat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -44673,47 +44543,65 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
+ CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
+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
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-chown system call, run the following command:
-$ sudo grep "chown" /etc/audit/audit.*
+fremovexattr system call, run the following command:
+$ sudo grep "fremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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
+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
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -44726,43 +44614,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80711-5: Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
+ CCE-80722-2: Ensure auditd Collects Information on Exporting to Media (successful) |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 auid>=1000 -F auid!=unset -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. |
+ 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 |
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-delete_module system call, run the following command:
-$ sudo grep "delete_module" /etc/audit/audit.*
+mount system call, run the following command:
+$ sudo grep "mount" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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 auid>=1000 -F auid!=unset -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. |
+ 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 |
medium |
|
|
@@ -44775,39 +44663,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-82280-9: Record Any Attempts to Run setfiles |
+ CCE-80733-9: Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect any execution attempt
-of the setfiles 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/sbin/setfiles -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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ 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/postqueue -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postqueue" command with the following command:
-$ sudo auditctl -l | grep setfiles
+$ sudo auditctl -l | grep postqueue
--a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- At a minimum, the audit system should collect any execution attempt
-of the setfiles 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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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/postqueue -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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -44820,120 +44708,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
+ CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+ 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lremovexattr system call, run the following command:
-$ sudo grep "lremovexattr" /etc/audit/audit.*
+finit_module system call, run the following command:
+$ sudo grep "finit_module" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000462-GPOS-00206 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
-
- CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+ | 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:
--w /etc/gshadow -p wa -k identity
+-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -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:
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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 |
+-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -F key=modules
medium |
|
|
@@ -44946,65 +44757,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
+ CCE-88437-9: Record Any Attempts to Run setfacl |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
-
+-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 line to
+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 fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fremovexattr system call, run the following command:
-$ sudo grep "fremovexattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfacl" command with the following command:
+
+$ sudo auditctl -l | grep setfacl
+
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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
+ | 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 arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
-
+-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 line to
+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 fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -45017,44 +44802,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
+ CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
-
-$ sudo auditctl -l | grep /var/log/lastlog
-
--w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes audit_backlog_limit=8192,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
+The command should not return any output. Is it the case that audit backlog limit is not configured? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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 |
- medium |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ low |
|
|
|
@@ -45066,84 +44852,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80698-4: Record Any Attempts to Run chcon |
+ CCE-82280-9: Record Any Attempts to Run setfiles |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
At a minimum, the audit system should collect any execution attempt
-of the chcon command for all users and root. If the auditd
+of the setfiles 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
+-a always,exit -F path=/usr/sbin/setfiles -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 |
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
-$ sudo auditctl -l | grep chcon
+$ sudo auditctl -l | grep setfiles
--a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
At a minimum, the audit system should collect any execution attempt
-of the chcon command for all users and root. If the auditd
+of the setfiles 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
+-a always,exit -F path=/usr/sbin/setfiles -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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000462-GPOS-00206 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
-
- CCE-89480-8: Ensure auditd Collects Information on the Use of Privileged Commands - unix_update |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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_update -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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_update" command with the following command:
-
-$ sudo auditctl -l | grep unix_update
-
--a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- 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_update -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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -45206,7 +44947,60 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80732-1: Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
+ CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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_mod |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+chmod system call, run the following command:
+$ sudo grep "chmod" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+ 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_mod |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000462-GPOS-00206 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+
+ CCE-89480-8: Ensure auditd Collects Information on the Use of Privileged Commands - unix_update |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -45216,29 +45010,29 @@
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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/sbin/unix_update -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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postdrop" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_update" command with the following command:
-$ sudo auditctl -l | grep postdrop
+$ sudo auditctl -l | grep unix_update
--a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/sbin/unix_update -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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -45251,93 +45045,299 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
+ CCE-80730-5: Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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/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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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/pam_timestamp_check
+-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-renameat system call, run the following command:
-$ sudo grep "renameat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command:
+
+$ sudo auditctl -l | grep pam_timestamp_check
+
+-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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/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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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/pam_timestamp_check
+-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
|
-
-
-
-
-
| CCI-000172 |
- SRG-OS-000463-GPOS-00207 |
+ SRG-OS-000462-GPOS-00206 |
TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify security objects occur. |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
- CCE-80701-6: Record Any Attempts to Run setsebool |
+ CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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:
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify security objects occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
+/etc/audit/audit.rules file, in order to capture events that modify
+account changes:
+
+-w /etc/gshadow -p wa -k audit_rules_usergroup_modification |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-$ sudo auditctl -l | grep setsebool
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes?
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000462-GPOS-00206 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+
+ CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+
+-w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000462-GPOS-00206 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+
+ CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/group)'
+
+-w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000462-GPOS-00206 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+
+ CCE-80698-4: Record Any Attempts to Run chcon |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
+
+$ sudo auditctl -l | grep chcon
+
+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
+
+
+
+
+
+
+ | CCI-000172 |
+ SRG-OS-000463-GPOS-00207 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify security objects occur. |
+
+ CCE-80700-8: Record Any Attempts to Run semanage |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ At a minimum, the audit system should collect any execution attempt
+of the semanage 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/sbin/semanage -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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to modify security objects occur. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
+
+$ sudo auditctl -l | grep semanage
+
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify security objects occur. |
At a minimum, the audit system should collect any execution attempt
-of the setsebool command for all users and root. If the auditd
+of the semanage 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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/sbin/semanage -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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -45350,55 +45350,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify security objects occur. |
- CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+ CCE-80701-6: Record Any Attempts to Run setsebool |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
-If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F path=/usr/sbin/setsebool -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 line to
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
-If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify security objects occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-lsetxattr system call, run the following command:
-$ sudo grep "lsetxattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
+
+$ sudo auditctl -l | grep setsebool
+
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify security objects occur. |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
-If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F path=/usr/sbin/setsebool -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 line to
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
-If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -45466,51 +45450,6 @@
|
-
- | CCI-000172 |
- SRG-OS-000463-GPOS-00207 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify security objects occur. |
-
- CCE-80700-8: Record Any Attempts to Run semanage |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify security objects occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
-
-$ sudo auditctl -l | grep semanage
-
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify security objects occur. |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
- medium |
- |
- |
- |
-
-
| CCI-000172 |
SRG-OS-000463-GPOS-00207 |
@@ -45580,51 +45519,6 @@
|
-
- | CCI-000172 |
- SRG-OS-000463-GPOS-00207 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify security objects occur. |
-
- CCE-82280-9: Record Any Attempts to Run setfiles |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect any execution attempt
-of the setfiles 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/sbin/setfiles -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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify security objects occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
-
-$ sudo auditctl -l | grep setfiles
-
--a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify security objects occur. |
- At a minimum, the audit system should collect any execution attempt
-of the setfiles 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/sbin/setfiles -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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
- medium |
- |
- |
- |
-
-
| CCI-000172 |
SRG-OS-000463-GPOS-00207 |
@@ -45696,6 +45590,67 @@
|
+
+ | CCI-000172 |
+ SRG-OS-000463-GPOS-00207 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify security objects occur. |
+
+ CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to modify security objects occur. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+lsetxattr system call, run the following command:
+$ sudo grep "lsetxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify security objects occur. |
+ 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+ medium |
+ |
+ |
+ |
+
+
| CCI-000172 |
SRG-OS-000463-GPOS-00207 |
@@ -45773,95 +45728,95 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify security objects occur. |
- CCE-80698-4: Record Any Attempts to Run chcon |
+ CCE-82280-9: Record Any Attempts to Run setfiles |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
At a minimum, the audit system should collect any execution attempt
-of the chcon command for all users and root. If the auditd
+of the setfiles 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
+-a always,exit -F path=/usr/sbin/setfiles -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 |
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify security objects occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
-$ sudo auditctl -l | grep chcon
+$ sudo auditctl -l | grep setfiles
--a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify security objects occur. |
At a minimum, the audit system should collect any execution attempt
-of the chcon command for all users and root. If the auditd
+of the setfiles 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
+-a always,exit -F path=/usr/sbin/setfiles -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 |
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
|
-
-
-
-
-
| CCI-000172 |
- SRG-OS-000465-GPOS-00209 |
+ SRG-OS-000463-GPOS-00207 |
TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify security objects occur. |
- CCE-80701-6: Record Any Attempts to Run setsebool |
+ CCE-80698-4: Record Any Attempts to Run chcon |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
At a minimum, the audit system should collect any execution attempt
-of the setsebool command for all users and root. If the auditd
+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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
+ | Verify the operating system generates audit records when successful/unsuccessful attempts to modify security objects occur. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
-$ sudo auditctl -l | grep setsebool
+$ sudo auditctl -l | grep chcon
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. |
+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out?
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify security objects occur. |
At a minimum, the audit system should collect any execution attempt
-of the setsebool command for all users and root. If the auditd
+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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
|
+
+
+
+
+
| CCI-000172 |
SRG-OS-000465-GPOS-00209 |
@@ -45913,39 +45868,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. |
- CCE-82280-9: Record Any Attempts to Run setfiles |
+ CCE-80701-6: Record Any Attempts to Run setsebool |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
At a minimum, the audit system should collect any execution attempt
-of the setfiles command for all users and root. If the auditd
+of the setsebool 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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/sbin/setsebool -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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
-$ sudo auditctl -l | grep setfiles
+$ sudo auditctl -l | grep setsebool
--a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. |
At a minimum, the audit system should collect any execution attempt
-of the setfiles command for all users and root. If the auditd
+of the setsebool 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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F path=/usr/sbin/setsebool -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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -45958,7 +45913,52 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. |
- CCE-80698-4: Record Any Attempts to Run chcon |
+ CCE-82280-9: Record Any Attempts to Run setfiles |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ At a minimum, the audit system should collect any execution attempt
+of the setfiles 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/sbin/setfiles -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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
+
+$ sudo auditctl -l | grep setfiles
+
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. |
+ At a minimum, the audit system should collect any execution attempt
+of the setfiles 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/sbin/setfiles -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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000465-GPOS-00209 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. |
+
+ CCE-80698-4: Record Any Attempts to Run chcon |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -46008,39 +46008,47 @@
| TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
+ CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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 |
+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_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
-
-$ sudo auditctl -l | grep su
-
--a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+chown system call, run the following command:
+$ sudo grep "chown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- 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
+ | 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 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 |
+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_mod
medium |
|
|
@@ -46053,47 +46061,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
+ CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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_mod |
+-w /etc/sudoers -p wa -k actions
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-lchown system call, run the following command:
-$ sudo grep "lchown" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+
+$ sudo auditctl -l | grep /etc/sudoers
+
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- 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
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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_mod |
+-w /etc/sudoers -p wa -k actions
medium |
|
|
@@ -46106,7 +46106,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -46117,21 +46117,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+$ sudo auditctl -l | grep -E '(/etc/shadow)'
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -46139,14 +46139,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -46159,39 +46159,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-89446-9: Record Any Attempts to Run chacl |
+ CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 lines to
+utility to read audit rules during daemon startup, add the following line 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 |
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
-
-$ sudo auditctl -l | grep chacl
-
--a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fsetxattr system call, run the following command:
+$ sudo grep "fsetxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- 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
+ | 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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 lines to
+utility to read audit rules during daemon startup, add the following line 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 |
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -46204,39 +46220,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
+ CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
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 |
+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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
-
-$ sudo auditctl -l | grep usermod
-
--a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+setxattr system call, run the following command:
+$ sudo grep "setxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
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 |
+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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -46249,39 +46281,63 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
+ CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+
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 |
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
-
-$ sudo auditctl -l | grep sudo
-
--a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+removexattr system call, run the following command:
+$ sudo grep "removexattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+
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 |
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -46294,7 +46350,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
+ CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -46305,17 +46361,17 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-unlink system call, run the following command:
-$ sudo grep "unlink" /etc/audit/audit.*
+unlinkat system call, run the following command:
+$ sudo grep "unlinkat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
@@ -46325,12 +46381,12 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -46343,47 +46399,53 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
+ CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | 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 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 |
+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_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
+ | To determine if the system is configured to audit calls to the
+fchown system call, run the following command:
+$ sudo grep "fchown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
+ 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
-$ sudo auditctl -l | grep -E '(/etc/shadow)'
+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
--w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- 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 |
+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_mod
medium |
|
|
@@ -46396,47 +46458,65 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
+ CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
+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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchmod system call, run the following command:
-$ sudo grep "fchmod" /etc/audit/audit.*
+lremovexattr system call, run the following command:
+$ sudo grep "lremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
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
+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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -46449,117 +46529,19 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
+ CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
-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:
--w /etc/sudoers.d/ -p wa -k actions |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-
-$ sudo auditctl -l | grep/etc/sudoers.d
-
--w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
-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:
--w /etc/sudoers.d/ -p wa -k actions |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000466-GPOS-00210 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
-
- CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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_mod |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchmodat system call, run the following command:
-$ sudo grep "fchmodat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- 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_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000466-GPOS-00210 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
-
- CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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:
@@ -46600,100 +46582,39 @@
| TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
+ CCE-89446-9: Record Any Attempts to Run chacl |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-setxattr system call, run the following command:
-$ sudo grep "setxattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- 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
+ | 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 arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000466-GPOS-00210 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
-
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+-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 line to
+utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
-$ sudo auditctl -l | grep /etc/sudoers
+$ sudo auditctl -l | grep chacl
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 line to
+utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -46706,47 +46627,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
+ CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | At a minimum, the audit system should collect file deletion 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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-chmod system call, run the following command:
-$ sudo grep "chmod" /etc/audit/audit.*
+unlink system call, run the following command:
+$ sudo grep "unlink" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- 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
+ | At a minimum, the audit system should collect file deletion 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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -46759,43 +46676,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
+ CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file deletion 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-unlinkat system call, run the following command:
-$ sudo grep "unlinkat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
+
+$ sudo auditctl -l | grep su
+
+-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- At a minimum, the audit system should collect file deletion 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
@@ -46808,7 +46721,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -46819,21 +46732,21 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
--w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -46841,14 +46754,14 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -46861,53 +46774,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
+ CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
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_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchown system call, run the following command:
-$ sudo grep "fchown" /etc/audit/audit.*
+rename system call, run the following command:
+$ sudo grep "rename" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- 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
-
+ | At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
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_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -46920,55 +46823,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+ CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lsetxattr system call, run the following command:
-$ sudo grep "lsetxattr" /etc/audit/audit.*
+fchmod system call, run the following command:
+$ sudo grep "fchmod" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -46981,7 +46876,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
+ CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -46991,24 +46886,20 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fsetxattr system call, run the following command:
-$ sudo grep "fsetxattr" /etc/audit/audit.*
+lchown system call, run the following command:
+$ sudo grep "lchown" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
@@ -47017,19 +46908,15 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -47042,7 +46929,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
+ CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -47053,17 +46940,17 @@
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 rename -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-rename system call, run the following command:
-$ sudo grep "rename" /etc/audit/audit.*
+renameat system call, run the following command:
+$ sudo grep "renameat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
@@ -47073,12 +46960,12 @@
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 rename -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
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 rename -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -47091,48 +46978,191 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+ CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers.d/ -p wa -k actions
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/group)'
+$ sudo auditctl -l | grep/etc/sudoers.d
--w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- 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
-
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 |
- medium |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers.d/ -p wa -k actions
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000466-GPOS-00210 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
+
+ CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
+
+$ sudo auditctl -l | grep usermod
+
+-a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000466-GPOS-00210 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
+
+ CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
+
+$ sudo auditctl -l | grep sudo
+
+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000466-GPOS-00210 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
+
+ CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+lsetxattr system call, run the following command:
+$ sudo grep "lsetxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
+ 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+ medium |
|
|
|
@@ -47193,63 +47223,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
+ CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-removexattr system call, run the following command:
-$ sudo grep "removexattr" /etc/audit/audit.*
+fchmodat system call, run the following command:
+$ sudo grep "fchmodat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -47262,47 +47276,65 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
+ CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
+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
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-chown system call, run the following command:
-$ sudo grep "chown" /etc/audit/audit.*
+fremovexattr system call, run the following command:
+$ sudo grep "fremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
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
+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
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -47315,65 +47347,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
+ CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lremovexattr system call, run the following command:
-$ sudo grep "lremovexattr" /etc/audit/audit.*
+chmod system call, run the following command:
+$ sudo grep "chmod" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-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 lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -47441,65 +47455,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
+ CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -F key=perm_mod
+ | 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:
-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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
+-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 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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -F key=perm_mod
+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:
-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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
+-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fremovexattr system call, run the following command:
-$ sudo grep "fremovexattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+
+-w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- 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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -F key=perm_mod
+ | 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:
-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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
+-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 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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -F key=perm_mod
+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:
-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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
+-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -47512,43 +47508,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
+ CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file deletion events
-for all users and root. If the auditd daemon is configured to use the
+ | 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-renameat system call, run the following command:
-$ sudo grep "renameat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/group)'
+
+-w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur. |
- At a minimum, the audit system should collect file deletion events
-for all users and root. If the auditd daemon is configured to use the
+ | 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
@@ -47566,7 +47566,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete security levels occur. |
- CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
+ CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -47577,17 +47577,17 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete security levels occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-unlink system call, run the following command:
-$ sudo grep "unlink" /etc/audit/audit.*
+unlinkat system call, run the following command:
+$ sudo grep "unlinkat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security levels occur. |
@@ -47597,12 +47597,12 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -47615,7 +47615,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete security levels occur. |
- CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
+ CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -47626,17 +47626,17 @@
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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete security levels occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-unlinkat system call, run the following command:
-$ sudo grep "unlinkat" /etc/audit/audit.*
+unlink system call, run the following command:
+$ sudo grep "unlink" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security levels occur. |
@@ -47646,12 +47646,12 @@
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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -47713,7 +47713,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete security levels occur. |
- CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
+ CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -47724,17 +47724,17 @@
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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
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 rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete security levels occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-rmdir system call, run the following command:
-$ sudo grep "rmdir" /etc/audit/audit.*
+renameat system call, run the following command:
+$ sudo grep "renameat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security levels occur. |
@@ -47744,12 +47744,12 @@
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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -47762,7 +47762,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete security levels occur. |
- CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
+ CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -47773,17 +47773,17 @@
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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete
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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete security levels occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-renameat system call, run the following command:
-$ sudo grep "renameat" /etc/audit/audit.*
+rmdir system call, run the following command:
+$ sudo grep "rmdir" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security levels occur. |
@@ -47793,12 +47793,12 @@
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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete
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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -47816,43 +47816,124 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete security objects occur. |
- CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
+ CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file deletion 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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+ | 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
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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, setting ARCH to either b32 or b64 as
-appropriate for your system:
--a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-unlink system call, run the following command:
-$ sudo grep "unlink" /etc/audit/audit.*
+fsetxattr system call, run the following command:
+$ sudo grep "fsetxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security objects occur. |
- At a minimum, the audit system should collect file deletion 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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+ | 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
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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, setting ARCH to either b32 or b64 as
-appropriate for your system:
--a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000468-GPOS-00212 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful attempts to delete security objects occur. |
+
+ CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+ Applicable - Configurable |
+ Verify the operating system generates audit records when successful/unsuccessful attempts to delete security objects occur. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+removexattr system call, run the following command:
+$ sudo grep "removexattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security objects occur. |
+ 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
medium |
|
|
@@ -47959,55 +48040,65 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete security objects occur. |
- CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+ CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
+
If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
+
If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lsetxattr system call, run the following command:
-$ sudo grep "lsetxattr" /etc/audit/audit.*
+lremovexattr system call, run the following command:
+$ sudo grep "lremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security objects occur. |
At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
+
If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
+
If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -48020,55 +48111,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete security objects occur. |
- CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
+ CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+ | At a minimum, the audit system should collect file deletion 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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fsetxattr system call, run the following command:
-$ sudo grep "fsetxattr" /etc/audit/audit.*
+unlink system call, run the following command:
+$ sudo grep "unlink" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security objects occur. |
- 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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+ | At a minimum, the audit system should collect file deletion 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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -48130,7 +48209,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete security objects occur. |
- CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
+ CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -48141,17 +48220,17 @@
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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
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 rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-rmdir system call, run the following command:
-$ sudo grep "rmdir" /etc/audit/audit.*
+renameat system call, run the following command:
+$ sudo grep "renameat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security objects occur. |
@@ -48161,12 +48240,12 @@
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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -48179,63 +48258,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete security objects occur. |
- CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
+ CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-removexattr system call, run the following command:
-$ sudo grep "removexattr" /etc/audit/audit.*
+lsetxattr system call, run the following command:
+$ sudo grep "lsetxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security objects occur. |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -48248,65 +48319,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful attempts to delete security objects occur. |
- CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
+ CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
-
+ | At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful attempts to delete security objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lremovexattr system call, run the following command:
-$ sudo grep "lremovexattr" /etc/audit/audit.*
+rmdir system call, run the following command:
+$ sudo grep "rmdir" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security objects occur. |
- 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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
-
+ | At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -48429,55 +48478,6 @@
|
-
- | CCI-000172 |
- SRG-OS-000468-GPOS-00212 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful attempts to delete security objects occur. |
-
- CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
-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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful attempts to delete security objects occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-renameat system call, run the following command:
-$ sudo grep "renameat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security objects occur. |
- At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
-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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
- medium |
- |
- |
- |
-
-
@@ -48489,47 +48489,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful logon attempts occur. |
-
CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+
CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
-
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
-
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+
/etc/audit/audit.rules file:
+
-w /etc/sudoers -p wa -k actions
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful logon attempts occur. If it does not, this is a finding. |
-
Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+$ sudo auditctl -l | grep /etc/sudoers
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful logon attempts occur. |
-
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
-
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+
/etc/audit/audit.rules file:
+
-w /etc/sudoers -p wa -k actions
medium |
|
|
@@ -48595,7 +48587,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful logon attempts occur. |
-
CCE-80718-0: Record Attempts to Alter Logon and Logout Events - faillock |
+
CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -48606,19 +48598,19 @@
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 -p wa -k logins
+-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 -p wa -k logins |
+
-w /var/log/lastlog -p wa -k logins
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful logon attempts occur. If it does not, this is a finding. |
-
Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
-$ sudo auditctl -l | grep
+$ sudo auditctl -l | grep /var/log/lastlog
--w -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
+-w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful logon attempts occur. |
The audit system already collects login information for all users
and root. If the auditd daemon is configured to use the
@@ -48626,12 +48618,12 @@
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 -p wa -k logins
+-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 -p wa -k logins |
+
-w /var/log/lastlog -p wa -k logins
medium |
|
|
@@ -48644,39 +48636,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful logon attempts occur. |
-
CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
+
CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
-
At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
+ | 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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers.d/ -p wa -k actions |
-
Applicable - Configurable |
-
Verify the operating system generates audit records when successful/unsuccessful logon attempts occur. If it does not, this is a finding. |
-
Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-
-$ sudo auditctl -l | grep/etc/sudoers.d
+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 |
+
Applicable - Configurable |
+
Verify the operating system generates audit records when successful/unsuccessful logon attempts occur. If it does not, this is a finding. |
+
Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
--w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
+
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful logon attempts occur. |
-
At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers.d/ -p wa -k actions
+ | 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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers.d/ -p wa -k actions |
+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
medium |
|
|
@@ -48689,7 +48689,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful logon attempts occur. |
-
CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+
CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -48699,29 +48699,29 @@
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:
--w /etc/sudoers -p wa -k actions
+-w /etc/sudoers.d/ -p wa -k actions
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:
--w /etc/sudoers -p wa -k actions |
+
-w /etc/sudoers.d/ -p wa -k actions
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful logon attempts occur. If it does not, this is a finding. |
-
Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-$ sudo auditctl -l | grep /etc/sudoers
+$ sudo auditctl -l | grep/etc/sudoers.d
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful logon attempts occur. |
At a minimum, the audit system should collect administrator actions
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:
--w /etc/sudoers -p wa -k actions
+-w /etc/sudoers.d/ -p wa -k actions
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:
--w /etc/sudoers -p wa -k actions |
+
-w /etc/sudoers.d/ -p wa -k actions
medium |
|
|
@@ -48734,47 +48734,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful logon attempts occur. |
-
CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+
CCE-80718-0: Record Attempts to Alter Logon and Logout Events - faillock |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
-
If the auditd daemon is configured to use the
+ | 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 capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
-
+directory /etc/audit/rules.d in order to watch for attempted manual
+edits of files involved in storing logon events:
+-w -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 capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification |
+
/etc/audit/audit.rules file in order to watch for unattempted manual
+edits of files involved in storing logon events:
+
-w -p wa -k logins
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful logon attempts occur. If it does not, this is a finding. |
Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+$ sudo auditctl -l | grep
--w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w
-p wa -k logins Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful logon attempts occur. |
-
If the auditd daemon is configured to use the
+ | 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 capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
-
+directory /etc/audit/rules.d in order to watch for attempted manual
+edits of files involved in storing logon events:
+-w -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 capture events that modify
-account changes:
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification |
+
/etc/audit/audit.rules file in order to watch for unattempted manual
+edits of files involved in storing logon events:
+
-w -p wa -k logins
medium |
|
|
@@ -48787,7 +48783,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful logon attempts occur. |
-
CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+
CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -48798,21 +48794,23 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/group -p wa -k audit_rules_usergroup_modification
+-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/group -p wa -k audit_rules_usergroup_modification |
+
-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful logon attempts occur. If it does not, this is a finding. |
-
Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/group)'
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
--w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes?
Configure the operating system to generate audit records when successful/unsuccessful logon attempts occur. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -48820,14 +48818,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/group -p wa -k audit_rules_usergroup_modification
+-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/group -p wa -k audit_rules_usergroup_modification |
+
-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -48840,7 +48838,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful logon attempts occur. |
-
CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
+
CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -48851,23 +48849,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification
+-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/gshadow -p wa -k audit_rules_usergroup_modification |
+
-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful logon attempts occur. If it does not, this is a finding. |
-
Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
--w /etc/gshadow -p wa -k identity
+$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
+-w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful logon attempts occur. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -48875,14 +48871,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification
+-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/gshadow -p wa -k audit_rules_usergroup_modification |
+
-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -48895,43 +48891,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful logon attempts occur. |
-
CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
+
CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
-
The audit system already collects login information for all users
-and root. If the auditd daemon is configured to use the
+ | 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
+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 watch for unattempted manual
-edits of files involved in storing logon events:
--w /var/log/lastlog -p wa -k logins |
+
/etc/audit/audit.rules file, in order to capture events that modify
+account changes:
+
+
-w /etc/group -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful logon attempts occur. If it does not, this is a finding. |
-
Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
-$ sudo auditctl -l | grep /var/log/lastlog
+$ sudo auditctl -l | grep -E '(/etc/group)'
--w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when successful/unsuccessful logon attempts occur. |
-
The audit system already collects login information for all users
-and root. If the auditd daemon is configured to use the
+ | 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
+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 watch for unattempted manual
-edits of files involved in storing logon events:
--w /var/log/lastlog -p wa -k logins |
+
/etc/audit/audit.rules file, in order to capture events that modify
+account changes:
+
+
-w /etc/group -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -48949,39 +48949,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
-
CCE-85944-7: Record Any Attempts to Run ssh-agent |
+
CCE-80700-8: Record Any Attempts to Run semanage |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
At a minimum, the audit system should collect any execution attempt
-of the ssh-agent command for all users and root. If the auditd
+of the semanage 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
+-a always,exit -F path=/usr/sbin/semanage -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/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
+
-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
-
Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
-$ sudo auditctl -l | grep ssh-agent
+$ sudo auditctl -l | grep semanage
--a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
At a minimum, the audit system should collect any execution attempt
-of the ssh-agent command for all users and root. If the auditd
+of the semanage 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
+-a always,exit -F path=/usr/sbin/semanage -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/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
+
-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -48994,7 +48994,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
-
CCE-80730-5: Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
+
CCE-80989-7: Ensure auditd Collects Information on the Use of Privileged Commands - mount |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -49004,33 +49004,29 @@
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/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+
-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
-
Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "mount" command with the following command:
-$ sudo auditctl -l | grep pam_timestamp_check
+$ sudo auditctl -l | grep mount
--a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
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/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/pam_timestamp_check
--F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+
-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -49088,7 +49084,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
-
CCE-80728-9: Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
+
CCE-80731-3: Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -49098,29 +49094,29 @@
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
+-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/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+
-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
-
Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "gpasswd" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "passwd" command with the following command:
-$ sudo auditctl -l | grep gpasswd
+$ sudo auditctl -l | grep passwd
--a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
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
+-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/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+
-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -49133,39 +49129,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
-
CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
+
CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
-
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
+ | 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 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 |
+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_mod
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
-
Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
-
-$ sudo auditctl -l | grep su
-
--a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out? |
+
To determine if the system is configured to audit calls to the
+chown system call, run the following command:
+$ sudo grep "chown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
-
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
+ | 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 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 |
+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_mod
medium |
|
|
@@ -49178,76 +49182,72 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
-
CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
+
CCE-82168-6: Log USBGuard daemon audit events using Linux Audit |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
-
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
+ | To configure USBGuard daemon to log via Linux Audit
+(as opposed directly to a file),
+AuditBackend option in /etc/usbguard/usbguard-daemon.conf
+needs to be set to LinuxAudit. |
+
Applicable - Configurable |
+
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
+
To verify that Linux Audit logging is enabled for the USBGuard daemon,
+run the following command:
+$ sudo grep AuditBackend /etc/usbguard/usbguard-daemon.conf
+The output should be
+AuditBackend=LinuxAudit Is it the case that AuditBackend is not set to LinuxAudit? |
+
Configure the operating system to generate audit records for privileged activities or other system-level access. |
+
To configure USBGuard daemon to log via Linux Audit
+(as opposed directly to a file),
+AuditBackend option in /etc/usbguard/usbguard-daemon.conf
+needs to be set to LinuxAudit. |
+
low |
+
|
+
|
+
|
+
-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
+
+ | CCI-000172 |
+ SRG-OS-000471-GPOS-00215 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records for privileged activities or other system-level access. |
+
+ CCE-80701-6: Record Any Attempts to Run setsebool |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ At a minimum, the audit system should collect any execution attempt
+of the setsebool 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/sbin/setsebool -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 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 |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r truncate /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep truncate /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep setsebool
--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+ | At a minimum, the audit system should collect any execution attempt
+of the setsebool 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 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
-
+-a always,exit -F path=/usr/sbin/setsebool -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 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 |
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -49260,39 +49260,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80729-7: Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
+ CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers -p wa -k actions
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "newgrp" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-$ sudo auditctl -l | grep newgrp
+$ sudo auditctl -l | grep /etc/sudoers
--a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+ | At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
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 |
+utility to read audit rules during daemon startup, add the following line to
+/etc/audit/audit.rules file:
+-w /etc/sudoers -p wa -k actions
medium |
|
|
@@ -49305,70 +49305,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
+ CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+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:
--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=access |
+/etc/audit/audit.rules file, in order to capture events that modify
+account changes:
+
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r open_by_handle_at /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep open_by_handle_at /etc/audit/audit.rules
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep -E '(/etc/shadow)'
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+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:
--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=access |
+/etc/audit/audit.rules file, in order to capture events that modify
+account changes:
+
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -49381,60 +49358,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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_mod |
- Applicable - Configurable |
- Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-lchown system call, run the following command:
-$ sudo grep "lchown" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000471-GPOS-00215 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records for privileged activities or other system-level access. |
-
- CCE-89455-0: Ensure auditd Collects Information on the Use of Privileged Commands - kmod |
+ CCE-89455-0: Ensure auditd Collects Information on the Use of Privileged Commands - kmod |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -49479,47 +49403,55 @@
| TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | 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
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 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 |
+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
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
-
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fsetxattr system call, run the following command:
+$ sudo grep "fsetxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
-
+ | 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
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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 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 |
+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
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -49532,39 +49464,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80733-9: Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
+ CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postqueue" command with the following command:
-
-$ sudo auditctl -l | grep postqueue
-
--a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+setxattr system call, run the following command:
+$ sudo grep "setxattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
+-a always,exit -F arch=b32 -S setxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -49577,39 +49525,76 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-89446-9: Record Any Attempts to Run chacl |
+ CCE-80756-0: Record Unsuccessful Access Attempts to Files - truncate |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call.
-$ sudo auditctl -l | grep chacl
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r truncate /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep truncate /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+ | 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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
medium |
|
|
@@ -49622,39 +49607,63 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80740-4: Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
+ CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+
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 |
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command:
-
-$ sudo auditctl -l | grep unix_chkpwd
-
--a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+removexattr system call, run the following command:
+$ sudo grep "removexattr" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+
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 |
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -49667,84 +49676,76 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
+ CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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=access
+
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 |
+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=access
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
-$ sudo auditctl -l | grep usermod
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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 |
- medium |
- |
- |
- |
-
+$ sudo grep -r ftruncate /etc/audit/rules.d
-
- | CCI-000172 |
- SRG-OS-000471-GPOS-00215 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records for privileged activities or other system-level access. |
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
- CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
+$ sudo grep ftruncate /etc/audit/audit.rules
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+The output should be the following:
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 |
- Applicable - Configurable |
- Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records for privileged activities or other system-level access. |
+ 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
-$ sudo auditctl -l | grep sudo
+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=access
--a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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 |
+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=access
medium |
|
|
@@ -49757,7 +49758,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80726-3: Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
+ CCE-80732-1: Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -49767,29 +49768,29 @@
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
+-a always,exit -F path=/usr/sbin/postdrop -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 |
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chsh" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postdrop" command with the following command:
-$ sudo auditctl -l | grep chsh
+$ sudo auditctl -l | grep postdrop
--a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
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
+-a always,exit -F path=/usr/sbin/postdrop -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 |
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -49802,7 +49803,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
+ CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -49813,17 +49814,17 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete |
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-unlink system call, run the following command:
-$ sudo grep "unlink" /etc/audit/audit.*
+unlinkat system call, run the following command:
+$ sudo grep "unlinkat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
@@ -49833,12 +49834,12 @@
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
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 unlink -F auid>=1000 -F auid!=unset -F key=delete
+-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -49851,7 +49852,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80741-2: Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
+ CCE-80728-9: Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -49861,29 +49862,29 @@
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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "userhelper" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "gpasswd" command with the following command:
-$ sudo auditctl -l | grep userhelper
+$ sudo auditctl -l | grep gpasswd
--a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -49896,43 +49897,98 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
+ CCE-80725-5: Ensure auditd Collects Information on the Use of Privileged Commands - chage |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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:
+ | 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 |
+ Applicable - Configurable |
+ Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chage" command with the following command:
--a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -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:
+$ sudo auditctl -l | grep chage
--a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -F key=modules |
+-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out?
+ Configure the operating system to generate audit records for privileged activities or other system-level access. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000471-GPOS-00215 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records for privileged activities or other system-level access. |
+
+ CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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_mod |
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-finit_module system call, run the following command:
-$ sudo grep "finit_module" /etc/audit/audit.*
+fchown system call, run the following command:
+$ sudo grep "fchown" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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:
+ | 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
--a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -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:
+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
--a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -F key=modules |
+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_mod
medium |
|
|
@@ -49945,47 +50001,70 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
+ CCE-80755-2: Record Unsuccessful Access Attempts to Files - open_by_handle_at |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | 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, in order to capture events that modify
-account changes:
-
--w /etc/shadow -p wa -k audit_rules_usergroup_modification |
+/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=access
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call.
-$ sudo auditctl -l | grep -E '(/etc/shadow)'
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
+$ sudo grep -r open_by_handle_at /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep open_by_handle_at /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
-
+ | 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, in order to capture events that modify
-account changes:
-
--w /etc/shadow -p wa -k audit_rules_usergroup_modification |
+/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=access
medium |
|
|
@@ -49998,7 +50077,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80727-1: Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
+ CCE-80729-7: Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -50008,29 +50087,29 @@
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
+-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/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "crontab" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "newgrp" command with the following command:
-$ sudo auditctl -l | grep crontab
+$ sudo auditctl -l | grep newgrp
--a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
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
+-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/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -50043,39 +50122,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80701-6: Record Any Attempts to Run setsebool |
+ CCE-80741-2: Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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/userhelper -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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setsebool" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "userhelper" command with the following command:
-$ sudo auditctl -l | grep setsebool
+$ sudo auditctl -l | grep userhelper
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- At a minimum, the audit system should collect any execution attempt
-of the setsebool 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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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/userhelper -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/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -50088,70 +50167,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
+ CCE-80740-4: Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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=access |
+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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r creat /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep creat /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep unix_chkpwd
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+ | 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 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=access |
+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
medium |
|
|
@@ -50164,43 +50212,65 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80722-2: Ensure auditd Collects Information on Exporting to Media (successful) |
+ CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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, 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 |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-mount system call, run the following command:
-$ sudo grep "mount" /etc/audit/audit.*
+lremovexattr system call, run the following command:
+$ sudo grep "lremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+ | 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
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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, 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 |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -50213,47 +50283,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
+ CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
+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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchmod system call, run the following command:
-$ sudo grep "fchmod" /etc/audit/audit.*
+fchownat system call, run the following command:
+$ sudo grep "fchownat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
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
+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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -50266,45 +50336,40 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
+ CCE-89446-9: Record Any Attempts to Run chacl |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ 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 |
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes audit_backlog_limit=8192,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
-The command should not return any output. Is it the case that audit backlog limit is not configured? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chacl" command with the following command:
+
+$ sudo auditctl -l | grep chacl
+
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- To improve the kernel capacity to queue all log events, even those which occurred
-prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit_backlog_limit=8192 is added as a kernel command line
-argument to newly installed kernels, add audit_backlog_limit=8192 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
- low |
+ 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 |
+ medium |
|
|
|
@@ -50316,39 +50381,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
+ CCE-80706-5: Ensure auditd Collects File Deletion Events by User - unlink |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect administrator actions
+ | At a minimum, the audit system should collect file deletion 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:
--w /etc/sudoers.d/ -p wa -k actions
+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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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:
--w /etc/sudoers.d/ -p wa -k actions |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
-
-$ sudo auditctl -l | grep/etc/sudoers.d
-
--w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+unlink system call, run the following command:
+$ sudo grep "unlink" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- At a minimum, the audit system should collect administrator actions
+ | At a minimum, the audit system should collect file deletion 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:
--w /etc/sudoers.d/ -p wa -k actions
+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 unlink -F auid>=1000 -F auid!=unset -F key=delete
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:
--w /etc/sudoers.d/ -p wa -k actions |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -50361,7 +50430,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80752-9: Record Unsuccessful Access Attempts to Files - ftruncate |
+ CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -50371,233 +50440,66 @@
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
+-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 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=access
+-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 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
+-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 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=access |
+-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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r ftruncate /etc/audit/rules.d
+$ sudo grep -r open /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep ftruncate /etc/audit/audit.rules
+$ sudo grep open /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
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
+-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 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=access
+-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 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
+-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 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=access |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000471-GPOS-00215 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records for privileged activities or other system-level access. |
-
- CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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_mod |
- Applicable - Configurable |
- Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchmodat system call, run the following command:
-$ sudo grep "fchmodat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000471-GPOS-00215 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records for privileged activities or other system-level access. |
-
- CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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_mod |
- Applicable - Configurable |
- Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fchownat system call, run the following command:
-$ sudo grep "fchownat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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_mod |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000471-GPOS-00215 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records for privileged activities or other system-level access. |
-
- CCE-80697-6: Record Events that Modify the System's Discretionary Access Controls - setxattr |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
- Applicable - Configurable |
- Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-setxattr system call, run the following command:
-$ sudo grep "setxattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -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
--a always,exit -F arch=b32 -S setxattr -F auid=0 -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
--a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
+-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
medium |
|
|
@@ -50610,39 +50512,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+ CCE-80726-3: Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 the following line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chsh" command with the following command:
-$ sudo auditctl -l | grep /etc/sudoers
+$ sudo auditctl -l | grep chsh
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 the following line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
medium |
|
|
@@ -50655,43 +50557,88 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80713-1: Ensure auditd Collects Information on Kernel Module Loading - init_module |
+ CCE-80739-6: Ensure auditd Collects Information on the Use of Privileged Commands - umount |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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:
+ | 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 |
+ Applicable - Configurable |
+ Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "umount" command with the following command:
--a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modules
+$ sudo auditctl -l | grep umount
+-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records for privileged activities or other system-level access. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
-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.
+
+ | CCI-000172 |
+ SRG-OS-000471-GPOS-00215 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records for privileged activities or other system-level access. |
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules.
- Applicable - Configurable |
- Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-init_module system call, run the following command:
-$ sudo grep "init_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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:
+ | CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
--a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modules
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
-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.
+$ sudo auditctl -l | grep /var/log/lastlog
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules. |
+-w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out?
+ Configure the operating system to generate audit records for privileged activities or other system-level access. |
+ 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 |
medium |
|
|
@@ -50704,47 +50651,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
+ CCE-80736-2: Ensure auditd Collects Information on the Use of Privileged Commands - su |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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_mod |
+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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-chmod system call, run the following command:
-$ sudo grep "chmod" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "su" command with the following command:
+
+$ sudo auditctl -l | grep su
+
+-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+ | 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 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_mod |
+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
medium |
|
|
@@ -50757,43 +50696,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80707-3: Ensure auditd Collects File Deletion Events by User - unlinkat |
+ CCE-80727-1: Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file deletion 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-unlinkat system call, run the following command:
-$ sudo grep "unlinkat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "crontab" command with the following command:
+
+$ sudo auditctl -l | grep crontab
+
+-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- At a minimum, the audit system should collect file deletion 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
@@ -50806,7 +50741,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -50817,21 +50752,21 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
--w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -50839,59 +50774,14 @@
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
+-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/security/opasswd -p wa -k audit_rules_usergroup_modification |
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000471-GPOS-00215 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records for privileged activities or other system-level access. |
-
- CCE-88437-9: Record Any Attempts to Run setfacl |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 |
- Applicable - Configurable |
- Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfacl" command with the following command:
-
-$ sudo auditctl -l | grep setfacl
-
--a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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 |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -50904,53 +50794,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80689-3: Record Events that Modify the System's Discretionary Access Controls - fchown |
+ CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
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_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchown system call, run the following command:
-$ sudo grep "fchown" /etc/audit/audit.*
+rename system call, run the following command:
+$ sudo grep "rename" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
-
+ | At a minimum, the audit system should collect file deletion 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 rename -F auid>=1000 -F auid!=unset -F key=delete
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_mod |
+/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
+appropriate for your system:
+-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -50963,76 +50843,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
+ CCE-85944-7: Record Any Attempts to Run ssh-agent |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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
-
+-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 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 |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
-
-If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-
-$ sudo grep -r openat /etc/audit/rules.d
-
-If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-
-$ sudo grep openat /etc/audit/audit.rules
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command:
-The output should be the following:
+$ sudo auditctl -l | grep ssh-agent
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+ | 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 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
-
+-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 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 |
+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent
medium |
|
|
@@ -51045,39 +50888,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80725-5: Ensure auditd Collects Information on the Use of Privileged Commands - chage |
+ CCE-80713-1: Ensure auditd Collects Information on Kernel Module Loading - init_module |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 |
+ 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 auid>=1000 -F auid!=unset -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. |
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chage" command with the following command:
+ | To determine if the system is configured to audit calls to the
+init_module system call, run the following command:
+$ sudo grep "init_module" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records for privileged activities or other system-level access. |
+ 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:
-$ sudo auditctl -l | grep chage
+-a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modules
--a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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 |
+
+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.
medium |
|
|
@@ -51090,55 +50937,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+ CCE-80687-7: Record Events that Modify the System's Discretionary Access Controls - fchmod |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lsetxattr system call, run the following command:
-$ sudo grep "lsetxattr" /etc/audit/audit.*
+fchmod system call, run the following command:
+$ sudo grep "fchmod" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -51151,7 +50990,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
+ CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -51161,24 +51000,20 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fsetxattr system call, run the following command:
-$ sudo grep "fsetxattr" /etc/audit/audit.*
+lchown system call, run the following command:
+$ sudo grep "lchown" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
@@ -51187,19 +51022,15 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -51212,39 +51043,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80989-7: Ensure auditd Collects Information on the Use of Privileged Commands - mount |
+ CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
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 |
+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 renameat -F auid>=1000 -F auid!=unset -F key=delete
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "mount" command with the following command:
-
-$ sudo auditctl -l | grep mount
-
--a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+renameat system call, run the following command:
+$ sudo grep "renameat" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+ | At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
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 |
+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 renameat -F auid>=1000 -F auid!=unset -F key=delete
medium |
|
|
@@ -51257,7 +51092,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80753-7: Record Unsuccessful Access Attempts to Files - open |
+ CCE-80751-1: Record Unsuccessful Access Attempts to Files - creat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -51267,66 +51102,60 @@
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the open system call.
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the creat system call.
If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
-$ sudo grep -r open /etc/audit/rules.d
+$ sudo grep -r creat /etc/audit/rules.d
If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
-$ sudo grep open /etc/audit/audit.rules
+$ sudo grep creat /etc/audit/audit.rules
The output should be the following:
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
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
-
+-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 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
-
+-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 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
-
+-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 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 |
+-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
medium |
|
|
@@ -51339,43 +51168,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80703-2: Ensure auditd Collects File Deletion Events by User - rename |
+ CCE-89497-2: Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file deletion events
+ | At a minimum, the audit system should collect administrator actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-w /etc/sudoers.d/ -p wa -k actions
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-rename system call, run the following command:
-$ sudo grep "rename" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command:
+
+$ sudo auditctl -l | grep/etc/sudoers.d
+
+-w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- At a minimum, the audit system should collect file deletion events
+ | At a minimum, the audit system should collect administrator actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete
+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:
+-w /etc/sudoers.d/ -p wa -k actions
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 rename -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-w /etc/sudoers.d/ -p wa -k actions
medium |
|
|
@@ -51388,7 +51213,56 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80739-6: Ensure auditd Collects Information on the Use of Privileged Commands - umount |
+ CCE-80711-5: Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 auid>=1000 -F auid!=unset -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. |
+ Applicable - Configurable |
+ Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+delete_module system call, run the following command:
+$ sudo grep "delete_module" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records for privileged activities or other system-level access. |
+ 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 auid>=1000 -F auid!=unset -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. |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000471-GPOS-00215 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records for privileged activities or other system-level access. |
+
+ CCE-86027-0: Ensure auditd Collects Information on the Use of Privileged Commands - usermod |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -51398,29 +51272,29 @@
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
+-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/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "umount" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "usermod" command with the following command:
-$ sudo auditctl -l | grep umount
+$ sudo auditctl -l | grep usermod
--a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
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
+-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/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -51433,47 +51307,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
+ CCE-80737-0: Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | 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 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 |
+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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "sudo" command with the following command:
-$ sudo auditctl -l | grep -E '(/etc/group)'
+$ sudo auditctl -l | grep sudo
--w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
-
+ | 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 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 |
+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
medium |
|
|
@@ -51486,43 +51352,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
+ CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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, setting ARCH to either b32 or b64 as
-appropriate for your system:
--a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-rmdir system call, run the following command:
-$ sudo grep "rmdir" /etc/audit/audit.*
+lsetxattr system call, run the following command:
+$ sudo grep "lsetxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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, setting ARCH to either b32 or b64 as
-appropriate for your system:
--a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+/etc/audit/audit.rules file:
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+If the system is 64 bit then also add the following line:
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -51535,39 +51413,76 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80731-3: Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
+ CCE-80754-5: Record Unsuccessful Access Attempts to Files - openat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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 |
+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=access
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "passwd" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates an audit record for unsuccessful attempts to use the openat system call.
-$ sudo auditctl -l | grep passwd
+If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command:
--a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out? |
+$ sudo grep -r openat /etc/audit/rules.d
+
+If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command:
+
+$ sudo grep openat /etc/audit/audit.rules
+
+The output should be the following:
+
+-a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access
+-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+ | 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 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 |
+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=access
medium |
|
|
@@ -51580,39 +51495,96 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80700-8: Record Any Attempts to Run semanage |
+ CCE-80705-7: Ensure auditd Collects File Deletion Events by User - rmdir |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+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 rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+ Applicable - Configurable |
+ Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+rmdir system call, run the following command:
+$ sudo grep "rmdir" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records for privileged activities or other system-level access. |
+ At a minimum, the audit system should collect file deletion 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 rmdir -F auid>=1000 -F auid!=unset -F key=delete
+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 rmdir -F auid>=1000 -F auid!=unset -F key=delete |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000172 |
+ SRG-OS-000471-GPOS-00215 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records for privileged activities or other system-level access. |
+
+ CCE-80688-5: Record Events that Modify the System's Discretionary Access Controls - fchmodat |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 lines to
+utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "semanage" command with the following command:
-
-$ sudo auditctl -l | grep semanage
-
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
+ To determine if the system is configured to audit calls to the
+fchmodat system call, run the following command:
+$ sudo grep "fchmodat" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- At a minimum, the audit system should collect any execution attempt
-of the semanage 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/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 lines to
+utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
--a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-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
medium |
|
|
@@ -51625,7 +51597,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
+ CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -51633,55 +51605,57 @@
| 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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
+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
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-removexattr system call, run the following command:
-$ sudo grep "removexattr" /etc/audit/audit.*
+fremovexattr system call, run the following command:
+$ sudo grep "fremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
+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
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -51694,47 +51668,43 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
+ CCE-80722-2: Ensure auditd Collects Information on Exporting to Media (successful) |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured to
+ | 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:
--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
+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:
--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 |
+/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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-chown system call, run the following command:
-$ sudo grep "chown" /etc/audit/audit.*
+mount system call, run the following command:
+$ sudo grep "mount" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured to
+ | 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:
--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
+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:
--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 |
+/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
medium |
|
|
@@ -51747,43 +51717,88 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80711-5: Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
+ CCE-80733-9: Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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:
+ | 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/postqueue -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ Applicable - Configurable |
+ Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postqueue" command with the following command:
--a always,exit -F arch=ARCH -S delete_module -F auid>=1000 -F auid!=unset -F key=modules
+$ sudo auditctl -l | grep postqueue
+-a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out? |
+ Configure the operating system to generate audit records for privileged activities or other system-level access. |
+ 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/postqueue -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/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ medium |
+ |
+ |
+ |
+
-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.
+
+ | CCI-000172 |
+ SRG-OS-000471-GPOS-00215 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records for privileged activities or other system-level access. |
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules.
+ CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-delete_module system call, run the following command:
-$ sudo grep "delete_module" /etc/audit/audit.*
+finit_module system call, run the following command:
+$ sudo grep "finit_module" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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 auid>=1000 -F auid!=unset -F key=modules
-
+ | 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:
-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.
+-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -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:
-If the auditd daemon is configured to use the auditctl utility,
-add the line to file /etc/audit/audit.rules. |
+-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -F key=modules
medium |
|
|
@@ -51796,39 +51811,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-82280-9: Record Any Attempts to Run setfiles |
+ CCE-88437-9: Record Any Attempts to Run setfacl |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
At a minimum, the audit system should collect any execution attempt
-of the setfiles command for all users and root. If the auditd
+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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfacl" command with the following command:
-$ sudo auditctl -l | grep setfiles
+$ sudo auditctl -l | grep setfacl
--a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
At a minimum, the audit system should collect any execution attempt
-of the setfiles command for all users and root. If the auditd
+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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+-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/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -51841,66 +51856,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
+ CCE-80943-4: Extend Audit Backlog Limit for the Audit Daemon |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-lremovexattr system call, run the following command:
-$ sudo grep "lremovexattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes audit_backlog_limit=8192,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192'
+The command should not return any output. Is it the case that audit backlog limit is not configured? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
- medium |
+ To improve the kernel capacity to queue all log events, even those which occurred
+prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit_backlog_limit=8192 is added as a kernel command line
+argument to newly installed kernels, add audit_backlog_limit=8192 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
+ low |
|
|
|
@@ -51912,49 +51906,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
+ CCE-82280-9: Record Any Attempts to Run setfiles |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
-
+ | At a minimum, the audit system should collect any execution attempt
+of the setfiles 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/sbin/setfiles -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, in order to capture events that modify
-account changes:
-
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification |
+/etc/audit/audit.rules file:
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "setfiles" command with the following command:
--w /etc/gshadow -p wa -k identity
+$ sudo auditctl -l | grep setfiles
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
-
+ | At a minimum, the audit system should collect any execution attempt
+of the setfiles 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/sbin/setfiles -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, in order to capture events that modify
-account changes:
-
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification |
+/etc/audit/audit.rules file:
+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -51967,66 +51951,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80691-9: Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
+ CCE-80825-3: Enable Auditing for Processes Which Start Prior to the Audit Daemon |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
+ To ensure all processes can be audited, even those which start
+prior to the audit daemon, add the argument audit=1 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit=1 is added as a kernel command line
+argument to newly installed kernels, add audit=1 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit=1 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-fremovexattr system call, run the following command:
-$ sudo grep "fremovexattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes audit=1,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit=1.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*audit=1.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'audit=1'
+The command should not return any output. Is it the case that auditing is not enabled at boot time? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -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
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
- medium |
+ To ensure all processes can be audited, even those which start
+prior to the audit daemon, add the argument audit=1 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that audit=1 is added as a kernel command line
+argument to newly installed kernels, add audit=1 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... audit=1 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
+ low |
|
|
|
@@ -52038,43 +52001,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
+ CCE-80685-1: Record Events that Modify the System's Discretionary Access Controls - chmod |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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 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 |
+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_mod
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
-
-$ sudo auditctl -l | grep /var/log/lastlog
-
--w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
- Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+ | To determine if the system is configured to audit calls to the
+chmod system call, run the following command:
+$ sudo grep "chmod" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records for privileged activities or other system-level access. |
+ 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 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 |
+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_mod
medium |
|
|
@@ -52087,39 +52054,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80698-4: Record Any Attempts to Run chcon |
+ CCE-89480-8: Ensure auditd Collects Information on the Use of Privileged Commands - unix_update |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
+ | 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_update -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 |
+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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
+ | Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_update" command with the following command:
-$ sudo auditctl -l | grep chcon
+$ sudo auditctl -l | grep unix_update
--a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
+-a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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
+ | 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_update -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 |
+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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
medium |
|
|
@@ -52132,28 +52099,44 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-82168-6: Log USBGuard daemon audit events using Linux Audit |
+ CCE-80730-5: Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- To configure USBGuard daemon to log via Linux Audit
-(as opposed directly to a file),
-AuditBackend option in /etc/usbguard/usbguard-daemon.conf
-needs to be set to LinuxAudit. |
+ 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/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=/usr/sbin/pam_timestamp_check
+-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- To verify that Linux Audit logging is enabled for the USBGuard daemon,
-run the following command:
-$ sudo grep AuditBackend /etc/usbguard/usbguard-daemon.conf
-The output should be
-AuditBackend=LinuxAudit Is it the case that AuditBackend is not set to LinuxAudit? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command:
+
+$ sudo auditctl -l | grep pam_timestamp_check
+
+-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- To configure USBGuard daemon to log via Linux Audit
-(as opposed directly to a file),
-AuditBackend option in /etc/usbguard/usbguard-daemon.conf
-needs to be set to LinuxAudit. |
- low |
+ 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/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=/usr/sbin/pam_timestamp_check
+-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+ medium |
|
|
|
@@ -52165,39 +52148,49 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-89480-8: Ensure auditd Collects Information on the Use of Privileged Commands - unix_update |
+ CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 a line of the following
-form to /etc/audit/audit.rules:
--a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "unix_update" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-$ sudo auditctl -l | grep unix_update
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
--a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 a line of the following
-form to /etc/audit/audit.rules:
--a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
medium |
|
|
@@ -52210,45 +52203,48 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80825-3: Enable Auditing for Processes Which Start Prior to the Audit Daemon |
+ CCE-80760-2: Record Events that Modify User/Group Information - /etc/security/opasswd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- To ensure all processes can be audited, even those which start
-prior to the audit daemon, add the argument audit=1 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit=1 is added as a kernel command line
-argument to newly installed kernels, add audit=1 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit=1 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
+ 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 |
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes audit=1,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit=1.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*audit=1.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'audit=1'
-The command should not return any output. Is it the case that auditing is not enabled at boot time? |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+
+$ sudo auditctl -l | grep -E '(/etc/security/opasswd)'
+
+-w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- To ensure all processes can be audited, even those which start
-prior to the audit daemon, add the argument audit=1 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that audit=1 is added as a kernel command line
-argument to newly installed kernels, add audit=1 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... audit=1 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="audit=1" |
- low |
+ 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 |
+ medium |
|
|
|
@@ -52260,39 +52256,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80732-1: Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
+ CCE-80758-6: Record Events that Modify User/Group Information - /etc/group |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 a line of the following
-form to /etc/audit/audit.rules:
--a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "postdrop" command with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command:
-$ sudo auditctl -l | grep postdrop
+$ sudo auditctl -l | grep -E '(/etc/group)'
--a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- 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/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
+ | 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 a line of the following
-form to /etc/audit/audit.rules:
--a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
+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
medium |
|
|
@@ -52305,43 +52309,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for privileged activities or other system-level access. |
- CCE-80704-0: Ensure auditd Collects File Deletion Events by User - renameat |
+ CCE-80698-4: Record Any Attempts to Run chcon |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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
Applicable - Configurable |
Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-renameat system call, run the following command:
-$ sudo grep "renameat" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to audit the execution of the "chcon" command with the following command:
+
+$ sudo auditctl -l | grep chcon
+
+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
Configure the operating system to generate audit records for privileged activities or other system-level access. |
- At a minimum, the audit system should collect file deletion 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 renameat -F auid>=1000 -F auid!=unset -F key=delete
+ | 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 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 renameat -F auid>=1000 -F auid!=unset -F key=delete |
+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
medium |
|
|
@@ -52398,55 +52398,6 @@
|
-
- | CCI-000172 |
- SRG-OS-000471-GPOS-00216 |
- TBD - Assigned by DISA after STIG release |
- The audit system must be configured to audit the loading and unloading of dynamic kernel modules. |
-
- CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
- Applicable - Configurable |
- Verify the audit system is configured to audit the loading and unloading of dynamic kernel modules. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-finit_module system call, run the following command:
-$ sudo grep "finit_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the audit system to audit the loading and unloading of dynamic kernel modules. |
- 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
- medium |
- |
- |
- |
-
-
| CCI-000172 |
SRG-OS-000471-GPOS-00216 |
@@ -52545,6 +52496,55 @@
|
+
+ | CCI-000172 |
+ SRG-OS-000471-GPOS-00216 |
+ TBD - Assigned by DISA after STIG release |
+ The audit system must be configured to audit the loading and unloading of dynamic kernel modules. |
+
+ CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
+ Applicable - Configurable |
+ Verify the audit system is configured to audit the loading and unloading of dynamic kernel modules. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+finit_module system call, run the following command:
+$ sudo grep "finit_module" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the audit system to audit the loading and unloading of dynamic kernel modules. |
+ 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
+ medium |
+ |
+ |
+ |
+
+
@@ -52580,7 +52580,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when concurrent logons to the same account occur from different sources. |
-
CCE-80718-0: Record Attempts to Alter Logon and Logout Events - faillock |
+
CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -52591,19 +52591,19 @@
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 -p wa -k logins
+-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 -p wa -k logins |
+
-w /var/log/lastlog -p wa -k logins
Applicable - Configurable |
Verify the operating system generates audit records when concurrent logons to the same account occur from different sources. If it does not, this is a finding. |
-
Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
-$ sudo auditctl -l | grep
+$ sudo auditctl -l | grep /var/log/lastlog
--w -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
+-w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when concurrent logons to the same account occur from different sources. |
The audit system already collects login information for all users
and root. If the auditd daemon is configured to use the
@@ -52611,12 +52611,12 @@
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 -p wa -k logins
+-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 -p wa -k logins |
+
-w /var/log/lastlog -p wa -k logins
medium |
|
|
@@ -52629,7 +52629,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when concurrent logons to the same account occur from different sources. |
-
CCE-80719-8: Record Attempts to Alter Logon and Logout Events - lastlog |
+
CCE-80718-0: Record Attempts to Alter Logon and Logout Events - faillock |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -52640,19 +52640,19 @@
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
+-w -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 |
+
-w -p wa -k logins
Applicable - Configurable |
Verify the operating system generates audit records when concurrent logons to the same account occur from different sources. If it does not, this is a finding. |
-
Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command:
-$ sudo auditctl -l | grep /var/log/lastlog
+$ sudo auditctl -l | grep
--w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
+-w
-p wa -k logins Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records when concurrent logons to the same account occur from different sources. |
The audit system already collects login information for all users
and root. If the auditd daemon is configured to use the
@@ -52660,12 +52660,12 @@
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
+-w -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 |
+
-w -p wa -k logins
medium |
|
|
@@ -52733,7 +52733,60 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful accesses to objects occur. |
-
CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
+
CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
+
+
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+
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_mod |
+
Applicable - Configurable |
+
Verify the operating system generates audit records when successful/unsuccessful accesses to objects occur. If it does not, this is a finding. |
+
To determine if the system is configured to audit calls to the
+chown system call, run the following command:
+$ sudo grep "chown" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+
Configure the operating system to generate audit records when successful/unsuccessful accesses to objects occur. |
+
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_mod |
+
medium |
+
|
+
|
+
|
+
+
+
+ | CCI-000172 |
+ SRG-OS-000474-GPOS-00219 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records when successful/unsuccessful accesses to objects occur. |
+
+ CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -52743,20 +52796,24 @@
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
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful accesses to objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lchown system call, run the following command:
-$ sudo grep "lchown" /etc/audit/audit.*
+fsetxattr system call, run the following command:
+$ sudo grep "fsetxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful accesses to objects occur. |
@@ -52765,15 +52822,19 @@
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
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
+-a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -52786,47 +52847,63 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful accesses to objects occur. |
- CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
+ CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful accesses to objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fchownat system call, run the following command:
-$ sudo grep "fchownat" /etc/audit/audit.*
+removexattr system call, run the following command:
+$ sudo grep "removexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful accesses to objects occur. |
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
+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
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -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
+-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S removexattr -F auid=0 -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 |
+-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -52898,55 +52975,65 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful accesses to objects occur. |
- CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
+ CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
+
If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
+
If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful accesses to objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lsetxattr system call, run the following command:
-$ sudo grep "lsetxattr" /etc/audit/audit.*
+lremovexattr system call, run the following command:
+$ sudo grep "lremovexattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful accesses to objects occur. |
At a minimum, the audit system should collect file permission
-changes for all users and root. If the auditd daemon is configured
+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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
+
If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
+
If the system is 64 bit then also add the following line:
--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -52959,7 +53046,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful accesses to objects occur. |
- CCE-80692-7: Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
+ CCE-80690-1: Record Events that Modify the System's Discretionary Access Controls - fchownat |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -52969,24 +53056,20 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_mod
+-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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful accesses to objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-fsetxattr system call, run the following command:
-$ sudo grep "fsetxattr" /etc/audit/audit.*
+fchownat system call, run the following command:
+$ sudo grep "fchownat" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful accesses to objects occur. |
@@ -52995,88 +53078,15 @@
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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod
- medium |
- |
- |
- |
-
-
-
- | CCI-000172 |
- SRG-OS-000474-GPOS-00219 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records when successful/unsuccessful accesses to objects occur. |
-
- CCE-80696-8: Record Events that Modify the System's Discretionary Access Controls - removexattr |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -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
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
- Applicable - Configurable |
- Verify the operating system generates audit records when successful/unsuccessful accesses to objects occur. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-removexattr system call, run the following command:
-$ sudo grep "removexattr" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records when successful/unsuccessful accesses to objects occur. |
- 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
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod
-
+-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 removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -53089,47 +53099,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful accesses to objects occur. |
- CCE-80686-9: Record Events that Modify the System's Discretionary Access Controls - chown |
+ CCE-80693-5: Record Events that Modify the System's Discretionary Access Controls - lchown |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
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
+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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful accesses to objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-chown system call, run the following command:
-$ sudo grep "chown" /etc/audit/audit.*
+lchown system call, run the following command:
+$ sudo grep "lchown" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful accesses to objects occur. |
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
+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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod
+-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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod |
+-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
medium |
|
|
@@ -53142,65 +53152,55 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records when successful/unsuccessful accesses to objects occur. |
- CCE-80694-3: Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
+ CCE-80695-0: Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
At a minimum, the audit system should collect file permission
-changes for all users and root.
-
-If the auditd daemon is configured
+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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
Applicable - Configurable |
Verify the operating system generates audit records when successful/unsuccessful accesses to objects occur. If it does not, this is a finding. |
To determine if the system is configured to audit calls to the
-lremovexattr system call, run the following command:
-$ sudo grep "lremovexattr" /etc/audit/audit.*
+lsetxattr system call, run the following command:
+$ sudo grep "lsetxattr" /etc/audit/audit.*
If the system is configured to audit this activity, it will return a line.
Is it the case that no line is returned? |
Configure the operating system to generate audit records when successful/unsuccessful accesses to objects occur. |
At a minimum, the audit system should collect file permission
-changes for all users and root.
-
-If the auditd daemon is configured
+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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod
-
+-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -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
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
+-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
+-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod
medium |
|
|
@@ -53283,6 +53283,44 @@
+
+ | CCI-000172 |
+ SRG-OS-000475-GPOS-00220 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records for all direct access to the information system. |
+
+ CCE-80872-5: Enable auditd Service |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system generates audit records for all direct access to the information system. If it does not, this is a finding. |
+
+
+Run the following command to determine the current status of the
+auditd service:
+$ sudo systemctl is-active auditd
+If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
+ Configure the operating system to generate audit records for all direct access to the information system. |
+ 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 |
+ medium |
+ |
+ |
+ |
+
+
| CCI-000172 |
SRG-OS-000475-GPOS-00220 |
@@ -53365,56 +53403,63 @@
|
+
+
+
+
+
| CCI-000172 |
- SRG-OS-000475-GPOS-00220 |
+ SRG-OS-000476-GPOS-00221 |
TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records for all direct access to the information system. |
+ The operating system must generate audit records for all account creations, modifications, disabling, and termination events. |
- CCE-80872-5: Enable auditd Service |
+ CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 |
+ At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
+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:
+-w /etc/sudoers -p wa -k actions |
Applicable - Configurable |
- Verify the operating system generates audit records for all direct access to the information system. If it does not, this is a finding. |
-
+ | Verify the operating system generates audit records for all account creations, modifications, disabling, and termination events. If it does not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
-Run the following command to determine the current status of the
-auditd service:
-$ sudo systemctl is-active auditd
-If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
- Configure the operating system to generate audit records for all direct access to the information system. |
- The auditd service is an essential userspace component of
-the Linux Auditing System, as it is responsible for writing audit records to
-disk.
+$ sudo auditctl -l | grep /etc/sudoers
-The auditd service can be enabled with the following command:
-$ sudo systemctl enable auditd.service |
+-w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
+ Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events. |
+ At a minimum, the audit system should collect administrator actions
+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:
+-w /etc/sudoers -p wa -k actions
+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:
+-w /etc/sudoers -p wa -k actions |
medium |
|
|
|
-
-
-
-
-
| CCI-000172 |
SRG-OS-000476-GPOS-00221 |
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for all account creations, modifications, disabling, and termination events. |
- CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
+ CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -53425,21 +53470,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system generates audit records for all account creations, modifications, disabling, and termination events. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
-$ sudo auditctl -l | grep -E '(/etc/passwd)'
+$ sudo auditctl -l | grep -E '(/etc/shadow)'
--w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -53447,14 +53492,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
+-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/passwd -p wa -k audit_rules_usergroup_modification |
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -53467,7 +53512,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for all account creations, modifications, disabling, and termination events. |
- CCE-80762-8: Record Events that Modify User/Group Information - /etc/shadow |
+ CCE-80761-0: Record Events that Modify User/Group Information - /etc/passwd |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
@@ -53478,21 +53523,21 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/shadow -p wa -k audit_rules_usergroup_modification
+-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/shadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
Applicable - Configurable |
Verify the operating system generates audit records for all account creations, modifications, disabling, and termination events. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command:
-$ sudo auditctl -l | grep -E '(/etc/shadow)'
+$ sudo auditctl -l | grep -E '(/etc/passwd)'
--w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
+-w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out?
Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events. |
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
@@ -53500,14 +53545,14 @@
directory /etc/audit/rules.d, in order to capture events that modify
account changes:
--w /etc/shadow -p wa -k audit_rules_usergroup_modification
+-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/shadow -p wa -k audit_rules_usergroup_modification |
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
medium |
|
|
@@ -53565,39 +53610,49 @@
TBD - Assigned by DISA after STIG release |
The operating system must generate audit records for all account creations, modifications, disabling, and termination events. |
- CCE-90175-1: Ensure auditd Collects System Administrator Actions - /etc/sudoers |
+ CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
Applicable - Configurable |
Verify the operating system generates audit records for all account creations, modifications, disabling, and termination events. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command:
+ | Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-$ sudo auditctl -l | grep /etc/sudoers
+$ sudo auditctl -l | grep -E '(/etc/gshadow)'
--w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
+-w /etc/gshadow -p wa -k identity
+
+If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes?
Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events. |
- At a minimum, the audit system should collect administrator actions
-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:
--w /etc/sudoers -p wa -k actions
+ | 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 line to
-/etc/audit/audit.rules file:
--w /etc/sudoers -p wa -k actions |
+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
medium |
|
|
@@ -53710,61 +53765,6 @@
|
-
- | CCI-000172 |
- SRG-OS-000476-GPOS-00221 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records for all account creations, modifications, disabling, and termination events. |
-
- CCE-80759-4: Record Events that Modify User/Group Information - /etc/gshadow |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 |
- Applicable - Configurable |
- Verify the operating system generates audit records for all account creations, modifications, disabling, and termination events. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command:
-
-$ sudo auditctl -l | grep -E '(/etc/gshadow)'
-
--w /etc/gshadow -p wa -k identity
-
-If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
- Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events. |
- 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 |
- medium |
- |
- |
- |
-
-
@@ -53815,55 +53815,6 @@
|
-
- | CCI-000172 |
- SRG-OS-000477-GPOS-00222 |
- TBD - Assigned by DISA after STIG release |
- The operating system must generate audit records for all kernel module load, unload, and restart actions, and also for all program initiations. |
-
- CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
-
- Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-
-Audit records can be generated from various components within the information system (e.g., module or policy filter). |
- 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
- Applicable - Configurable |
- Verify the operating system generates audit records for all kernel module load, unload, and restart actions, and also for all program initiations. If it does not, this is a finding. |
- To determine if the system is configured to audit calls to the
-finit_module system call, run the following command:
-$ sudo grep "finit_module" /etc/audit/audit.*
-If the system is configured to audit this activity, it will return a line.
- Is it the case that no line is returned? |
- Configure the operating system to generate audit records for all kernel module load, unload, and restart actions, and also for all program initiations. |
- 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
- medium |
- |
- |
- |
-
-
| CCI-000172 |
SRG-OS-000477-GPOS-00222 |
@@ -53962,6 +53913,55 @@
|
+
+ | CCI-000172 |
+ SRG-OS-000477-GPOS-00222 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must generate audit records for all kernel module load, unload, and restart actions, and also for all program initiations. |
+
+ CCE-80712-3: Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
+
+ Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+
+Audit records can be generated from various components within the information system (e.g., module or policy filter). |
+ 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
+ Applicable - Configurable |
+ Verify the operating system generates audit records for all kernel module load, unload, and restart actions, and also for all program initiations. If it does not, this is a finding. |
+ To determine if the system is configured to audit calls to the
+finit_module system call, run the following command:
+$ sudo grep "finit_module" /etc/audit/audit.*
+If the system is configured to audit this activity, it will return a line.
+ Is it the case that no line is returned? |
+ Configure the operating system to generate audit records for all kernel module load, unload, and restart actions, and also for all program initiations. |
+ 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 auid>=1000 -F auid!=unset -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 auid>=1000 -F auid!=unset -F key=modules |
+ medium |
+ |
+ |
+ |
+
+
@@ -54172,7 +54172,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must, at a minimum, off-load audit data from interconnected systems in real time and off-load audit data from standalone systems weekly. |
-
CCE-86339-9: Ensure Rsyslog Authenticates Off-Loaded Audit Records |
+
CCE-86098-1: Ensure Rsyslog Encrypts Off-Loaded Audit Records |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
@@ -54183,14 +54183,17 @@
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.
-When using rsyslogd to off-load logs the remote system must be authenticated. |
+When using
rsyslogd to off-load logs off a encrpytion system must be used.
Applicable - Configurable |
Verify the operating system, at a minimum, off-loads interconnected systems in real time and off-loads standalone systems weekly. If it does not, this is a finding. |
-
Verify the operating system authenticates the remote logging server for off-loading audit logs with the following command:
+ | Verify the operating system encrypts audit records off-loaded onto a different system
+or media from the system being audited with the following commands:
-$ sudo grep -i '$ActionSendStreamDriverAuthMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf
-The output should be
-$/etc/rsyslog.conf:$ActionSendStreamDriverAuthMode x509/name Is it the case that $ActionSendStreamDriverAuthMode in /etc/rsyslog.conf is not set to x509/name? |
+
$ sudo grep -i '$ActionSendStreamDriverMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf
+
+The output should be:
+
+
/etc/rsyslog.conf:$ActionSendStreamDriverMode 1
Is it the case that rsyslogd ActionSendStreamDriverMode is not set to 1?
Configure the operating system to, at a minimum, off-load interconnected systems in real time and off-load standalone systems weekly. |
Rsyslogd is a system utility providing support for message logging. Support
for both internet and UNIX domain sockets enables this utility to support both local
@@ -54198,40 +54201,7 @@
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.
-When using rsyslogd to off-load logs the remote system must be authenticated. |
-
medium |
-
|
-
|
-
|
-
-
-
- | CCI-001851 |
- SRG-OS-000479-GPOS-00224 |
- TBD - Assigned by DISA after STIG release |
- The operating system must, at a minimum, off-load audit data from interconnected systems in real time and off-load audit data from standalone systems weekly. |
-
- CCE-82897-0: Set type of computer node name logging in audit logs |
-
- 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. |
- To configure Audit daemon to use a unique identifier
-as computer node name in the audit events,
-set name_format to
-in /etc/audit/auditd.conf. |
- Applicable - Configurable |
- Verify the operating system, at a minimum, off-loads interconnected systems in real time and off-loads standalone systems weekly. If it does not, this is a finding. |
- To verify that Audit Daemon is configured to record the computer node
-name in the audit events, run the following command:
-$ sudo grep name_format /etc/audit/auditd.conf
-The output should return the following:
-name_format = Is it the case that name_format isn't set to ? |
- Configure the operating system to, at a minimum, off-load interconnected systems in real time and off-load standalone systems weekly. |
- To configure Audit daemon to use a unique identifier
-as computer node name in the audit events,
-set name_format to
-in /etc/audit/auditd.conf. |
+When using rsyslogd to off-load logs off a encrpytion system must be used.
medium |
|
|
@@ -54316,17 +54286,27 @@
TBD - Assigned by DISA after STIG release |
The operating system must, at a minimum, off-load audit data from interconnected systems in real time and off-load audit data from standalone systems weekly. |
- CCE-80847-7: Ensure rsyslog is Installed |
+ CCE-82897-0: Set type of computer node name logging in audit logs |
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. |
- Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
+ To configure Audit daemon to use a unique identifier
+as computer node name in the audit events,
+set name_format to
+in /etc/audit/auditd.conf. |
Applicable - Configurable |
Verify the operating system, at a minimum, off-loads interconnected systems in real time and off-loads standalone systems weekly. If it does not, this is a finding. |
- Run the following command to determine if the rsyslog package is installed: $ rpm -q rsyslog Is it the case that the package is not installed? |
+ To verify that Audit Daemon is configured to record the computer node
+name in the audit events, run the following command:
+$ sudo grep name_format /etc/audit/auditd.conf
+The output should return the following:
+name_format = Is it the case that name_format isn't set to ? |
Configure the operating system to, at a minimum, off-load interconnected systems in real time and off-load standalone systems weekly. |
- Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
+ To configure Audit daemon to use a unique identifier
+as computer node name in the audit events,
+set name_format to
+in /etc/audit/auditd.conf. |
medium |
|
|
@@ -54339,7 +54319,7 @@
TBD - Assigned by DISA after STIG release |
The operating system must, at a minimum, off-load audit data from interconnected systems in real time and off-load audit data from standalone systems weekly. |
- CCE-86098-1: Ensure Rsyslog Encrypts Off-Loaded Audit Records |
+ CCE-86339-9: Ensure Rsyslog Authenticates Off-Loaded Audit Records |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
@@ -54350,17 +54330,14 @@
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.
-When using rsyslogd to off-load logs off a encrpytion system must be used. |
+When using rsyslogd to off-load logs the remote system must be authenticated.
Applicable - Configurable |
Verify the operating system, at a minimum, off-loads interconnected systems in real time and off-loads standalone systems weekly. If it does not, this is a finding. |
- Verify the operating system encrypts audit records off-loaded onto a different system
-or media from the system being audited with the following commands:
-
-$ sudo grep -i '$ActionSendStreamDriverMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf
-
-The output should be:
+ | Verify the operating system authenticates the remote logging server for off-loading audit logs with the following command:
-/etc/rsyslog.conf:$ActionSendStreamDriverMode 1 Is it the case that rsyslogd ActionSendStreamDriverMode is not set to 1? |
+$ sudo grep -i '$ActionSendStreamDriverAuthMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf
+The output should be
+$/etc/rsyslog.conf:$ActionSendStreamDriverAuthMode x509/name
Is it the case that $ActionSendStreamDriverAuthMode in /etc/rsyslog.conf is not set to x509/name?
Configure the operating system to, at a minimum, off-load interconnected systems in real time and off-load standalone systems weekly. |
Rsyslogd is a system utility providing support for message logging. Support
for both internet and UNIX domain sockets enables this utility to support both local
@@ -54368,7 +54345,30 @@
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.
-When using rsyslogd to off-load logs off a encrpytion system must be used. |
+When using rsyslogd to off-load logs the remote system must be authenticated.
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-001851 |
+ SRG-OS-000479-GPOS-00224 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must, at a minimum, off-load audit data from interconnected systems in real time and off-load audit data from standalone systems weekly. |
+
+ CCE-80847-7: Ensure rsyslog is 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. |
+ Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
+ Applicable - Configurable |
+ Verify the operating system, at a minimum, off-loads interconnected systems in real time and off-loads standalone systems weekly. If it does not, this is a finding. |
+ Run the following command to determine if the rsyslog package is installed: $ rpm -q rsyslog Is it the case that the package is not installed? |
+ Configure the operating system to, at a minimum, off-load interconnected systems in real time and off-load standalone systems weekly. |
+ Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
medium |
|
|
@@ -54451,89 +54451,26 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81037-4: Ensure the Default C Shell Umask is Set Correctly |
-
- Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
-
-Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To ensure the default umask for users of the C shell is set properly,
-add or correct the umask setting in /etc/csh.cshrc to read as follows:
-umask |
- Applicable - Configurable |
- Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify the "umask" setting is configured correctly in the "/etc/csh.cshrc" file with the following command:
-
-$ grep umask /etc/csh.cshrc
-
-umask 077
-umask 077 Is it the case that the value for the "umask" parameter is not "", or the "umask" parameter is missing or is commented out? |
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To ensure the default umask for users of the C shell is set properly,
-add or correct the umask setting in /etc/csh.cshrc to read as follows:
-umask |
- medium |
- |
- |
- |
-
-
-
- | CCI-000366 |
- SRG-OS-000480-GPOS-00227 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-
- CCE-82283-3: Ensure System is Not Acting as a Network Sniffer |
-
- Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
-
-Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
- Applicable - Configurable |
- Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that Promiscuous mode of an interface is disabled, run the following command:
-$ ip link | grep PROMISC Is it the case that any network device is in promiscuous mode? |
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-000366 |
- SRG-OS-000480-GPOS-00227 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-
- CCE-86220-1: Disable Kernel Parameter for IPv4 Forwarding on all IPv4 Interfaces |
+ CCE-85872-0: Ensure PAM password complexity module is enabled in system-auth |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To set the runtime status of the net.ipv4.conf.all.forwarding kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.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.ipv4.conf.all.forwarding = 0 |
+ To enable PAM password complexity in system-auth file:
+Edit the password section in
+/etc/pam.d/system-auth to show
+password requisite pam_pwquality.so. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv4.conf.all.forwarding kernel parameter can be queried
-by running the following command:
-$ sysctl net.ipv4.conf.all.forwarding
-0.
-The ability to forward packets is only appropriate for routers. Is it the case that IP forwarding value is "1" and the system is not router? |
+ To check if pam_pwquality.so is enabled in system-auth, run the following command:
+$ grep pam_pwquality /etc/pam.d/system-auth
+The output should be similar to the following:
+password requisite pam_pwquality.so Is it the case that pam_pwquality.so is not enabled in system-auth? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To set the runtime status of the net.ipv4.conf.all.forwarding kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.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.ipv4.conf.all.forwarding = 0 |
+ To enable PAM password complexity in system-auth file:
+Edit the password section in
+/etc/pam.d/system-auth to show
+password requisite pam_pwquality.so. |
medium |
|
|
@@ -54546,28 +54483,26 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80859-2: Ensure cron Is Logging To Rsyslog |
+ CCE-81039-0: Uninstall Sendmail Package |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Cron logging must be implemented to spot intrusions or trace
-cron job status. If cron is not logging to rsyslog, it
-can be implemented by adding the following to the RULES section of
-/etc/rsyslog.conf:
-cron.* /var/log/cron |
+ Sendmail is not the default mail transfer agent and is
+not installed by default.
+The sendmail package can be removed with the following command:
+
+$ sudo yum erase sendmail |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that cron is logging to rsyslog,
-run the following command:
-grep -rni "cron\.\*" /etc/rsyslog.*
-cron.* /var/log/cron Is it the case that cron is not logging to rsyslog? |
+ Run the following command to determine if the sendmail package is installed:
+$ rpm -q sendmail Is it the case that the package is installed? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Cron logging must be implemented to spot intrusions or trace
-cron job status. If cron is not logging to rsyslog, it
-can be implemented by adding the following to the RULES section of
-/etc/rsyslog.conf:
-cron.* /var/log/cron |
+ Sendmail is not the default mail transfer agent and is
+not installed by default.
+The sendmail package can be removed with the following command:
+
+$ sudo yum erase sendmail |
medium |
|
|
@@ -54580,208 +54515,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80851-9: Ensure /tmp Located On Separate Partition |
-
- Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
-
-Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The /tmp directory is a world-writable directory used
-for temporary file storage. Ensure it has its own partition or
-logical volume at installation time, or migrate it using LVM. |
- Applicable - Configurable |
- Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that a separate file system/partition has been created for /tmp with the following command:
-
-$ mountpoint /tmp
- Is it the case that "/tmp is not a mountpoint" is returned? |
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The /tmp directory is a world-writable directory used
-for temporary file storage. Ensure it has its own partition or
-logical volume at installation time, or migrate it using LVM. |
- low |
- |
- |
- |
-
-
-
- | CCI-000366 |
- SRG-OS-000480-GPOS-00227 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-
- CCE-82863-2: Disable Kernel Parameter for IPv6 Forwarding |
+ CCE-81010-1: Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv6 Interfaces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv6.conf.all.forwarding kernel parameter can be queried
+ | The runtime status of the net.ipv6.conf.default.accept_redirects kernel parameter can be queried
by running the following command:
-$ sysctl net.ipv6.conf.all.forwarding
+$ sysctl net.ipv6.conf.default.accept_redirects
0.
-The ability to forward packets is only appropriate for routers. Is it the case that IP forwarding value is "1" and the system is not router? |
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
- medium |
- |
- |
- |
-
-
-
- | CCI-000366 |
- SRG-OS-000480-GPOS-00227 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-
- CCE-82934-1: Harden the operation of the BPF just-in-time compiler |
-
- Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
-
-Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To set the runtime status of the net.core.bpf_jit_harden kernel parameter, run the following command: $ sudo sysctl -w net.core.bpf_jit_harden=2
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.core.bpf_jit_harden = 2 |
- Applicable - Configurable |
- Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.core.bpf_jit_harden kernel parameter can be queried
-by running the following command:
-$ sysctl net.core.bpf_jit_harden
-2.
Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To set the runtime status of the net.core.bpf_jit_harden kernel parameter, run the following command: $ sudo sysctl -w net.core.bpf_jit_harden=2
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.core.bpf_jit_harden = 2 |
- medium |
- |
- |
- |
-
-
-
- | CCI-000366 |
- SRG-OS-000480-GPOS-00227 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-
- CCE-82462-3: SSH server uses strong entropy to seed |
-
- Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
-
-Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To set up SSH server to use entropy from a high-quality source, edit the /etc/sysconfig/sshd file.
-The SSH_USE_STRONG_RNG configuration value determines how many bytes of entropy to use, so
-make sure that the file contains line
-SSH_USE_STRONG_RNG=32 |
- Applicable - Configurable |
- Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To determine whether the SSH service is configured to use strong entropy seed,
-run $ sudo grep SSH_USE_STRONG_RNG /etc/sysconfig/sshd
-If a line indicating that SSH_USE_STRONG_RNG is set to 32 is returned,
-then the option is set correctly. Is it the case that the SSH_USE_STRONG_RNG is not set to 32 in /etc/sysconfig/sshd? |
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To set up SSH server to use entropy from a high-quality source, edit the /etc/sysconfig/sshd file.
-The SSH_USE_STRONG_RNG configuration value determines how many bytes of entropy to use, so
-make sure that the file contains line
-SSH_USE_STRONG_RNG=32 |
- low |
- |
- |
- |
-
-
-
- | CCI-000366 |
- SRG-OS-000480-GPOS-00227 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-
- CCE-82968-9: Install rng-tools Package |
-
- Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
-
-Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The rng-tools package can be installed with the following command:
-
-$ sudo yum install rng-tools |
- Applicable - Configurable |
- Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Run the following command to determine if the rng-tools package is installed: $ rpm -q rng-tools Is it the case that the package is not installed? |
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The rng-tools package can be installed with the following command:
-
-$ sudo yum install rng-tools |
- low |
- |
- |
- |
-
-
-
- | CCI-000366 |
- SRG-OS-000480-GPOS-00227 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-
- CCE-82904-4: Uninstall tuned Package |
-
- Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
-
-Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The tuned package can be removed with the following command:
-
-$ sudo yum erase tuned |
- Applicable - Configurable |
- Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Run the following command to determine if the tuned package is installed:
-$ rpm -q tuned Is it the case that the package is installed? |
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The tuned package can be removed with the following command:
-
-$ sudo yum erase tuned |
- medium |
- |
- |
- |
-
-
-
- | CCI-000366 |
- SRG-OS-000480-GPOS-00227 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-
- CCE-81035-8: Ensure the Default Umask is Set Correctly in /etc/profile |
-
- Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
-
-Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To ensure the default umask controlled by /etc/profile is set properly,
-add or correct the umask setting in /etc/profile to read as follows:
-umask
-
-Note that /etc/profile also reads scrips within /etc/profile.d directory.
-These scripts are also valid files to set umask value. Therefore, they should also be
-considered during the check and properly remediated, if necessary. |
- Applicable - Configurable |
- Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify the umask setting is configured correctly in the /etc/profile file
-or scripts within /etc/profile.d directory with the following command:
-$ grep "umask" /etc/profile*
-umask Is it the case that the value for the "umask" parameter is not "",
-or the "umask" parameter is missing or is commented out? |
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To ensure the default umask controlled by /etc/profile is set properly,
-add or correct the umask setting in /etc/profile to read as follows:
-umask
-
-Note that /etc/profile also reads scrips within /etc/profile.d directory.
-These scripts are also valid files to set umask value. Therefore, they should also be
-considered during the check and properly remediated, if necessary. |
+ 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 |
medium |
|
|
@@ -54794,29 +54544,26 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-83424-2: All Interactive Users Home Directories Must Exist |
+ CCE-81037-4: Ensure the Default C Shell Umask is Set Correctly |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Create home directories to all local 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 |
+ To ensure the default umask for users of the C shell is set properly,
+add or correct the umask setting in /etc/csh.cshrc to read as follows:
+umask |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify the assigned home directories of all interactive users on the system exist with the following command:
-
-$ sudo pwck -r
+ | Verify the "umask" setting is configured correctly in the "/etc/csh.cshrc" file with the following command:
-user 'mailnull': directory 'var/spool/mqueue' does not exist
+$ grep umask /etc/csh.cshrc
-The output should not return any interactive users. Is it the case that users home directory does not exist? |
+umask 077
+umask 077 Is it the case that the value for the "umask" parameter is not "", or the "umask" parameter is missing or is commented out? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Create home directories to all local 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 |
+ To ensure the default umask for users of the C shell is set properly,
+add or correct the umask setting in /etc/csh.cshrc to read as follows:
+umask |
medium |
|
|
@@ -54863,76 +54610,38 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82744-4: Add nosuid Option to Removable Media Partitions |
+ CCE-83411-9: Disable graphical user interface |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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
+ | By removing the following packages, the system no longer has X Windows installed.
- any removable media partitions. |
+xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland
+
+If X Windows is not installed then the system cannot boot into graphical user mode.
+This prevents the system from being accidentally or maliciously booted into a graphical.target
+mode. To do so, run the following command:
+
+sudo yum remove xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify file systems that are used for removable media are mounted with the "nosuid" option with the following command:
+ | To ensure the X Windows package group is removed, run the following command:
-$ sudo more /etc/fstab
+$ rpm -qi xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland
-UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid,nodev,noexec 0 0 Is it the case that file system found in "/etc/fstab" refers to removable media and it does not have the "nosuid" option set? |
+For each package mentioned above you should receive following line:
+package <package> is not installed
Is it the case that xorg related packages are not removed and run level is not correctly configured?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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. |
- medium |
- |
- |
- |
-
-
-
- | CCI-000366 |
- SRG-OS-000480-GPOS-00227 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ By removing the following packages, the system no longer has X Windows installed.
- | CCE-83380-6: Disable X Windows Startup By Setting Default Target |
+xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland
- Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
+If X Windows is not installed then the system cannot boot into graphical user mode.
+This prevents the system from being accidentally or maliciously booted into a graphical.target
+mode. To do so, run the following command:
-Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Systems that do not require a graphical user interface should only boot by
-default into multi-user.target mode. This prevents accidental booting of the system
-into a graphical.target mode. Setting the system's default target to
-multi-user.target will prevent automatic startup of the X server. To do so, run:
-$ systemctl set-default multi-user.target
-You should see the following output:
-Removed symlink /etc/systemd/system/default.target.
-Created symlink from /etc/systemd/system/default.target to /usr/lib/systemd/system/multi-user.target. |
- Applicable - Configurable |
- Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to boot to the command line:
-$ systemctl get-default
-multi-user.target Is it the case that the system default target is not set to "multi-user.target" and the Information System Security Officer (ISSO) lacks a documented requirement for a graphical user interface? |
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Systems that do not require a graphical user interface should only boot by
-default into multi-user.target mode. This prevents accidental booting of the system
-into a graphical.target mode. Setting the system's default target to
-multi-user.target will prevent automatic startup of the X server. To do so, run:
-$ systemctl set-default multi-user.target
-You should see the following output:
-Removed symlink /etc/systemd/system/default.target.
-Created symlink from /etc/systemd/system/default.target to /usr/lib/systemd/system/multi-user.target. |
+sudo yum remove xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland
medium |
|
|
@@ -54945,23 +54654,27 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84053-8: Mount Remote Filesystems with nosuid |
+ CCE-81036-6: Ensure the Default Bash Umask is Set Correctly |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of
-any NFS mounts. |
+ To ensure the default umask for users of the Bash shell is set properly,
+add or correct the umask setting in /etc/bashrc to read
+as follows:
+umask |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify the nosuid option is configured for all NFS mounts, run
-the following command:
-$ mount | grep nfs
-All NFS mounts should show the nosuid setting in parentheses. This
-is not applicable if NFS is not implemented. Is it the case that the setting does not show? |
+ Verify the umask setting is configured correctly in the /etc/bashrc file with the following command:
+
+$ sudo grep "umask" /etc/bashrc
+
+umask Is it the case that the value for the "umask" parameter is not "", or the "umask" parameter is missing or is commented out? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of
-any NFS mounts. |
+ To ensure the default umask for users of the Bash shell is set properly,
+add or correct the umask setting in /etc/bashrc to read
+as follows:
+umask |
medium |
|
|
@@ -54974,57 +54687,29 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81009-3: Disable Accepting ICMP Redirects for All IPv6 Interfaces |
+ CCE-84044-7: Ensure the Default Umask is Set Correctly For Interactive Users |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ Remove the UMASK environment variable from all interactive users initialization files. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv6.conf.all.accept_redirects kernel parameter can be queried
-by running the following command:
-$ sysctl net.ipv6.conf.all.accept_redirects
-0.
- Is it the case that the correct value is not returned? |
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
- medium |
- |
- |
- |
-
+
Verify that the default umask for all local interactive users is "077".
- |
- | CCI-000366 |
- SRG-OS-000480-GPOS-00227 |
- TBD - Assigned by DISA after STIG release |
- The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+Identify the locations of all local interactive user home directories by looking at the "/etc/passwd" file.
- CCE-84056-1: Remove User Host-Based Authentication Files |
+Check all local interactive user initialization files for interactive users with the following command:
- Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
+Note: The example is for a system that is configured to create users home directories in the "/home" directory.
-Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
- Applicable - Configurable |
- Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify that there are no .shosts files
-on the system, run the following command:
-$ sudo find / -name '.shosts' Is it the case that .shosts files exist? |
+# grep -ri umask /home/
+
+/home/smithj/.bash_history:grep -i umask /etc/bashrc /etc/csh.cshrc /etc/profile
+/home/smithj/.bash_history:grep -i umask /etc/login.defs Is it the case that any local interactive user initialization files are found to have a umask statement that sets a value less restrictive than "077"?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
- high |
+ Remove the UMASK environment variable from all interactive users initialization files. |
+ medium |
|
|
|
@@ -55036,39 +54721,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-85953-8: Ensure There Are No Accounts With Blank or Null Passwords |
+ CCE-83375-6: Ensure All World-Writable Directories Are Owned by root User |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Check the "/etc/shadow" file for blank passwords with the
-following command:
-$ sudo awk -F: '!$2 {print $1}' /etc/shadow
-If the command returns any results, this is a finding.
-Configure all accounts on the system to have a password or lock
-the account with the following commands:
-Perform a password reset:
-$ sudo passwd [username]
-Lock an account:
-$ sudo passwd -l [username] |
+ All directories in local partitions which are world-writable should be owned by root.
+If any world-writable directories are not owned by root, this should be investigated.
+Following this, the files should be deleted or assigned to root user. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify that null passwords cannot be used, run the following command:
-$ sudo awk -F: '!$2 {print $1}' /etc/shadow
-If this produces any output, it may be possible to log into accounts
-with empty passwords. Is it the case that Blank or NULL passwords can be used? |
+ The following command will discover and print world-writable directories that
+are not owned by root. Run it once for each local partition PART:
+$ sudo find PART -xdev -type d -perm -0002 -uid +0 -print Is it the case that there are world-writable directories not owned by root? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Check the "/etc/shadow" file for blank passwords with the
-following command:
-$ sudo awk -F: '!$2 {print $1}' /etc/shadow
-If the command returns any results, this is a finding.
-Configure all accounts on the system to have a password or lock
-the account with the following commands:
-Perform a password reset:
-$ sudo passwd [username]
-Lock an account:
-$ sudo passwd -l [username] |
- high |
+ All directories in local partitions which are world-writable should be owned by root.
+If any world-writable directories are not owned by root, this should be investigated.
+Following this, the files should be deleted or assigned to root user. |
+ medium |
|
|
|
@@ -55080,38 +54750,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84220-3: Configure AIDE to Verify Access Control Lists (ACLs) |
+ CCE-84043-9: Ensure All User Initialization Files Have Mode 0740 Or Less Permissive |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ Set the mode of the user initialization files to 0740 with the
+following command:
+$ sudo chmod 0740 /home/USER/.INIT_FILE |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To determine that AIDE is verifying ACLs, run the following command:
-$ grep acl /etc/aide.conf
-Verify that the acl option is added to the correct ruleset. Is it the case that the acl option is missing or not added to the correct ruleset? |
+ To verify that all user initialization files have a mode of 0740 or
+less permissive, run the following command:
+$ sudo find /home -type f -name '\.*' \( -perm -0002 -o -perm -0020 \)
+There should be no output. Is it the case that they are not 0740 or more permissive? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
- low |
+ Set the mode of the user initialization files to 0740 with the
+following command:
+$ sudo chmod 0740 /home/USER/.INIT_FILE |
+ medium |
|
|
|
@@ -55123,41 +54780,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-85987-6: Only Authorized Local User Accounts Exist on Operating System |
+ CCE-80922-8: Enable Kernel Parameter to Ignore ICMP Broadcast Echo Requests on IPv4 Interfaces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Enterprise Application tends to use the server or virtual machine exclusively.
-Besides the default operating system user, there should be only authorized local
-users required by the installed software groups and applications that exist on
-the operating system. The authorized user list can be customized in the refine
-value variable var_accounts_authorized_local_users_regex.
-OVAL regular expression is used for the user list.
-Configure the system so all accounts on the system are assigned to an active system,
-application, or user account. Remove accounts that do not support approved system
-activities or that allow for a normal user to perform administrative-level actions.
-To remove unauthorized system accounts, use the following command:
-$ sudo userdel unauthorized_user |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify that there are no unauthorized local user accounts, run the following command:
-$ less /etc/passwd
-Inspect the results, and if unauthorized local user accounts exist, remove them by running
-the following command:
-$ sudo userdel unauthorized_user Is it the case that there are unauthorized local user accounts on the system? |
+ The runtime status of the net.ipv4.icmp_echo_ignore_broadcasts kernel parameter can be queried
+by running the following command:
+$ sysctl net.ipv4.icmp_echo_ignore_broadcasts
+1.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Enterprise Application tends to use the server or virtual machine exclusively.
-Besides the default operating system user, there should be only authorized local
-users required by the installed software groups and applications that exist on
-the operating system. The authorized user list can be customized in the refine
-value variable var_accounts_authorized_local_users_regex.
-OVAL regular expression is used for the user list.
-Configure the system so all accounts on the system are assigned to an active system,
-application, or user account. Remove accounts that do not support approved system
-activities or that allow for a normal user to perform administrative-level actions.
-To remove unauthorized system accounts, use the following command:
-$ sudo userdel unauthorized_user |
+ 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 |
medium |
|
|
@@ -55170,57 +54809,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80876-6: Disable debug-shell SystemD Service |
+ CCE-80878-2: Disable KDump Kernel Crash Analyzer (kdump) |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- SystemD's debug-shell service is intended to
-diagnose SystemD related boot issues with various systemctl
-commands. Once enabled and following a system reboot, the root shell
-will be available on tty9 which is access by pressing
-CTRL-ALT-F9. The debug-shell service should only be used
-for SystemD related issues and should otherwise be disabled.
-
-By default, the debug-shell SystemD service is already disabled.
+ | 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 debug-shell service can be disabled with the following command:
-$ sudo systemctl mask --now debug-shell.service |
+The kdump service can be disabled with the following command:
+$ sudo systemctl mask --now kdump.service
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To check that the debug-shell service is disabled in system boot configuration,
+ | To check that the kdump service is disabled in system boot configuration,
run the following command:
-$ sudo systemctl is-enabled debug-shell
-Output should indicate the debug-shell service has either not been installed,
+$ sudo systemctl is-enabled kdump
+Output should indicate the kdump service has either not been installed,
or has been disabled at all runlevels, as shown in the example below:
-$ sudo systemctl is-enabled debug-shell
disabled
+$ sudo systemctl is-enabled kdump
disabled
-Run the following command to verify debug-shell is not active (i.e. not running) through current runtime configuration:
-$ sudo systemctl is-active debug-shell
+Run the following command to verify kdump is not active (i.e. not running) through current runtime configuration:
+$ sudo systemctl is-active kdump
If the service is not running the command will return the following output:
inactive
-The service will also be masked, to check that the debug-shell is masked, run the following command:
-$ sudo systemctl show debug-shell | grep "LoadState\|UnitFileState"
+The service will also be masked, to check that the kdump is masked, run the following command:
+$ sudo systemctl show kdump | grep "LoadState\|UnitFileState"
If the service is masked the command will return the following outputs:
LoadState=masked
-UnitFileState=masked Is it the case that the "debug-shell" is loaded and not masked? |
+UnitFileState=masked
Is it the case that the "kdump" is loaded and not masked?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- SystemD's debug-shell service is intended to
-diagnose SystemD related boot issues with various systemctl
-commands. Once enabled and following a system reboot, the root shell
-will be available on tty9 which is access by pressing
-CTRL-ALT-F9. The debug-shell service should only be used
-for SystemD related issues and should otherwise be disabled.
-
-By default, the debug-shell SystemD service is already disabled.
+ | 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 debug-shell service can be disabled with the following command:
-$ sudo systemctl mask --now debug-shell.service |
+The kdump service can be disabled with the following command:
+$ sudo systemctl mask --now kdump.service
medium |
|
|
@@ -55233,33 +54862,29 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84036-3: All Interactive Users Must Have A Home Directory Defined |
+ CCE-82251-0: Disable core dump backtraces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Assign home directories to all interactive users that currently do not
-have a home directory assigned.
-
-This rule checks if the home directory is properly defined in a folder which has
-at least one parent folder, like "user" in "/home/user" or "/remote/users/user".
-Therefore, this rule will report a finding for home directories like /users,
-/tmp or /. |
+ The ProcessSizeMax option in [Coredump] section
+of /etc/systemd/coredump.conf
+specifies the maximum size in bytes of a core which will be processed.
+Core dumps exceeding this size may be stored, but the backtrace will not
+be generated. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that interactive users on the system have a home directory assigned with the following command:
+ | Verify Red Hat Enterprise Linux 8 disables core dump backtraces by issuing the following command:
-$ sudo awk -F: '($3>=1000)&&($7 !~ /nologin/){print $1, $3, $6}' /etc/passwd
+$ grep -i process /etc/systemd/coredump.conf
-Inspect the output and verify that all interactive users (normally users with a UID greater than 1000) have a home directory defined. Is it the case that users home directory is not defined? |
+ProcessSizeMax=0 Is it the case that the "ProcessSizeMax" item is missing, commented out, or the value is anything other than "0" and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core" item assigned?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Assign home directories to all interactive users that currently do not
-have a home directory assigned.
-
-This rule checks if the home directory is properly defined in a folder which has
-at least one parent folder, like "user" in "/home/user" or "/remote/users/user".
-Therefore, this rule will report a finding for home directories like /users,
-/tmp or /. |
+ The ProcessSizeMax option in [Coredump] section
+of /etc/systemd/coredump.conf
+specifies the maximum size in bytes of a core which will be processed.
+Core dumps exceeding this size may be stored, but the backtrace will not
+be generated. |
medium |
|
|
@@ -55272,21 +54897,37 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82998-6: Install firewalld Package |
+ CCE-82744-4: Add nosuid Option to Removable Media Partitions |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The firewalld package can be installed with the following command:
-
-$ sudo yum install firewalld |
+ 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. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Run the following command to determine if the firewalld package is installed: $ rpm -q firewalld Is it the case that the package is not installed? |
+ Verify file systems that are used for removable media are mounted with the "nosuid" option with the following command:
+
+$ sudo more /etc/fstab
+
+UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid,nodev,noexec 0 0 Is it the case that file system found in "/etc/fstab" refers to removable media and it does not have the "nosuid" option set? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The firewalld package can be installed with the following command:
-
-$ sudo yum install firewalld |
+ 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. |
medium |
|
|
@@ -55299,40 +54940,29 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82434-2: Ensure tftp Daemon Uses Secure Mode |
+ CCE-80947-5: The Installed Operating System Is Vendor Supported |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- If running the Trivial File Transfer Protocol (TFTP) service is necessary,
-it should be configured to change its root directory at startup. To do so,
-ensure /etc/xinetd.d/tftp includes -s as a command line argument,
-as shown in the following example:
-server_args = -s |
+ The installed operating system must be maintained by a vendor.
+
+Red Hat Enterprise Linux is supported by Red Hat, Inc. As the Red Hat Enterprise
+Linux vendor, Red Hat, Inc. is responsible for providing security patches. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify the TFTP daemon is configured to operate in secure mode.
-
-Check if a TFTP server is installed with the following command:
-
-$ rpm -qa | grep tftp
-
-
-If a TFTP server is not installed, this is Not Applicable.
-
+ | To verify that the installed operating system is supported, run
+the following command:
-If a TFTP server is installed, verify TFTP is configured by with
-the -s option by running the following command:
+$ grep -i "red hat" /etc/redhat-release
-grep "server_args" /etc/xinetd.d/tftp
-server_args = -s Is it the case that '"server_args" line does not have a "-s" option, and a subdirectory is not assigned'? |
+Red Hat Enterprise Linux 8
Is it the case that the installed operating system is not supported?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- If running the Trivial File Transfer Protocol (TFTP) service is necessary,
-it should be configured to change its root directory at startup. To do so,
-ensure /etc/xinetd.d/tftp includes -s as a command line argument,
-as shown in the following example:
-server_args = -s |
- medium |
+ The installed operating system must be maintained by a vendor.
+
+Red Hat Enterprise Linux is supported by Red Hat, Inc. As the Red Hat Enterprise
+Linux vendor, Red Hat, Inc. is responsible for providing security patches. |
+ high |
|
|
|
@@ -55371,29 +55001,82 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80947-5: The Installed Operating System Is Vendor Supported |
+ CCE-83422-6: Ensure invoking users password for privilege escalation when using sudo |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The installed operating system must be maintained by a vendor.
-
-Red Hat Enterprise Linux is supported by Red Hat, Inc. As the Red Hat Enterprise
-Linux vendor, Red Hat, Inc. is responsible for providing security patches. |
+ 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 cvtsudoers -f sudoers /etc/sudoers | grep -E '^Defaults !?(rootpw|targetpw|runaspw)$'
+ Defaults !targetpw
+ Defaults !rootpw
+ Defaults !runaspw
+or if cvtsudoers not supported:
+ sudo find /etc/sudoers /etc/sudoers.d \( \! -name '*~' -a \! -name '*.*' \) -exec grep -E --with-filename '^[[:blank:]]*Defaults[[:blank:]](.*[[:blank:]])?!?\b(rootpw|targetpw|runaspw)' -- {} \;
+ /etc/sudoers:Defaults !targetpw
+ /etc/sudoers:Defaults !rootpw
+ /etc/sudoers:Defaults !runaspw |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify that the installed operating system is supported, run
-the following command:
+ | Run the following command to Verify that the sudoers security policy is configured to use the invoking user's password for privilege escalation:
+ sudo cvtsudoers -f sudoers /etc/sudoers | grep -E '^Defaults !?(rootpw|targetpw|runaspw)'
+or if cvtsudoers not supported:
+ sudo find /etc/sudoers /etc/sudoers.d \( \! -name '*~' -a \! -name '*.*' \) -exec grep -E --with-filename '^[[:blank:]]*Defaults[[:blank:]](.*[[:blank:]])?!?\b(rootpw|targetpw|runaspw)' -- {} \;
+If no results are returned, this is a finding.
+If conflicting results are returned, this is a finding.
+If "Defaults !targetpw" is not defined, this is a finding.
+If "Defaults !rootpw" is not defined, this is a finding.
+If "Defaults !runaspw" is not defined, this is a finding. Is it the case that invoke user passwd when using sudo? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ 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 cvtsudoers -f sudoers /etc/sudoers | grep -E '^Defaults !?(rootpw|targetpw|runaspw)$'
+ Defaults !targetpw
+ Defaults !rootpw
+ Defaults !runaspw
+or if cvtsudoers not supported:
+ sudo find /etc/sudoers /etc/sudoers.d \( \! -name '*~' -a \! -name '*.*' \) -exec grep -E --with-filename '^[[:blank:]]*Defaults[[:blank:]](.*[[:blank:]])?!?\b(rootpw|targetpw|runaspw)' -- {} \;
+ /etc/sudoers:Defaults !targetpw
+ /etc/sudoers:Defaults !rootpw
+ /etc/sudoers:Defaults !runaspw |
+ medium |
+ |
+ |
+ |
+
-
$ grep -i "red hat" /etc/redhat-release
+
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00227 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-Red Hat Enterprise Linux 8
Is it the case that the installed operating system is not supported?
+ CCE-82831-9: Enable the Hardware RNG Entropy Gatherer Service |
+
+ Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
+
+Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
+ The Hardware RNG Entropy Gatherer service should be enabled.
+
+The rngd service can be enabled with the following command:
+$ sudo systemctl enable rngd.service |
+ Applicable - Configurable |
+ Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
+
+
+Run the following command to determine the current status of the
+rngd service:
+$ sudo systemctl is-active rngd
+If the service is running, it should return the following: active Is it the case that the "rngd" service is disabled, masked, or not started.? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The installed operating system must be maintained by a vendor.
+ | The Hardware RNG Entropy Gatherer service should be enabled.
-Red Hat Enterprise Linux is supported by Red Hat, Inc. As the Red Hat Enterprise
-Linux vendor, Red Hat, Inc. is responsible for providing security patches. |
- high |
+The rngd service can be enabled with the following command:
+$ sudo systemctl enable rngd.service
+ low |
|
|
|
@@ -55405,26 +55088,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-85877-9: Ensure PAM password complexity module is enabled in password-auth |
+ CCE-84052-0: Mount Remote Filesystems with nodev |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To enable PAM password complexity in password-auth file:
-Edit the password section in
-/etc/pam.d/password-auth to show
-password requisite pam_pwquality.so. |
+ Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of
+any NFS mounts. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To check if pam_pwquality.so is enabled in password-auth, run the following command:
-$ grep pam_pwquality /etc/pam.d/password-auth
-The output should be similar to the following:
-password requisite pam_pwquality.so Is it the case that pam_pwquality.so is not enabled in password-auth? |
+ To verify the nodev option is configured for all NFS mounts, run
+the following command:
+$ mount | grep nfs
+All NFS mounts should show the nodev setting in parentheses. This
+is not applicable if NFS is not implemented. Is it the case that the setting does not show? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To enable PAM password complexity in password-auth file:
-Edit the password section in
-/etc/pam.d/password-auth to show
-password requisite pam_pwquality.so. |
+ Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of
+any NFS mounts. |
medium |
|
|
@@ -55437,23 +55117,59 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81013-5: Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv6 Interfaces |
+ CCE-85886-0: Ensure All World-Writable Directories Are Group Owned by a System Account |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ 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. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv6.conf.all.accept_source_route kernel parameter can be queried
+ | The following command will discover and print world-writable directories that
+are not group owned by a system account, given the assumption that only system
+accounts have a gid lower than 1000. Run it once for each local partition PART:
+$ sudo find PART -xdev -type d -perm -0002 -gid +999 -print Is it the case that there is output? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ 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. |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00227 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+
+ CCE-80920-2: Disable Kernel Parameter for Accepting Source-Routed Packets on IPv4 Interfaces by Default |
+
+ Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
+
+Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
+ The runtime status of the net.ipv4.conf.default.accept_source_route kernel parameter can be queried
by running the following command:
-$ sysctl net.ipv6.conf.all.accept_source_route
+$ sysctl net.ipv4.conf.default.accept_source_route
0.
Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
+ 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 |
medium |
|
|
@@ -55466,40 +55182,44 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-83499-4: Ensure All Files Are Owned by a User |
+ CCE-80897-2: Disable GSSAPI Authentication |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 -nouser |
+ Unless needed, SSH should not permit extraneous or unnecessary
+authentication mechanisms like GSSAPI.
+
+The default SSH configuration disallows authentications based on GSSAPI. The appropriate
+configuration is used if no value is set for GSSAPIAuthentication.
+
+To explicitly disable GSSAPI authentication, add or correct the following line in
+
+
+/etc/ssh/sshd_config:
+
+GSSAPIAuthentication no |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- 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
-
-Either remove all files and directories from the system that do not have a
-valid user, or assign a valid user to all unowned files and directories on
-the system with the chown command:
-$ sudo chown user file Is it the case that files exist that are not owned by a valid user? |
+ To determine how the SSH daemon's GSSAPIAuthentication option is set, run the following command:
+
+$ sudo grep -i GSSAPIAuthentication /etc/ssh/sshd_config
+
+If a line indicating no is returned, then the required value is set.
+ Is it the case that the required value is not set? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 -nouser |
+ Unless needed, SSH should not permit extraneous or unnecessary
+authentication mechanisms like GSSAPI.
+
+The default SSH configuration disallows authentications based on GSSAPI. The appropriate
+configuration is used if no value is set for GSSAPIAuthentication.
+
+To explicitly disable GSSAPI authentication, add or correct the following line in
+
+
+/etc/ssh/sshd_config:
+
+GSSAPIAuthentication no |
medium |
|
|
@@ -55512,29 +55232,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81044-0: Ensure /home Located On Separate Partition |
+ CCE-84053-8: Mount Remote Filesystems with nosuid |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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. |
+ Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of
+any NFS mounts. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that a separate file system/partition has been created for /home with the following command:
-
-$ mountpoint /home
- Is it the case that "/home is not a mountpoint" is returned? |
+ To verify the nosuid option is configured for all NFS mounts, run
+the following command:
+$ mount | grep nfs
+All NFS mounts should show the nosuid setting in parentheses. This
+is not applicable if NFS is not implemented. Is it the case that the setting does not show? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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. |
- low |
+ Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of
+any NFS mounts. |
+ medium |
|
|
|
@@ -55546,23 +55261,28 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80916-0: Enable Randomized Layout of Virtual Address Space |
+ CCE-80859-2: Ensure cron Is Logging To Rsyslog |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ Cron logging must be implemented to spot intrusions or trace
+cron job status. If cron is not logging to rsyslog, it
+can be implemented by adding the following to the RULES section of
+/etc/rsyslog.conf:
+cron.* /var/log/cron |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the kernel.randomize_va_space kernel parameter can be queried
-by running the following command:
-$ sysctl kernel.randomize_va_space
-2.
- Is it the case that the correct value is not returned? |
+ Verify that cron is logging to rsyslog,
+run the following command:
+grep -rni "cron\.\*" /etc/rsyslog.*
+cron.* /var/log/cron Is it the case that cron is not logging to rsyslog? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
+ Cron logging must be implemented to spot intrusions or trace
+cron job status. If cron is not logging to rsyslog, it
+can be implemented by adding the following to the RULES section of
+/etc/rsyslog.conf:
+cron.* /var/log/cron |
medium |
|
|
@@ -55575,23 +55295,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84055-3: Remove Host-Based Authentication Files |
+ CCE-81009-3: Disable Accepting ICMP Redirects for All IPv6 Interfaces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The shosts.equiv file lists 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 |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that there are no shosts.equiv files on the system, run the following command:
-$ find / -name shosts.equiv Is it the case that shosts.equiv files exist? |
+ The runtime status of the net.ipv6.conf.all.accept_redirects kernel parameter can be queried
+by running the following command:
+$ sysctl net.ipv6.conf.all.accept_redirects
+0.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The shosts.equiv file lists 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 |
- high |
+ 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 |
+ medium |
|
|
|
@@ -55603,29 +55324,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82831-9: Enable the Hardware RNG Entropy Gatherer Service |
+ CCE-81011-9: Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv4 Interfaces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The Hardware RNG Entropy Gatherer service should be enabled.
-
-The rngd service can be enabled with the following command:
-$ sudo systemctl enable rngd.service |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-rngd service:
-$ sudo systemctl is-active rngd
-If the service is running, it should return the following: active Is it the case that the "rngd" service is disabled, masked, or not started.? |
+ The runtime status of the net.ipv4.conf.all.accept_source_route kernel parameter can be queried
+by running the following command:
+$ sysctl net.ipv4.conf.all.accept_source_route
+0.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The Hardware RNG Entropy Gatherer service should be enabled.
-
-The rngd service can be enabled with the following command:
-$ sudo systemctl enable rngd.service |
- low |
+ 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 |
+ medium |
|
|
|
@@ -55637,25 +55353,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81038-2: Disable Core Dumps for All Users |
+ CCE-82934-1: Harden the operation of the BPF just-in-time compiler |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To disable core dumps for all users, add the following line to
-/etc/security/limits.conf, or to a file within the
-/etc/security/limits.d/ directory:
-* hard core 0 |
+ To set the runtime status of the net.core.bpf_jit_harden kernel parameter, run the following command: $ sudo sysctl -w net.core.bpf_jit_harden=2
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.core.bpf_jit_harden = 2 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that core dumps are disabled for all users, run the following command:
-$ grep core /etc/security/limits.conf
-* hard core 0 Is it the case that the "core" item is missing, commented out, or the value is anything other than "0" and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core"? |
+ The runtime status of the net.core.bpf_jit_harden kernel parameter can be queried
+by running the following command:
+$ sysctl net.core.bpf_jit_harden
+2.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To disable core dumps for all users, add the following line to
-/etc/security/limits.conf, or to a file within the
-/etc/security/limits.d/ directory:
-* hard core 0 |
+ To set the runtime status of the net.core.bpf_jit_harden kernel parameter, run the following command: $ sudo sysctl -w net.core.bpf_jit_harden=2
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.core.bpf_jit_harden = 2 |
medium |
|
|
@@ -55668,22 +55382,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82976-2: Install policycoreutils Package |
+ CCE-86220-1: Disable Kernel Parameter for IPv4 Forwarding on all IPv4 Interfaces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The policycoreutils package can be installed with the following command:
-
-$ sudo yum install policycoreutils |
+ To set the runtime status of the net.ipv4.conf.all.forwarding kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.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.ipv4.conf.all.forwarding = 0 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Run the following command to determine if the policycoreutils package is installed: $ rpm -q policycoreutils Is it the case that the policycoreutils package is not installed? |
+ The runtime status of the net.ipv4.conf.all.forwarding kernel parameter can be queried
+by running the following command:
+$ sysctl net.ipv4.conf.all.forwarding
+0.
+The ability to forward packets is only appropriate for routers. Is it the case that IP forwarding value is "1" and the system is not router? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The policycoreutils package can be installed with the following command:
-
-$ sudo yum install policycoreutils |
- low |
+ To set the runtime status of the net.ipv4.conf.all.forwarding kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.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.ipv4.conf.all.forwarding = 0 |
+ medium |
|
|
|
@@ -55695,49 +55411,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80896-4: Disable SSH Access via Empty Passwords |
+ CCE-81006-9: Configure Accepting Router Advertisements on All IPv6 Interfaces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Disallow SSH login with empty passwords.
-The default SSH configuration disables logins with empty passwords. The appropriate
-configuration is used if no value is set for PermitEmptyPasswords.
-
-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. |
+ To set the runtime status of the net.ipv6.conf.all.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_ra=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_ra = 0 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To determine how the SSH daemon's PermitEmptyPasswords option is set, run the following command:
-
-$ sudo grep -i PermitEmptyPasswords /etc/ssh/sshd_config
-
-If a line indicating no is returned, then the required value is set.
- Is it the case that the required value is not set? |
+ The runtime status of the net.ipv6.conf.all.accept_ra kernel parameter can be queried
+by running the following command:
+$ sysctl net.ipv6.conf.all.accept_ra
+0.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Disallow SSH login with empty passwords.
-The default SSH configuration disables logins with empty passwords. The appropriate
-configuration is used if no value is set for PermitEmptyPasswords.
-
-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. |
- high |
+ To set the runtime status of the net.ipv6.conf.all.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_ra=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_ra = 0 |
+ medium |
|
|
|
@@ -55749,23 +55440,31 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81015-0: Disable Kernel Parameter for Accepting Source-Routed Packets on IPv6 Interfaces by Default |
+ CCE-86038-7: Add nosuid Option to /boot/efi |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ The nosuid mount option can be used to prevent
+execution of setuid programs in /boot/efi. The SUID and SGID permissions
+should not be required on the boot partition.
+Add the nosuid option to the fourth column of
+/etc/fstab for the line which controls mounting of
+/boot/efi. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv6.conf.default.accept_source_route kernel parameter can be queried
-by running the following command:
-$ sysctl net.ipv6.conf.default.accept_source_route
-0.
- Is it the case that the correct value is not returned? |
+ Verify the nosuid option is configured for the /boot/efi mount point,
+ run the following command:
+ $ sudo mount | grep '\s/boot/efi\s'
+ . . . /boot/efi . . . nosuid . . .
+ Is it the case that the "/boot/efi" file system does not have the "nosuid" option set? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
+ The nosuid mount option can be used to prevent
+execution of setuid programs in /boot/efi. The SUID and SGID permissions
+should not be required on the boot partition.
+Add the nosuid option to the fourth column of
+/etc/fstab for the line which controls mounting of
+/boot/efi. |
medium |
|
|
@@ -55778,22 +55477,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82946-5: Uninstall iprutils Package |
+ CCE-80915-2: Restrict Exposed Kernel Pointer Addresses Access |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The iprutils package can be removed with the following command:
-
-$ sudo yum erase iprutils |
+ To set the runtime status of the kernel.kptr_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.kptr_restrict=
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kptr_restrict = |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Run the following command to determine if the iprutils package is installed:
-$ rpm -q iprutils Is it the case that the package is installed? |
+ The runtime status of the kernel.kptr_restrict kernel parameter can be queried
+by running the following command:
+$ sysctl kernel.kptr_restrict
+The output of the command should indicate either:
+kernel.kptr_restrict = 1
+or:
+kernel.kptr_restrict = 2
+The output of the command should not indicate:
+kernel.kptr_restrict = 0
+
+The preferable way how to assure the runtime compliance is to have
+correct persistent configuration, and rebooting the system.
+
+The persistent kernel parameter configuration is performed by specifying the appropriate
+assignment in any file located in the /etc/sysctl.d directory.
+Verify that there is not any existing incorrect configuration by executing the following command:
+$ grep -r '^\s*kernel.kptr_restrict\s*=' /etc/sysctl.conf /etc/sysctl.d
+The command should not find any assignments other than:
+kernel.kptr_restrict = 1
+or:
+kernel.kptr_restrict = 2
+
+Conflicting assignments are not allowed. Is it the case that the kernel.kptr_restrict is not set to 1 or 2 or is configured to be 0? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The iprutils package can be removed with the following command:
-
-$ sudo yum erase iprutils |
+ To set the runtime status of the kernel.kptr_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.kptr_restrict=
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kptr_restrict = |
medium |
|
|
@@ -55806,26 +55524,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82859-0: Ensure rsyslog-gnutls is installed |
+ CCE-80916-0: Enable Randomized Layout of Virtual Address Space |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- TLS protocol support for rsyslog is installed.
-
-The rsyslog-gnutls package can be installed with the following command:
-
-$ sudo yum install rsyslog-gnutls |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Run the following command to determine if the rsyslog-gnutls package is installed:
-$ rpm -q rsyslog-gnutls Is it the case that the package is installed? |
+ The runtime status of the kernel.randomize_va_space kernel parameter can be queried
+by running the following command:
+$ sysctl kernel.randomize_va_space
+2.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- TLS protocol support for rsyslog is installed.
-
-The rsyslog-gnutls package can be installed with the following command:
-
-$ sudo yum install rsyslog-gnutls |
+ 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 |
medium |
|
|
@@ -55838,23 +55553,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84054-6: Prevent Unrestricted Mail Relaying |
+ CCE-81013-5: Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv6 Interfaces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Modify the /etc/postfix/main.cf file to restrict client connections
-to the local network with the following command:
-$ sudo postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject' |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 is configured to prevent unrestricted mail relaying,
-run the following command:
-$ sudo postconf -n smtpd_client_restrictions Is it the case that the "smtpd_client_restrictions" parameter contains any entries other than "permit_mynetworks" and "reject"? |
+ The runtime status of the net.ipv6.conf.all.accept_source_route kernel parameter can be queried
+by running the following command:
+$ sysctl net.ipv6.conf.all.accept_source_route
+0.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Modify the /etc/postfix/main.cf file to restrict client connections
-to the local network with the following command:
-$ sudo postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject' |
+ 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 |
medium |
|
|
@@ -55867,57 +55582,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80873-3: Disable the Automounter |
+ CCE-81015-0: Disable Kernel Parameter for Accepting Source-Routed Packets on IPv6 Interfaces by Default |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To check that the autofs service is disabled in system boot configuration,
-run the following command:
-$ sudo systemctl is-enabled autofs
-Output should indicate the autofs service has either not been installed,
-or has been disabled at all runlevels, as shown in the example below:
-$ sudo systemctl is-enabled autofs
disabled
-
-Run the following command to verify autofs is not active (i.e. not running) through current runtime configuration:
-$ sudo systemctl is-active autofs
-
-If the service is not running the command will return the following output:
-inactive
-
-The service will also be masked, to check that the autofs is masked, run the following command:
-$ sudo systemctl show autofs | grep "LoadState\|UnitFileState"
-
-If the service is masked the command will return the following outputs:
-
-LoadState=masked
-
-UnitFileState=masked Is it the case that the "autofs" is loaded and not masked? |
+ The runtime status of the net.ipv6.conf.default.accept_source_route kernel parameter can be queried
+by running the following command:
+$ sysctl net.ipv6.conf.default.accept_source_route
+0.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
+ 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 |
medium |
|
|
@@ -55930,23 +55611,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80918-6: Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces |
+ CCE-80919-4: Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv4 Interfaces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv4.conf.all.send_redirects kernel parameter can be queried
+ | The runtime status of the net.ipv4.conf.default.accept_redirects kernel parameter can be queried
by running the following command:
-$ sysctl net.ipv4.conf.all.send_redirects
+$ sysctl net.ipv4.conf.default.accept_redirects
0.
Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
+ 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 |
medium |
|
|
@@ -55959,31 +55640,33 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-86038-7: Add nosuid Option to /boot/efi |
+ CCE-80664-6: Ensure PAM Enforces Password Requirements - Authentication Retry Prompts Permitted Per-Session |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The nosuid mount option can be used to prevent
-execution of setuid programs in /boot/efi. The SUID and SGID permissions
-should not be required on the boot partition.
-Add the nosuid option to the fourth column of
-/etc/fstab for the line which controls mounting of
-/boot/efi. |
+ To configure the number of retry prompts that are permitted per-session:
+
+Edit the /etc/security/pwquality.conf to include
+
+retry=, or a lower value if site
+policy is more restrictive. The DoD requirement is a maximum of 3 prompts
+per session. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify the nosuid option is configured for the /boot/efi mount point,
- run the following command:
- $ sudo mount | grep '\s/boot/efi\s'
- . . . /boot/efi . . . nosuid . . .
- Is it the case that the "/boot/efi" file system does not have the "nosuid" option set? |
+ Verify Red Hat Enterprise Linux 8 is configured to limit the "pwquality" retry option to .
+
+
+Check for the use of the "pwquality" retry option in the pwquality.conf file with the following command:
+$ grep retry /etc/security/pwquality.conf Is it the case that the value of "retry" is set to "0" or greater than "", or is missing? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The nosuid mount option can be used to prevent
-execution of setuid programs in /boot/efi. The SUID and SGID permissions
-should not be required on the boot partition.
-Add the nosuid option to the fourth column of
-/etc/fstab for the line which controls mounting of
-/boot/efi. |
+ To configure the number of retry prompts that are permitted per-session:
+
+Edit the /etc/security/pwquality.conf to include
+
+retry=, or a lower value if site
+policy is more restrictive. The DoD requirement is a maximum of 3 prompts
+per session. |
medium |
|
|
@@ -55996,35 +55679,27 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80649-7: Verify Only Root Has UID 0 |
+ CCE-82859-0: Ensure rsyslog-gnutls is installed |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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. |
+ TLS protocol support for rsyslog is installed.
+
+The rsyslog-gnutls package can be installed with the following command:
+
+$ sudo yum install rsyslog-gnutls |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that only the "root" account has a UID "0" assignment with the
-following command:
-$ awk -F: '$3 == 0 {print $1}' /etc/passwd
-root Is it the case that any accounts other than "root" have a UID of "0"? |
+ Run the following command to determine if the rsyslog-gnutls package is installed:
+$ rpm -q rsyslog-gnutls Is it the case that the package is installed? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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. |
- high |
+ TLS protocol support for rsyslog is installed.
+
+The rsyslog-gnutls package can be installed with the following command:
+
+$ sudo yum install rsyslog-gnutls |
+ medium |
|
|
|
@@ -56036,56 +55711,26 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80865-9: Ensure Software Patches Installed |
+ CCE-80877-4: Verify firewalld Enabled |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
-If the system is joined to the Red Hat Network, a Red Hat Satellite Server,
-or a yum server, run the following command to install updates:
-$ sudo yum update
-If the system is not configured to use one of these sources, updates (in the form of RPM packages)
-can be manually downloaded from the Red Hat Network and installed using rpm.
-
-
-NOTE: U.S. Defense systems are required to be patched within 30 days or sooner as local policy
-dictates. |
+The firewalld service can be enabled with the following command:
+$ sudo systemctl enable firewalld.service
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 security patches and updates are installed and up to date.
-Updates are required to be applied with a frequency determined by organizational policy.
-
-
-Obtain the list of available package security updates from Red Hat. The URL for updates is https://access.redhat.com/errata-search/.
-It is important to note that updates provided by Red Hat may not be present on the system if the underlying packages are not installed.
-
-
-Check that the available package security updates have been installed on the system with the following command:
-
-$ sudo yum history list | more
-
-Loaded plugins: langpacks, product-id, subscription-manager
-ID | Command line | Date and time | Action(s) | Altered
--------------------------------------------------------------------------------
-70 | install aide | 2020-03-05 10:58 | Install | 1
-69 | update -y | 2020-03-04 14:34 | Update | 18 EE
-68 | install vlc | 2020-02-21 17:12 | Install | 21
-67 | update -y | 2020-02-21 17:04 | Update | 7 EE
-
+ |
-Typical update frequency may be overridden by Information Assurance Vulnerability Alert (IAVA) notifications from CYBERCOM. Is it the case that Red Hat Enterprise Linux 8 is in non-compliance with the organizational patching policy? |
+Run the following command to determine the current status of the
+firewalld service:
+$ sudo systemctl is-active firewalld
+If the service is running, it should return the following: active
Is it the case that the "firewalld" service is disabled, masked, or not started.?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-If the system is joined to the Red Hat Network, a Red Hat Satellite Server,
-or a yum server, run the following command to install updates:
-$ sudo yum update
-If the system is not configured to use one of these sources, updates (in the form of RPM packages)
-can be manually downloaded from the Red Hat Network and installed using rpm.
-
-
-NOTE: U.S. Defense systems are required to be patched within 30 days or sooner as local policy
-dictates. |
+The firewalld service can be enabled with the following command:
+$ sudo systemctl enable firewalld.service
medium |
|
|
@@ -56098,28 +55743,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80886-5: Enable rsyslog Service |
+ CCE-83497-8: Ensure All Files Are Owned by a Group |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The rsyslog service provides syslog-style logging by default on Red Hat Enterprise Linux 8.
-
-The rsyslog service can be enabled with the following command:
-$ sudo systemctl enable rsyslog.service |
+ 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 -nogroup |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-rsyslog service:
-$ sudo systemctl is-active rsyslog
-If the service is running, it should return the following: active Is it the case that the "rsyslog" service is disabled, masked, or not started.? |
+ 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
+
+Either remove all files and directories from the system that do not have a valid group,
+or assign a valid group with the chgrp command:
+$ sudo chgrp group file Is it the case that there is output? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The rsyslog service provides syslog-style logging by default on Red Hat Enterprise Linux 8.
-
-The rsyslog service can be enabled with the following command:
-$ sudo systemctl enable rsyslog.service |
+ 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 -nogroup |
medium |
|
|
@@ -56132,25 +55788,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80852-7: Ensure /var Located On Separate Partition |
+ CCE-83499-4: Ensure All Files Are Owned by a User |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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. |
+ 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 -nouser |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that a separate file system/partition has been created for /var with the following command:
-
-$ mountpoint /var
- Is it the case that "/var is not a mountpoint" is returned? |
+ 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
+
+Either remove all files and directories from the system that do not have a
+valid user, or assign a valid user to all unowned files and directories on
+the system with the chown command:
+$ sudo chown user file Is it the case that files exist that are not owned by a valid user? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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. |
- low |
+ 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 -nouser |
+ medium |
|
|
|
@@ -56162,23 +55834,31 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81011-9: Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv4 Interfaces |
+ CCE-81033-3: Add nosuid Option to /boot |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ The nosuid mount option can be used to prevent
+execution of setuid programs in /boot. The SUID and SGID permissions
+should not be required on the boot partition.
+Add the nosuid option to the fourth column of
+/etc/fstab for the line which controls mounting of
+/boot. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv4.conf.all.accept_source_route kernel parameter can be queried
-by running the following command:
-$ sysctl net.ipv4.conf.all.accept_source_route
-0.
- Is it the case that the correct value is not returned? |
+ Verify the nosuid option is configured for the /boot mount point,
+ run the following command:
+ $ sudo mount | grep '\s/boot\s'
+ . . . /boot . . . nosuid . . .
+ Is it the case that the "/boot" file system does not have the "nosuid" option set? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
+ The nosuid mount option can be used to prevent
+execution of setuid programs in /boot. The SUID and SGID permissions
+should not be required on the boot partition.
+Add the nosuid option to the fourth column of
+/etc/fstab for the line which controls mounting of
+/boot. |
medium |
|
|
@@ -56191,47 +55871,30 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80834-5: Disable SCTP Support |
+ CCE-83789-8: Ensure Home Directories are Created for New Users |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The Stream Control Transmission Protocol (SCTP) is a
-transport layer protocol, designed to support the idea of
-message-oriented communication, with several streams of messages
-within one connection.
-
-To configure the system to prevent the sctp
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/sctp.conf:
-install sctp /bin/true
-
-To configure the system to prevent the sctp from being used,
-add the following line to file /etc/modprobe.d/sctp.conf:
-blacklist sctp |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
-
-If the system is configured to prevent the loading of the sctp kernel module,
-it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
-These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
-
-These lines can also instruct the module loading system to ignore the sctp kernel module via blacklist keyword.
-
-Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
-$ grep -r sctp /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
+ Verify all local interactive users on Red Hat Enterprise Linux 8 are assigned a home
+directory upon creation with the following command:
+$ grep -i create_home /etc/login.defs
+CREATE_HOME yes Is it the case that the value for "CREATE_HOME" parameter is not set to "yes", the line is missing, or the line is commented out? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The Stream Control Transmission Protocol (SCTP) is a
-transport layer protocol, designed to support the idea of
-message-oriented communication, with several streams of messages
-within one connection.
-
-To configure the system to prevent the sctp
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/sctp.conf:
-install sctp /bin/true
-
-To configure the system to prevent the sctp from being used,
-add the following line to file /etc/modprobe.d/sctp.conf:
-blacklist sctp |
+ 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 |
medium |
|
|
@@ -56244,42 +55907,26 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82281-7: Enable SSH Print Last Log |
+ CCE-84038-9: All Interactive User Home Directories Must Have mode 0750 Or Less Permissive |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Ensure that SSH will display the date and time of the last successful account logon.
-
-The default SSH configuration enables print of the date and time of the last login.
-The appropriate configuration is used if no value is set for PrintLastLog.
-
-To explicitly enable LastLog in SSH, add or correct the following line in
-
-
-/etc/ssh/sshd_config:
-
-PrintLastLog yes |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To determine how the SSH daemon's PrintLastLog option is set, run the following command:
-
-$ sudo grep -i PrintLastLog /etc/ssh/sshd_config
-
-If a line indicating yes is returned, then the required value is set.
- Is it the case that the required value is not set? |
+ To verify the assigned home directory of all interactive user home directories
+have a mode of 0750 or less permissive, run the following command:
+$ sudo ls -l /home
+Inspect the output for any directories with incorrect permissions. Is it the case that they are more permissive? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Ensure that SSH will display the date and time of the last successful account logon.
-
-The default SSH configuration enables print of the date and time of the last login.
-The appropriate configuration is used if no value is set for PrintLastLog.
-
-To explicitly enable LastLog in SSH, add or correct the following line in
-
-
-/etc/ssh/sshd_config:
-
-PrintLastLog yes |
+ 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 |
medium |
|
|
@@ -56292,25 +55939,37 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84040-5: Ensure that Users Path Contains Only Local Directories |
+ CCE-82742-8: Add nodev Option to Removable Media Partitions |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 nodev mount option prevents files from being
+interpreted as character or block devices.
+Legitimate character and block devices should exist only in
+the /dev directory on the root partition or within chroot
+jails built for system services.
+Add the nodev option to the fourth column of
+/etc/fstab for the line which controls mounting of
+
+ any removable media partitions. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that all local interactive user initialization file executable search path statements do not contain statements that will reference a working directory other than user home directories with the following commands:
+ | Verify file systems that are used for removable media are mounted with the "nodev" option with the following command:
-$ sudo grep -i path= /home/*/.*
+$ sudo more /etc/fstab
-/home/[localinteractiveuser]/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin Is it the case that any local interactive user initialization files have executable search path statements that include directories outside of their home directory and is not documented with the ISSO as an operational requirement? |
+UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid,nodev,noexec 0 0 Is it the case that a file system found in "/etc/fstab" refers to removable media and it does not have the "nodev" option set?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 nodev mount option prevents files from being
+interpreted as character or block devices.
+Legitimate character and block devices should exist only in
+the /dev directory on the root partition or within chroot
+jails built for system services.
+Add the nodev option to the fourth column of
+/etc/fstab for the line which controls mounting of
+
+ any removable media partitions. |
medium |
|
|
@@ -56323,30 +55982,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-85886-0: Ensure All World-Writable Directories Are Group Owned by a System Account |
+ CCE-81021-8: Enable Kernel Parameter to Use Reverse Path Filtering on all IPv4 Interfaces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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. |
+ To set the runtime status of the net.ipv4.conf.all.rp_filter kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.rp_filter=1
+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.rp_filter = 1 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The following command will discover and print world-writable directories that
-are not group owned by a system account, given the assumption that only system
-accounts have a gid lower than 1000. Run it once for each local partition PART:
-$ sudo find PART -xdev -type d -perm -0002 -gid +999 -print Is it the case that there is output? |
+ The runtime status of the net.ipv4.conf.all.rp_filter parameter can be queried
+by running the following command:
+$ sysctl net.ipv4.conf.all.rp_filter
+The output of the command should indicate either:
+net.ipv4.conf.all.rp_filter = 1
+or:
+net.ipv4.conf.all.rp_filter = 2
+The output of the command should not indicate:
+net.ipv4.conf.all.rp_filter = 0
+
+The preferable way how to assure the runtime compliance is to have
+correct persistent configuration, and rebooting the system.
+
+The persistent sysctl parameter configuration is performed by specifying the appropriate
+assignment in any file located in the /etc/sysctl.d directory.
+Verify that there is not any existing incorrect configuration by executing the following command:
+$ grep -r '^\s*net.ipv4.conf.all.rp_filter\s*=' /etc/sysctl.conf /etc/sysctl.d
+The command should not find any assignments other than:
+net.ipv4.conf.all.rp_filter = 1
+or:
+net.ipv4.conf.all.rp_filter = 2
+
+Conflicting assignments are not allowed. Is it the case that the net.ipv4.conf.all.rp_filter is not set to 1 or 2 or is configured to be 0? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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. |
+ To set the runtime status of the net.ipv4.conf.all.rp_filter kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.rp_filter=1
+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.rp_filter = 1 |
medium |
|
|
@@ -56359,37 +56029,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82742-8: Add nodev Option to Removable Media Partitions |
+ CCE-82974-7: Disable Access to Network bpf() Syscall From Unprivileged Processes |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The nodev mount option prevents files from being
-interpreted as character or block devices.
-Legitimate character and block devices should exist only in
-the /dev directory on the root partition or within chroot
-jails built for system services.
-Add the nodev option to the fourth column of
-/etc/fstab for the line which controls mounting of
-
- any removable media partitions. |
+ To set the runtime status of the kernel.unprivileged_bpf_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.unprivileged_bpf_disabled=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.unprivileged_bpf_disabled = 1 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify file systems that are used for removable media are mounted with the "nodev" option with the following command:
-
-$ sudo more /etc/fstab
-
-UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid,nodev,noexec 0 0 Is it the case that a file system found in "/etc/fstab" refers to removable media and it does not have the "nodev" option set? |
+ The runtime status of the kernel.unprivileged_bpf_disabled kernel parameter can be queried
+by running the following command:
+$ sysctl kernel.unprivileged_bpf_disabled
+1.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The nodev mount option prevents files from being
-interpreted as character or block devices.
-Legitimate character and block devices should exist only in
-the /dev directory on the root partition or within chroot
-jails built for system services.
-Add the nodev option to the fourth column of
-/etc/fstab for the line which controls mounting of
-
- any removable media partitions. |
+ To set the runtime status of the kernel.unprivileged_bpf_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.unprivileged_bpf_disabled=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.unprivileged_bpf_disabled = 1 |
medium |
|
|
@@ -56402,24 +56058,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82730-3: Ensure /var/tmp Located On Separate Partition |
+ CCE-84058-7: Prevent remote hosts from connecting to the proxy display |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The /var/tmp directory is a world-writable directory used
-for temporary file storage. Ensure it has its own partition or
-logical volume at installation time, or migrate it using LVM. |
+ The SSH daemon should prevent remote hosts from connecting to the proxy
+display.
+
+The default SSH configuration for X11UseLocalhost is yes,
+which prevents remote hosts from connecting to the proxy display.
+
+To explicitly prevent remote connections to the proxy display, add or correct
+the following line in
+
+
+/etc/ssh/sshd_config:
+
+X11UseLocalhost yes |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that a separate file system/partition has been created for /var/tmp with the following command:
+ | To determine how the SSH daemon's X11UseLocalhost option is set, run the following command:
-$ mountpoint /var/tmp
- Is it the case that "/var/tmp is not a mountpoint" is returned? |
+$ sudo grep -i X11UseLocalhost /etc/ssh/sshd_config
+
+If a line indicating yes is returned, then the required value is set. Is it the case that the display proxy is listening on wildcard address?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The /var/tmp directory is a world-writable directory used
-for temporary file storage. Ensure it has its own partition or
-logical volume at installation time, or migrate it using LVM. |
+ The SSH daemon should prevent remote hosts from connecting to the proxy
+display.
+
+The default SSH configuration for X11UseLocalhost is yes,
+which prevents remote hosts from connecting to the proxy display.
+
+To explicitly prevent remote connections to the proxy display, add or correct
+the following line in
+
+
+/etc/ssh/sshd_config:
+
+X11UseLocalhost yes |
medium |
|
|
@@ -56470,26 +56147,33 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80877-4: Verify firewalld Enabled |
+ CCE-83434-1: All Interactive User Home Directories Must Be Group-Owned By The Primary Group |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
-
-The firewalld service can be enabled with the following command:
-$ sudo systemctl enable firewalld.service |
+ 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
+
+This rule ensures every home directory related to an interactive user is
+group-owned by an interactive user. It also ensures that interactive users
+are group-owners of one and only one home directory. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
-
-
-Run the following command to determine the current status of the
-firewalld service:
-$ sudo systemctl is-active firewalld
-If the service is running, it should return the following: active Is it the case that the "firewalld" service is disabled, masked, or not started.? |
+ To verify the assigned home directory of all interactive users is group-
+owned by that users primary GID, run the following command:
+# ls -ld $(awk -F: '($3>=1000)&&($7 !~ /nologin/){print $6}' /etc/passwd) Is it the case that the group ownership is incorrect? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-
-The firewalld service can be enabled with the following command:
-$ sudo systemctl enable firewalld.service |
+ 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
+
+This rule ensures every home directory related to an interactive user is
+group-owned by an interactive user. It also ensures that interactive users
+are group-owners of one and only one home directory. |
medium |
|
|
@@ -56502,29 +56186,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82251-0: Disable core dump backtraces |
+ CCE-82863-2: Disable Kernel Parameter for IPv6 Forwarding |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The ProcessSizeMax option in [Coredump] section
-of /etc/systemd/coredump.conf
-specifies the maximum size in bytes of a core which will be processed.
-Core dumps exceeding this size may be stored, but the backtrace will not
-be generated. |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 disables core dump backtraces by issuing the following command:
-
-$ grep -i process /etc/systemd/coredump.conf
-
-ProcessSizeMax=0 Is it the case that the "ProcessSizeMax" item is missing, commented out, or the value is anything other than "0" and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core" item assigned? |
+ The runtime status of the net.ipv6.conf.all.forwarding kernel parameter can be queried
+by running the following command:
+$ sysctl net.ipv6.conf.all.forwarding
+0.
+The ability to forward packets is only appropriate for routers. Is it the case that IP forwarding value is "1" and the system is not router? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The ProcessSizeMax option in [Coredump] section
-of /etc/systemd/coredump.conf
-specifies the maximum size in bytes of a core which will be processed.
-Core dumps exceeding this size may be stored, but the backtrace will not
-be generated. |
+ 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 |
medium |
|
|
@@ -56537,41 +56215,44 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80915-2: Restrict Exposed Kernel Pointer Addresses Access |
+ CCE-80898-0: Disable Kerberos Authentication |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To set the runtime status of the kernel.kptr_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.kptr_restrict=
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kptr_restrict = |
+ Unless needed, SSH should not permit extraneous or unnecessary
+authentication mechanisms like Kerberos.
+
+The default SSH configuration disallows authentication validation through Kerberos.
+The appropriate configuration is used if no value is set for KerberosAuthentication.
+
+To explicitly disable Kerberos authentication, add or correct the following line in
+
+
+/etc/ssh/sshd_config:
+
+KerberosAuthentication no |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the kernel.kptr_restrict kernel parameter can be queried
-by running the following command:
-$ sysctl kernel.kptr_restrict
-The output of the command should indicate either:
-kernel.kptr_restrict = 1
-or:
-kernel.kptr_restrict = 2
-The output of the command should not indicate:
-kernel.kptr_restrict = 0
-
-The preferable way how to assure the runtime compliance is to have
-correct persistent configuration, and rebooting the system.
+ | To determine how the SSH daemon's KerberosAuthentication option is set, run the following command:
-The persistent kernel parameter configuration is performed by specifying the appropriate
-assignment in any file located in the /etc/sysctl.d directory.
-Verify that there is not any existing incorrect configuration by executing the following command:
-$ grep -r '^\s*kernel.kptr_restrict\s*=' /etc/sysctl.conf /etc/sysctl.d
-The command should not find any assignments other than:
-kernel.kptr_restrict = 1
-or:
-kernel.kptr_restrict = 2
+$ sudo grep -i KerberosAuthentication /etc/ssh/sshd_config
-Conflicting assignments are not allowed. Is it the case that the kernel.kptr_restrict is not set to 1 or 2 or is configured to be 0? |
+If a line indicating no is returned, then the required value is set.
+ Is it the case that the required value is not set?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To set the runtime status of the kernel.kptr_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.kptr_restrict=
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kptr_restrict = |
+ Unless needed, SSH should not permit extraneous or unnecessary
+authentication mechanisms like Kerberos.
+
+The default SSH configuration disallows authentication validation through Kerberos.
+The appropriate configuration is used if no value is set for KerberosAuthentication.
+
+To explicitly disable Kerberos authentication, add or correct the following line in
+
+
+/etc/ssh/sshd_config:
+
+KerberosAuthentication no |
medium |
|
|
@@ -56584,27 +56265,29 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-83328-5: Add noexec Option to /home |
+ CCE-81050-7: Add nosuid Option to /home |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The noexec mount option can be used to prevent binaries from being
-executed out of /home.
-Add the noexec option to the fourth column of
+ | 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. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify the noexec option is configured for the /home mount point,
+ | Verify the nosuid option is configured for the /home mount point,
run the following command:
$ sudo mount | grep '\s/home\s'
- . . . /home . . . noexec . . .
- Is it the case that the "/home" file system does not have the "noexec" option set? |
+ . . . /home . . . nosuid . . .
+ Is it the case that the "/home" file system does not have the "nosuid" option set?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The noexec mount option can be used to prevent binaries from being
-executed out of /home.
-Add the noexec option to the fourth column of
+ | 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. |
medium |
@@ -56619,25 +56302,62 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84039-7: User Initialization Files Must Not Run World-Writable Programs |
+ CCE-84049-6: Configure Multiple DNS Servers in /etc/resolv.conf |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Set the mode on files being executed by the user initialization files with the
+ |
+Determine whether the system is using local or DNS name resolution with the
following command:
-$ sudo chmod o-w FILE |
+$ sudo grep hosts /etc/nsswitch.conf
+hosts: files dns
+If the DNS entry is missing from the host's line in the "/etc/nsswitch.conf"
+file, the "/etc/resolv.conf" file must be empty.
+Verify the "/etc/resolv.conf" file is empty with the following command:
+$ sudo ls -al /etc/resolv.conf
+-rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.conf
+If the DNS entry is found on the host's line of the "/etc/nsswitch.conf" file,
+then verify the following:
+
+Multiple Domain Name System (DNS) Servers should be configured
+in /etc/resolv.conf. This provides redundant name resolution services
+in the event that a domain server crashes. To configure the system to contain
+as least 2 DNS servers, add a corresponding nameserver
+ip_address entry in /etc/resolv.conf for each DNS
+server where ip_address is the IP address of a valid DNS server.
+For example:
+search example.com
+nameserver 192.168.0.1
+nameserver 192.168.0.2
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that local initialization files do not execute world-writable programs with the following command:
-
-Note: The example will be for a system that is configured to create user home directories in the "/home" directory.
-
-$ sudo find /home -perm -002 -type f -name ".[^.]*" -exec ls -ld {} \; Is it the case that any local initialization files are found to reference world-writable files? |
+ Verify that DNS servers have been configured properly, perform the following:
+$ sudo grep nameserver /etc/resolv.conf Is it the case that less than two lines are returned that are not commented out? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Set the mode on files being executed by the user initialization files with the
+ |
+Determine whether the system is using local or DNS name resolution with the
following command:
-$ sudo chmod o-w FILE |
+$ sudo grep hosts /etc/nsswitch.conf
+hosts: files dns
+If the DNS entry is missing from the host's line in the "/etc/nsswitch.conf"
+file, the "/etc/resolv.conf" file must be empty.
+Verify the "/etc/resolv.conf" file is empty with the following command:
+$ sudo ls -al /etc/resolv.conf
+-rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.conf
+If the DNS entry is found on the host's line of the "/etc/nsswitch.conf" file,
+then verify the following:
+
+Multiple Domain Name System (DNS) Servers should be configured
+in /etc/resolv.conf. This provides redundant name resolution services
+in the event that a domain server crashes. To configure the system to contain
+as least 2 DNS servers, add a corresponding nameserver
+ip_address entry in /etc/resolv.conf for each DNS
+server where ip_address is the IP address of a valid DNS server.
+For example:
+search example.com
+nameserver 192.168.0.1
+nameserver 192.168.0.2
medium |
|
|
@@ -56650,44 +56370,28 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80944-2: Enable page allocator poisoning |
+ CCE-82283-3: Ensure System is Not Acting as a Network Sniffer |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To enable poisoning of free pages,
-add the argument page_poison=1 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that page_poison=1 is added as a kernel command line
-argument to newly installed kernels, add page_poison=1 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... page_poison=1 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="page_poison=1" |
- Applicable - Configurable |
- Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Inspect the form of default GRUB 2 command line for the Linux operating system
-in /etc/default/grub. If it includes page_poison=1,
-then the parameter will be configured for newly installed kernels.
-First check if the GRUB recovery is enabled:
-$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
-If this option is set to true, then check that a line is output by the following command:
-$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*page_poison=1.*' /etc/default/grub
-If the recovery is disabled, check the line with
-$ sudo grep 'GRUB_CMDLINE_LINUX.*page_poison=1.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
-Run the following command:
-$ sudo grubby --info=ALL | grep args | grep -v 'page_poison=1'
-The command should not return any output. Is it the case that page allocator poisoning is not enabled? |
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To enable poisoning of free pages,
-add the argument page_poison=1 to the default
-GRUB 2 command line for the Linux operating system.
-To ensure that page_poison=1 is added as a kernel command line
-argument to newly installed kernels, add page_poison=1 to the
-default Grub2 command line for Linux operating systems. Modify the line within
-/etc/default/grub as shown below:
-GRUB_CMDLINE_LINUX="... page_poison=1 ..."
-Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="page_poison=1" |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
+ Verify that Promiscuous mode of an interface is disabled, run the following command:
+$ ip link | grep PROMISC Is it the case that any network device is in promiscuous mode? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ 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 |
medium |
|
|
@@ -56700,23 +56404,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81010-1: Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv6 Interfaces |
+ CCE-82211-4: Disable the use of user namespaces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ To set the runtime status of the user.max_user_namespaces kernel parameter,
+run the following command:
+$ sudo sysctl -w user.max_user_namespaces=0
+
+To make sure that the setting is persistent,
+add the following line to a file in the directory /etc/sysctl.d:
+user.max_user_namespaces = 0
+When containers are deployed on the machine, the value should be set
+to large non-zero value. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv6.conf.default.accept_redirects kernel parameter can be queried
+ | Verify that Red Hat Enterprise Linux 8 disables the use of user namespaces with the following commands:
+
+Note: User namespaces are used primarily for Linux containers. If containers are in use, this requirement is not applicable.
+
+The runtime status of the user.max_user_namespaces kernel parameter can be queried
by running the following command:
-$ sysctl net.ipv6.conf.default.accept_redirects
+$ sysctl user.max_user_namespaces
0.
Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
+ To set the runtime status of the user.max_user_namespaces kernel parameter,
+run the following command:
+$ sudo sysctl -w user.max_user_namespaces=0
+
+To make sure that the setting is persistent,
+add the following line to a file in the directory /etc/sysctl.d:
+user.max_user_namespaces = 0
+When containers are deployed on the machine, the value should be set
+to large non-zero value. |
medium |
|
|
@@ -56729,23 +56451,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82252-8: Disable storing core dump |
+ CCE-82434-2: Ensure tftp Daemon Uses Secure Mode |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The Storage option in [Coredump] sectionof /etc/systemd/coredump.conf
-can be set to none to disable storing core dumps permanently. |
+ If running the Trivial File Transfer Protocol (TFTP) service is necessary,
+it should be configured to change its root directory at startup. To do so,
+ensure /etc/xinetd.d/tftp includes -s as a command line argument,
+as shown in the following example:
+server_args = -s |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 disables storing core dumps for all users by issuing the following command:
+ | Verify the TFTP daemon is configured to operate in secure mode.
-$ grep -i storage /etc/systemd/coredump.conf
+Check if a TFTP server is installed with the following command:
-Storage=none Is it the case that Storage is not set to none or is commented out and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core" item assigned? |
+$ rpm -qa | grep tftp
+
+
+If a TFTP server is not installed, this is Not Applicable.
+
+
+If a TFTP server is installed, verify TFTP is configured by with
+the -s option by running the following command:
+
+grep "server_args" /etc/xinetd.d/tftp
+server_args = -s
Is it the case that '"server_args" line does not have a "-s" option, and a subdirectory is not assigned'?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The Storage option in [Coredump] sectionof /etc/systemd/coredump.conf
-can be set to none to disable storing core dumps permanently. |
+ If running the Trivial File Transfer Protocol (TFTP) service is necessary,
+it should be configured to change its root directory at startup. To do so,
+ensure /etc/xinetd.d/tftp includes -s as a command line argument,
+as shown in the following example:
+server_args = -s |
medium |
|
|
@@ -56758,49 +56496,42 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84028-0: Disable Ctrl-Alt-Del Reboot Key Sequence in GNOME3 |
+ CCE-85987-6: Only Authorized Local User Accounts Exist on Operating System |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- By default, GNOME 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 Graphical User Interface (GUI) instead of rebooting the system,
-add or set logout to '' in
-/etc/dconf/db/local.d/00-security-settings. For example:
-[org/gnome/settings-daemon/plugins/media-keys]
-logout=''
-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/settings-daemon/plugins/media-keys/logout
-After the settings have been set, run dconf update. |
+ Enterprise Application tends to use the server or virtual machine exclusively.
+Besides the default operating system user, there should be only authorized local
+users required by the installed software groups and applications that exist on
+the operating system. The authorized user list can be customized in the refine
+value variable var_accounts_authorized_local_users_regex.
+OVAL regular expression is used for the user list.
+Configure the system so all accounts on the system are assigned to an active system,
+application, or user account. Remove accounts that do not support approved system
+activities or that allow for a normal user to perform administrative-level actions.
+To remove unauthorized system accounts, use the following command:
+$ sudo userdel unauthorized_user |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To ensure the system is configured to ignore the Ctrl-Alt-Del sequence,
-run the following command:
-$ gsettings get org.gnome.settings-daemon.plugins.media-keys logout
-$ grep logout /etc/dconf/db/local.d/locks/*
-If properly configured, the output should be
-/org/gnome/settings-daemon/plugins/media-keys/logout Is it the case that GNOME3 is configured to reboot when Ctrl-Alt-Del is pressed? |
+ To verify that there are no unauthorized local user accounts, run the following command:
+$ less /etc/passwd
+Inspect the results, and if unauthorized local user accounts exist, remove them by running
+the following command:
+$ sudo userdel unauthorized_user Is it the case that there are unauthorized local user accounts on the system? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- By default, GNOME 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 Graphical User Interface (GUI) instead of rebooting the system,
-add or set logout to '' in
-/etc/dconf/db/local.d/00-security-settings. For example:
-[org/gnome/settings-daemon/plugins/media-keys]
-logout=''
-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/settings-daemon/plugins/media-keys/logout
-After the settings have been set, run dconf update. |
- high |
+ Enterprise Application tends to use the server or virtual machine exclusively.
+Besides the default operating system user, there should be only authorized local
+users required by the installed software groups and applications that exist on
+the operating system. The authorized user list can be customized in the refine
+value variable var_accounts_authorized_local_users_regex.
+OVAL regular expression is used for the user list.
+Configure the system so all accounts on the system are assigned to an active system,
+application, or user account. Remove accounts that do not support approved system
+activities or that allow for a normal user to perform administrative-level actions.
+To remove unauthorized system accounts, use the following command:
+$ sudo userdel unauthorized_user |
+ medium |
|
|
|
@@ -56812,23 +56543,40 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84050-4: Mount Remote Filesystems with noexec |
+ CCE-80841-0: Prevent Login to Accounts With Empty Password |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of
-any NFS mounts. |
+ 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
+
+/etc/pam.d/system-auth and
+/etc/pam.d/password-auth
+
+to prevent logins with empty passwords. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify the noexec option is configured for all NFS mounts, run the following command:
-$ mount | grep nfs
-All NFS mounts should show the noexec setting in parentheses. This is not applicable if NFS is
-not implemented. Is it the case that the setting does not show? |
+ To verify that null passwords cannot be used, run the following command:
+
+$ grep nullok /etc/pam.d/system-auth /etc/pam.d/password-auth
+
+If this produces any output, it may be possible to log into accounts
+with empty passwords. Remove any instances of the nullok option to
+prevent logins with empty passwords. Is it the case that NULL passwords can be used? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of
-any NFS mounts. |
- medium |
+ 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
+
+/etc/pam.d/system-auth and
+/etc/pam.d/password-auth
+
+to prevent logins with empty passwords. |
+ high |
|
|
|
@@ -56840,48 +56588,22 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-83360-8: Disable X11 Forwarding |
+ CCE-82946-5: Uninstall iprutils Package |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The X11Forwarding parameter provides the ability to tunnel X11 traffic
-through the connection to enable remote graphic connections.
-SSH has the capability to encrypt remote X11 connections when SSH's
-X11Forwarding option is enabled.
-
-The default SSH configuration disables X11Forwarding. The appropriate
-configuration is used if no value is set for X11Forwarding.
-
-To explicitly disable X11 Forwarding, add or correct the following line in
-
-
-/etc/ssh/sshd_config:
-
-X11Forwarding no |
+ The iprutils package can be removed with the following command:
+
+$ sudo yum erase iprutils |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To determine how the SSH daemon's X11Forwarding option is set, run the following command:
-
-$ sudo grep -i X11Forwarding /etc/ssh/sshd_config
-
-If a line indicating no is returned, then the required value is set.
- Is it the case that the required value is not set? |
+ Run the following command to determine if the iprutils package is installed:
+$ rpm -q iprutils Is it the case that the package is installed? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The X11Forwarding parameter provides the ability to tunnel X11 traffic
-through the connection to enable remote graphic connections.
-SSH has the capability to encrypt remote X11 connections when SSH's
-X11Forwarding option is enabled.
-
-The default SSH configuration disables X11Forwarding. The appropriate
-configuration is used if no value is set for X11Forwarding.
-
-To explicitly disable X11 Forwarding, add or correct the following line in
-
-
-/etc/ssh/sshd_config:
-
-X11Forwarding no |
+ The iprutils package can be removed with the following command:
+
+$ sudo yum erase iprutils |
medium |
|
|
@@ -56894,34 +56616,29 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82069-6: Add nodev Option to Non-Root Local Partitions |
+ CCE-83328-5: Add noexec Option to /home |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The nodev mount option prevents files from being interpreted as
-character or block devices. Legitimate character and block devices should
-exist only in the /dev directory on the root partition or within
-chroot jails built for system services.
-Add the nodev option to the fourth column of
+ | The noexec mount option can be used to prevent binaries from being
+executed out of /home.
+Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
-
- any non-root local partitions. |
+/home.
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify the nodev option is configured for non-root local partitions, run the following command:
-$ sudo mount | grep '^/dev\S* on /\S' | grep --invert-match 'nodev'
-The output shows local non-root partitions mounted without the nodev option, and there should be no output at all.
- Is it the case that some mounts appear among output lines? |
+ Verify the noexec option is configured for the /home mount point,
+ run the following command:
+ $ sudo mount | grep '\s/home\s'
+ . . . /home . . . noexec . . .
+ Is it the case that the "/home" file system does not have the "noexec" option set? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The nodev mount option prevents files from being interpreted as
-character or block devices. Legitimate character and block devices should
-exist only in the /dev directory on the root partition or within
-chroot jails built for system services.
-Add the nodev option to the fourth column of
+ | The noexec mount option can be used to prevent binaries from being
+executed out of /home.
+Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
-
- any non-root local partitions. |
+/home.
medium |
|
|
@@ -56934,24 +56651,28 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-83375-6: Ensure All World-Writable Directories Are Owned by root User |
+ CCE-84056-1: Remove User Host-Based Authentication Files |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- All directories in local partitions which are world-writable should be owned by root.
-If any world-writable directories are not owned by root, this should be investigated.
-Following this, the files should be deleted or assigned to root user. |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The following command will discover and print world-writable directories that
-are not owned by root. Run it once for each local partition PART:
-$ sudo find PART -xdev -type d -perm -0002 -uid +0 -print Is it the case that there are world-writable directories not owned by root? |
+ To verify that there are no .shosts files
+on the system, run the following command:
+$ sudo find / -name '.shosts' Is it the case that .shosts files exist? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- All directories in local partitions which are world-writable should be owned by root.
-If any world-writable directories are not owned by root, this should be investigated.
-Following this, the files should be deleted or assigned to root user. |
- medium |
+ 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 |
+ high |
|
|
|
@@ -56963,41 +56684,46 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81021-8: Enable Kernel Parameter to Use Reverse Path Filtering on all IPv4 Interfaces |
+ CCE-80904-6: Enable Use of Strict Mode Checking |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To set the runtime status of the net.ipv4.conf.all.rp_filter kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.rp_filter=1
-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.rp_filter = 1 |
+ 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.
+
+The default SSH configuration has StrictModes enabled. The appropriate
+configuration is used if no value is set for StrictModes.
+
+To explicitly enable StrictModes in SSH, add or correct the following line in
+
+
+/etc/ssh/sshd_config:
+
+StrictModes yes |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv4.conf.all.rp_filter parameter can be queried
-by running the following command:
-$ sysctl net.ipv4.conf.all.rp_filter
-The output of the command should indicate either:
-net.ipv4.conf.all.rp_filter = 1
-or:
-net.ipv4.conf.all.rp_filter = 2
-The output of the command should not indicate:
-net.ipv4.conf.all.rp_filter = 0
-
-The preferable way how to assure the runtime compliance is to have
-correct persistent configuration, and rebooting the system.
+ | To determine how the SSH daemon's StrictModes option is set, run the following command:
-The persistent sysctl parameter configuration is performed by specifying the appropriate
-assignment in any file located in the /etc/sysctl.d directory.
-Verify that there is not any existing incorrect configuration by executing the following command:
-$ grep -r '^\s*net.ipv4.conf.all.rp_filter\s*=' /etc/sysctl.conf /etc/sysctl.d
-The command should not find any assignments other than:
-net.ipv4.conf.all.rp_filter = 1
-or:
-net.ipv4.conf.all.rp_filter = 2
+$ sudo grep -i StrictModes /etc/ssh/sshd_config
-Conflicting assignments are not allowed. Is it the case that the net.ipv4.conf.all.rp_filter is not set to 1 or 2 or is configured to be 0? |
+If a line indicating yes is returned, then the required value is set.
+ Is it the case that the required value is not set?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To set the runtime status of the net.ipv4.conf.all.rp_filter kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.rp_filter=1
-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.rp_filter = 1 |
+ 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.
+
+The default SSH configuration has StrictModes enabled. The appropriate
+configuration is used if no value is set for StrictModes.
+
+To explicitly enable StrictModes in SSH, add or correct the following line in
+
+
+/etc/ssh/sshd_config:
+
+StrictModes yes |
medium |
|
|
@@ -57010,26 +56736,22 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84038-9: All Interactive User Home Directories Must Have mode 0750 Or Less Permissive |
+ CCE-82904-4: Uninstall tuned Package |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ The tuned package can be removed with the following command:
+
+$ sudo yum erase tuned |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify the assigned home directory of all interactive user home directories
-have a mode of 0750 or less permissive, run the following command:
-$ sudo ls -l /home
-Inspect the output for any directories with incorrect permissions. Is it the case that they are more permissive? |
+ Run the following command to determine if the tuned package is installed:
+$ rpm -q tuned Is it the case that the package is installed? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
+ The tuned package can be removed with the following command:
+
+$ sudo yum erase tuned |
medium |
|
|
@@ -57042,27 +56764,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80853-5: Ensure /var/log Located On Separate Partition |
+ CCE-80921-0: Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces by Default |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- System logs are stored in the /var/log directory.
-
-Ensure that /var/log has its own partition or logical
-volume at installation time, or migrate it using LVM. |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that a separate file system/partition has been created for /var/log with the following command:
-
-$ mountpoint /var/log
- Is it the case that "/var/log is not a mountpoint" is returned? |
+ The runtime status of the net.ipv4.conf.default.send_redirects kernel parameter can be queried
+by running the following command:
+$ sysctl net.ipv4.conf.default.send_redirects
+0.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- System logs are stored in the /var/log directory.
-
-Ensure that /var/log has its own partition or logical
-volume at installation time, or migrate it using LVM. |
- low |
+ 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 |
+ medium |
|
|
|
@@ -57074,46 +56793,47 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80904-6: Enable Use of Strict Mode Checking |
+ CCE-80834-5: Disable SCTP Support |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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.
-
-The default SSH configuration has StrictModes enabled. The appropriate
-configuration is used if no value is set for StrictModes.
-
-To explicitly enable StrictModes in SSH, add or correct the following line in
-
+ | The Stream Control Transmission Protocol (SCTP) is a
+transport layer protocol, designed to support the idea of
+message-oriented communication, with several streams of messages
+within one connection.
-/etc/ssh/sshd_config:
+To configure the system to prevent the sctp
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/sctp.conf:
+install sctp /bin/true
-StrictModes yes |
+To configure the system to prevent the sctp from being used,
+add the following line to file /etc/modprobe.d/sctp.conf:
+blacklist sctp
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To determine how the SSH daemon's StrictModes option is set, run the following command:
+ |
+If the system is configured to prevent the loading of the sctp kernel module,
+it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
+These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
-$ sudo grep -i StrictModes /etc/ssh/sshd_config
+These lines can also instruct the module loading system to ignore the sctp kernel module via blacklist keyword.
-If a line indicating yes is returned, then the required value is set.
- Is it the case that the required value is not set? |
+Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
+$ grep -r sctp /etc/modprobe.conf /etc/modprobe.d
Is it the case that no line is returned?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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.
-
-The default SSH configuration has StrictModes enabled. The appropriate
-configuration is used if no value is set for StrictModes.
-
-To explicitly enable StrictModes in SSH, add or correct the following line in
-
+ | The Stream Control Transmission Protocol (SCTP) is a
+transport layer protocol, designed to support the idea of
+message-oriented communication, with several streams of messages
+within one connection.
-/etc/ssh/sshd_config:
+To configure the system to prevent the sctp
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/sctp.conf:
+install sctp /bin/true
-StrictModes yes |
+To configure the system to prevent the sctp from being used,
+add the following line to file /etc/modprobe.d/sctp.conf:
+blacklist sctp
medium |
|
|
@@ -57126,62 +56846,52 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84049-6: Configure Multiple DNS Servers in /etc/resolv.conf |
+ CCE-80917-8: Disable Accepting ICMP Redirects for All IPv4 Interfaces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
-
-Determine whether the system is using local or DNS name resolution with the
-following command:
-$ sudo grep hosts /etc/nsswitch.conf
-hosts: files dns
-If the DNS entry is missing from the host's line in the "/etc/nsswitch.conf"
-file, the "/etc/resolv.conf" file must be empty.
-Verify the "/etc/resolv.conf" file is empty with the following command:
-$ sudo ls -al /etc/resolv.conf
--rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.conf
-If the DNS entry is found on the host's line of the "/etc/nsswitch.conf" file,
-then verify the following:
-
-Multiple Domain Name System (DNS) Servers should be configured
-in /etc/resolv.conf. This provides redundant name resolution services
-in the event that a domain server crashes. To configure the system to contain
-as least 2 DNS servers, add a corresponding nameserver
-ip_address entry in /etc/resolv.conf for each DNS
-server where ip_address is the IP address of a valid DNS server.
-For example:
-search example.com
-nameserver 192.168.0.1
-nameserver 192.168.0.2 |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that DNS servers have been configured properly, perform the following:
-$ sudo grep nameserver /etc/resolv.conf Is it the case that less than two lines are returned that are not commented out? |
+ The runtime status of the net.ipv4.conf.all.accept_redirects kernel parameter can be queried
+by running the following command:
+$ sysctl net.ipv4.conf.all.accept_redirects
+0.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-
-Determine whether the system is using local or DNS name resolution with the
-following command:
-$ sudo grep hosts /etc/nsswitch.conf
-hosts: files dns
-If the DNS entry is missing from the host's line in the "/etc/nsswitch.conf"
-file, the "/etc/resolv.conf" file must be empty.
-Verify the "/etc/resolv.conf" file is empty with the following command:
-$ sudo ls -al /etc/resolv.conf
--rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.conf
-If the DNS entry is found on the host's line of the "/etc/nsswitch.conf" file,
-then verify the following:
+ | 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 |
+ medium |
+ |
+ |
+ |
+
-Multiple Domain Name System (DNS) Servers should be configured
-in
/etc/resolv.conf. This provides redundant name resolution services
-in the event that a domain server crashes. To configure the system to contain
-as least
2 DNS servers, add a corresponding
nameserver
-ip_address entry in
/etc/resolv.conf for each DNS
-server where
ip_address is the IP address of a valid DNS server.
-For example:
-
search example.com
-nameserver 192.168.0.1
-nameserver 192.168.0.2
+
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00227 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+
+ CCE-84054-6: Prevent Unrestricted Mail Relaying |
+
+ Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
+
+Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
+ Modify the /etc/postfix/main.cf file to restrict client connections
+to the local network with the following command:
+$ sudo postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject' |
+ Applicable - Configurable |
+ Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
+ Verify that Red Hat Enterprise Linux 8 is configured to prevent unrestricted mail relaying,
+run the following command:
+$ sudo postconf -n smtpd_client_restrictions Is it the case that the "smtpd_client_restrictions" parameter contains any entries other than "permit_mynetworks" and "reject"? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ Modify the /etc/postfix/main.cf file to restrict client connections
+to the local network with the following command:
+$ sudo postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject' |
medium |
|
|
@@ -57194,45 +56904,26 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82059-7: Disable CAN Support |
+ CCE-85877-9: Ensure PAM password complexity module is enabled in password-auth |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The Controller Area Network (CAN) is a serial communications
-protocol which was initially developed for automotive and
-is now also used in marine, industrial, and medical applications.
-
-To configure the system to prevent the can
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/can.conf:
-install can /bin/true
-
-To configure the system to prevent the can from being used,
-add the following line to file /etc/modprobe.d/can.conf:
-blacklist can |
+ To enable PAM password complexity in password-auth file:
+Edit the password section in
+/etc/pam.d/password-auth to show
+password requisite pam_pwquality.so. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
-
-If the system is configured to prevent the loading of the can kernel module,
-it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
-These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
-
-These lines can also instruct the module loading system to ignore the can kernel module via blacklist keyword.
-
-Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
-$ grep -r can /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
+ To check if pam_pwquality.so is enabled in password-auth, run the following command:
+$ grep pam_pwquality /etc/pam.d/password-auth
+The output should be similar to the following:
+password requisite pam_pwquality.so Is it the case that pam_pwquality.so is not enabled in password-auth? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The Controller Area Network (CAN) is a serial communications
-protocol which was initially developed for automotive and
-is now also used in marine, industrial, and medical applications.
-
-To configure the system to prevent the can
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/can.conf:
-install can /bin/true
-
-To configure the system to prevent the can from being used,
-add the following line to file /etc/modprobe.d/can.conf:
-blacklist can |
+ To enable PAM password complexity in password-auth file:
+Edit the password section in
+/etc/pam.d/password-auth to show
+password requisite pam_pwquality.so. |
medium |
|
|
@@ -57245,33 +56936,48 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80784-2: Disable Ctrl-Alt-Del Burst Action |
+ CCE-84028-0: Disable Ctrl-Alt-Del Reboot Key Sequence in GNOME3 |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- By default, SystemD will reboot the system if the Ctrl-Alt-Del
-key sequence is pressed Ctrl-Alt-Delete more than 7 times in 2 seconds.
+ | By default, GNOME will reboot the system if the
+Ctrl-Alt-Del key sequence is pressed.
-To configure the system to ignore the CtrlAltDelBurstAction
-
-setting, add or modify the following to /etc/systemd/system.conf:
-CtrlAltDelBurstAction=none |
+To configure the system to ignore the Ctrl-Alt-Del key sequence
+from the Graphical User Interface (GUI) instead of rebooting the system,
+add or set logout to '' in
+/etc/dconf/db/local.d/00-security-settings. For example:
+[org/gnome/settings-daemon/plugins/media-keys]
+logout=''
+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/settings-daemon/plugins/media-keys/logout
+After the settings have been set, run dconf update.
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To ensure the system is configured to ignore the Ctrl-Alt-Del setting,
-enter the following command:
-$ sudo grep -i ctrlaltdelburstaction /etc/systemd/system.conf
-The output should return:
-CtrlAltDelBurstAction=none Is it the case that the system is configured to reboot when Ctrl-Alt-Del is pressed more than 7 times in 2 seconds.? |
+ To ensure the system is configured to ignore the Ctrl-Alt-Del sequence,
+run the following command:
+$ gsettings get org.gnome.settings-daemon.plugins.media-keys logout
+$ grep logout /etc/dconf/db/local.d/locks/*
+If properly configured, the output should be
+/org/gnome/settings-daemon/plugins/media-keys/logout Is it the case that GNOME3 is configured to reboot when Ctrl-Alt-Del is pressed? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- By default, SystemD will reboot the system if the Ctrl-Alt-Del
-key sequence is pressed Ctrl-Alt-Delete more than 7 times in 2 seconds.
+ | By default, GNOME will reboot the system if the
+Ctrl-Alt-Del key sequence is pressed.
-To configure the system to ignore the CtrlAltDelBurstAction
-
-setting, add or modify the following to /etc/systemd/system.conf:
-CtrlAltDelBurstAction=none |
+To configure the system to ignore the Ctrl-Alt-Del key sequence
+from the Graphical User Interface (GUI) instead of rebooting the system,
+add or set logout to '' in
+/etc/dconf/db/local.d/00-security-settings. For example:
+[org/gnome/settings-daemon/plugins/media-keys]
+logout=''
+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/settings-daemon/plugins/media-keys/logout
+After the settings have been set, run dconf update.
high |
|
|
@@ -57334,31 +57040,37 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80854-3: Ensure /var/log/audit Located On Separate Partition |
+ CCE-80901-2: Disable SSH Root Login |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Audit logs are stored in the /var/log/audit directory.
+ | 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
-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. |
+
+/etc/ssh/sshd_config:
+
+PermitRootLogin no
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that a separate file system/partition has been created for /var/log/audit with the following command:
+ | To determine how the SSH daemon's PermitRootLogin option is set, run the following command:
-$ mountpoint /var/log/audit
- Is it the case that "/var/log/audit is not a mountpoint" is returned? |
+$ sudo grep -i PermitRootLogin /etc/ssh/sshd_config
+
+If a line indicating no is returned, then the required value is set.
+ Is it the case that the required value is not set?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Audit logs are stored in the /var/log/audit directory.
+ | 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
-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. |
- low |
+
+/etc/ssh/sshd_config:
+
+PermitRootLogin no
+ medium |
|
|
|
@@ -57370,38 +57082,34 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-83411-9: Disable graphical user interface |
+ CCE-82746-9: Add noexec Option to Removable Media Partitions |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- By removing the following packages, the system no longer has X Windows installed.
-
-xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland
-
-If X Windows is not installed then the system cannot boot into graphical user mode.
-This prevents the system from being accidentally or maliciously booted into a graphical.target
-mode. To do so, run the following command:
+ | The noexec mount option prevents the direct execution of binaries
+on the mounted filesystem. Preventing the direct execution of binaries from
+removable media (such as a USB key) provides a defense against malicious
+software that may be present on such untrusted media.
+Add the noexec option to the fourth column of
+/etc/fstab for the line which controls mounting of
-sudo yum remove xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland |
+ any removable media partitions.
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To ensure the X Windows package group is removed, run the following command:
-
-$ rpm -qi xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland
-
-For each package mentioned above you should receive following line:
-package <package> is not installed Is it the case that xorg related packages are not removed and run level is not correctly configured? |
+ To verify that binaries cannot be directly executed from removable media, run the following command:
+$ grep -v noexec /etc/fstab
+The resulting output will show partitions which do not have the noexec flag. Verify all partitions
+in the output are not removable media. Is it the case that removable media partitions are present? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- By removing the following packages, the system no longer has X Windows installed.
-
-xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland
-
-If X Windows is not installed then the system cannot boot into graphical user mode.
-This prevents the system from being accidentally or maliciously booted into a graphical.target
-mode. To do so, run the following command:
+ | The noexec mount option prevents the direct execution of binaries
+on the mounted filesystem. Preventing the direct execution of binaries from
+removable media (such as a USB key) provides a defense against malicious
+software that may be present on such untrusted media.
+Add the noexec option to the fourth column of
+/etc/fstab for the line which controls mounting of
-sudo yum remove xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland |
+ any removable media partitions.
medium |
|
|
@@ -57414,31 +57122,66 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81033-3: Add nosuid Option to /boot |
+ CCE-80863-4: Ensure Logs Sent To Remote Host |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The nosuid mount option can be used to prevent
-execution of setuid programs in /boot. The SUID and SGID permissions
-should not be required on the boot partition.
-Add the nosuid option to the fourth column of
-/etc/fstab for the line which controls mounting of
-/boot. |
+ 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 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:
+*.* @
+
+To use TCP for log message delivery:
+*.* @@
+
+To use RELP for log message delivery:
+*.* :omrelp:
+
+There must be a resolvable DNS CNAME or Alias record set to "" for logs to be sent correctly to the centralized logging utility. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify the nosuid option is configured for the /boot mount point,
- run the following command:
- $ sudo mount | grep '\s/boot\s'
- . . . /boot . . . nosuid . . .
- Is it the case that the "/boot" file system does not have the "nosuid" option set? |
+ To ensure logs are sent to a remote host, examine the file
+/etc/rsyslog.conf.
+If using UDP, a line similar to the following should be present:
+ *.* @
+If using TCP, a line similar to the following should be present:
+ *.* @@
+If using RELP, a line similar to the following should be present:
+ *.* :omrelp: Is it the case that no evidence that the audit logs are being off-loaded to another system or media? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The nosuid mount option can be used to prevent
-execution of setuid programs in /boot. The SUID and SGID permissions
-should not be required on the boot partition.
-Add the nosuid option to the fourth column of
-/etc/fstab for the line which controls mounting of
-/boot. |
+ 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 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:
+*.* @
+
+To use TCP for log message delivery:
+*.* @@
+
+To use RELP for log message delivery:
+*.* :omrelp:
+
+There must be a resolvable DNS CNAME or Alias record set to "" for logs to be sent correctly to the centralized logging utility. |
medium |
|
|
@@ -57451,22 +57194,48 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82428-4: Verify Permissions on SSH Server Public *.pub Key Files |
+ CCE-80785-9: Disable Ctrl-Alt-Del Reboot Activation |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To properly set the permissions of /etc/ssh/*.pub, run the command: $ sudo chmod 0644 /etc/ssh/*.pub |
+ 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. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To check the permissions of /etc/ssh/*.pub,
-run the command:
-$ ls -l /etc/ssh/*.pub
-If properly configured, the output should indicate the following permissions:
--rw-r--r-- Is it the case that /etc/ssh/*.pub does not have unix mode -rw-r--r--? |
+ To ensure the system is configured to mask the Ctrl-Alt-Del sequence, Check
+that the ctrl-alt-del.target is masked and not active with the following
+command:
+sudo systemctl status ctrl-alt-del.target
+The output should indicate that the target is masked and not active. It
+might resemble following output:
+ctrl-alt-del.target
+Loaded: masked (/dev/null; bad)
+Active: inactive (dead) Is it the case that the system is configured to reboot when Ctrl-Alt-Del is pressed? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To properly set the permissions of /etc/ssh/*.pub, run the command: $ sudo chmod 0644 /etc/ssh/*.pub |
- medium |
+ 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. |
+ high |
|
|
|
@@ -57478,34 +57247,33 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82746-9: Add noexec Option to Removable Media Partitions |
+ CCE-81035-8: Ensure the Default Umask is Set Correctly in /etc/profile |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The noexec mount option prevents the direct execution of binaries
-on the mounted filesystem. Preventing the direct execution of binaries from
-removable media (such as a USB key) provides a defense against malicious
-software that may be present on such untrusted media.
-Add the noexec option to the fourth column of
-/etc/fstab for the line which controls mounting of
+ | To ensure the default umask controlled by /etc/profile is set properly,
+add or correct the umask setting in /etc/profile to read as follows:
+umask
- any removable media partitions. |
+Note that /etc/profile also reads scrips within /etc/profile.d directory.
+These scripts are also valid files to set umask value. Therefore, they should also be
+considered during the check and properly remediated, if necessary.
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify that binaries cannot be directly executed from removable media, run the following command:
-$ grep -v noexec /etc/fstab
-The resulting output will show partitions which do not have the noexec flag. Verify all partitions
-in the output are not removable media. Is it the case that removable media partitions are present? |
+ Verify the umask setting is configured correctly in the /etc/profile file
+or scripts within /etc/profile.d directory with the following command:
+$ grep "umask" /etc/profile*
+umask Is it the case that the value for the "umask" parameter is not "",
+or the "umask" parameter is missing or is commented out? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The noexec mount option prevents the direct execution of binaries
-on the mounted filesystem. Preventing the direct execution of binaries from
-removable media (such as a USB key) provides a defense against malicious
-software that may be present on such untrusted media.
-Add the noexec option to the fourth column of
-/etc/fstab for the line which controls mounting of
+ | To ensure the default umask controlled by /etc/profile is set properly,
+add or correct the umask setting in /etc/profile to read as follows:
+umask
- any removable media partitions. |
+Note that /etc/profile also reads scrips within /etc/profile.d directory.
+These scripts are also valid files to set umask value. Therefore, they should also be
+considered during the check and properly remediated, if necessary.
medium |
|
|
@@ -57518,41 +57286,98 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82211-4: Disable the use of user namespaces |
+ CCE-86195-5: Disable the GNOME3 Login User List |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To set the runtime status of the user.max_user_namespaces kernel parameter,
-run the following command:
-$ sudo sysctl -w user.max_user_namespaces=0
-
-To make sure that the setting is persistent,
-add the following line to a file in the directory /etc/sysctl.d:
-user.max_user_namespaces = 0
-When containers are deployed on the machine, the value should be set
-to large non-zero value. |
+ In the default graphical environment, users logging directly into the
+system are greeted with a login screen that displays all known users.
+This functionality should be disabled by setting disable-user-list
+to true.
+
+To disable, add or edit disable-user-list to
+/etc/dconf/db/gdm.d/00-security-settings. For example:
+[org/gnome/login-screen]
+disable-user-list=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/disable-user-list
+After the settings have been set, run dconf update. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that Red Hat Enterprise Linux 8 disables the use of user namespaces with the following commands:
+ | To ensure the user list is disabled, run the following command:
+$ grep disable-user-list /etc/dconf/db/gdm.d/*
+The output should be true.
+To ensure that users cannot enable displaying the user list, run the following:
+$ grep disable-user-list /etc/dconf/db/gdm.d/locks/*
+If properly configured, the output should be /org/gnome/login-screen/disable-user-list Is it the case that disable-user-list has not been configured or is not disabled? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ In the default graphical environment, users logging directly into the
+system are greeted with a login screen that displays all known users.
+This functionality should be disabled by setting disable-user-list
+to true.
+
+To disable, add or edit disable-user-list to
+/etc/dconf/db/gdm.d/00-security-settings. For example:
+[org/gnome/login-screen]
+disable-user-list=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/disable-user-list
+After the settings have been set, run dconf update. |
+ medium |
+ |
+ |
+ |
+
-Note: User namespaces are used primarily for Linux containers. If containers are in use, this requirement is not applicable.
+
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00227 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-The runtime status of the user.max_user_namespaces kernel parameter can be queried
-by running the following command:
-$ sysctl user.max_user_namespaces
-0.
- Is it the case that the correct value is not returned?
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To set the runtime status of the user.max_user_namespaces kernel parameter,
-run the following command:
-$ sudo sysctl -w user.max_user_namespaces=0
+ | CCE-80944-2: Enable page allocator poisoning |
-To make sure that the setting is persistent,
-add the following line to a file in the directory /etc/sysctl.d:
-user.max_user_namespaces = 0
-When containers are deployed on the machine, the value should be set
-to large non-zero value.
+ Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
+
+Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
+ To enable poisoning of free pages,
+add the argument page_poison=1 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that page_poison=1 is added as a kernel command line
+argument to newly installed kernels, add page_poison=1 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... page_poison=1 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="page_poison=1" |
+ Applicable - Configurable |
+ Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
+ Inspect the form of default GRUB 2 command line for the Linux operating system
+in /etc/default/grub. If it includes page_poison=1,
+then the parameter will be configured for newly installed kernels.
+First check if the GRUB recovery is enabled:
+$ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub
+If this option is set to true, then check that a line is output by the following command:
+$ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*page_poison=1.*' /etc/default/grub
+If the recovery is disabled, check the line with
+$ sudo grep 'GRUB_CMDLINE_LINUX.*page_poison=1.*' /etc/default/grub .Moreover, command line parameters for currently installed kernels should be checked as well.
+Run the following command:
+$ sudo grubby --info=ALL | grep args | grep -v 'page_poison=1'
+The command should not return any output. Is it the case that page allocator poisoning is not enabled? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ To enable poisoning of free pages,
+add the argument page_poison=1 to the default
+GRUB 2 command line for the Linux operating system.
+To ensure that page_poison=1 is added as a kernel command line
+argument to newly installed kernels, add page_poison=1 to the
+default Grub2 command line for Linux operating systems. Modify the line within
+/etc/default/grub as shown below:
+GRUB_CMDLINE_LINUX="... page_poison=1 ..."
+Run the following command to update command line for already installed kernels:# grubby --update-kernel=ALL --args="page_poison=1" |
medium |
|
|
@@ -57565,25 +57390,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82215-5: Disable storing core dumps |
+ CCE-80918-6: Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To set the runtime status of the kernel.core_pattern kernel parameter, run the following command: $ sudo sysctl -w kernel.core_pattern=|/bin/false
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.core_pattern = |/bin/false |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the kernel.core_pattern kernel parameter can be queried
+ | The runtime status of the net.ipv4.conf.all.send_redirects kernel parameter can be queried
by running the following command:
-$ sysctl kernel.core_pattern
-|/bin/false.
- Is it the case that the returned line does not have a value of "|/bin/false", or a line is not
-returned and the need for core dumps is not documented with the Information
-System Security Officer (ISSO) as an operational requirement? |
+$ sysctl net.ipv4.conf.all.send_redirects
+0.
+ Is it the case that the correct value is not returned?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To set the runtime status of the kernel.core_pattern kernel parameter, run the following command: $ sudo sysctl -w kernel.core_pattern=|/bin/false
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.core_pattern = |/bin/false |
+ 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 |
medium |
|
|
@@ -57596,44 +57419,69 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80897-2: Disable GSSAPI Authentication |
+ CCE-80902-0: Disable SSH Support for User Known Hosts |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Unless needed, SSH should not permit extraneous or unnecessary
-authentication mechanisms like GSSAPI.
-
-The default SSH configuration disallows authentications based on GSSAPI. The appropriate
-configuration is used if no value is set for GSSAPIAuthentication.
-
-To explicitly disable GSSAPI authentication, add or correct the following line in
+ | 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:
-GSSAPIAuthentication no |
+IgnoreUserKnownHosts yes
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To determine how the SSH daemon's GSSAPIAuthentication option is set, run the following command:
+ | To determine how the SSH daemon's IgnoreUserKnownHosts option is set, run the following command:
-$ sudo grep -i GSSAPIAuthentication /etc/ssh/sshd_config
+$ sudo grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config
-If a line indicating no is returned, then the required value is set.
+If a line indicating yes is returned, then the required value is set.
Is it the case that the required value is not set? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Unless needed, SSH should not permit extraneous or unnecessary
-authentication mechanisms like GSSAPI.
-
-The default SSH configuration disallows authentications based on GSSAPI. The appropriate
-configuration is used if no value is set for GSSAPIAuthentication.
-
-To explicitly disable GSSAPI authentication, add or correct the following line in
+ | 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 |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00227 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ CCE-81038-2: Disable Core Dumps for All Users |
-/etc/ssh/sshd_config:
+ Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
-GSSAPIAuthentication no |
+Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.
+ To disable core dumps for all users, add the following line to
+/etc/security/limits.conf, or to a file within the
+/etc/security/limits.d/ directory:
+* hard core 0 |
+ Applicable - Configurable |
+ Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
+ Verify that core dumps are disabled for all users, run the following command:
+$ grep core /etc/security/limits.conf
+* hard core 0 Is it the case that the "core" item is missing, commented out, or the value is anything other than "0" and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core"? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ To disable core dumps for all users, add the following line to
+/etc/security/limits.conf, or to a file within the
+/etc/security/limits.d/ directory:
+* hard core 0 |
medium |
|
|
@@ -57646,24 +57494,19 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80921-0: Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces by Default |
+ CCE-82436-7: Uninstall tftp-server Package |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ The tftp-server package can be removed with the following command: $ sudo yum erase tftp-server |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv4.conf.default.send_redirects kernel parameter can be queried
-by running the following command:
-$ sysctl net.ipv4.conf.default.send_redirects
-0.
- Is it the case that the correct value is not returned? |
+ Run the following command to determine if the tftp-server package is installed:
+$ rpm -q tftp-server Is it the case that the package is installed? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
- medium |
+ The tftp-server package can be removed with the following command: $ sudo yum erase tftp-server |
+ high |
|
|
|
@@ -57675,29 +57518,26 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82201-5: Resolve information before writing to audit logs |
+ CCE-82233-8: Include Local Events in Audit Logs |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To configure Audit daemon to resolve all uid, gid, syscall,
-architecture, and socket address information before writing the
-events to disk, set log_format to ENRICHED
-in /etc/audit/auditd.conf. |
+ To configure Audit daemon to include local events in Audit logs, set
+local_events to yes in /etc/audit/auditd.conf.
+This is the default setting. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify that Audit Daemon is configured to resolve all uid, gid, syscall,
-architecture, and socket address information before writing the event to disk,
-run the following command:
-$ sudo grep log_format /etc/audit/auditd.conf
+ | To verify that Audit Daemon is configured to include local events, run the
+following command:
+$ sudo grep local_events /etc/audit/auditd.conf
The output should return the following:
-log_format = ENRICHED Is it the case that log_format isn't set to ENRICHED? |
+local_events = yes
Is it the case that local_events isn't set to yes?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To configure Audit daemon to resolve all uid, gid, syscall,
-architecture, and socket address information before writing the
-events to disk, set log_format to ENRICHED
-in /etc/audit/auditd.conf. |
- low |
+ To configure Audit daemon to include local events in Audit logs, set
+local_events to yes in /etc/audit/auditd.conf.
+This is the default setting. |
+ medium |
|
|
|
@@ -57709,40 +57549,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80841-0: Prevent Login to Accounts With Empty Password |
+ CCE-80953-3: Restrict usage of ptrace to descendant processes |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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
-
-/etc/pam.d/system-auth and
-/etc/pam.d/password-auth
-
-to prevent logins with empty passwords. |
+ To set the runtime status of the kernel.yama.ptrace_scope kernel parameter, run the following command: $ sudo sysctl -w kernel.yama.ptrace_scope=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.yama.ptrace_scope = 1 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify that null passwords cannot be used, run the following command:
-
-$ grep nullok /etc/pam.d/system-auth /etc/pam.d/password-auth
-
-If this produces any output, it may be possible to log into accounts
-with empty passwords. Remove any instances of the nullok option to
-prevent logins with empty passwords. Is it the case that NULL passwords can be used? |
+ The runtime status of the kernel.yama.ptrace_scope kernel parameter can be queried
+by running the following command:
+$ sysctl kernel.yama.ptrace_scope
+1.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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
-
-/etc/pam.d/system-auth and
-/etc/pam.d/password-auth
-
-to prevent logins with empty passwords. |
- high |
+ To set the runtime status of the kernel.yama.ptrace_scope kernel parameter, run the following command: $ sudo sysctl -w kernel.yama.ptrace_scope=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.yama.ptrace_scope = 1 |
+ medium |
|
|
|
@@ -57754,66 +57578,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80863-4: Ensure Logs Sent To Remote Host |
+ CCE-84040-5: Ensure that Users Path Contains Only Local Directories |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 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:
-*.* @
-
-To use TCP for log message delivery:
-*.* @@
-
-To use RELP for log message delivery:
-*.* :omrelp:
-
-There must be a resolvable DNS CNAME or Alias record set to "" for logs to be sent correctly to the centralized logging utility. |
+ 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. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To ensure logs are sent to a remote host, examine the file
-/etc/rsyslog.conf.
-If using UDP, a line similar to the following should be present:
- *.* @
-If using TCP, a line similar to the following should be present:
- *.* @@
-If using RELP, a line similar to the following should be present:
- *.* :omrelp: Is it the case that no evidence that the audit logs are being off-loaded to another system or media? |
+ Verify that all local interactive user initialization file executable search path statements do not contain statements that will reference a working directory other than user home directories with the following commands:
+
+$ sudo grep -i path= /home/*/.*
+
+/home/[localinteractiveuser]/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin Is it the case that any local interactive user initialization files have executable search path statements that include directories outside of their home directory and is not documented with the ISSO as an operational requirement? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 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:
-*.* @
-
-To use TCP for log message delivery:
-*.* @@
-
-To use RELP for log message delivery:
-*.* :omrelp:
-
-There must be a resolvable DNS CNAME or Alias record set to "" for logs to be sent correctly to the centralized logging utility. |
+ 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. |
medium |
|
|
@@ -57826,23 +57609,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80922-8: Enable Kernel Parameter to Ignore ICMP Broadcast Echo Requests on IPv4 Interfaces |
+ CCE-82215-5: Disable storing core dumps |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ To set the runtime status of the kernel.core_pattern kernel parameter, run the following command: $ sudo sysctl -w kernel.core_pattern=|/bin/false
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.core_pattern = |/bin/false |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv4.icmp_echo_ignore_broadcasts kernel parameter can be queried
+ | The runtime status of the kernel.core_pattern kernel parameter can be queried
by running the following command:
-$ sysctl net.ipv4.icmp_echo_ignore_broadcasts
-1.
- Is it the case that the correct value is not returned? |
+$ sysctl kernel.core_pattern
+|/bin/false.
+ Is it the case that the returned line does not have a value of "|/bin/false", or a line is not
+returned and the need for core dumps is not documented with the Information
+System Security Officer (ISSO) as an operational requirement?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
+ To set the runtime status of the kernel.core_pattern kernel parameter, run the following command: $ sudo sysctl -w kernel.core_pattern=|/bin/false
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.core_pattern = |/bin/false |
medium |
|
|
@@ -57855,45 +57640,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84058-7: Prevent remote hosts from connecting to the proxy display |
+ CCE-82028-2: Disable ATM Support |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The SSH daemon should prevent remote hosts from connecting to the proxy
-display.
-
-The default SSH configuration for X11UseLocalhost is yes,
-which prevents remote hosts from connecting to the proxy display.
-
-To explicitly prevent remote connections to the proxy display, add or correct
-the following line in
-
+ | The Asynchronous Transfer Mode (ATM) is a protocol operating on
+network, data link, and physical layers, based on virtual circuits
+and virtual paths.
-/etc/ssh/sshd_config:
+To configure the system to prevent the atm
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/atm.conf:
+install atm /bin/true
-X11UseLocalhost yes |
+To configure the system to prevent the atm from being used,
+add the following line to file /etc/modprobe.d/atm.conf:
+blacklist atm
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To determine how the SSH daemon's X11UseLocalhost option is set, run the following command:
+ |
+If the system is configured to prevent the loading of the atm kernel module,
+it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
+These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
-$ sudo grep -i X11UseLocalhost /etc/ssh/sshd_config
+These lines can also instruct the module loading system to ignore the atm kernel module via blacklist keyword.
-If a line indicating yes is returned, then the required value is set. Is it the case that the display proxy is listening on wildcard address? |
+Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
+$ grep -r atm /etc/modprobe.conf /etc/modprobe.d
Is it the case that no line is returned?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The SSH daemon should prevent remote hosts from connecting to the proxy
-display.
-
-The default SSH configuration for X11UseLocalhost is yes,
-which prevents remote hosts from connecting to the proxy display.
-
-To explicitly prevent remote connections to the proxy display, add or correct
-the following line in
-
+ | The Asynchronous Transfer Mode (ATM) is a protocol operating on
+network, data link, and physical layers, based on virtual circuits
+and virtual paths.
-/etc/ssh/sshd_config:
+To configure the system to prevent the atm
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/atm.conf:
+install atm /bin/true
-X11UseLocalhost yes |
+To configure the system to prevent the atm from being used,
+add the following line to file /etc/modprobe.d/atm.conf:
+blacklist atm
medium |
|
|
@@ -57906,38 +57691,56 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80902-0: Disable SSH Support for User Known Hosts |
+ CCE-80865-9: Ensure Software Patches Installed |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- SSH can allow system users to connect to systems if a cache of the remote
-systems public keys is available. This should be disabled.
+ |
+If the system is joined to the Red Hat Network, a Red Hat Satellite Server,
+or a yum server, run the following command to install updates:
+$ sudo yum update
+If the system is not configured to use one of these sources, updates (in the form of RPM packages)
+can be manually downloaded from the Red Hat Network and installed using rpm.
+
-To ensure this behavior is disabled, add or correct the following line in
+NOTE: U.S. Defense systems are required to be patched within 30 days or sooner as local policy
+dictates. |
+ Applicable - Configurable |
+ Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
+ Verify Red Hat Enterprise Linux 8 security patches and updates are installed and up to date.
+Updates are required to be applied with a frequency determined by organizational policy.
-/etc/ssh/sshd_config:
+Obtain the list of available package security updates from Red Hat. The URL for updates is https://access.redhat.com/errata-search/.
+It is important to note that updates provided by Red Hat may not be present on the system if the underlying packages are not installed.
-IgnoreUserKnownHosts yes |
- Applicable - Configurable |
- Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To determine how the SSH daemon's IgnoreUserKnownHosts option is set, run the following command:
-$ sudo grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config
+Check that the available package security updates have been installed on the system with the following command:
-If a line indicating yes is returned, then the required value is set.
- Is it the case that the required value is not set? |
- Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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
+$ sudo yum history list | more
+Loaded plugins: langpacks, product-id, subscription-manager
+ID | Command line | Date and time | Action(s) | Altered
+-------------------------------------------------------------------------------
+70 | install aide | 2020-03-05 10:58 | Install | 1
+69 | update -y | 2020-03-04 14:34 | Update | 18 EE
+68 | install vlc | 2020-02-21 17:12 | Install | 21
+67 | update -y | 2020-02-21 17:04 | Update | 7 EE
-/etc/ssh/sshd_config:
-IgnoreUserKnownHosts yes |
+Typical update frequency may be overridden by Information Assurance Vulnerability Alert (IAVA) notifications from CYBERCOM. Is it the case that Red Hat Enterprise Linux 8 is in non-compliance with the organizational patching policy?
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+
+If the system is joined to the Red Hat Network, a Red Hat Satellite Server,
+or a yum server, run the following command to install updates:
+$ sudo yum update
+If the system is not configured to use one of these sources, updates (in the form of RPM packages)
+can be manually downloaded from the Red Hat Network and installed using rpm.
+
+
+NOTE: U.S. Defense systems are required to be patched within 30 days or sooner as local policy
+dictates. |
medium |
|
|
@@ -57950,26 +57753,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81039-0: Uninstall Sendmail Package |
+ CCE-86377-9: Ensure sudo only includes the default configuration directory |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Sendmail is not the default mail transfer agent and is
-not installed by default.
-The sendmail package can be removed with the following command:
-
-$ sudo yum erase sendmail |
+ Administrators can configure authorized sudo users via drop-in files, and it is possible to include
+other directories and configuration files from the file currently being parsed.
+
+Make sure that /etc/sudoers only includes drop-in configuration files from /etc/sudoers.d,
+or that no drop-in file is included.
+Either the /etc/sudoers should contain only one #includedir directive pointing to
+/etc/sudoers.d, and no file in /etc/sudoers.d/ should include other files or directories;
+Or the /etc/sudoers should not contain any #include,
+@include, #includedir or @includedir directives.
+Note that the '#' character doesn't denote a comment in the configuration file. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Run the following command to determine if the sendmail package is installed:
-$ rpm -q sendmail Is it the case that the package is installed? |
+ To determine whether sudo command includes configuration files from the appropriate directory,
+run the following command:
+$ sudo grep -rP '^[#@]include(dir)?' /etc/sudoers /etc/sudoers.d
+If only the line /etc/sudoers:#includedir /etc/sudoers.d is returned, then the drop-in include configuration is set correctly.
+Any other line returned is a finding. Is it the case that the /etc/sudoers doesn't include /etc/sudores.d or includes other directories?? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Sendmail is not the default mail transfer agent and is
-not installed by default.
-The sendmail package can be removed with the following command:
-
-$ sudo yum erase sendmail |
+ Administrators can configure authorized sudo users via drop-in files, and it is possible to include
+other directories and configuration files from the file currently being parsed.
+
+Make sure that /etc/sudoers only includes drop-in configuration files from /etc/sudoers.d,
+or that no drop-in file is included.
+Either the /etc/sudoers should contain only one #includedir directive pointing to
+/etc/sudoers.d, and no file in /etc/sudoers.d/ should include other files or directories;
+Or the /etc/sudoers should not contain any #include,
+@include, #includedir or @includedir directives.
+Note that the '#' character doesn't denote a comment in the configuration file. |
medium |
|
|
@@ -57982,48 +57798,58 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80785-9: Disable Ctrl-Alt-Del Reboot Activation |
+ CCE-80876-6: Disable debug-shell SystemD Service |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- By default, SystemD will reboot the system if the Ctrl-Alt-Del
-key sequence is pressed.
+ | SystemD's debug-shell service is intended to
+diagnose SystemD related boot issues with various systemctl
+commands. Once enabled and following a system reboot, the root shell
+will be available on tty9 which is access by pressing
+CTRL-ALT-F9. The debug-shell service should only be used
+for SystemD related issues and should otherwise be disabled.
-To configure the system to ignore the Ctrl-Alt-Del key sequence from the
+By default, the debug-shell SystemD service is already disabled.
-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. |
+The debug-shell service can be disabled with the following command:
+$ sudo systemctl mask --now debug-shell.service
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To ensure the system is configured to mask the Ctrl-Alt-Del sequence, Check
-that the ctrl-alt-del.target is masked and not active with the following
-command:
-sudo systemctl status ctrl-alt-del.target
-The output should indicate that the target is masked and not active. It
-might resemble following output:
-ctrl-alt-del.target
-Loaded: masked (/dev/null; bad)
-Active: inactive (dead) Is it the case that the system is configured to reboot when Ctrl-Alt-Del is pressed? |
+ To check that the debug-shell service is disabled in system boot configuration,
+run the following command:
+$ sudo systemctl is-enabled debug-shell
+Output should indicate the debug-shell service has either not been installed,
+or has been disabled at all runlevels, as shown in the example below:
+$ sudo systemctl is-enabled debug-shell
disabled
+
+Run the following command to verify debug-shell is not active (i.e. not running) through current runtime configuration:
+$ sudo systemctl is-active debug-shell
+
+If the service is not running the command will return the following output:
+inactive
+
+The service will also be masked, to check that the debug-shell is masked, run the following command:
+$ sudo systemctl show debug-shell | grep "LoadState\|UnitFileState"
+
+If the service is masked the command will return the following outputs:
+
+LoadState=masked
+
+UnitFileState=masked Is it the case that the "debug-shell" is loaded and not masked? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- By default, SystemD will reboot the system if the Ctrl-Alt-Del
-key sequence is pressed.
+ | SystemD's debug-shell service is intended to
+diagnose SystemD related boot issues with various systemctl
+commands. Once enabled and following a system reboot, the root shell
+will be available on tty9 which is access by pressing
+CTRL-ALT-F9. The debug-shell service should only be used
+for SystemD related issues and should otherwise be disabled.
-To configure the system to ignore the Ctrl-Alt-Del key sequence from the
+By default, the debug-shell SystemD service is already disabled.
-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. |
- high |
+The debug-shell service can be disabled with the following command:
+$ sudo systemctl mask --now debug-shell.service
+ medium |
|
|
|
@@ -58035,19 +57861,29 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82436-7: Uninstall tftp-server Package |
+ CCE-82201-5: Resolve information before writing to audit logs |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The tftp-server package can be removed with the following command: $ sudo yum erase tftp-server |
+ To configure Audit daemon to resolve all uid, gid, syscall,
+architecture, and socket address information before writing the
+events to disk, set log_format to ENRICHED
+in /etc/audit/auditd.conf. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Run the following command to determine if the tftp-server package is installed:
-$ rpm -q tftp-server Is it the case that the package is installed? |
+ To verify that Audit Daemon is configured to resolve all uid, gid, syscall,
+architecture, and socket address information before writing the event to disk,
+run the following command:
+$ sudo grep log_format /etc/audit/auditd.conf
+The output should return the following:
+log_format = ENRICHED Is it the case that log_format isn't set to ENRICHED? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The tftp-server package can be removed with the following command: $ sudo yum erase tftp-server |
- high |
+ To configure Audit daemon to resolve all uid, gid, syscall,
+architecture, and socket address information before writing the
+events to disk, set log_format to ENRICHED
+in /etc/audit/auditd.conf. |
+ low |
|
|
|
@@ -58059,24 +57895,22 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80953-3: Restrict usage of ptrace to descendant processes |
+ CCE-82968-9: Install rng-tools Package |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To set the runtime status of the kernel.yama.ptrace_scope kernel parameter, run the following command: $ sudo sysctl -w kernel.yama.ptrace_scope=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.yama.ptrace_scope = 1 |
+ The rng-tools package can be installed with the following command:
+
+$ sudo yum install rng-tools |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the kernel.yama.ptrace_scope kernel parameter can be queried
-by running the following command:
-$ sysctl kernel.yama.ptrace_scope
-1.
- Is it the case that the correct value is not returned? |
+ Run the following command to determine if the rng-tools package is installed: $ rpm -q rng-tools Is it the case that the package is not installed? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To set the runtime status of the kernel.yama.ptrace_scope kernel parameter, run the following command: $ sudo sysctl -w kernel.yama.ptrace_scope=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.yama.ptrace_scope = 1 |
- medium |
+ The rng-tools package can be installed with the following command:
+
+$ sudo yum install rng-tools |
+ low |
|
|
|
@@ -58088,51 +57922,88 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80835-2: Disable Modprobe Loading of USB Storage Driver |
+ CCE-80853-5: Ensure /var/log Located On Separate Partition |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To prevent USB storage devices from being used, configure the kernel module loading system
-to prevent automatic loading of the USB storage driver.
+ | System logs are stored in the /var/log directory.
-To configure the system to prevent the usb-storage
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/usb-storage.conf:
-install usb-storage /bin/true
+Ensure that /var/log has its own partition or logical
+volume at installation time, or migrate it using LVM. |
+ Applicable - Configurable |
+ Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
+ Verify that a separate file system/partition has been created for /var/log with the following command:
-To configure the system to prevent the usb-storage from being used,
-add the following line to file /etc/modprobe.d/usb-storage.conf:
-blacklist usb-storage
+$ mountpoint /var/log
+ Is it the case that "/var/log is not a mountpoint" is returned? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ System logs are stored in the /var/log directory.
-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. |
+Ensure that /var/log has its own partition or logical
+volume at installation time, or migrate it using LVM.
+ low |
+ |
+ |
+ |
+
+
+
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00227 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+
+ CCE-80886-5: Enable rsyslog Service |
+
+ Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
+
+Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
+ The rsyslog service provides syslog-style logging by default on Red Hat Enterprise Linux 8.
+
+The rsyslog service can be enabled with the following command:
+$ sudo systemctl enable rsyslog.service |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
-If the system is configured to prevent the loading of the usb-storage kernel module,
-it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
-These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
-These lines can also instruct the module loading system to ignore the usb-storage kernel module via blacklist keyword.
+Run the following command to determine the current status of the
+rsyslog service:
+$ sudo systemctl is-active rsyslog
+If the service is running, it should return the following: active Is it the case that the "rsyslog" service is disabled, masked, or not started.? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ The rsyslog service provides syslog-style logging by default on Red Hat Enterprise Linux 8.
+
+The rsyslog service can be enabled with the following command:
+$ sudo systemctl enable rsyslog.service |
+ medium |
+ |
+ |
+ |
+
-Run the following command to search for such lines in all files in
/etc/modprobe.d and the deprecated
/etc/modprobe.conf:
-
$ grep -r usb-storage /etc/modprobe.conf /etc/modprobe.d
Is it the case that no line is returned?
-
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-
To prevent USB storage devices from being used, configure the kernel module loading system
-to prevent automatic loading of the USB storage driver.
+ |
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00227 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-To configure the system to prevent the usb-storage
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/usb-storage.conf:
-install usb-storage /bin/true
+ CCE-82943-2: Uninstall gssproxy Package |
-To configure the system to prevent the usb-storage from being used,
-add the following line to file /etc/modprobe.d/usb-storage.conf:
-blacklist usb-storage
+ Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
-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. |
+Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.
+ The gssproxy package can be removed with the following command:
+
+$ sudo yum erase gssproxy |
+ Applicable - Configurable |
+ Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
+ Run the following command to determine if the gssproxy package is installed:
+$ rpm -q gssproxy Is it the case that the package is installed? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ The gssproxy package can be removed with the following command:
+
+$ sudo yum erase gssproxy |
medium |
|
|
@@ -58145,44 +58016,42 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80898-0: Disable Kerberos Authentication |
+ CCE-82281-7: Enable SSH Print Last Log |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Unless needed, SSH should not permit extraneous or unnecessary
-authentication mechanisms like Kerberos.
+ | Ensure that SSH will display the date and time of the last successful account logon.
-The default SSH configuration disallows authentication validation through Kerberos.
-The appropriate configuration is used if no value is set for KerberosAuthentication.
+The default SSH configuration enables print of the date and time of the last login.
+The appropriate configuration is used if no value is set for PrintLastLog.
-To explicitly disable Kerberos authentication, add or correct the following line in
+To explicitly enable LastLog in SSH, add or correct the following line in
/etc/ssh/sshd_config:
-KerberosAuthentication no |
+PrintLastLog yes
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To determine how the SSH daemon's KerberosAuthentication option is set, run the following command:
+ | To determine how the SSH daemon's PrintLastLog option is set, run the following command:
-$ sudo grep -i KerberosAuthentication /etc/ssh/sshd_config
+$ sudo grep -i PrintLastLog /etc/ssh/sshd_config
-If a line indicating no is returned, then the required value is set.
+If a line indicating yes is returned, then the required value is set.
Is it the case that the required value is not set? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Unless needed, SSH should not permit extraneous or unnecessary
-authentication mechanisms like Kerberos.
+ | Ensure that SSH will display the date and time of the last successful account logon.
-The default SSH configuration disallows authentication validation through Kerberos.
-The appropriate configuration is used if no value is set for KerberosAuthentication.
+The default SSH configuration enables print of the date and time of the last login.
+The appropriate configuration is used if no value is set for PrintLastLog.
-To explicitly disable Kerberos authentication, add or correct the following line in
+To explicitly enable LastLog in SSH, add or correct the following line in
/etc/ssh/sshd_config:
-KerberosAuthentication no |
+PrintLastLog yes
medium |
|
|
@@ -58195,24 +58064,31 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84043-9: Ensure All User Initialization Files Have Mode 0740 Or Less Permissive |
+ CCE-83425-9: The operating system must restrict privilege elevation to authorized personnel |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Set the mode of the user initialization files to 0740 with the
-following command:
-$ sudo chmod 0740 /home/USER/.INIT_FILE |
+ 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) ALL |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify that all user initialization files have a mode of 0740 or
-less permissive, run the following command:
-$ sudo find /home -type f -name '\.*' \( -perm -0002 -o -perm -0020 \)
-There should be no output. Is it the case that they are not 0740 or more permissive? |
+ Determine if "sudoers" file restricts sudo access run the following commands:
+$ sudo grep -PR '^\s*ALL\s+ALL\=\(ALL\)\s+ALL\s*$' /etc/sudoers /etc/sudoers.d/*
+$ sudo grep -PR '^\s*ALL\s+ALL\=\(ALL\:ALL\)\s+ALL\s*$' /etc/sudoers /etc/sudoers.d/* Is it the case that either of the commands returned a line? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Set the mode of the user initialization files to 0740 with the
-following command:
-$ sudo chmod 0740 /home/USER/.INIT_FILE |
+ 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) ALL |
medium |
|
|
@@ -58225,28 +58101,33 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84044-7: Ensure the Default Umask is Set Correctly For Interactive Users |
+ CCE-84036-3: All Interactive Users Must Have A Home Directory Defined |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Remove the UMASK environment variable from all interactive users initialization files. |
+ Assign home directories to all interactive users that currently do not
+have a home directory assigned.
+
+This rule checks if the home directory is properly defined in a folder which has
+at least one parent folder, like "user" in "/home/user" or "/remote/users/user".
+Therefore, this rule will report a finding for home directories like /users,
+/tmp or /. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify that the default umask for all local interactive users is "077".
-
-Identify the locations of all local interactive user home directories by looking at the "/etc/passwd" file.
-
-Check all local interactive user initialization files for interactive users with the following command:
-
-Note: The example is for a system that is configured to create users home directories in the "/home" directory.
+ | Verify that interactive users on the system have a home directory assigned with the following command:
-# grep -ri umask /home/
+$ sudo awk -F: '($3>=1000)&&($7 !~ /nologin/){print $1, $3, $6}' /etc/passwd
-/home/smithj/.bash_history:grep -i umask /etc/bashrc /etc/csh.cshrc /etc/profile
-/home/smithj/.bash_history:grep -i umask /etc/login.defs Is it the case that any local interactive user initialization files are found to have a umask statement that sets a value less restrictive than "077"? |
+Inspect the output and verify that all interactive users (normally users with a UID greater than 1000) have a home directory defined. Is it the case that users home directory is not defined?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Remove the UMASK environment variable from all interactive users initialization files. |
+ Assign home directories to all interactive users that currently do not
+have a home directory assigned.
+
+This rule checks if the home directory is properly defined in a folder which has
+at least one parent folder, like "user" in "/home/user" or "/remote/users/user".
+Therefore, this rule will report a finding for home directories like /users,
+/tmp or /. |
medium |
|
|
@@ -58259,25 +58140,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82424-3: Verify Permissions on SSH Server Private *_key Key Files |
+ CCE-82252-8: Disable storing core dump |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- SSH server private keys - files that match the /etc/ssh/*_key glob, have to have restricted permissions.
-If those files are owned by the root user and the root group, they have to have the 0600 permission or stricter.
-If they are owned by the root user, but by a dedicated group ssh_keys, they can have the 0640 permission or stricter. |
+ The Storage option in [Coredump] sectionof /etc/systemd/coredump.conf
+can be set to none to disable storing core dumps permanently. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To check the permissions of /etc/ssh/*_key,
-run the command:
-$ ls -l /etc/ssh/*_key
-If properly configured, the output should indicate the following permissions:
--rw------- Is it the case that /etc/ssh/*_key does not have unix mode -rw-------? |
+ Verify Red Hat Enterprise Linux 8 disables storing core dumps for all users by issuing the following command:
+
+$ grep -i storage /etc/systemd/coredump.conf
+
+Storage=none Is it the case that Storage is not set to none or is commented out and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core" item assigned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- SSH server private keys - files that match the /etc/ssh/*_key glob, have to have restricted permissions.
-If those files are owned by the root user and the root group, they have to have the 0600 permission or stricter.
-If they are owned by the root user, but by a dedicated group ssh_keys, they can have the 0640 permission or stricter. |
+ The Storage option in [Coredump] sectionof /etc/systemd/coredump.conf
+can be set to none to disable storing core dumps permanently. |
medium |
|
|
@@ -58290,24 +58169,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80920-2: Disable Kernel Parameter for Accepting Source-Routed Packets on IPv4 Interfaces by Default |
+ CCE-84055-3: Remove Host-Based Authentication Files |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ The shosts.equiv file lists 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv4.conf.default.accept_source_route kernel parameter can be queried
-by running the following command:
-$ sysctl net.ipv4.conf.default.accept_source_route
-0.
- Is it the case that the correct value is not returned? |
+ Verify that there are no shosts.equiv files on the system, run the following command:
+$ find / -name shosts.equiv Is it the case that shosts.equiv files exist? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
- medium |
+ The shosts.equiv file lists 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 |
+ high |
|
|
|
@@ -58319,48 +58197,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-86195-5: Disable the GNOME3 Login User List |
+ CCE-82424-3: Verify Permissions on SSH Server Private *_key Key Files |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- In the default graphical environment, users logging directly into the
-system are greeted with a login screen that displays all known users.
-This functionality should be disabled by setting disable-user-list
-to true.
-
-To disable, add or edit disable-user-list to
-/etc/dconf/db/gdm.d/00-security-settings. For example:
-[org/gnome/login-screen]
-disable-user-list=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/disable-user-list
-After the settings have been set, run dconf update. |
+ SSH server private keys - files that match the /etc/ssh/*_key glob, have to have restricted permissions.
+If those files are owned by the root user and the root group, they have to have the 0600 permission or stricter.
+If they are owned by the root user, but by a dedicated group ssh_keys, they can have the 0640 permission or stricter. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To ensure the user list is disabled, run the following command:
-$ grep disable-user-list /etc/dconf/db/gdm.d/*
-The output should be true.
-To ensure that users cannot enable displaying the user list, run the following:
-$ grep disable-user-list /etc/dconf/db/gdm.d/locks/*
-If properly configured, the output should be /org/gnome/login-screen/disable-user-list Is it the case that disable-user-list has not been configured or is not disabled? |
+ To check the permissions of /etc/ssh/*_key,
+run the command:
+$ ls -l /etc/ssh/*_key
+If properly configured, the output should indicate the following permissions:
+-rw------- Is it the case that /etc/ssh/*_key does not have unix mode -rw-------? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- In the default graphical environment, users logging directly into the
-system are greeted with a login screen that displays all known users.
-This functionality should be disabled by setting disable-user-list
-to true.
-
-To disable, add or edit disable-user-list to
-/etc/dconf/db/gdm.d/00-security-settings. For example:
-[org/gnome/login-screen]
-disable-user-list=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/disable-user-list
-After the settings have been set, run dconf update. |
+ SSH server private keys - files that match the /etc/ssh/*_key glob, have to have restricted permissions.
+If those files are owned by the root user and the root group, they have to have the 0600 permission or stricter.
+If they are owned by the root user, but by a dedicated group ssh_keys, they can have the 0640 permission or stricter. |
medium |
|
|
@@ -58373,48 +58228,49 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-83422-6: Ensure invoking users password for privilege escalation when using sudo |
+ CCE-80896-4: Disable SSH Access via Empty Passwords |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 cvtsudoers -f sudoers /etc/sudoers | grep -E '^Defaults !?(rootpw|targetpw|runaspw)$'
- Defaults !targetpw
- Defaults !rootpw
- Defaults !runaspw
-or if cvtsudoers not supported:
- sudo find /etc/sudoers /etc/sudoers.d \( \! -name '*~' -a \! -name '*.*' \) -exec grep -E --with-filename '^[[:blank:]]*Defaults[[:blank:]](.*[[:blank:]])?!?\b(rootpw|targetpw|runaspw)' -- {} \;
- /etc/sudoers:Defaults !targetpw
- /etc/sudoers:Defaults !rootpw
- /etc/sudoers:Defaults !runaspw |
+ Disallow SSH login with empty passwords.
+The default SSH configuration disables logins with empty passwords. The appropriate
+configuration is used if no value is set for PermitEmptyPasswords.
+
+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. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Run the following command to Verify that the sudoers security policy is configured to use the invoking user's password for privilege escalation:
- sudo cvtsudoers -f sudoers /etc/sudoers | grep -E '^Defaults !?(rootpw|targetpw|runaspw)'
-or if cvtsudoers not supported:
- sudo find /etc/sudoers /etc/sudoers.d \( \! -name '*~' -a \! -name '*.*' \) -exec grep -E --with-filename '^[[:blank:]]*Defaults[[:blank:]](.*[[:blank:]])?!?\b(rootpw|targetpw|runaspw)' -- {} \;
-If no results are returned, this is a finding.
-If conflicting results are returned, this is a finding.
-If "Defaults !targetpw" is not defined, this is a finding.
-If "Defaults !rootpw" is not defined, this is a finding.
-If "Defaults !runaspw" is not defined, this is a finding. Is it the case that invoke user passwd when using sudo? |
+ To determine how the SSH daemon's PermitEmptyPasswords option is set, run the following command:
+
+$ sudo grep -i PermitEmptyPasswords /etc/ssh/sshd_config
+
+If a line indicating no is returned, then the required value is set.
+ Is it the case that the required value is not set? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 cvtsudoers -f sudoers /etc/sudoers | grep -E '^Defaults !?(rootpw|targetpw|runaspw)$'
- Defaults !targetpw
- Defaults !rootpw
- Defaults !runaspw
-or if cvtsudoers not supported:
- sudo find /etc/sudoers /etc/sudoers.d \( \! -name '*~' -a \! -name '*.*' \) -exec grep -E --with-filename '^[[:blank:]]*Defaults[[:blank:]](.*[[:blank:]])?!?\b(rootpw|targetpw|runaspw)' -- {} \;
- /etc/sudoers:Defaults !targetpw
- /etc/sudoers:Defaults !rootpw
- /etc/sudoers:Defaults !runaspw |
- medium |
+ Disallow SSH login with empty passwords.
+The default SSH configuration disables logins with empty passwords. The appropriate
+configuration is used if no value is set for PermitEmptyPasswords.
+
+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. |
+ high |
|
|
|
@@ -58426,17 +58282,29 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80847-7: Ensure rsyslog is Installed |
+ CCE-83424-2: All Interactive Users Home Directories Must Exist |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
+ Create home directories to all local 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Run the following command to determine if the rsyslog package is installed: $ rpm -q rsyslog Is it the case that the package is not installed? |
+ Verify the assigned home directories of all interactive users on the system exist with the following command:
+
+$ sudo pwck -r
+
+user 'mailnull': directory 'var/spool/mqueue' does not exist
+
+The output should not return any interactive users. Is it the case that users home directory does not exist? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
+ Create home directories to all local 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 |
medium |
|
|
@@ -58449,19 +58317,38 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82414-4: Uninstall vsftpd Package |
+ CCE-84220-3: Configure AIDE to Verify Access Control Lists (ACLs) |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The vsftpd package can be removed with the following command: $ sudo yum erase vsftpd |
+ 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 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Run the following command to determine if the vsftpd package is installed:
-$ rpm -q vsftpd Is it the case that the package is installed? |
+ To determine that AIDE is verifying ACLs, run the following command:
+$ grep acl /etc/aide.conf
+Verify that the acl option is added to the correct ruleset. Is it the case that the acl option is missing or not added to the correct ruleset? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The vsftpd package can be removed with the following command: $ sudo yum erase vsftpd |
- high |
+ 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 |
+ low |
|
|
|
@@ -58473,45 +58360,62 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82028-2: Disable ATM Support |
+ CCE-82069-6: Add nodev Option to Non-Root Local Partitions |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The Asynchronous Transfer Mode (ATM) is a protocol operating on
-network, data link, and physical layers, based on virtual circuits
-and virtual paths.
-
-To configure the system to prevent the atm
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/atm.conf:
-install atm /bin/true
+ | The nodev mount option prevents files from being interpreted as
+character or block devices. Legitimate character and block devices should
+exist only in the /dev directory on the root partition or within
+chroot jails built for system services.
+Add the nodev option to the fourth column of
+/etc/fstab for the line which controls mounting of
-To configure the system to prevent the atm from being used,
-add the following line to file /etc/modprobe.d/atm.conf:
-blacklist atm |
+ any non-root local partitions.
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
-
-If the system is configured to prevent the loading of the atm kernel module,
-it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
-These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
+ | To verify the nodev option is configured for non-root local partitions, run the following command:
+$ sudo mount | grep '^/dev\S* on /\S' | grep --invert-match 'nodev'
+The output shows local non-root partitions mounted without the nodev option, and there should be no output at all.
+ Is it the case that some mounts appear among output lines? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ The nodev mount option prevents files from being interpreted as
+character or block devices. Legitimate character and block devices should
+exist only in the /dev directory on the root partition or within
+chroot jails built for system services.
+Add the nodev option to the fourth column of
+/etc/fstab for the line which controls mounting of
-These lines can also instruct the module loading system to ignore the atm kernel module via blacklist keyword.
+ any non-root local partitions. |
+ medium |
+ |
+ |
+ |
+
-Run the following command to search for such lines in all files in
/etc/modprobe.d and the deprecated
/etc/modprobe.conf:
-
$ grep -r atm /etc/modprobe.conf /etc/modprobe.d
Is it the case that no line is returned?
-
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-
The Asynchronous Transfer Mode (ATM) is a protocol operating on
-network, data link, and physical layers, based on virtual circuits
-and virtual paths.
+ |
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00227 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
-To configure the system to prevent the atm
-kernel module from being loaded, add the following line to the file /etc/modprobe.d/atm.conf:
-install atm /bin/true
+ CCE-84050-4: Mount Remote Filesystems with noexec |
-To configure the system to prevent the atm from being used,
-add the following line to file /etc/modprobe.d/atm.conf:
-blacklist atm
+ Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
+
+Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
+ Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of
+any NFS mounts. |
+ Applicable - Configurable |
+ Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
+ To verify the noexec option is configured for all NFS mounts, run the following command:
+$ mount | grep nfs
+All NFS mounts should show the noexec setting in parentheses. This is not applicable if NFS is
+not implemented. Is it the case that the setting does not show? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of
+any NFS mounts. |
medium |
|
|
@@ -58524,29 +58428,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80788-3: Ensure PAM Displays Last Logon/Access Notification |
+ CCE-80851-9: Ensure /tmp Located On Separate Partition |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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/postlogin
-to include showfailed option, such as:
-session [default=1] pam_lastlog.so showfailed
-And make sure that the silent option is not set for this specific line. |
+ The /tmp directory is a world-writable directory used
+for temporary file storage. Ensure it has its own partition or
+logical volume at installation time, or migrate it using LVM. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify users are provided with feedback on when account accesses last occurred with the following command:
-
-$ sudo grep pam_lastlog /etc/pam.d/postlogin
+ Verify that a separate file system/partition has been created for /tmp with the following command:
-session [default=1] pam_lastlog.so showfailed Is it the case that "pam_lastlog.so" is not properly configured in "/etc/pam.d/postlogin" file? |
+$ mountpoint /tmp
+ Is it the case that "/tmp is not a mountpoint" is returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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/postlogin
-to include showfailed option, such as:
-session [default=1] pam_lastlog.so showfailed
-And make sure that the silent option is not set for this specific line. |
+ The /tmp directory is a world-writable directory used
+for temporary file storage. Ensure it has its own partition or
+logical volume at installation time, or migrate it using LVM. |
low |
|
|
@@ -58559,36 +58458,48 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80901-2: Disable SSH Root Login |
+ CCE-83360-8: Disable X11 Forwarding |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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
+ | The X11Forwarding parameter provides the ability to tunnel X11 traffic
+through the connection to enable remote graphic connections.
+SSH has the capability to encrypt remote X11 connections when SSH's
+X11Forwarding option is enabled.
+
+The default SSH configuration disables X11Forwarding. The appropriate
+configuration is used if no value is set for X11Forwarding.
+
+To explicitly disable X11 Forwarding, add or correct the following line in
/etc/ssh/sshd_config:
-PermitRootLogin no |
+X11Forwarding no
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To determine how the SSH daemon's PermitRootLogin option is set, run the following command:
+ | To determine how the SSH daemon's X11Forwarding option is set, run the following command:
-$ sudo grep -i PermitRootLogin /etc/ssh/sshd_config
+$ sudo grep -i X11Forwarding /etc/ssh/sshd_config
If a line indicating no is returned, then the required value is set.
Is it the case that the required value is not set? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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
+ | The X11Forwarding parameter provides the ability to tunnel X11 traffic
+through the connection to enable remote graphic connections.
+SSH has the capability to encrypt remote X11 connections when SSH's
+X11Forwarding option is enabled.
+
+The default SSH configuration disables X11Forwarding. The appropriate
+configuration is used if no value is set for X11Forwarding.
+
+To explicitly disable X11 Forwarding, add or correct the following line in
/etc/ssh/sshd_config:
-PermitRootLogin no |
+X11Forwarding no
medium |
|
|
@@ -58601,42 +58512,69 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82177-7: Force frequent session key renegotiation |
+ CCE-80784-2: Disable Ctrl-Alt-Del Burst Action |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The RekeyLimit parameter specifies how often
-the session key of the is renegotiated, both in terms of
-amount of data that may be transmitted and the time
-elapsed.
-To decrease the default limits, add or correct the following line in
+ | By default, SystemD will reboot the system if the Ctrl-Alt-Del
+key sequence is pressed Ctrl-Alt-Delete more than 7 times in 2 seconds.
+
+To configure the system to ignore the CtrlAltDelBurstAction
+
+setting, add or modify the following to /etc/systemd/system.conf:
+CtrlAltDelBurstAction=none |
+ Applicable - Configurable |
+ Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
+ To ensure the system is configured to ignore the Ctrl-Alt-Del setting,
+enter the following command:
+$ sudo grep -i ctrlaltdelburstaction /etc/systemd/system.conf
+The output should return:
+CtrlAltDelBurstAction=none Is it the case that the system is configured to reboot when Ctrl-Alt-Del is pressed more than 7 times in 2 seconds.? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ By default, SystemD will reboot the system if the Ctrl-Alt-Del
+key sequence is pressed Ctrl-Alt-Delete more than 7 times in 2 seconds.
+
+To configure the system to ignore the CtrlAltDelBurstAction
+
+setting, add or modify the following to /etc/systemd/system.conf:
+CtrlAltDelBurstAction=none |
+ high |
+ |
+ |
+ |
+
+
+
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00227 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ CCE-80788-3: Ensure PAM Displays Last Logon/Access Notification |
-/etc/ssh/sshd_config:
+ Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
-RekeyLimit |
+Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.
+ 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/postlogin
+to include showfailed option, such as:
+session [default=1] pam_lastlog.so showfailed
+And make sure that the silent option is not set for this specific line. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To check if RekeyLimit is set correctly, run the
-following command:
+ | Verify users are provided with feedback on when account accesses last occurred with the following command:
-$ sudo grep RekeyLimit /etc/ssh/sshd_config
+$ sudo grep pam_lastlog /etc/pam.d/postlogin
-If configured properly, output should be
-RekeyLimit Is it the case that it is commented out or is not set? |
+session [default=1] pam_lastlog.so showfailed Is it the case that "pam_lastlog.so" is not properly configured in "/etc/pam.d/postlogin" file?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The RekeyLimit parameter specifies how often
-the session key of the is renegotiated, both in terms of
-amount of data that may be transmitted and the time
-elapsed.
-To decrease the default limits, add or correct the following line in
-
-
-/etc/ssh/sshd_config:
-
-RekeyLimit |
- medium |
+ 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/postlogin
+to include showfailed option, such as:
+session [default=1] pam_lastlog.so showfailed
+And make sure that the silent option is not set for this specific line. |
+ low |
|
|
|
@@ -58648,24 +58586,22 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80919-4: Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv4 Interfaces |
+ CCE-82976-2: Install policycoreutils Package |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ The policycoreutils package can be installed with the following command:
+
+$ sudo yum install policycoreutils |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv4.conf.default.accept_redirects kernel parameter can be queried
-by running the following command:
-$ sysctl net.ipv4.conf.default.accept_redirects
-0.
- Is it the case that the correct value is not returned? |
+ Run the following command to determine if the policycoreutils package is installed: $ rpm -q policycoreutils Is it the case that the policycoreutils package is not installed? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
- medium |
+ The policycoreutils package can be installed with the following command:
+
+$ sudo yum install policycoreutils |
+ low |
|
|
|
@@ -58677,23 +58613,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-84052-0: Mount Remote Filesystems with nodev |
+ CCE-81007-7: Disable Accepting Router Advertisements on all IPv6 Interfaces by Default |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of
-any NFS mounts. |
+ To set the runtime status of the net.ipv6.conf.default.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_ra=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_ra = 0 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify the nodev option is configured for all NFS mounts, run
-the following command:
-$ mount | grep nfs
-All NFS mounts should show the nodev setting in parentheses. This
-is not applicable if NFS is not implemented. Is it the case that the setting does not show? |
+ The runtime status of the net.ipv6.conf.default.accept_ra kernel parameter can be queried
+by running the following command:
+$ sysctl net.ipv6.conf.default.accept_ra
+0.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of
-any NFS mounts. |
+ To set the runtime status of the net.ipv6.conf.default.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_ra=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_ra = 0 |
medium |
|
|
@@ -58706,32 +58642,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-83425-9: The operating system must restrict privilege elevation to authorized personnel |
+ CCE-80852-7: Ensure /var Located On Separate Partition |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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) ALL |
+ 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. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Determine if "sudoers" file restricts sudo access run the following commands:
-$ sudo grep -PR '^\s*ALL\s+ALL\=\(ALL\)\s+ALL\s*$' /etc/sudoers /etc/sudoers.d/*
-$ sudo grep -PR '^\s*ALL\s+ALL\=\(ALL\:ALL\)\s+ALL\s*$' /etc/sudoers /etc/sudoers.d/* Is it the case that either of the commands returned a line? |
+ Verify that a separate file system/partition has been created for /var with the following command:
+
+$ mountpoint /var
+ Is it the case that "/var is not a mountpoint" is returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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) ALL |
- medium |
+ 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. |
+ low |
|
|
|
@@ -58743,33 +58672,45 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80664-6: Ensure PAM Enforces Password Requirements - Authentication Retry Prompts Permitted Per-Session |
+ CCE-82059-7: Disable CAN Support |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To configure the number of retry prompts that are permitted per-session:
+ | The Controller Area Network (CAN) is a serial communications
+protocol which was initially developed for automotive and
+is now also used in marine, industrial, and medical applications.
-Edit the /etc/security/pwquality.conf to include
+To configure the system to prevent the can
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/can.conf:
+install can /bin/true
-retry=, or a lower value if site
-policy is more restrictive. The DoD requirement is a maximum of 3 prompts
-per session. |
+To configure the system to prevent the can from being used,
+add the following line to file /etc/modprobe.d/can.conf:
+blacklist can
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 is configured to limit the "pwquality" retry option to .
+ |
+If the system is configured to prevent the loading of the can kernel module,
+it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
+These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
+These lines can also instruct the module loading system to ignore the can kernel module via blacklist keyword.
-Check for the use of the "pwquality" retry option in the pwquality.conf file with the following command:
-$ grep retry /etc/security/pwquality.conf Is it the case that the value of "retry" is set to "0" or greater than "", or is missing? |
+Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
+$ grep -r can /etc/modprobe.conf /etc/modprobe.d
Is it the case that no line is returned?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To configure the number of retry prompts that are permitted per-session:
+ | The Controller Area Network (CAN) is a serial communications
+protocol which was initially developed for automotive and
+is now also used in marine, industrial, and medical applications.
-Edit the /etc/security/pwquality.conf to include
+To configure the system to prevent the can
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/can.conf:
+install can /bin/true
-retry=, or a lower value if site
-policy is more restrictive. The DoD requirement is a maximum of 3 prompts
-per session. |
+To configure the system to prevent the can from being used,
+add the following line to file /etc/modprobe.d/can.conf:
+blacklist can
medium |
|
|
@@ -58782,33 +58723,41 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-83434-1: All Interactive User Home Directories Must Be Group-Owned By The Primary Group |
+ CCE-82177-7: Force frequent session key renegotiation |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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
+ | The RekeyLimit parameter specifies how often
+the session key of the is renegotiated, both in terms of
+amount of data that may be transmitted and the time
+elapsed.
+To decrease the default limits, add or correct the following line in
-This rule ensures every home directory related to an interactive user is
-group-owned by an interactive user. It also ensures that interactive users
-are group-owners of one and only one home directory. |
+
+/etc/ssh/sshd_config:
+
+RekeyLimit
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify the assigned home directory of all interactive users is group-
-owned by that users primary GID, run the following command:
-# ls -ld $(awk -F: '($3>=1000)&&($7 !~ /nologin/){print $6}' /etc/passwd) Is it the case that the group ownership is incorrect? |
+ To check if RekeyLimit is set correctly, run the
+following command:
+
+$ sudo grep RekeyLimit /etc/ssh/sshd_config
+
+If configured properly, output should be
+RekeyLimit Is it the case that it is commented out or is not set? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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
+ | The RekeyLimit parameter specifies how often
+the session key of the is renegotiated, both in terms of
+amount of data that may be transmitted and the time
+elapsed.
+To decrease the default limits, add or correct the following line in
-This rule ensures every home directory related to an interactive user is
-group-owned by an interactive user. It also ensures that interactive users
-are group-owners of one and only one home directory. |
+
+/etc/ssh/sshd_config:
+
+RekeyLimit
medium |
|
|
@@ -58821,27 +58770,35 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-85888-6: All User Files and Directories In The Home Directory Must Have Mode 0750 Or Less Permissive |
+ CCE-80649-7: Verify Only Root Has UID 0 |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Set the mode on files and directories in the local interactive user home
-directory with the following command:
-$ sudo chmod 0750 /home/USER/FILE_DIR
-Files that begin with a "." are excluded from this requirement. |
+ 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. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify all files and directories contained in interactive user home
-directory, excluding local initialization files, have a mode of 0750,
-run the following command:
-$ sudo ls -lLR /home/USER Is it the case that home directory files or folders have incorrect permissions? |
+ Verify that only the "root" account has a UID "0" assignment with the
+following command:
+$ awk -F: '$3 == 0 {print $1}' /etc/passwd
+root Is it the case that any accounts other than "root" have a UID of "0"? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Set the mode on files and directories in the local interactive user home
-directory with the following command:
-$ sudo chmod 0750 /home/USER/FILE_DIR
-Files that begin with a "." are excluded from this requirement. |
- medium |
+ 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. |
+ high |
|
|
|
@@ -58853,26 +58810,39 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82233-8: Include Local Events in Audit Logs |
+ CCE-85953-8: Ensure There Are No Accounts With Blank or Null Passwords |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To configure Audit daemon to include local events in Audit logs, set
-local_events to yes in /etc/audit/auditd.conf.
-This is the default setting. |
+ Check the "/etc/shadow" file for blank passwords with the
+following command:
+$ sudo awk -F: '!$2 {print $1}' /etc/shadow
+If the command returns any results, this is a finding.
+Configure all accounts on the system to have a password or lock
+the account with the following commands:
+Perform a password reset:
+$ sudo passwd [username]
+Lock an account:
+$ sudo passwd -l [username] |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To verify that Audit Daemon is configured to include local events, run the
-following command:
-$ sudo grep local_events /etc/audit/auditd.conf
-The output should return the following:
-local_events = yes Is it the case that local_events isn't set to yes? |
+ To verify that null passwords cannot be used, run the following command:
+$ sudo awk -F: '!$2 {print $1}' /etc/shadow
+If this produces any output, it may be possible to log into accounts
+with empty passwords. Is it the case that Blank or NULL passwords can be used? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To configure Audit daemon to include local events in Audit logs, set
-local_events to yes in /etc/audit/auditd.conf.
-This is the default setting. |
- medium |
+ Check the "/etc/shadow" file for blank passwords with the
+following command:
+$ sudo awk -F: '!$2 {print $1}' /etc/shadow
+If the command returns any results, this is a finding.
+Configure all accounts on the system to have a password or lock
+the account with the following commands:
+Perform a password reset:
+$ sudo passwd [username]
+Lock an account:
+$ sudo passwd -l [username] |
+ high |
|
|
|
@@ -58884,40 +58854,19 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-83497-8: Ensure All Files Are Owned by a Group |
+ CCE-82414-4: Uninstall vsftpd Package |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 -nogroup |
+ The vsftpd package can be removed with the following command: $ sudo yum erase vsftpd |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- 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
-
-Either remove all files and directories from the system that do not have a valid group,
-or assign a valid group with the chgrp command:
-$ sudo chgrp group file Is it the case that there is output? |
+ Run the following command to determine if the vsftpd package is installed:
+$ rpm -q vsftpd Is it the case that the package is installed? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 -nogroup |
- medium |
+ The vsftpd package can be removed with the following command: $ sudo yum erase vsftpd |
+ high |
|
|
|
@@ -58929,24 +58878,27 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80952-5: Disable Kernel Image Loading |
+ CCE-82462-3: SSH server uses strong entropy to seed |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To set the runtime status of the kernel.kexec_load_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.kexec_load_disabled=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kexec_load_disabled = 1 |
+ To set up SSH server to use entropy from a high-quality source, edit the /etc/sysconfig/sshd file.
+The SSH_USE_STRONG_RNG configuration value determines how many bytes of entropy to use, so
+make sure that the file contains line
+SSH_USE_STRONG_RNG=32 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the kernel.kexec_load_disabled kernel parameter can be queried
-by running the following command:
-$ sysctl kernel.kexec_load_disabled
-1.
- Is it the case that the correct value is not returned? |
+ To determine whether the SSH service is configured to use strong entropy seed,
+run $ sudo grep SSH_USE_STRONG_RNG /etc/sysconfig/sshd
+If a line indicating that SSH_USE_STRONG_RNG is set to 32 is returned,
+then the option is set correctly. Is it the case that the SSH_USE_STRONG_RNG is not set to 32 in /etc/sysconfig/sshd? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To set the runtime status of the kernel.kexec_load_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.kexec_load_disabled=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kexec_load_disabled = 1 |
- medium |
+ To set up SSH server to use entropy from a high-quality source, edit the /etc/sysconfig/sshd file.
+The SSH_USE_STRONG_RNG configuration value determines how many bytes of entropy to use, so
+make sure that the file contains line
+SSH_USE_STRONG_RNG=32 |
+ low |
|
|
|
@@ -58958,39 +58910,51 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-86377-9: Ensure sudo only includes the default configuration directory |
+ CCE-80835-2: Disable Modprobe Loading of USB Storage Driver |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- Administrators can configure authorized sudo users via drop-in files, and it is possible to include
-other directories and configuration files from the file currently being parsed.
+ | To prevent USB storage devices from being used, configure the kernel module loading system
+to prevent automatic loading of the USB storage driver.
-Make sure that /etc/sudoers only includes drop-in configuration files from /etc/sudoers.d,
-or that no drop-in file is included.
-Either the /etc/sudoers should contain only one #includedir directive pointing to
-/etc/sudoers.d, and no file in /etc/sudoers.d/ should include other files or directories;
-Or the /etc/sudoers should not contain any #include,
-@include, #includedir or @includedir directives.
-Note that the '#' character doesn't denote a comment in the configuration file. |
+To configure the system to prevent the usb-storage
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/usb-storage.conf:
+install usb-storage /bin/true
+
+To configure the system to prevent the usb-storage from being used,
+add the following line to file /etc/modprobe.d/usb-storage.conf:
+blacklist usb-storage
+
+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.
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To determine whether sudo command includes configuration files from the appropriate directory,
-run the following command:
-$ sudo grep -rP '^[#@]include(dir)?' /etc/sudoers /etc/sudoers.d
-If only the line /etc/sudoers:#includedir /etc/sudoers.d is returned, then the drop-in include configuration is set correctly.
-Any other line returned is a finding. Is it the case that the /etc/sudoers doesn't include /etc/sudores.d or includes other directories?? |
+
+If the system is configured to prevent the loading of the usb-storage kernel module,
+it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf.
+These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event.
+
+These lines can also instruct the module loading system to ignore the usb-storage kernel module via blacklist keyword.
+
+Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf:
+$ grep -r usb-storage /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- Administrators can configure authorized sudo users via drop-in files, and it is possible to include
-other directories and configuration files from the file currently being parsed.
+ | To prevent USB storage devices from being used, configure the kernel module loading system
+to prevent automatic loading of the USB storage driver.
-Make sure that /etc/sudoers only includes drop-in configuration files from /etc/sudoers.d,
-or that no drop-in file is included.
-Either the /etc/sudoers should contain only one #includedir directive pointing to
-/etc/sudoers.d, and no file in /etc/sudoers.d/ should include other files or directories;
-Or the /etc/sudoers should not contain any #include,
-@include, #includedir or @includedir directives.
-Note that the '#' character doesn't denote a comment in the configuration file. |
+To configure the system to prevent the usb-storage
+kernel module from being loaded, add the following line to the file /etc/modprobe.d/usb-storage.conf:
+install usb-storage /bin/true
+
+To configure the system to prevent the usb-storage from being used,
+add the following line to file /etc/modprobe.d/usb-storage.conf:
+blacklist usb-storage
+
+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.
medium |
|
|
@@ -59003,22 +58967,23 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82943-2: Uninstall gssproxy Package |
+ CCE-80952-5: Disable Kernel Image Loading |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- The gssproxy package can be removed with the following command:
-
-$ sudo yum erase gssproxy |
+ To set the runtime status of the kernel.kexec_load_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.kexec_load_disabled=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kexec_load_disabled = 1 |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Run the following command to determine if the gssproxy package is installed:
-$ rpm -q gssproxy Is it the case that the package is installed? |
+ The runtime status of the kernel.kexec_load_disabled kernel parameter can be queried
+by running the following command:
+$ sysctl kernel.kexec_load_disabled
+1.
+ Is it the case that the correct value is not returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- The gssproxy package can be removed with the following command:
-
-$ sudo yum erase gssproxy |
+ To set the runtime status of the kernel.kexec_load_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.kexec_load_disabled=1
+To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kexec_load_disabled = 1 |
medium |
|
|
@@ -59031,23 +58996,33 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80917-8: Disable Accepting ICMP Redirects for All IPv4 Interfaces |
+ CCE-83380-6: Disable X Windows Startup By Setting Default Target |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ Systems that do not require a graphical user interface should only boot by
+default into multi-user.target mode. This prevents accidental booting of the system
+into a graphical.target mode. Setting the system's default target to
+multi-user.target will prevent automatic startup of the X server. To do so, run:
+$ systemctl set-default multi-user.target
+You should see the following output:
+Removed symlink /etc/systemd/system/default.target.
+Created symlink from /etc/systemd/system/default.target to /usr/lib/systemd/system/multi-user.target. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv4.conf.all.accept_redirects kernel parameter can be queried
-by running the following command:
-$ sysctl net.ipv4.conf.all.accept_redirects
-0.
- Is it the case that the correct value is not returned? |
+ Verify that Red Hat Enterprise Linux 8 is configured to boot to the command line:
+$ systemctl get-default
+multi-user.target Is it the case that the system default target is not set to "multi-user.target" and the Information System Security Officer (ISSO) lacks a documented requirement for a graphical user interface? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
+ Systems that do not require a graphical user interface should only boot by
+default into multi-user.target mode. This prevents accidental booting of the system
+into a graphical.target mode. Setting the system's default target to
+multi-user.target will prevent automatic startup of the X server. To do so, run:
+$ systemctl set-default multi-user.target
+You should see the following output:
+Removed symlink /etc/systemd/system/default.target.
+Created symlink from /etc/systemd/system/default.target to /usr/lib/systemd/system/multi-user.target. |
medium |
|
|
@@ -59103,23 +59078,84 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-82974-7: Disable Access to Network bpf() Syscall From Unprivileged Processes |
+ CCE-82998-6: Install firewalld Package |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To set the runtime status of the kernel.unprivileged_bpf_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.unprivileged_bpf_disabled=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.unprivileged_bpf_disabled = 1 |
+ The firewalld package can be installed with the following command:
+
+$ sudo yum install firewalld |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the kernel.unprivileged_bpf_disabled kernel parameter can be queried
-by running the following command:
-$ sysctl kernel.unprivileged_bpf_disabled
-1.
- Is it the case that the correct value is not returned? |
+ Run the following command to determine if the firewalld package is installed: $ rpm -q firewalld Is it the case that the package is not installed? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To set the runtime status of the kernel.unprivileged_bpf_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.unprivileged_bpf_disabled=1
-To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.unprivileged_bpf_disabled = 1 |
+ The firewalld package can be installed with the following command:
+
+$ sudo yum install firewalld |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00227 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+
+ CCE-80873-3: Disable the Automounter |
+
+ Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
+
+Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
+ 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 |
+ Applicable - Configurable |
+ Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
+ To check that the autofs service is disabled in system boot configuration,
+run the following command:
+$ sudo systemctl is-enabled autofs
+Output should indicate the autofs service has either not been installed,
+or has been disabled at all runlevels, as shown in the example below:
+$ sudo systemctl is-enabled autofs
disabled
+
+Run the following command to verify autofs is not active (i.e. not running) through current runtime configuration:
+$ sudo systemctl is-active autofs
+
+If the service is not running the command will return the following output:
+inactive
+
+The service will also be masked, to check that the autofs is masked, run the following command:
+$ sudo systemctl show autofs | grep "LoadState\|UnitFileState"
+
+If the service is masked the command will return the following outputs:
+
+LoadState=masked
+
+UnitFileState=masked Is it the case that the "autofs" is loaded and not masked? |
+ Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
+ 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 |
medium |
|
|
@@ -59132,31 +59168,21 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81050-7: Add nosuid Option to /home |
+ CCE-82428-4: Verify Permissions on SSH Server Public *.pub Key Files |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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. |
+ To properly set the permissions of /etc/ssh/*.pub, run the command: $ sudo chmod 0644 /etc/ssh/*.pub |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify the nosuid option is configured for the /home mount point,
- run the following command:
- $ sudo mount | grep '\s/home\s'
- . . . /home . . . nosuid . . .
- Is it the case that the "/home" file system does not have the "nosuid" option set? |
+ To check the permissions of /etc/ssh/*.pub,
+run the command:
+$ ls -l /etc/ssh/*.pub
+If properly configured, the output should indicate the following permissions:
+-rw-r--r-- Is it the case that /etc/ssh/*.pub does not have unix mode -rw-r--r--? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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. |
+ To properly set the permissions of /etc/ssh/*.pub, run the command: $ sudo chmod 0644 /etc/ssh/*.pub |
medium |
|
|
@@ -59169,48 +59195,31 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-80878-2: Disable KDump Kernel Crash Analyzer (kdump) |
+ CCE-80854-3: Ensure /var/log/audit Located On Separate Partition |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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.
+ | Audit logs are stored in the /var/log/audit directory.
-The kdump service can be disabled with the following command:
-$ sudo systemctl mask --now kdump.service |
+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.
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To check that the kdump service is disabled in system boot configuration,
-run the following command:
-$ sudo systemctl is-enabled kdump
-Output should indicate the kdump service has either not been installed,
-or has been disabled at all runlevels, as shown in the example below:
-$ sudo systemctl is-enabled kdump
disabled
-
-Run the following command to verify kdump is not active (i.e. not running) through current runtime configuration:
-$ sudo systemctl is-active kdump
-
-If the service is not running the command will return the following output:
-inactive
-
-The service will also be masked, to check that the kdump is masked, run the following command:
-$ sudo systemctl show kdump | grep "LoadState\|UnitFileState"
-
-If the service is masked the command will return the following outputs:
-
-LoadState=masked
+ | Verify that a separate file system/partition has been created for /var/log/audit with the following command:
-UnitFileState=masked Is it the case that the "kdump" is loaded and not masked? |
+$ mountpoint /var/log/audit
+ Is it the case that "/var/log/audit is not a mountpoint" is returned?
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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.
+ | Audit logs are stored in the /var/log/audit directory.
-The kdump service can be disabled with the following command:
-$ sudo systemctl mask --now kdump.service |
- medium |
+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.
+ low |
|
|
|
@@ -59222,27 +59231,17 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81036-6: Ensure the Default Bash Umask is Set Correctly |
+ CCE-80847-7: Ensure rsyslog is Installed |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To ensure the default umask for users of the Bash shell is set properly,
-add or correct the umask setting in /etc/bashrc to read
-as follows:
-umask |
+ Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify the umask setting is configured correctly in the /etc/bashrc file with the following command:
-
-$ sudo grep "umask" /etc/bashrc
-
-umask Is it the case that the value for the "umask" parameter is not "", or the "umask" parameter is missing or is commented out? |
+ Run the following command to determine if the rsyslog package is installed: $ rpm -q rsyslog Is it the case that the package is not installed? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To ensure the default umask for users of the Bash shell is set properly,
-add or correct the umask setting in /etc/bashrc to read
-as follows:
-umask |
+ Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
medium |
|
|
@@ -59255,30 +59254,24 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-83789-8: Ensure Home Directories are Created for New Users |
+ CCE-82730-3: Ensure /var/tmp Located On Separate Partition |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- 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 |
+ The /var/tmp directory is a world-writable directory used
+for temporary file storage. Ensure it has its own partition or
+logical volume at installation time, or migrate it using LVM. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- Verify all local interactive users on Red Hat Enterprise Linux 8 are assigned a home
-directory upon creation with the following command:
-$ grep -i create_home /etc/login.defs
-CREATE_HOME yes Is it the case that the value for "CREATE_HOME" parameter is not set to "yes", the line is missing, or the line is commented out? |
+ Verify that a separate file system/partition has been created for /var/tmp with the following command:
+
+$ mountpoint /var/tmp
+ Is it the case that "/var/tmp is not a mountpoint" is returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- 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 |
+ The /var/tmp directory is a world-writable directory used
+for temporary file storage. Ensure it has its own partition or
+logical volume at installation time, or migrate it using LVM. |
medium |
|
|
@@ -59291,23 +59284,26 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81006-9: Configure Accepting Router Advertisements on All IPv6 Interfaces |
+ CCE-85888-6: All User Files and Directories In The Home Directory Must Have Mode 0750 Or Less Permissive |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To set the runtime status of the net.ipv6.conf.all.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_ra=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_ra = 0 |
+ Set the mode on files and directories in the local interactive user home
+directory with the following command:
+$ sudo chmod 0750 /home/USER/FILE_DIR
+Files that begin with a "." are excluded from this requirement. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv6.conf.all.accept_ra kernel parameter can be queried
-by running the following command:
-$ sysctl net.ipv6.conf.all.accept_ra
-0.
- Is it the case that the correct value is not returned? |
+ To verify all files and directories contained in interactive user home
+directory, excluding local initialization files, have a mode of 0750,
+run the following command:
+$ sudo ls -lLR /home/USER Is it the case that home directory files or folders have incorrect permissions? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To set the runtime status of the net.ipv6.conf.all.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_ra=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_ra = 0 |
+ Set the mode on files and directories in the local interactive user home
+directory with the following command:
+$ sudo chmod 0750 /home/USER/FILE_DIR
+Files that begin with a "." are excluded from this requirement. |
medium |
|
|
@@ -59320,24 +59316,29 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-81007-7: Disable Accepting Router Advertisements on all IPv6 Interfaces by Default |
+ CCE-81044-0: Ensure /home Located On Separate Partition |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To set the runtime status of the net.ipv6.conf.default.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_ra=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_ra = 0 |
+ 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. |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- The runtime status of the net.ipv6.conf.default.accept_ra kernel parameter can be queried
-by running the following command:
-$ sysctl net.ipv6.conf.default.accept_ra
-0.
- Is it the case that the correct value is not returned? |
+ Verify that a separate file system/partition has been created for /home with the following command:
+
+$ mountpoint /home
+ Is it the case that "/home is not a mountpoint" is returned? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To set the runtime status of the net.ipv6.conf.default.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_ra=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_ra = 0 |
- medium |
+ 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. |
+ low |
|
|
|
@@ -59349,26 +59350,25 @@
TBD - Assigned by DISA after STIG release |
The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- CCE-85872-0: Ensure PAM password complexity module is enabled in system-auth |
+ CCE-84039-7: User Initialization Files Must Not Run World-Writable Programs |
Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. |
- To enable PAM password complexity in system-auth file:
-Edit the password section in
-/etc/pam.d/system-auth to show
-password requisite pam_pwquality.so. |
+ Set the mode on files being executed by the user initialization files with the
+following command:
+$ sudo chmod o-w FILE |
Applicable - Configurable |
Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding. |
- To check if pam_pwquality.so is enabled in system-auth, run the following command:
-$ grep pam_pwquality /etc/pam.d/system-auth
-The output should be similar to the following:
-password requisite pam_pwquality.so Is it the case that pam_pwquality.so is not enabled in system-auth? |
+ Verify that local initialization files do not execute world-writable programs with the following command:
+
+Note: The example will be for a system that is configured to create user home directories in the "/home" directory.
+
+$ sudo find /home -perm -002 -type f -name ".[^.]*" -exec ls -ld {} \; Is it the case that any local initialization files are found to reference world-writable files? |
Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
- To enable PAM password complexity in system-auth file:
-Edit the password section in
-/etc/pam.d/system-auth to show
-password requisite pam_pwquality.so. |
+ Set the mode on files being executed by the user initialization files with the
+following command:
+$ sudo chmod o-w FILE |
medium |
|
|
@@ -59416,23 +59416,57 @@
TBD - Assigned by DISA after STIG release |
The operating system must define default permissions for all authenticated users in such a way that the user can only read and modify their own files. |
- CCE-82888-9: Ensure the Default Umask is Set Correctly in login.defs |
+ CCE-81036-6: Ensure the Default Bash Umask is Set Correctly |
Setting the most restrictive default permissions ensures that when new accounts are created they do not have unnecessary access. |
- 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 |
+ To ensure the default umask for users of the Bash shell is set properly,
+add or correct the umask setting in /etc/bashrc to read
+as follows:
+umask |
Applicable - Configurable |
Verify the operating system defines default permissions for all authenticated users in such a way that the user can only read and modify their own files. If it does not, this is a finding. |
- Verify Red Hat Enterprise Linux 8 defines default permissions for all authenticated users in such a way that the user can only read and modify their own files with the following command:
+ | Verify the umask setting is configured correctly in the /etc/bashrc file with the following command:
-# grep -i umask /etc/login.defs
+$ sudo grep "umask" /etc/bashrc
-UMASK Is it the case that the value for the "UMASK" parameter is not "", or the "UMASK" parameter is missing or is commented out? |
+umask Is it the case that the value for the "umask" parameter is not "", or the "umask" parameter is missing or is commented out?
Configure the operating system to define default permissions for all authenticated users in such a way that the user can only read and modify their own files. |
- 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 |
+ To ensure the default umask for users of the Bash shell is set properly,
+add or correct the umask setting in /etc/bashrc to read
+as follows:
+umask |
+ medium |
+ |
+ |
+ |
+
+
+
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00228 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must define default permissions for all authenticated users in such a way that the user can only read and modify their own files. |
+
+ CCE-84044-7: Ensure the Default Umask is Set Correctly For Interactive Users |
+
+ Setting the most restrictive default permissions ensures that when new accounts are created they do not have unnecessary access. |
+ Remove the UMASK environment variable from all interactive users initialization files. |
+ Applicable - Configurable |
+ Verify the operating system defines default permissions for all authenticated users in such a way that the user can only read and modify their own files. If it does not, this is a finding. |
+ Verify that the default umask for all local interactive users is "077".
+
+Identify the locations of all local interactive user home directories by looking at the "/etc/passwd" file.
+
+Check all local interactive user initialization files for interactive users with the following command:
+
+Note: The example is for a system that is configured to create users home directories in the "/home" directory.
+
+# grep -ri umask /home/
+
+/home/smithj/.bash_history:grep -i umask /etc/bashrc /etc/csh.cshrc /etc/profile
+/home/smithj/.bash_history:grep -i umask /etc/login.defs Is it the case that any local interactive user initialization files are found to have a umask statement that sets a value less restrictive than "077"? |
+ Configure the operating system to define default permissions for all authenticated users in such a way that the user can only read and modify their own files. |
+ Remove the UMASK environment variable from all interactive users initialization files. |
medium |
|
|
@@ -59482,68 +59516,71 @@
TBD - Assigned by DISA after STIG release |
The operating system must define default permissions for all authenticated users in such a way that the user can only read and modify their own files. |
- CCE-84044-7: Ensure the Default Umask is Set Correctly For Interactive Users |
+ CCE-82888-9: Ensure the Default Umask is Set Correctly in login.defs |
Setting the most restrictive default permissions ensures that when new accounts are created they do not have unnecessary access. |
- Remove the UMASK environment variable from all interactive users initialization files. |
+ 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 |
Applicable - Configurable |
Verify the operating system defines default permissions for all authenticated users in such a way that the user can only read and modify their own files. If it does not, this is a finding. |
- Verify that the default umask for all local interactive users is "077".
-
-Identify the locations of all local interactive user home directories by looking at the "/etc/passwd" file.
-
-Check all local interactive user initialization files for interactive users with the following command:
-
-Note: The example is for a system that is configured to create users home directories in the "/home" directory.
+ | Verify Red Hat Enterprise Linux 8 defines default permissions for all authenticated users in such a way that the user can only read and modify their own files with the following command:
-# grep -ri umask /home/
+# grep -i umask /etc/login.defs
-/home/smithj/.bash_history:grep -i umask /etc/bashrc /etc/csh.cshrc /etc/profile
-/home/smithj/.bash_history:grep -i umask /etc/login.defs Is it the case that any local interactive user initialization files are found to have a umask statement that sets a value less restrictive than "077"? |
+UMASK Is it the case that the value for the "UMASK" parameter is not "", or the "UMASK" parameter is missing or is commented out?
Configure the operating system to define default permissions for all authenticated users in such a way that the user can only read and modify their own files. |
- Remove the UMASK environment variable from all interactive users initialization files. |
+ 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 |
medium |
|
|
|
+
+
+
+
+
| CCI-000366 |
- SRG-OS-000480-GPOS-00228 |
+ SRG-OS-000480-GPOS-00229 |
TBD - Assigned by DISA after STIG release |
- The operating system must define default permissions for all authenticated users in such a way that the user can only read and modify their own files. |
+ The operating system must not allow an unattended or automatic logon to the system. |
- CCE-81036-6: Ensure the Default Bash Umask is Set Correctly |
+ CCE-80823-8: Disable GDM Automatic Login |
- Setting the most restrictive default permissions ensures that when new accounts are created they do not have unnecessary access. |
- To ensure the default umask for users of the Bash shell is set properly,
-add or correct the umask setting in /etc/bashrc to read
-as follows:
-umask |
+ Failure to restrict system access to authenticated users negatively impacts operating system security. |
+ The GNOME Display Manager (GDM) can allow users to automatically login without
+user interaction or credentials. 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 AutomaticLoginEnable to false in the
+[daemon] section in /etc/gdm/custom.conf. For example:
+[daemon]
+AutomaticLoginEnable=false |
Applicable - Configurable |
- Verify the operating system defines default permissions for all authenticated users in such a way that the user can only read and modify their own files. If it does not, this is a finding. |
- Verify the umask setting is configured correctly in the /etc/bashrc file with the following command:
-
-$ sudo grep "umask" /etc/bashrc
-
-umask Is it the case that the value for the "umask" parameter is not "", or the "umask" parameter is missing or is commented out? |
- Configure the operating system to define default permissions for all authenticated users in such a way that the user can only read and modify their own files. |
- To ensure the default umask for users of the Bash shell is set properly,
-add or correct the umask setting in /etc/bashrc to read
-as follows:
-umask |
- medium |
+ If the operating system provides a public access service, such as a kiosk, this is not applicable. Verify the operating system does not allow an unattended or automatic logon to the system. If it does, this is a finding. Automatic logon as an authorized user allows access to any user with physical access to the operating system. |
+ To verify that automatic logins are disabled, run the following command:
+$ grep -Pzoi "^\[daemon]\\nautomaticlogin.*" /etc/gdm/custom.conf
+The output should show the following:
+[daemon]
+AutomaticLoginEnable=false Is it the case that GDM allows users to automatically login? |
+ If the operating system provides a public access service, such as a kiosk, this is not applicable. Configure the operating system to not allow an unattended or automatic logon to the system. Automatic logon as an authorized user allows access to any user with physical access to the operating system. |
+ The GNOME Display Manager (GDM) can allow users to automatically login without
+user interaction or credentials. 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 AutomaticLoginEnable to false in the
+[daemon] section in /etc/gdm/custom.conf. For example:
+[daemon]
+AutomaticLoginEnable=false |
+ high |
|
|
|
-
-
-
-
-
| CCI-000366 |
SRG-OS-000480-GPOS-00229 |
@@ -59642,48 +59679,36 @@
|
+
+
+
+
+
| CCI-000366 |
- SRG-OS-000480-GPOS-00229 |
+ SRG-OS-000480-GPOS-00230 |
TBD - Assigned by DISA after STIG release |
- The operating system must not allow an unattended or automatic logon to the system. |
+ The operating system must limit the ability of non-privileged users to grant other users direct access to the contents of their home directories/folders. |
- CCE-80823-8: Disable GDM Automatic Login |
+ CCE-82191-8: Install fapolicyd Package |
- Failure to restrict system access to authenticated users negatively impacts operating system security. |
- The GNOME Display Manager (GDM) can allow users to automatically login without
-user interaction or credentials. 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 AutomaticLoginEnable to false in the
-[daemon] section in /etc/gdm/custom.conf. For example:
-[daemon]
-AutomaticLoginEnable=false |
+ Users' home directories/folders may contain information of a sensitive nature. Non-privileged users should coordinate any sharing of information with an SA through shared resources. |
+ The fapolicyd package can be installed with the following command:
+
+$ sudo yum install fapolicyd |
Applicable - Configurable |
- If the operating system provides a public access service, such as a kiosk, this is not applicable. Verify the operating system does not allow an unattended or automatic logon to the system. If it does, this is a finding. Automatic logon as an authorized user allows access to any user with physical access to the operating system. |
- To verify that automatic logins are disabled, run the following command:
-$ grep -Pzoi "^\[daemon]\\nautomaticlogin.*" /etc/gdm/custom.conf
-The output should show the following:
-[daemon]
-AutomaticLoginEnable=false Is it the case that GDM allows users to automatically login? |
- If the operating system provides a public access service, such as a kiosk, this is not applicable. Configure the operating system to not allow an unattended or automatic logon to the system. Automatic logon as an authorized user allows access to any user with physical access to the operating system. |
- The GNOME Display Manager (GDM) can allow users to automatically login without
-user interaction or credentials. 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 AutomaticLoginEnable to false in the
-[daemon] section in /etc/gdm/custom.conf. For example:
-[daemon]
-AutomaticLoginEnable=false |
- high |
+ Verify the operating system limits the ability of non-privileged users to grant other users direct access to the contents of their home directories/folders. If it does not, this is a finding. |
+ Run the following command to determine if the fapolicyd package is installed: $ rpm -q fapolicyd Is it the case that the fapolicyd package is not installed? |
+ Configure the operating system to limit the ability of non-privileged users to grant other users direct access to the contents of their home directories/folders. |
+ The fapolicyd package can be installed with the following command:
+
+$ sudo yum install fapolicyd |
+ medium |
|
|
|
-
-
-
-
-
| CCI-000366 |
SRG-OS-000480-GPOS-00230 |
@@ -59716,90 +59741,10 @@
|
-
- | CCI-000366 |
- SRG-OS-000480-GPOS-00230 |
- TBD - Assigned by DISA after STIG release |
- The operating system must limit the ability of non-privileged users to grant other users direct access to the contents of their home directories/folders. |
-
- CCE-82191-8: Install fapolicyd Package |
-
- Users' home directories/folders may contain information of a sensitive nature. Non-privileged users should coordinate any sharing of information with an SA through shared resources. |
- The fapolicyd package can be installed with the following command:
-
-$ sudo yum install fapolicyd |
- Applicable - Configurable |
- Verify the operating system limits the ability of non-privileged users to grant other users direct access to the contents of their home directories/folders. If it does not, this is a finding. |
- Run the following command to determine if the fapolicyd package is installed: $ rpm -q fapolicyd Is it the case that the fapolicyd package is not installed? |
- Configure the operating system to limit the ability of non-privileged users to grant other users direct access to the contents of their home directories/folders. |
- The fapolicyd package can be installed with the following command:
-
-$ sudo yum install fapolicyd |
- medium |
- |
- |
- |
-
-
-
-
-
-
-
-
- | CCI-000366 |
- SRG-OS-000480-GPOS-00232 |
- TBD - Assigned by DISA after STIG release |
- The operating system must enable an application firewall, if available. |
-
- CCE-82462-3: SSH server uses strong entropy to seed |
- Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Application firewalls limit which applications are allowed to communicate over the network. |
- To set up SSH server to use entropy from a high-quality source, edit the /etc/sysconfig/sshd file.
-The SSH_USE_STRONG_RNG configuration value determines how many bytes of entropy to use, so
-make sure that the file contains line
-SSH_USE_STRONG_RNG=32 |
- Applicable - Configurable |
- Verify the operating system enabled an application firewall, if available. If it does not, this is a finding. If the operating system does not support an application firewall, this may be downgraded to a CAT III finding. |
- To determine whether the SSH service is configured to use strong entropy seed,
-run $ sudo grep SSH_USE_STRONG_RNG /etc/sysconfig/sshd
-If a line indicating that SSH_USE_STRONG_RNG is set to 32 is returned,
-then the option is set correctly. Is it the case that the SSH_USE_STRONG_RNG is not set to 32 in /etc/sysconfig/sshd? |
- Ensure the operating system's application firewall is enabled, if available. |
- To set up SSH server to use entropy from a high-quality source, edit the /etc/sysconfig/sshd file.
-The SSH_USE_STRONG_RNG configuration value determines how many bytes of entropy to use, so
-make sure that the file contains line
-SSH_USE_STRONG_RNG=32 |
- low |
- |
- |
- |
-
-
- | CCI-000366 |
- SRG-OS-000480-GPOS-00232 |
- TBD - Assigned by DISA after STIG release |
- The operating system must enable an application firewall, if available. |
- CCE-82998-6: Install firewalld Package |
- Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Application firewalls limit which applications are allowed to communicate over the network. |
- The firewalld package can be installed with the following command:
-
-$ sudo yum install firewalld |
- Applicable - Configurable |
- Verify the operating system enabled an application firewall, if available. If it does not, this is a finding. If the operating system does not support an application firewall, this may be downgraded to a CAT III finding. |
- Run the following command to determine if the firewalld package is installed: $ rpm -q firewalld Is it the case that the package is not installed? |
- Ensure the operating system's application firewall is enabled, if available. |
- The firewalld package can be installed with the following command:
-
-$ sudo yum install firewalld |
- medium |
- |
- |
- |
-
| CCI-000366 |
@@ -59870,6 +59815,61 @@
|
+
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00232 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must enable an application firewall, if available. |
+
+ CCE-82462-3: SSH server uses strong entropy to seed |
+
+ Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Application firewalls limit which applications are allowed to communicate over the network. |
+ To set up SSH server to use entropy from a high-quality source, edit the /etc/sysconfig/sshd file.
+The SSH_USE_STRONG_RNG configuration value determines how many bytes of entropy to use, so
+make sure that the file contains line
+SSH_USE_STRONG_RNG=32 |
+ Applicable - Configurable |
+ Verify the operating system enabled an application firewall, if available. If it does not, this is a finding. If the operating system does not support an application firewall, this may be downgraded to a CAT III finding. |
+ To determine whether the SSH service is configured to use strong entropy seed,
+run $ sudo grep SSH_USE_STRONG_RNG /etc/sysconfig/sshd
+If a line indicating that SSH_USE_STRONG_RNG is set to 32 is returned,
+then the option is set correctly. Is it the case that the SSH_USE_STRONG_RNG is not set to 32 in /etc/sysconfig/sshd? |
+ Ensure the operating system's application firewall is enabled, if available. |
+ To set up SSH server to use entropy from a high-quality source, edit the /etc/sysconfig/sshd file.
+The SSH_USE_STRONG_RNG configuration value determines how many bytes of entropy to use, so
+make sure that the file contains line
+SSH_USE_STRONG_RNG=32 |
+ low |
+ |
+ |
+ |
+
+
+
+ | CCI-000366 |
+ SRG-OS-000480-GPOS-00232 |
+ TBD - Assigned by DISA after STIG release |
+ The operating system must enable an application firewall, if available. |
+
+ CCE-82998-6: Install firewalld Package |
+
+ Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Application firewalls limit which applications are allowed to communicate over the network. |
+ The firewalld package can be installed with the following command:
+
+$ sudo yum install firewalld |
+ Applicable - Configurable |
+ Verify the operating system enabled an application firewall, if available. If it does not, this is a finding. If the operating system does not support an application firewall, this may be downgraded to a CAT III finding. |
+ Run the following command to determine if the firewalld package is installed: $ rpm -q firewalld Is it the case that the package is not installed? |
+ Ensure the operating system's application firewall is enabled, if available. |
+ The firewalld package can be installed with the following command:
+
+$ sudo yum install firewalld |
+ medium |
+ |
+ |
+ |
+
+